we recently upgraded SCCM from SCCM 2012 R SP1 CU2 to Cu3 and PXE has stopped working.

We have around 55 DP servers in various locations and all of them have PXE enabled. We have this issue in all locations.

Until I have done followed below troubleshooting steps

1) Uninstall WAIK 10,

2) Removed Boot images from sccm

3) Installed WAIK 10

4) Imported boot images to sccm

Redistributed boot images , but still PXE boot fails with message "PXE-53 No boot file name received"

SMS PXE logs does not show any errors. Anyone else has faced this issue.?

Hi,

I have the following standard partition set in my org.

C: OS 

D: data

and 350 MB for system reserved.

I m just formatting the C partition. After deployment the data drive is labeled as E and system preserve as D. 

However I want the same drive letter as it was before the formatting.I have disabled the format and partition task and running script to format C only. Please let me know how this can be achieved.

Regards, "If this thread answered your question, please click on "Mark as Answer"

I am working on using PXE with SCCM 2012 and finally got my test VM to boot with the standard x86 boot image. This is the process:

1. Start up VM with no OS

2. Contacts SCCM and I press F12 to Network Boot

3. Boots into a SCCM screen and says " Windows is starting up" then " Preparing Network Connections".

4. Then all i see is a blank screen. After about a minute it will just reboot.

I found this post that discusses adding the drivers need for the boot images:

http://social.technet.microsoft.com/Forums/en-US/fd96466b-0521-48d8-b31e-4477468982fe/sccm-pxe-boot-initiated-but-nothing-happens-after-that?forum=configmgrosd

I added the entire VMware tools Driver folder to both my boot images. (All it had in there was a SCSI adapter)

Tried to redo the PXE and still get the same menages with the blank screen after that. 

What am I missing here? 

We currently use WinPE 3.1 x86 in our environment because we still have legacy PC's (600) we are slowly replacing them however, we nee to also start rolling out our new pc's. The new pc's will be running Windows 8.1 x64 and I'm attempting to use our existing WinPE 3.1 x86 boot wim. I have injected the appropriate x64 NIC driver but when I PXE boot I receive the following message;

"Initializing hardware devices"

Then,

"Unable to read task sequence configuration disk"

What am I doing wrong? Is it even possible to run a Windows 8.1 x64 task sequence using WinPE 3.1 x86 boot wim?

DHeinz

uExitCode == 0, HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,548)	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)Dism failed with return code 2	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)
AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,658)	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)Failed to add driver to driver store. Code 0x80070002	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)InstallDriver( iInstallParams->sContentId, iInstallParams->sSource, iInstallParams->pBootCriticalInfo ), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\driverinstaller.cpp,557)	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)
ReleaseSource() for C:\_SMSTaskSequence\Packages\CA30001A.	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)
reference count 1 for the source C:\_SMSTaskSequence\Packages\CA30001A before releasing	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)
Released the resolved source C:\_SMSTaskSequence\Packages\CA30001A	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)
pDriverInstaller->InstallDriverPackage( sPackageId, pBootCriticalInfo ), HRESULT=80070002 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\osddriverclient.cpp,380)	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)Failed to provision driver. Code 0x80070002	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)Exiting with return code 0x80070002	OSDDriverClient	4/12/2016 1:27:21 PM	1856 (0x0740)
Process completed with exit code 2147942402	TSManager	4/12/2016 1:27:21 PM	1324 (0x052C)
!--------------------------------------------------------------------------------------------!	TSManager	4/12/2016 1:27:21 PM	1324 (0x052C)Failed to run the action: Optiplex 790. The system cannot find the file specified. (Error: 80070002; Source: Windows)	TSManager	4/12/2016 1:27:21 PM	1324 (0x052C)MP server http://FSCCM3.college.mptc.tech. Ports 80,443. CRL=false.	TSManager	4/12/2016 1:27:21 PM	1324 (0x052C)

I have some new Dell Precision Laptops (All have Samsung NVM Drives) After trying to lay down the image multiple times after apply os it just gets in a blue screen loop.

I found that I need to apply these 2 updates:

https://support.microsoft.com/en-us/kb/2990941

https://support.microsoft.com/en-us/kb/3087873

But I tried adding in my current task sequence after the WIM is laid down to dism those to updates in and it does nothing.  What am I missing?  Has anyone else ran into this problem how did you resolve.  I appreciate your assistance in this issue.

I also have the NVM Drivers needed for Samsung and they are in my driver package but it is not getting that far.  I can install Windows 7 on these precisions from usb thumb drive and using the NVM driver... I followed this guide for that testing.

http://forum.notebookreview.com/threads/guide-installing-windows-7-on-an-nvme-ssd-from-a-usb-3-0-thumbdrive.783921/

we have just upgraded to CM2012 1602. We are no longer able to press F8 during an OSD to bring up the CMD window. I also do not see any option on the Boot.wim to enable F8. Was this taken away in 1602?  And if it was how do you capture log files during a failed OSD?

Thank you. 

mqh7

Hi there...I'm fairly new to OSD on SCCM 2012 and am troubleshooting driver deployment for a specific machine. I've set up my driver store based on Johan's article at http://deploymentresearch.com/Research/Post/273/The-Drivers-Saga-continues-How-to-Master-Drivers-in-ConfigMgr-2012. I've been able to image various machines (mostly Lenovos) this way, using either driver packages or auto-applying drivers, and haven't had driver issues until now with either approach.

Now I have some older hardware (Acer netbooks) that, as far as I can tell, downloads the image AND driver package. For troubleshooting purposes, I've removed any conditions based on WMI queries and am simply pushing the driver package for the Acer D257 netbook. Windows setup completes, installs the CfgMgr client and reboots. I can then log onto the client desktop but most of the netbook-specific drivers are missing, including network and chipset, etc. The Intel graphics makes it for some reason though...I can copy the drivers used from my SCCM driver source onto USB, go to Device Manager and update the unknown devices, and Windows installs all the unknown devices. The drivers for the Acer netbook are directly from Acer's site. I removed any files marked for x64/DOS etc since these are definitely x86 only.

I've been going through the smstslog but am not finding anything obvious. I've posted snippets of it below. Following that are sniipets from setupact.log as well.

Any ideas? I'm stuck! Thanks in advance.

Sir_Timbit

