When attempting to re-image a laptop I have found that SCCM replaced the wired MAC address in properties with the wireless MAC. This is only an issue when I go to image as it will not PXE, I get a no boot file received message.

I have been deleting the laptops from SCCM completely and then re-importing them using the wired MAC.

After re-adding the laptop with the wired MAC it is still holding a record of the last PXE Deployment (once deleted the system will PXE boot fine). 

Is there a way to have SCCM actively hold both MAC addresses?

Hi everybody,

first of all to the System configuration:

SCCM2012R2SP1 with MDT 2013 SP1 (6.3.8298.1000)

The current productive tasksequence ( Windows 7 SP1 Ent. Driver applications etc) runs as it should.

The Story I did ( want to include IE 11 to the Image via dism):

-copy the current OS.wim

- insert IE 11 cab and language packs with dism.exe (everything successfull)

- imported the OS.wim with IE as a ne OS-System (and distributed it)

- make a copy of the productive tasksequence

- set the new OS.wim with IE included at the step apply Operating System 

- started the tasksequence at a Client

Now the Problem is the Tasksequece stops at the Step Setup Windows and Config Manager (SCCM Console Monitoring Status of deployment) and at the Client I have to select a language. ( After selecting a language at the client the tasksequence continues and succeeds, Applications, etc and the IE 11 is also installed).

After searching for this issue (Posts at TechNet etc.) I created a New MDT Files package with a new unattended.xml edited the contend of the new configsettings.ini (because it´s customized but as written above in the current productive ts the old one still works) distributed the packageannd applied it at the tasksequence step:

 The result was the same as with the old package tasksequence stops without an error at the client the setup window to choose a language , after doing that tasksequnce continues and succeds.

OK go to the client have a look at smsts.log what happens at OS deployment..here it becomes strange...

***SMS TS LOG****

Run in attribute: WinPE TSManager 05.04.2016 10:47:48 2392 (0x0958)
Timeout:  TSManager 05.04.2016 10:47:48 2392 (0x0958)
DefaultVarlist found TSManager 05.04.2016 10:47:48 2392 (0x0958)
Variable name: OSDConfigFileName TSManager 05.04.2016 10:47:48 2392 (0x0958)
Variable name: OSDImageIndex TSManager 05.04.2016 10:47:48 2392 (0x0958)
Action command line: OSDApplyOS.exe /image:S0100252,%OSDImageIndex% "/config:S0100023,%OSDConfigFileName%" /target:%OSDisk% /runfromnet:False TSManager 05.04.2016 10:47:48 2392 (0x0958)
Adding instruction at 84 TSManager 05.04.2016 10:47:48 2392 (0x0958)

Parsing step node: Use Toolkit Package TSManager 05.04.2016 10:47:48 2392 (0x0958)
Description:  TSManager 05.04.2016 10:47:48 2392 (0x0958)
ContinueOnError:  TSManager 05.04.2016 10:47:48 2392 (0x0958)
SuccessCodeList: 0 TSManager 05.04.2016 10:47:48 2392 (0x0958)
RetryCount: 0 TSManager 05.04.2016 10:47:48 2392 (0x0958)
A condition is associated with the step found TSManager 05.04.2016 10:47:48 2392 (0x0958)
Found and operator. TSManager 05.04.2016 10:47:48 2392 (0x0958)
There are 1 operands TSManager 05.04.2016 10:47:48 2392 (0x0958)
**Processing operator node TSManager 05.04.2016 10:47:48 2392 (0x0958)
Found not operator. TSManager 05.04.2016 10:47:48 2392 (0x0958)
There are 1 operands TSManager 05.04.2016 10:47:48 2392 (0x0958)
**Processing expression node TSManager 05.04.2016 10:47:48 2392 (0x0958)
Found SMS_TaskSequence_FolderConditionExpression expression. TSManager 05.04.2016 10:47:48 2392 (0x0958)
**In ProcessBuiltInCondition node: expression TSManager 05.04.2016 10:47:48 2392 (0x0958)
There are 1 operands in the built in action TSManager 05.04.2016 10:47:48 2392 (0x0958)
Operand Path=%ScriptRoot% TSManager 05.04.2016 10:47:48 2392 (0x0958)
Successfully added 3 condition parameters TSManager 05.04.2016 10:47:48 2392 (0x0958)
Disable:  TSManager 05.04.2016 10:47:48 2392 (0x0958)
Run in attribute: WinPEandFullOS TSManager 05.04.2016 10:47:48 2392 (0x0958)
Timeout:  TSManager 05.04.2016 10:47:48 2392 (0x0958)
DefaultVarlist found TSManager 05.04.2016 10:47:48 2392 (0x0958)
No variables found in default variable list TSManager 05.04.2016 10:47:48 2392 (0x0958)
Action command line: smsswd.exe /run:S0100138 cscript.exe Scripts\ZTISCCM.wsf TSManager 05.04.2016 10:47:48 2392 (0x0958)
Adding instruction at 85 TSManager 05.04.2016 10:47:48 2392 (0x0958)
Processed all elements TSManager 05.04.2016 10:47:48 2392 (0x0958)
Adding end group instruction at 86 TSManager 05.04.2016 10:47:48 2392 (0x0958)
The next instruction after group will be at 87 TSManager 05.04.2016 10:47:48 2392 (0x0958)
Processing group TSManager 05.04.2016 10:47:48 2392 (0x0958)

