Hi folks,
I'm dabbling with image deployment, as part of building several images for different types of PCs.
I started with the base installer for Windows 10 1607, and used Create Task Sequence > Install an existing image package. This was configured with the relevant settings for our environment e.g. join to a domain.
I then setup a Gen 1 Hyper-V VM, installed Win 10 1607 to it, applied Windows updates, and used Capture Media to create a WIM.
Again I used Create Task Sequence > Install an existing image package. The task sequence did not work, and failed with a 0x80004005 error when applied to a PC. It did get as far as applying the image, so the test machine was able to boot, and I was able
to recover the SMSTS.log. The problem seemed to relate to partioning, as I got the following:
Executing command line: OSDApplyOS.exe /data:S0100028,%OSDDataImageIndex%
TSManager
20/04/2017 08:29:24
1468 (0x05BC)
Command line for extension .exe is "%1" %*
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
Set command line: "OSDApplyOS.exe" /data:S0100028,1
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
Searching for next available volume:
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
Volume C:\ has already used.
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
Volume D:\ has already used.
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
Volume F:\ is not a local hard drive.
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
Volume X:\ is not a local hard drive.
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
it != volumes.end(), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installcommon.cpp,519)
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
There are no more volumes available for use.
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
GetNextAvailableVolume(allowFAT, volume), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installcommon.cpp,651)
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
The requested target could not be resolved to a valid volume on this computer. Check your task sequence to ensure this drive is correct and that it is being created
The parameter is incorrect. (Error: 80070057; Source: Windows)
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
ResolveTarget( g_Target, g_InstallType == InstallType_DataImage, targetVolume ), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,483)
ApplyOperatingSystem
20/04/2017 08:29:24
1180 (0x049C)
Process completed with exit code 2147500037
TSManager
20/04/2017 08:29:24
1468 (0x05BC)
!--------------------------------------------------------------------------------------------!
TSManager
20/04/2017 08:29:24
1468 (0x05BC)
Failed to run the action: Apply Data Image 1.
Unspecified error (Error: 80004005; Source: Windows)
TSManager
20/04/2017 08:29:24
1468 (0x05BC)
When I looked at the partioning sequences they differed in the first and second task sequence. I'm not sure why the task sequence creator has created two differing sequences. In the first sequence it first uses BIOS, then UEFI. I copied this into my task
sequence and it failed, because it tried to use BIOS, which worked, then UEFI failed. So instead I have created one task sequence for BIOS, and a second task sequence for UEFI. So far, applying the BIOS task sequence on one of the test PCs is working, presumably
because it doesn't have UEFI, or it's not enabled.
The two questions I have are:
1. Why did the task sequence creator build two different partioning sequences, does it try to guess based on the WIM?
2. Why when I used the same approach of a step for BIOS and then UEFI did it fail in my task sequence, yet it works in the original task sequence based on the vanilla WIM?
Thanks