Executing command line: osddriverclient.exe /install:BGS0004B  /unsigned:%OSDAllowUnsignedDriver%    TSManager    4/12/2016 10:07:16 AM    1640 (0x0668)
============================[ OSDDriverClient.exe ]============================    OSDDriverClient    4/12/2016 10:07:16 AM    2040 (0x07F8)
Command line: "osddriverclient.exe" /install:BGS0004B /unsigned:false    OSDDriverClient    4/12/2016 10:07:16 AM    2040 (0x07F8)
Driver path is C:\_SMSTaskSequence\drivers    OSDDriverClient    4/12/2016 10:07:16 AM    2040 (0x07F8)
Applying driver package "BGS0004B".    OSDDriverClient    4/12/2016 10:07:16 AM    2040 (0x07F8)
Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL'    OSDDriverClient    4/12/2016 10:07:16 AM    2040 (0x07F8)
ResolveSource flags: 0x00000000    OSDDriverClient    4/12/2016 10:07:16 AM    2040 (0x07F8)
SMSTSPersistContent: . The content for package BGS0004B will be persisted    OSDDriverClient    4/12/2016 10:07:16 AM    2040 (0x07F8)
DownloadOnDemand flag is true. Attempting to download content locally for Package BGS0004B.    OSDDriverClient    4/12/2016 10:07:16 AM    2040 (0x07F8)
...
List of files to be downloaded    OSDDriverClient    4/12/2016 10:07:22 AM    2040 (0x07F8)  Directory: http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/04236342-4E41-4E70-A901-6AE4FC77BAA0/    OSDDriverClient    4/12/2016 10:07:22 AM    2040 (0x07F8)  File: http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/04236342-4E41-4E70-A901-6AE4FC77BAA0/852.inf    OSDDriverClient    4/12/2016 10:07:22 AM    2040 (0x07F8)  File: http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/04236342-4E41-4E70-A901-6AE4FC77BAA0/ich7core.inf    OSDDriverClient    4/12/2016 10:07:23 AM    2040 (0x07F8)  File: http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/0445550D-6A31-4474-954D-F8D2AC6A8D00/NETwLv32.INF    OSDDriverClient    4/12/2016 10:07:24 AM    2040 (0x07F8)  File: http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/1BDF0A1A-4CCE-48C2-8EE6-2F8CA0AAD50A/HDARt.inf    OSDDriverClient    4/12/2016 10:07:25 AM    2040 (0x07F8)  File: http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/1BDF0A1A-4CCE-48C2-8EE6-2F8CA0AAD50A/RtkAudioService.exe    OSDDriverClient    4/12/2016 10:07:25 AM    2040 (0x07F8)  File: http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/1F6C4F9D-C4EA-41AB-ADB8-C5CA29075E53/igfxsrvc.exe    OSDDriverClient    4/12/2016 10:07:26 AM    2040 (0x07F8)  File: http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/1F6C4F9D-C4EA-41AB-ADB8-C5CA29075E53/kit31053.inf    OSDDriverClient    4/12/2016 10:07:26 AM    2040 (0x07F8)  File: http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/1F6C4F9D-C4EA-41AB-ADB8-C5CA29075E53/kit31053.cat    OSDDriverClient    4/12/2016 10:07:26 AM    2040 (0x07F8)
...
GetDirectoryListing() successfully completed    OSDDriverClient    4/12/2016 10:07:31 AM    2040 (0x07F8)
Creating folder: C:\_SMSTaskSequence\Packages\BGS0004B\04236342-4E41-4E70-A901-6AE4FC77BAA0     OSDDriverClient    4/12/2016 10:07:31 AM    2040 (0x07F8)
...
Downloading file /SMS_DP_SMSPKG$/BGS0004B/sccm?/04236342-4E41-4E70-A901-6AE4FC77BAA0/945.inf range 0-4630    OSDDriverClient    4/12/2016 10:07:34 AM    2040 (0x07F8)
Downloaded file from http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/04236342-4E41-4E70-A901-6AE4FC77BAA0/945.inf to C:\_SMSTaskSequence\Packages\BGS0004B\04236342-4E41-4E70-A901-6AE4FC77BAA0/945.inf     OSDDriverClient   4/12/2016 10:07:34 AM    2040 (0x07F8)
Downloading file /SMS_DP_SMSPKG$/BGS0004B/sccm?/04236342-4E41-4E70-A901-6AE4FC77BAA0/945gm.cat range 0-10872    OSDDriverClient    4/12/2016 10:07:34 AM    2040 (0x07F8)
Downloaded file from http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/04236342-4E41-4E70-A901-6AE4FC77BAA0/945gm.cat to C:\_SMSTaskSequence\Packages\BGS0004B\04236342-4E41-4E70-A901-6AE4FC77BAA0/945gm.cat     OSDDriverClient   4/12/2016 10:07:34 AM    2040 (0x07F8)
Downloaded file from http://SCCMsrv.contoso.com:80/SMS_DP_SMSPKG$/BGS0004B/sccm?/1BDF0A1A-4CCE-48C2-8EE6-2F8CA0AAD50A/Alcmtr.exe to C:\_SMSTaskSequence\Packages\BGS0004B\1BDF0A1A-4CCE-48C2-8EE6-2F8CA0AAD50A/Alcmtr.exe     OSDDriverClient   4/12/2016 10:07:54 AM    2040 (0x07F8)
Downloading file /SMS_DP_SMSPKG$/BGS0004B/sccm?/1BDF0A1A-4CCE-48C2-8EE6-2F8CA0AAD50A/AlcWzrd.exe range 0-2815591    OSDDriverClient    4/12/2016 10:07:54 AM    2040 (0x07F8)
...
Content successfully downloaded at C:\_SMSTaskSequence\Packages\BGS0004B.    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Adding "C:\_SMSTaskSequence\Packages\BGS0004B\04236342-4E41-4E70-A901-6AE4FC77BAA0" to Windows driver store.    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Setting %SystemRoot% to "C:\WINDOWS"    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86"    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Added list item with key value '1'    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Writing configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Successfully saved configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Setting temporary directory to 'C:\_SMSTaskSequence\PkgMgrTemp'.    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Calling Package manager to add drivers to the offline driver store.    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Command line for extension .exe is "%1" %*    OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Set command line: "X:\WINDOWS\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"    OSDDriverClient   4/12/2016 10:09:52 AM    2040 (0x07F8)
Executing command line: "X:\WINDOWS\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"   OSDDriverClient    4/12/2016 10:09:52 AM    2040 (0x07F8)
Process completed with exit code 0    OSDDriverClient    4/12/2016 10:11:33 AM    2040 (0x07F8)
Dism successfully added drivers to the offline driver store.    OSDDriverClient    4/12/2016 10:11:33 AM    2040 (0x07F8)
Successfully added "C:\_SMSTaskSequence\Packages\BGS0004B\04236342-4E41-4E70-A901-6AE4FC77BAA0" to the Windows driver store.    OSDDriverClient    4/12/2016 10:11:33 AM    2040 (0x07F8)
...
Writing configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    4/12/2016 10:22:17 AM    2040 (0x07F8)
Successfully saved configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    4/12/2016 10:22:17 AM    2040 (0x07F8)
Setting temporary directory to 'C:\_SMSTaskSequence\PkgMgrTemp'.    OSDDriverClient    4/12/2016 10:22:17 AM    2040 (0x07F8)
Calling Package manager to add drivers to the offline driver store.    OSDDriverClient    4/12/2016 10:22:17 AM    2040 (0x07F8)
Command line for extension .exe is "%1" %*    OSDDriverClient    4/12/2016 10:22:17 AM    2040 (0x07F8)
Set command line: "X:\WINDOWS\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"    OSDDriverClient   4/12/2016 10:22:17 AM    2040 (0x07F8)
Executing command line: "X:\WINDOWS\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"   OSDDriverClient    4/12/2016 10:22:17 AM    2040 (0x07F8)
Process completed with exit code 0    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Dism successfully added drivers to the offline driver store.    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Successfully added "C:\_SMSTaskSequence\Packages\BGS0004B\F83361CB-B1DE-49BD-BB83-8DCC39B24E67" to the Windows driver store.    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Adding "C:\_SMSTaskSequence\Packages\BGS0004B\F8E9756B-3361-433C-BDC7-33DBE30A5227" to Windows driver store.    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Setting %SystemRoot% to "C:\WINDOWS"    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Getting namespace "Microsoft-Windows-PnpCustomizationsNonWinPE" for architecture "x86"    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Added list item with key value '1'    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Writing configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Successfully saved configuration information to C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Setting temporary directory to 'C:\_SMSTaskSequence\PkgMgrTemp'.    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Calling Package manager to add drivers to the offline driver store.    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Command line for extension .exe is "%1" %*    OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Set command line: "X:\WINDOWS\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"    OSDDriverClient   4/12/2016 10:23:09 AM    2040 (0x07F8)
Executing command line: "X:\WINDOWS\system32\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"   OSDDriverClient    4/12/2016 10:23:09 AM    2040 (0x07F8)
Process completed with exit code 0    OSDDriverClient    4/12/2016 10:24:09 AM    2040 (0x07F8)
Dism successfully added drivers to the offline driver store.    OSDDriverClient    4/12/2016 10:24:09 AM    2040 (0x07F8)
Successfully added "C:\_SMSTaskSequence\Packages\BGS0004B\F8E9756B-3361-433C-BDC7-33DBE30A5227" to the Windows driver store.    OSDDriverClient    4/12/2016 10:24:09 AM    2040 (0x07F8)
Successfully applied driver package "BGS0004B".    OSDDriverClient    4/12/2016 10:24:09 AM    2040 (0x07F8)
ReleaseSource() for C:\_SMSTaskSequence\Packages\BGS0004B.    OSDDriverClient    4/12/2016 10:24:09 AM    2040 (0x07F8)
reference count 1 for the source C:\_SMSTaskSequence\Packages\BGS0004B before releasing    OSDDriverClient    4/12/2016 10:24:09 AM    2040 (0x07F8)
Released the resolved source C:\_SMSTaskSequence\Packages\BGS0004B    OSDDriverClient    4/12/2016 10:24:09 AM    2040 (0x07F8)
Exiting with return code 0x00000000    OSDDriverClient    4/12/2016 10:24:09 AM    2040 (0x07F8)
Process completed with exit code 0    TSManager    4/12/2016 10:24:09 AM    1640 (0x0668)
!--------------------------------------------------------------------------------------------!    TSManager    4/12/2016 10:24:09 AM    1640 (0x0668)
Successfully completed the action (Acer AOD257 drivers) with the exit win32 code 0    TSManager    4/12/2016 10:24:09 AM    1640 (0x0668)