Parsing group node: PostInstall TSManager 05.04.2016 10:47:48 2392 (0x0958)

********

Action command line: OSDApplyOS.exe /image:S0100252,%OSDImageIndex% "/config:S0100023,%

The Image ID is correct S0100252 is my wim file with the IE included.

The config Package S0100023 is NOT The MDT 2013 IE 11 Files package. ( The ID of the new package is S100254)

Package S0100023 ist the old MDT Flies package ( Named MDT Custom Settings 4.0) that I use in the productive tasksequence but it´s not selected at this tasksequence.

Any ideas why / how to get the Problems solved withou choosing laanguage at the client during install?

Thanks in advance

Thomas 

Hi,

I am using SCCM v1511 integrated with MDT 2013 Update1. Install Application TS step takes really long time. I have 8 application and the biggest application is Office2016. The other apps are really small like chrome, google drive etc. It took 2hours and 42 minutes to complete the OSD. I tested the task sequence with Software Updates and without software updates. Both took really long time (around 3 hours) while installing applications. I read Jim Depsey's explanation about the issue, he says:

" not including software updates in the task sequence won't make any difference.  The policies that are received by the client and subsequently compiled before each app installation include any CI-based deployments targeted at the client, even if they aren't referenced in the task sequence.  So, if you are deploying a task sequence to an existing client and that client has a large number of updates and/or applications deployed to it, all of those policies will be compiled during the task sequence.  If you are dealing with a brand new machine with no existing client, then you're still dealing with anything deployed to All Unknown Systems or All Systems."

https://social.technet.microsoft.com/Forums/en-US/1aca7077-2ae0-4c45-9527-88236fd66f29/install-applications-in-task-sequence-is-very-slow?forum=configmanagerosd

My question is: Is 3 hours normal for deployment. Because by using WDS and a thick image I can install my image with all setting to the same computer in 17 minutes. 

Yavuz Selim Atmaca

I was getting Windows Hardware initialization error after upgraded my SCCM 2012 R2 to 1511.  When Microsoft released hotfix KB3143760, I didn’t apply the hot fix.

With Successful upgrade to SCCM 1602, I still have Hardware initialization error.

Was 1602 upgrade supposed to have fixed the 1511 error?

How do I fix this error?

Greetings!

We've been doing in-place upgrade from Windows 7 virtual desktops to Windows 10 using a task sequence which was working until yesterday. The last time I tried, it failed with error code "0x00000A58" and I haven't tried to run the same task sequence on another machine yet.

Could anyone shed some light on the reason for this error?

Following is the error that I see in the SMSTS.log;

The execution of the group (Upgrade the Operating System) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)

Failed to run the last action: Recover from Setup Failure. Execution of task sequence failed.
Unknown error (Error: 00000A58; Source: Unknown)

Please advise!

Hi All,

I'm having a issues with task sequence not running. When i select the task sequence starts to run i get the following error