I do however get a number of errors/warnings when I check out c:\windows\panther\setupact.log:

...
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: Driver storvsc was retrieved from the CDDB.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: Driver VMBusHID was retrieved from the CDDB.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: Driver hyperkbd was retrieved from the CDDB.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: Driver gencounter was retrieved from the CDDB.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: Driver vhdmp was retrieved from the CDDB.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: Finished retrieving the list of function drivers from the CDDB.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: Retrieving the list of drivers that are currently in use by devices.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: {Retrieving drivers used by device ACPI\PNP0C0A\1}
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: {Retrieving drivers used by device PCI\VEN_8086&DEV_A011&SUBSYS_05901025&REV_02\3&21436425&0&10}
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: The device setup class for device PCI\VEN_8086&DEV_A011&SUBSYS_05901025&REV_02\3&21436425&0&10
 is 4d36e968-e325-11ce-bfc1-08002be10318.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: igfx is the function driver for device PCI\VEN_8086&DEV_A011&SUBSYS_05901025&REV_02\3&21436425&0&10
...
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: {Retrieving drivers used by device ACPI\PNP0200\4&215D0F95&0}
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: The device setup class for device ACPI\PNP0200\4&215D0F95&0 is 4d36e97d-e325-11ce-bfc1-08002be10318.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: No function driver specified for device ACPI\PNP0200\4&215D0F95&0.
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: No device upper filter drivers are specified for device ACPI\PNP0200\4&215D0F95&0
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: No device lower filter drivers are specified for device ACPI\PNP0200\4&215D0F95&0
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: No class upper filter drivers are specified for device ACPI\PNP0200\4&215D0F95&0
2016-04-12 10:27:27, Info                  SYSPRP SPPNP: No class lower filter drivers are specified for device ACPI\PNP0200\4&215D0F95&0
...
this goes on for quite a while for various devices...
...
2016-04-12 10:30:43, Info                  SYSPRP Status: End
2016-04-12 10:30:43, Info                  SYSPRP Status: Total = -1,    Complete = -1,     Progress = 100%    (100%)
2016-04-12 10:30:43, Info                  SYSPRP Callback canceled operation, Err = 1223!
2016-04-12 10:30:43, Info                  SYSPRP DeviceInstallStatusThreadProc failed, Err = 1223
2016-04-12 10:30:47, Info                  SYSPRP SPPNP: Devices reinstallation completed.
2016-04-12 10:30:47, Info                  SYSPRP Waiting for thread to exit
2016-04-12 10:30:47, Info                  SYSPRP Thread exited
2016-04-12 10:30:48, Info                  SYSPRP SPPNP: Sysprep_Specialize_Pnp: Exit
...
2016-04-12 10:31:01, Info                  CBS    SQM: Cleaning up report files older than 10 days.
2016-04-12 10:31:01, Info                  CBS    SQM: Requesting upload of all unsent reports.
2016-04-12 10:31:01, Info                  CBS    SQM: Failed to start upload with file pattern: C:\WINDOWS\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005
 - E_FAIL]
2016-04-12 10:31:01, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2016-04-12 10:31:01, Info                  CBS    SQM: Failed to start upload with file pattern: C:\WINDOWS\servicing\sqm\*_all.sqm, flags: 0x6 [HRESULT = 0x80004005
 - E_FAIL]
2016-04-12 10:31:01, Info                  CBS    SQM: Failed to start always sample upload. [HRESULT = 0x80004005 - E_FAIL]
2016-04-12 10:31:01, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
...
2016-04-12 10:38:34, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
2016-04-12 10:38:34, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
2016-04-12 10:38:34, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
2016-04-12 10:38:34, Warning               IBSLIB ModifyBootEntriesLegacy: There was an error getting the path to the boot.ini or ntldr. dwRetCode=[0x1F]
2016-04-12 10:38:34, Warning               IBSLIB ModifyBootEntriesLegacy: We did not successfully complete ModifyBootEntriesLegacy.  This is non-fatal, continuing setup. dwRetCode[0x1F]
...
2016-04-12 10:38:34, Info       [0x0601dc] IBS    Setup has completed phase 4 at 2016-04-12 10:38:34
2016-04-12 10:38:35, Info                  IBS    Successfully logged OS information onto event viewer system channel
2016-04-12 10:38:35, Info       [0x0601e1] IBS    InstallWindows:First boot phase of setup done!!!!
2016-04-12 10:38:35, Info       [0x090009] PANTHR CBlackboard::Close: c:\windows\panther\setupinfo.

I am having issues imaging hard disk drives that are greater than 2TB in size and are formatted with a GUID Partition Scheme. I have tried the following:

1. The standard procedure. Boot to legacy device, diskpart the disk, reboot and image. I have found that 2 things happen -- one being that the computer gets to the partition disk step and then immediately reboots without any prompt or error message and two being that I get an error code of 0x80070490.

2. I made sure to change the storage configuration in the BIOS from RAID to AHCI. SCCM has a lot of trouble recognizing and imaging drives that are in a raided configuration.

3. I created a new task sequence that at the partition disk step, it formats the drive as GPT instead of MBR. You need to format the drive as GPT instead of MBR because MBR only recognizes up to 2TB of drive space. It will ignore the rest of the space, no matter how large. This test task sequence didn't work either. I got the error message listed above as well as 0x8007000F.

4. I then found out that the above methods under no circumstance would work. This is because you can't format a GPT drive when booted into a legacy device. You need to be booted into UEFI for this to work. So I tried booting to the sccm imaging usb in UEFI mode instead of legacy. Again, this didn't work. I got the same error message listed above.

5. Updated the BIOS just for kicks. This didn't help either.

6.  I have imported the latest HDD drivers into the boot image

Any ideas?

We are trying to use a task sequence media to capture a Windows 10. It seems that sysprep is breaking Windows 10.

We are running SCCM 2012 R2 SP1 CU3. We have installed ADK for Windows 10 and MDT 2013 Update 2. Any idea on what we are missing?

Ok so we got some new Lenovo Yoga460 laptops in. They have new Skylake Processor in them, so we decided to do a Win10 Build on them. I manually installed Win10 customized it to our wants and needs but now that I go to try and capture the image i'm running into issues. I created capture media in SCCM 2012 SP1 on a thumb drive, and when i plug it in it starts right up no issues. I put in where i want to save the image and the details and click next to start the capture process. It looks like it begins to load the sysprep, then almost immediately fails stating that "The Capture Wizard has failed with error code (0x00004005)." I can't seem to figure out what i'm doing wrong.  I've pasted the error log below. Any help that anyone can provide would be greatly appreciated.

Über Random

Looking way to add a description in AD during OSD, for this followed various blog articles and still not successful in ending up with this.

Please, have a look on configuration what I did so far,

1. Created a package with PowerShell script

Script contains 

#Create OSD Task Sequence Environment Object
$tsenv = New-Object -COMObject Microsoft.SMS.TSEnvironment

#Get the ComputerDescription
$strComputerDesc = $tsenv.Value("OSDComputerDesc")

#Computer Name
$strName = $env:computername

#Get PSSession Credentials
$strUser = "Domain\User"
$strPassword = "password"

#Connect to Remote PowerShell Session
#Set Active Directory Properties
$pw = ConvertTo-SecureString -AsPlainText -Force -String $strPassword
$cred = New-Object -TypeName System.Management.Automation.PSCredential -ArgumentList "$strUser", $pw
$s = New-PSSession -Computer SERVER -Credential $cred
Invoke-Command -Session $s -Script { Import-Module ActiveDirectory }
Invoke-Command -Session $s -ScriptBlock { Set-ADComputer -Identity "$using:strname" -Description "$using:strComputerDesc" }

2. OSDCompDesc variable defined in UDI

3. In task sequence executing by using a command line.

Run a command line,

moreover, in smsts.log file there is no failure of this task, last error code is 0 3010 (success)

Kindly suggest any changes are to be made in order to work this...

REGARDS DANISH DANIE

If this is addressed somewhere else, I apologize. I haven't been able to locate a resolution.

SCCM 2012 (1511), deploying Windows 10 to a Dell 7275 Tablet via Task Sequence Media on a USB stick.

The media is created with no issues and the tablet successfully boots. DISKPART show the HDD as Disk 0, online, 238gb, and the flash drive as Disk 1, Online, 29gb)

Task Sequence is as follows:

• Restart in Windows PE (Win10PE x64)
• Diskpart Clean Disk 0
• Partition Disk (Standard MBR, Primary, 100%, Make Boot, NTFS)
• Apply OS (Windows 10 Enterprise, Disk 0, Partition 1)
• Apply Windows Settings
• Apply Network Settings
• E7275 Driver Package
• Setup Windows and ConfigMgr
• Restart
• The TS is a stripped down version with no additional apps to install so I can created the media faster for testing.
• The sequence of events that leads to the error is:

• Boot to USB (Successful)
• TS Wizard opens, I click NEXT
• The TS shows the proper image, I click NEXT
• As soon as the TS goes to restart in Windows PE it pops an error (80070003)

I pull the logs and here is the SMSBOOT section. The C: it is listing is the USB stick...