"This task sequence cannot be run because a package referenced by the task sequence could not be found"

I have got the log file from the machine but i am still learning with sccm and truly don't know what i'm missing. I think it may be a new driver pack that i have put into the system but i have checked this 3 times now and it is definitely  deployed to all DP's

Thanks in advance for any help you can offer.

Kind Regards

Steve

I am having serious problems getting the last unknown driver to come in.

The machineID is IUSB3+ROOT_HUB30&VID_8086&PID_9D2F

I installed the PC, updated all drivers, extracted them into SCCM by using Double Driver.

I then created a driverpackage with query SELECT * FROM Win32_ComputerSystem WHERE Model LIKE '%ProBook 440 G3%'

I added another step after driverpackage, where I created another driverpackage including only 3.0 drivers, choosing Installing all compatible drivers.

I even created a package including the usb setup.exe which I deployed with the same query.

All of the above ends up with the same result. The USB 3.0 Intel driver doesn't show up when I deploy in SCCM.

Is there something I haven't thought of, done correctly, or should have? I am at my wits end here. Hope the collective mind of the Internet can help me out!

Thank you in advance.

Currently my organisation has a large number of individual MDT 2010 servers spread across a region, each which holds a copy of the desktop image which is deployed at the site it resides at.  We are looking to implement ConfigMgr to centralize this structure, building a primary server at the main site and 'converting' the current MDT servers into ConfigMgr distribution points.

We would still like to benefit from MDT in the OSD process, so we intend to integrate MDT with the Primary server in order to build and maintain the desktop image.

My understanding is that MDT only has to be installed on the Primary server where the image is managed and will not be required to be installed on the individual distribution points.  Is this understanding correct?  

Hi,

I'm using SCCM 2012 R2 Sp1 with integrated MDT 2013. When I trying create new MDT boot image, on "Components" stage I'm getting strange pop-up with: "The path is not of a legal form". Any ideas what can be wrong?

Thank you for all advices. 

We currently have a separate imaging server running MDT 2012 with WDS.  When I image new computers I PXE boot the computer and boot the MDT Boot wim and access the MDT task sequences I've created.  We are currently implementing SCCM.  If we want to move to SCCM to handle images, can I still PXE boot a machine and point to the toolkit?  Currently the MDT wim is loaded in the WDS boot image, does this wim just get moved to SCCM?

Thanks

Chris

Hi,

Where should I find history of an OSD TS deployment for a computer?

We are using combination of SCCM 2012 R2 SP1 and MDT.

OSD deployed Windows 2012 R2, but when I look at smsts.log* file under C:\Windows and/or C:\Windows\SysWOW64 directory, it failed to mentioned what was the task sequence name or package ID that was used to deploy OS to the machine.

The other TS package which is not related to OSD was mentioned in that file though.

SCCM Report failed to show TS deployment either as the Task Seq program has been removed from the computer membership, and/or it was deployed >3mths ago perhaps making the report to be purged?

Help.

---Pat

Hi

I am using SCCM R2 SP1 CU1

I have imported Windows 10 drivers for a new model of Lenovo X260, unfortunately I wasn't mean to import the Windows 10 drivers, I was meant to import the Windows 7 drivers.

When I imported the drivers I added them to a package called X260 Windows 7 x64 and a category called X260 Windows 7 x64.

For duplicate drivers, I chose the option to import and append a new category to the existing categories.

The source files for the drivers are located under Driver Source\Lenovo\X260\Windows7\x64

The location for the packages are located under Packages\Lenovo\X260\Windows7\x64

I am happy to keep the Windows 10 drivers, create a new package and add the drivers to the new package and remove them from the Windows 7 package, but I am not sure how I would go about changing the source location for all of the windows 10 drivers.

I think I am better off deleting the drivers out of the package or deleting the package and source files and the package files and then importing the Windows 7 drivers and creating the X260 Windows 7 package from scratch.

If I delete the Windows 7 package, does this delete the drivers as well ?  Or do I need to go into the driver package, select all the drivers in it, delete them and then delete the package then delete the source folder and package folders from windows explorer ?  Or is there a different way I should be doing this ?

What happens to the X260 Windows 7 category which I have created ?

Thanks

G

Hi,

I am unable to install updates on a vanilla Windows Server 2012 R2 WIM file using offline Servicing.

DISM is Version 10.0.10240.16384 and the error for each update within OfflineServicingMgr.log is as per the below....

Checking if update (54 of 270) with ID 16894087 needs to be applied on the image. 1 content binarie(s) are associated with the update.  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:46:35.580-60><thread=9308 (0x245C)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:46:35.596-60><thread=9308 (0x245C)>
Update applicability check is not supported. Dism.exe command line is below:~  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:46:49.346-60><thread=9308 (0x245C)>
"C:\Windows\system32\cmd.exe" /q /c ""C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\ConfigMgr_OfflineImageServicing\FCH00124\ImageMountDir" /LogPath:%WINDIR%\Logs\Dism\dism_sccmAMD64.log /English /Get-PackageInfo /Packagepath:"C:\ConfigMgr_OfflineImageServicing\f3b2ffde-1d99-45fb-a7e6-48351fbfb88c\windows8.1-kb3012702-x64.cab">>C:\ConfigMgr_OfflineImageServicing\FCH00124\_@2DA2.tmp"~  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:46:49.377-60><thread=9308 (0x245C)>
GetUpdateApplicability returned code 0x80070057~  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:46:49.393-60><thread=9308 (0x245C)>
Applicability State = APPLICABILITY_CHECK_NOT_SUPPORTED, Update Binary = C:\ConfigMgr_OfflineImageServicing\f3b2ffde-1d99-45fb-a7e6-48351fbfb88c\windows8.1-kb3012702-x64.cab.  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:46:49.408-60><thread=9308 (0x245C)>
Applying update with ID 16894087 on image at index 1.  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:46:49.440-60><thread=9308 (0x245C)>
dism.exe tool info: version=10.0.10240.16384, architecture=9~  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:46:49.471-60><thread=9308 (0x245C)>
Failed to install update with error code 87~  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:47:03.112-60><thread=9308 (0x245C)>
STATMSG: ID=7909 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=FCH-SCCM-01.fch.local SITE=FCH PID=9260 TID=9308 GMTDATE=Wed Apr 06 13:47:03.112 2016 ISTR0="16894087" ISTR1="FCH00124" ISTR2="1" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:47:03.112-60><thread=9308 (0x245C)>
No need to apply this update binary since it's not required on the mounted image.  $$<SMS_OFFLINE_SERVICING_MANAGER><04-06-2016 14:47:03.143-60><thread=9308 (0x245C)>

The process seems to work fine for a Windows 10 Version 1511 Wim file, so I was wondering if maybe using this version of DISM is not supported for Server 2012 R2 and I actually need to go ahead and install Windows ADK 8.1?

Regards

Leon

Hi Guys,

I am trying to upgrade from SCCM 2012 R2 CU3 to SCCM 1511.

Prior to that, i installed Windows ADK 10.0.26624 and couldn't add into SCCM console. it will not allow me to select the Boot Image.

Is it supported to add in SCCM 2012 R2 CU3 version?

If not, Do i need to install Windows ADK 10.0.26624 after SCCM 1511 ?

Karthick Jokirathinam | My blogs:http://www.karthickjokirathinam.com | Twitter: @KarthickJoki

All,

My SCCM environment is currently 5.00.8239.1000.  At this point, I am waiting for the next maintenance window I have to upgrade further, so I am stuck on this for now.  It has been a long time since I had to import drivers, so my memory about doing this is a bit fuzzy.

I imported new drivers for the Lenovo M700 running Windows 7 x86. The drivers appeared to import without an issue into SCCM but I can't seem to get them into the boot image. If I right click the driver, go to edit and then click Boot Images, the wizard shows.  My driver is in the top screen but a list of boot images never show.  I also thought there was a way to modify the drivers by going into the properties of the boot image itself, but the only tabs I have is General, Data Source, Data Access, Distribution Settings, Content Locations and Security.  I vaguely remember there being a drivers tab where I could modify what was in the image.

Am I missing something?  Did MS move something?

Thank you in advance.

-Brian