<![LOG[========================= [ smsboot.exe ] =========================]LOG]!><time="09:09:28.580+480" date="04-14-2016" component="Reboot" context="" type="1" thread="1368" file="rebootcomputer.cpp:184">
<![LOG[Command line: '"smsboot.exe" /target:WinPE']LOG]!><time="09:09:28.580+480" date="04-14-2016" component="Reboot" context="" type="0" thread="1368" file="rebootcomputer.cpp:186">
<![LOG[SMSTSRebootDelay=60]LOG]!><time="09:09:28.580+480" date="04-14-2016" component="Reboot" context="" type="1" thread="1368" file="rebootcomputer.cpp:122">
<![LOG[SMSTSRebootMessage=A new Microsoft Windows operating system is being installed. The computer must restart to continue.]LOG]!><time="09:09:28.580+480" date="04-14-2016" component="Reboot" context="" type="1" thread="1368" file="rebootcomputer.cpp:122">
<![LOG[SMSTSRebootRequested=WinPE]LOG]!><time="09:09:28.580+480" date="04-14-2016" component="Reboot" context="" type="1" thread="1368" file="rebootcomputer.cpp:122">
<![LOG[Process completed with exit code 0]LOG]!><time="09:09:28.595+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="commandline.cpp:1124">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="09:09:28.603+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="instruction.cxx:805">
<![LOG[Successfully completed the action (Restart in Windows PE) with the exit win32 code 0]LOG]!><time="09:09:28.603+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="instruction.cxx:846">
<![LOG[Do not send status message in full media case]LOG]!><time="09:09:28.603+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="utils.cpp:6053">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=0]LOG]!><time="09:09:28.603+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:669">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=true]LOG]!><time="09:09:28.603+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:669">
<![LOG[Expand a string: %_SMSTSMDataPath%\Logs]LOG]!><time="09:09:28.603+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:783">
<![LOG[Clear local default environment]LOG]!><time="09:09:28.603+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:808">
<![LOG[User did not specify local data drive]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="utils.cpp:2153">
<![LOG[Volume C:\ is not a fixed hard drive]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="utils.cpp:1234">
<![LOG[Volume X:\ is not a fixed hard drive]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="utils.cpp:1234">
<![LOG[TSM root drive = ]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="utils.cpp:1299">
<![LOG[We do not find an available volume to store the local data path]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="utils.cpp:2168">
<![LOG[Set a global environment variable _SMSTSNextInstructionPointer=2]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:669">
<![LOG[Set a TS execution environment variable _SMSTSNextInstructionPointer=2]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:387">
<![LOG[Set a global environment variable _SMSTSInstructionStackString=0]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:669">
<![LOG[Set a TS execution environment variable _SMSTSInstructionStackString=0]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:415">
<![LOG[Save the current environment block]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:834">
<![LOG[pszPath[0] != L'\0', HRESULT=80070057 (e:\nts_sccm_release\sms\framework\core\ccmcore\path.cpp,60)]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="path.cpp:60">
<![LOG[Filesystem::Path::Add(sEnvPath, EnvDataFileName, sEnvPath), HRESULT=80070057 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,726)]LOG]!><time="09:09:28.650+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="environmentlib.cpp:726">
<![LOG[Failed to save environment to  (80070057)]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="2" thread="1276" file="environmentlib.cpp:747">
<![LOG[TS::Environment::SharedEnvironment.saveEnvironment(szPath), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,843)]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:843">
<![LOG[Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="3" thread="1276" file="executionenv.cxx:843">
<![LOG[SaveEnvironment(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\executionenv.cxx,421)]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="executionenv.cxx:421">
<![LOG[Failed to persist execution state. Error 0x(80070057)]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="2" thread="1276" file="executionenv.cxx:427">
<![LOG[Failed to save execution state and environment to local hard disk]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="2" thread="1276" file="engine.cxx:258">
<![LOG[Reboot to WinPE]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="engine.cxx:464">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="commandline.cpp:229">
<![LOG[Set command line: "bcdedit.exe"]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="commandline.cpp:732">
<![LOG[Executing command line: "bcdedit.exe"]LOG]!><time="09:09:28.665+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="commandline.cpp:828">
<![LOG[Process completed with exit code 1]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="commandline.cpp:1124">
<![LOG[Calling RebootSystem()]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="engine.cxx:581">
<![LOG[OSD type of task sequence. ignore the service window setting]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="engine.cxx:683">
<![LOG[!sLocalDataPath.empty(), HRESULT=80070003 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,7386)]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="utils.cpp:7386">
<![LOG[Data path not set to save boot system.]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="3" thread="1276" file="utils.cpp:7386">
<![LOG[BackupEfiBootSystem() failed. 0x80070003.]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="3" thread="1276" file="utils.cpp:7415">
<![LOG[TS::Utility::BackupEfiBootSystem(), HRESULT=80070003 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,809)]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="engine.cxx:809">
<![LOG[Failed to reboot the system. Error 0x(80070003)]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="3" thread="1276" file="engine.cxx:965">
<![LOG[RebootSystem(pwszRebootMessage, dwRebootTimeout, dwRebootReason, bRebootWinPE), HRESULT=80070003 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,589)]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="engine.cxx:589">
<![LOG[Failed to initialize a system reboot.
The system cannot find the path specified. (Error: 80070003; Source: Windows)]LOG]!><time="09:09:28.705+480" date="04-14-2016" component="TSManager" context="" type="3" thread="1276" file="engine.cxx:589">
<![LOG[CheckForRebootRequest(&bRebootInitiated), HRESULT=80070003 (e:\nts_sccm_release\sms\client\tasksequence\executionengine\engine.cxx,282)]LOG]!><time="09:09:28.721+480" date="04-14-2016" component="TSManager" context="" type="0" thread="1276" file="engine.cxx:282">
<![LOG[Fatal error is returned in check for reboot request of the action (Restart in Windows PE).
The system cannot find the path specified. (Error: 80070003; Source: Windows)]LOG]!><time="09:09:28.724+480" date="04-14-2016" component="TSManager" context="" type="3" thread="1276" file="engine.cxx:282">
<![LOG[An error (0x80070003) is encountered in execution of the task sequence]LOG]!><time="09:09:28.725+480" date="04-14-2016" component="TSManager" context="" type="3" thread="1276" file="engine.cxx:360">
<![LOG[Do not send status message in full media case]LOG]!><time="09:09:28.727+480" date="04-14-2016" component="TSManager" context="" type="1" thread="1276" file="utils.cpp:6053">
<![LOG[Executing command line: X:\windows\system32\cmd.exe /k]LOG]!><time="09:09:34.844+480" date="04-14-2016" component="TSBootShell" context="" type="1" thread="936" file="bootshell.cpp:897">
<![LOG[The command completed successfully.]LOG]!><time="09:09:34.860+480" date="04-14-2016" component="TSBootShell" context="" type="1" thread="936" file="bootshell.cpp:979">
<![LOG[Successfully launched command shell.]LOG]!><time="09:09:34.860+480" date="04-14-2016" component="TSBootShell" context="" type="1" thread="936" file="bootshell.cpp:441">

Hi,

i am using MDT for my Tasksequence and it was working. Suddenly the domain join is not working any more.

So two questions.

1. Which driver is used for the domain join (NIC of Boot Image or the driver in the step Apply Drivers)

2. When does the domian join happens? I think the Apply Network Settings part not realy executes the domain join, it just preperas the unattend.xml

I changed my site to communicate over HTTPS and ever since I can't get OSD to complete. I am on the latest version of sccm and have MDT integration

This is a log file for an sccm OSD TSK 

LOGGING: Finalize process ID set to 732TSBootShell4/4/2016 10:51:30 AM736 (0x02E0)
==============================[ TSBootShell.exe ]==============================TSBootShell4/4/2016 10:51:30 AM736 (0x02E0)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'TSBootShell4/4/2016 10:51:30 AM736 (0x02E0)
Debug shell is enabledTSBootShell4/4/2016 10:51:30 AM736 (0x02E0)
Waiting for PNP initialization...TSBootShell4/4/2016 10:51:31 AM764 (0x02FC)
RAM Disk Boot Path: NET(0)\SMSIMAGES\NYC00098\WINPE.NYC00098.WIMTSBootShell4/4/2016 10:51:31 AM764 (0x02FC)
Booted from network (PXE)TSBootShell4/4/2016 10:51:31 AM764 (0x02FC)
Network(PXE) path: X:\sms\data\TSBootShell4/4/2016 10:51:31 AM764 (0x02FC)
Found config path X:\sms\data\TSBootShell4/4/2016 10:51:31 AM764 (0x02FC)
Booting from removable media, not restoring bootloaders on hard driveTSBootShell4/4/2016 10:51:31 AM764 (0x02FC)
X:\sms\data\WinPE does not exist.TSBootShell4/4/2016 10:51:31 AM764 (0x02FC)
X:\_SmsTsWinPE\WinPE does not exist.TSBootShell4/4/2016 10:51:31 AM764 (0x02FC)
Executing command line: wpeinit.exe -winpeTSBootShell4/4/2016 10:51:32 AM764 (0x02FC)
The command completed successfully.TSBootShell4/4/2016 10:51:35 AM764 (0x02FC)
Starting DNS client service.TSBootShell4/4/2016 10:51:35 AM764 (0x02FC)
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\TSBootShell4/4/2016 10:51:36 AM764 (0x02FC)
The command completed successfully.TSBootShell4/4/2016 10:51:36 AM764 (0x02FC)
==============================[ TSMBootStrap.exe ]==============================TSMBootstrap4/4/2016 10:51:36 AM844 (0x034C)
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\TSMBootstrap4/4/2016 10:51:36 AM844 (0x034C)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'TSMBootstrap4/4/2016 10:51:36 AM844 (0x034C)
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL'TSMBootstrap4/4/2016 10:51:36 AM844 (0x034C)
Current OS version is 10.0.10586.0TSMBootstrap4/4/2016 10:51:37 AM844 (0x034C)
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATHTSMBootstrap4/4/2016 10:51:37 AM844 (0x034C)
PXE Boot with Root = X:\TSMBootstrap4/4/2016 10:51:37 AM844 (0x034C)
Executing from PXE in WinPETSMBootstrap4/4/2016 10:51:37 AM844 (0x034C)
Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll TSMBootstrap4/4/2016 10:51:37 AM844 (0x034C)
TsPxe.dll loadedTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Device has PXE bootedTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Variable Path: \SMSTemp\2016.04.01.16.26.56.0003.{38C856C7-3291-4B55-A745-A6AE9283DD5E}.boot.varTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Variable Key Len: 69TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Succesfully added firewall rule for TftpTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Executing: X:\sms\bin\x64\smstftp.exe -i 192.168.25.5 get \SMSTemp\2016.04.01.16.26.56.0003.{38C856C7-3291-4B55-A745-A6AE9283DD5E}.boot.var X:\sms\data\variables.datTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Command line for extension .exe is "%1" %*TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Set command line: "X:\sms\bin\x64\smstftp.exe" -i 192.168.25.5 get \SMSTemp\2016.04.01.16.26.56.0003.{38C856C7-3291-4B55-A745-A6AE9283DD5E}.boot.var X:\sms\data\variables.datTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Executing command line: "X:\sms\bin\x64\smstftp.exe" -i 192.168.25.5 get \SMSTemp\2016.04.01.16.26.56.0003.{38C856C7-3291-4B55-A745-A6AE9283DD5E}.boot.var X:\sms\data\variables.datTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Process completed with exit code 0TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Succesfully removed firewall rule for TftpTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Successfully downloaded pxe variable file.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
we are booted using PXETSPxe4/4/2016 10:51:37 AM844 (0x034C)
we are booted using PXE and we use a generated passwordTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Loading Media Variables from "X:\sms\data\variables.dat"TSPxe4/4/2016 10:51:37 AM844 (0x034C)
CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,165)TSPxe4/4/2016 10:51:37 AM844 (0x034C)
SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387)TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Verifying media password.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Loading Media Variables from "X:\sms\data\variables.dat"TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Found network adapter "Intel 21140-Based PCI Fast Ethernet Adapter (Emulated)" with IP Address 192.168.25.63.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Loading Media Variables from "X:\sms\data\variables.dat"TSPxe4/4/2016 10:51:37 AM844 (0x034C)
CryptDecrypt (hKey, 0, 1, 0, pData, &dwDecryptedLen), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\smscrypt\windes.cpp,165)TSPxe4/4/2016 10:51:37 AM844 (0x034C)
SMS::Crypto::DES::DecryptBuffer( (BYTE*)pszPassword, (DWORD)(wcslen(pszPassword)*sizeof(WCHAR)), encryptedBuffer.getBuffer(), (DWORD)encryptedBuffer.size(), pbDecryptedBuffer, dwDecryptedBufferSize ), HRESULT=80090005 (e:\nts_sccm_release\sms\framework\tscore\tsremovablemedia.cpp,387)TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Entering TSMediaWizardControl::GetPolicy.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}TSPxe4/4/2016 10:51:37 AM844 (0x034C)
If current logging settings specify more logging details to be preserved, udpate these settings in TS environmentTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Current LogMaxSize is saved to TS environment since it has not been saved beforeTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Current LogMaxHistory is saved to TS environment since it has not been saved beforeTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Current LogLevel is saved to TS environment since it has not been saved beforeTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Current LogEnabled is saved to TS environment since it has not been saved beforeTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Current LogDebug is saved to TS environment since it has not been saved beforeTSPxe4/4/2016 10:51:37 AM844 (0x034C)
UEFI: falseTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Loading variables from the Task Sequencing Removable Media.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Loading Media Variables from "X:\sms\data\variables.dat"TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting SMSTSMP TS environment variableTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSMediaGuid TS environment variable TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSBootMediaPackageID TS environment variableTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSHTTPPort TS environment variable TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSHTTPSPort TS environment variable TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSIISSSLState TS environment variable TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSLaunchMode TS environment variable TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSMediaPFX TS environment variable TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSPublicRootKey TS environment variableTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSRootCACerts TS environment variable TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSSiteCode TS environment variable TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSSiteSigningCertificate TS environment variableTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSUseFirstCert TS environment variable TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSx64UnknownMachineGUID TS environment variableTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting _SMSTSx86UnknownMachineGUID TS environment variableTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Root CA Public Certs=308203733082025BA0030201020210218B512EAF8701BA45CACD7F58CE4EAD300D06092A864886F70D0101050500304031133011060A0992268993F22C64011916036F726731123010060A0992268993F22C64011916027261311530130603550403130C72612D5241444955532D4E59301E170D3134303631313136303533345A170D3139303631313136313533335A304031133011060A0992268993F22C64011916036F726731123010060A0992268993F22C64011916027261311530130603550403130C72612D5241444955532D4E5930820122300D06092A864886F70D01010105000382010F003082010A0282010100DFC89F36ACE841CB804C5C7AEF7A3641AD53A4214FCEEE1024EE3AAC6D48AD4EECD66EE6BE5C3279AB5AE71681E88EB1780D409A0ED79173CD8955BDB2210E4A955426AB478D14B81488C8B958B450F06C5CCC014E80E3F545D565D937663F00EE61A61D68C52CFEBBB477B05A39CD3CC72CFC1D1C459F05AC5180937D212CB3B7A807D9D400690A9384AF668E6E223C3296EF1D560B90749EA1D851AB7B1CA56013CBF94CB49FB2D0B94CFD05146D615217B279952F947181850D3FFA18C03D34827E4950E7832CB2A2CF0EA09E9C9866F25858F3622B528694FDB317F496B4D52FB5BFFDF03DF90C9ADACE587276D3B09EA8A19F0BA0169BA80C3C57A0CB6B0203010001A3693067301306092B060104018237140204061E0400430041300E0603551D0F0101FF040403020186300F0603551D130101FF040530030101FF301D0603551D0E04160414B246A99F9C66101668A6A3808CC9BFD4C8F45B29301006092B06010401823715010403020100300D06092A864886F70D0101050500038201010012DC6F6DF32A0F5814A0F2AD880986E80B491B17B0D9A6E9C58E720120238D6BE801EB329D811CD9591FF9E5851F31A9382A1E140EB73FCFD408605624AA6ADC910C68C47FC0AC8763EECB3B5DDC67407033A630F8759DBB67A527BCE76AF5CD0776191C8C0268520B189DF5F8ED7E4DFC49820B9591A8007CC2EC23B97A8F0F56A138767E77C878ACDDB8828DB3775EF57E011D1E27A8AF7D91FA84A54008D7CA286D41802FD8C08AF40F17BF997CD8AA616D9F7C11138F4C61635AAEB9F82AF0EFD199F7EF13BC7A99682F2859736A4B976990D18C5AD439C6BEAF22A132E62AC2F02B31F2055046F33B468EDDBA0362C068CB1C8C5F314708014EF90FA999,3082052C30820414A00302010202134900000256CFD32B89F5C2CE16000000000256300D06092A864886F70D0101050500304031133011060A0992268993F22C64011916036F726731123010060A0992268993F22C64011916027261311530130603550403130C72612D5241444955532D4E59301E170D3136303332393139333033305A170D3138303332393139343033305A300030820122300D06092A864886F70D01010105000382010F003082010A0282010100D233303F7909B0F1D70B4F90968B7198809EB8E99CCD9EAD9FBA6766D5AB32FEE4B8A4061D6A7B4211F78ED827A110673C6902ED3460289D83901E1FC573486E3561ECFA7763CCA9791630E1E0EB881EDBBDD8E70404B8CAC614F775A0CE2FD8FF4B2FF6C94237511C8CA1695C98C5F7C78DA2E60823823EEE43699A030637BB4FB4F65AD2A384E71200C6ED7D13B91251ADBD4CEDB649110B44E7F302A92ECCCCE9E765592F3EC3BC89C6A85A2B22C2F993E0E42CA1450DEE28B2082DF75A94F7FBCD115AB1553D16D286F94619566B856F7D8325FB172FD1DE80B14FF3E1B4C82095396C413AD722B8FB87A62AD9EA91AA4878AA7849624072B029AA273E450203010001A382025D30820259303C06092B0601040182371507042F302D06252B060104018237150882B4CA0486ACAB6085AD8503878B974C8596E14C07A69F6883A6C32702016402010630130603551D25040C300A06082B06010505070302300E0603551D0F0101FF0404030205A0301B06092B060104018237150A040E300C300A06082B06010505070302301D0603551D0E0416041452AA34C3DAAC0B027F618996C51AC36F76B8E13E301F0603551D23041830168014B246A99F9C66101668A6A3808CC9BFD4C8F45B293081C30603551D1F0481BB3081B83081B5A081B2A081AF8681AC6C6461703A2F2F2F434E3D72612D5241444955532D4E592C434E3D5241444955532D4E592C434E3D4344502C434E3D5075626C6963204B65792053657276696365732C434E3D53657276696365732C434E3D436F6E66696775726174696F6E2C44433D72612C44433D6F72673F63657274696669636174655265766F636174696F6E4C6973743F626173653F6F626A656374436C6173733D63524C446973747269627574696F6E506F696E743081B506082B060105050701010481A83081A53081A206082B060105050730028681956C6461703A2F2F2F434E3D72612D5241444955532D4E592C434E3D4149412C434E3D5075626C6963204B65792053657276696365732C434E3D53657276696365732C434E3D436F6E66696775726174696F6E2C44433D72612C44433D6F72673F634143657274696669636174653F626173653F6F626A656374436C6173733D63657274696669636174696F6E417574686F7269747930190603551D110101FF040F300D820B5343434D2E72612E6F7267300D06092A864886F70D010105050003820101002F56133AEC48385BC40E71385002B33EE984D503412F2375289B01567FB2744D2988BA3EDABB95A023300723A514546674E6B457510DB16CB1F31CE918DD763C87FBBB9FD1DB9096716DA1E50623D3B39ACFB4067D1F4022B8678955BFB83F51F0259A2CD63C86F4A380A903B54769FBC5CD828A942604B6ADEF129D54CBCE5B2AC9366A4B5F529703A4C1B3FC83A61DF306C93EAC78A85CF5211BDCDEFFEC8B3BE2E97D1CB80F3E6AA19AEA51DE569D37C8F238229585F070750906F20D878903250142F16E221440A23391AE04685CF2BB2BCD980F62E485B3A4F40DD399D8FC2C1E8D3E823776F475B8D7D16D04FDA6E4567F97848A3984E12714633D094CTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Importing certificates to root storeTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Added certificate to store or replaced matching certificate in store.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Added certificate to store or replaced matching certificate in store.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Support Unknown Machines: 0TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Custom hook from X:\\TSConfig.INI is TSPxe4/4/2016 10:51:37 AM844 (0x034C)
No hook is found to be executed before downloading policyTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Authenticator from the environment is empty. TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Need to create Authenticator Info using PFX TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Initialized CStringStream object with string: 270e037c-9847-4220-92df-1183515fbfa2;2016-04-04T18:51:37Z.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Current time info: .TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Getting MP time informationTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Set authenticator in transportTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Requesting client identityTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting message signatures.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
Setting the authenticator.TSPxe4/4/2016 10:51:37 AM844 (0x034C)
CLibSMSMessageWinHttpTransport::Send: URL: SCCM.ra.org:443  CCM_POST /ccm_system_AltAuth/requestTSPxe4/4/2016 10:51:37 AM844 (0x034C)
In SSL, but with no client certTSPxe4/4/2016 10:51:37 AM844 (0x034C)
Request was successful.TSPxe4/4/2016 10:51:40 AM844 (0x034C)
::DecompressBuffer(65536)TSPxe4/4/2016 10:51:40 AM844 (0x034C)
Decompression (zlib) succeeded: original size 411, uncompressed size 2432.TSPxe4/4/2016 10:51:40 AM844 (0x034C)
-60 -60TSPxe 4/4/2016 10:51:40 AM844 (0x034C)
Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60TSPxe4/4/2016 10:51:40 AM844 (0x034C)
Client Identity: TSPxe4/4/2016 10:51:40 AM844 (0x034C)
Netbios name: TSPxe4/4/2016 10:51:40 AM844 (0x034C)
Current time: 2016-04-04 18:51:40.105 TZ:Pacific Standard Time Bias:0480TSPxe4/4/2016 10:51:40 AM844 (0x034C)
Time zone: 480,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,Pacific Standard Time,TSPxe4/4/2016 10:51:40 AM844 (0x034C)
Bias=480,StandardBias=0,DaylightBias=0TSPxe4/4/2016 10:51:40 AM844 (0x034C)
StandardDate.wYear=0,wMonth=0,wDayOfWeek=0,wDay=0,wHour=0,wMinute=0,wSecond=0,wMilliseconds=0TSPxe4/4/2016 10:51:40 AM844 (0x034C)
DaylightDate.wYear=0,wMonth=0,wDayOfWeek=0,wDay=0,wHour=0,wMinute=0,wSecond=0,wMilliseconds=0TSPxe4/4/2016 10:51:40 AM844 (0x034C)
StandardName=Pacific Standard Time,DaylightName= TSPxe4/4/2016 10:51:40 AM844 (0x034C)
Adjusting the system time: -14399.118 seconds TSPxe4/4/2016 10:51:40 AM844 (0x034C)
Time zone: 300,0,-60,0,11,0,1,2,0,0,0,0,3,0,2,2,0,0,0,,TSPxe4/4/2016 2:51:40 PM844 (0x034C)
Bias=300,StandardBias=0,DaylightBias=-60TSPxe4/4/2016 2:51:40 PM844 (0x034C)
StandardDate.wYear=0,wMonth=11,wDayOfWeek=

Hi,

We are using SCCM 2012 task sequence for deployment.  We are not using PXE boot at this time.  32-bit task sequences are associated with the 32bit boot image and ISO file.  64-bit task sequence associate with the 64bit boot image respectively. We are using the same boot image in the task sequence properties under Advanced tab with ISO file created from this boot image.   Yet, we are seeing below Task Sequence Wizard prompt after copying the WIM file to the local computer.  Why can we find the setting to prevent this from happening?  Thanks.

Brian

Hello,

Environment:
1 Single SCCM 2012 R2 SP1 (OS = Windows 2012 R2) server which contains all the critical components to have this running (It's SCCM 2012 R2 SP1 with MDT integrated).
MDT is version MDT 2013 Update 2.

I'm currently trying to deploy x86 and x64 OS's to all of our machines using PXE.
I've created the x86 and x64 boot file, which works flawless along with the OS installation.

But the issue i'm encountering is when the architecture on a PC is x64.
It will only go directly to the x64 boot image and therefore only get the available x64 task sequences.

Is there a way to perhaps only use one boot image (i've tried removing the x64 and deploying the x86 TS's to the x64 computers but it does not work)
I've broken up the Unknown x64 and x86 computers into seperate collections.
Is there anyone who has solved this issue in a satisfying way? 

I understand the issue with only having the x86 PXE boot file, but I'm still unable to get a x64 architecture PC to boot from the file. It will only get stuck on the stage where it looks for the boot file from SCCM.

/Sebastian

EDIT:
The reason we are deploying x86 and x64 OS's is that we have locked down clients that use the Windows Embedded 7 OS (x86) for laptops and then the full Windows 7 Enterprise (x64) for our workstations.

Dear Expertz,

Recently, I started working on a windows 10 upgrade scenario using SCCM 2012 R2 where Vnext Windows10Upgrade1506.zip methods work as shown in technet article.

All seemed correct , I have a working SCM 2012 R2 server, I downloaded  Windows10Upgrade1506.zip, extracted, and put windows 10 source file into media folder,then I tried to import the zip file to the task sequence as shown in the blog, then I receive the following error

Does anyone has idea why it is coming??