Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Tuesday, June 28, 2016 6:00 PM
Hello. So I will start out with saying that I have been able to successfully image a computer with this task sequence when the computer is in legacy BIOS, but when I change it to UEFI w/ secure boot enabled (or even with it disabled so far) it does not work. It boots into PXE fine, then our Task Sequence Wizard starts, allows me to go through all of our UDI wizard options until it begins. Then it starts the TS where it formats and partitions the disk. It displays no errors and simply reboots within about 2 minutes of starting the process.
When I look at the smsts.log file I see:
Failed to read filesystem from OSDPartitions2FileSystem, not formatting OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Which is preceeded by:
Reading partition size info for partition 1 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Remaining size before partition: 127720135680 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
size units: SIZE_MB OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Set partition size: 536870912 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Remaining size after partition 1: 127183264768 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Reading partition size info for partition 2 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Remaining size before partition: 127183264768 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
size units: SIZE_MB OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Set partition size: 134217728 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Remaining size after partition 2: 127049047040 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
and suceeded by:
Reading partition size info for partition 3 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Remaining size before partition: 127049047040 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
size units: SIZE_PERCENT OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
100% size specified. OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Remaining size after partition 3: 0 OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Checking volume 'C:' for BitLocker OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Volume 'C:' is on disk '0l' OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Volume 'C:' is fully decrypted OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Checking volume 'X:' for BitLocker OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
diskpart: list volume
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Found an EFI partition to configure. OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
S partition is not used, will use it. OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
diskpart: list volume
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
diskpart: list volume
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
create partition MSR size=128
OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
diskpart: list volume
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
create partition MSR size=128
create partition PRIMARY
assign
OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Diskpart: list volume
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
create partition MSR size=128
create partition PRIMARY
assign
rescan
list volume
OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Executing diskpart script: list volume
select disk 0
clean
convert gpt
create partition PRIMARY size=300
format quick fs=ntfs label="Windows RE Tools"
attributes volume set nodefaultdriveletter noerr
create partition EFI size=512
assign letter=S
format fs=fat32 quick
create partition MSR size=128
create partition PRIMARY
assign
rescan
list volume
OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Command line for extension .exe is "%1" %* OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Set command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\DiskPartScript.txt" OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Executing command line: "X:\WINDOWS\system32\diskpart.exe" /s "X:\WINDOWS\TEMP\DiskPartScript.txt" OSDDiskPart 6/23/2016 10:05:30 AM 1136 (0x0470)
Process completed with exit code 0 OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Formatting partitions OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Partition: 1 PRIMARY OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Partition: 2 EFI OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Found EFI partition: 2 OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
EFI file system: FAT32 OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Partition: 3 MSR OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Found MSR partition: 3 OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Partition: 4 PRIMARY OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Adding logical drive: C: OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Adding logical drive: S: OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Skipping non-local logical drive: X: OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Formatting drive C: with NTFS filesystem, method quick OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Creating instance of service loader OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Loading service OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Waiting for service to initialize OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for software providers OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Found a VDS software provider OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for IVdsSwProvider OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for packs OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Found a VDS pack OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for IVdsPack OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for volumes OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Found a VDS software provider OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for IVdsSwProvider OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for packs OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Found a VDS pack OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for IVdsPack OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for volumes OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Found a VDS volume OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for IVdsVolumeMF OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for access paths OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Found a VDS volume OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for IVdsVolumeMF OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for access paths OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Found a volume with access path 'C:\ OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for IVdsVolume OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Querying for IVdsVolumeMF OSDDiskPart 6/23/2016 10:05:33 AM 1136 (0x0470)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 6/23/2016 10:05:33 AM 976 (0x03D0)
The command completed successfully. TSBootShell 6/23/2016 10:05:33 AM 976 (0x03D0)
Successfully launched command shell. TSBootShell 6/23/2016 10:05:33 AM 976 (0x03D0)
OSDDiskPart.exe completed successfully OSDDiskPart 6/23/2016 10:05:39 AM 1136 (0x0470)
Process completed with exit code 0 TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
!! TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Successfully completed the action (Format and Partition Disk (UEFI)) with the exit win32 code 0 TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
MP server http://USTLVUOI519.O-I.INTRATEST. Ports 80,443. CRL=false. TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Setting authenticator TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Set authenticator in transport TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Sending StatusMessage TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Setting message signatures. TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Setting the authenticator. TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
CLibSMSMessageWinHttpTransport::Send: URL: USTLVUOI519.O-I.INTRATEST:80 CCM_POST /ccm_system/request TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Request was successful. TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 6/23/2016 10:05:39 AM 1456 (0x05B0)
Then the log just abruptly ends, without an error. I am assuming that is when it reboots and then goes through it's normal boot cycle and when it gets to the HDD it states that an OS could not be found.
Little bit more information: We use SCCM 2012 R2 SP1 version 5.0.8239.1203 (with Windows 10 ADK installed) with MDT 2013 Update 2 I believe. And not that it matters too much to this process but in our test environment (where I am attempting this image) we also have Adaptiva version 5.5.659.3 which is an alternate content provider for SCCM instead of using a distribution point at each site we have what is called Adaptiva OneSite which allows us to have 1 DP in our global organization.
Let me know if more information is needed, any little bit helps. Thanks.
All replies (6)
Wednesday, June 29, 2016 12:24 PM âś…Answered
Windows 10 ADK with x64 boot wim.
But....I fixed the problem. Apparently something that was broken in 2013 was never fixed, because I tried what was suggested at the below link and was able to image both the E5450 and the Dell 7202 tablet with UEFI enabled instead of Legacy.
https://www.ronnipedersen.com/2013/04/fix-deploy-windows-to-uefi-devices-using-mdt-sccm/
Tuesday, June 28, 2016 6:27 PM
What version is your boot image?
Which ADK version are you using?
What do the status message for the TS deployment have to say?
Jason | http://blog.configmgrftw.com | @jasonsandys
Tuesday, June 28, 2016 6:56 PM
What I don't understand is this:
Parsing step node: User Cancelled Wizard TSManager 6/28/2016 1:01:07 PM 1512 (0x05E8)
Description: Step used to make the task sequence fail. TSManager 6/28/2016 1:01:07 PM 1512 (0x05E8)
I in no way cancelled the task sequence, I enabled command prompt with F8 and then finished out our UDI Wizard prompts when it begins the task sequence.
I see "Cancelled Wizard Group" pop up right before the task sequence fails. I just tried imaging a UEFI build computer with legacy option ROM on with a Dell E5450 and a Dell 7202 rugged tablet, and both failed with that flashing right before the restart. I have command prompt enabled, so I am capturing these logs right as it tries to reboot.
Latest SMSTS.log file from my E5450 in test (filtered to show just the failures)
Description: Step used to make the task sequence fail. TSManager 6/28/2016 1:01:07 PM 1512 (0x05E8)
Parsing group node: Gather Logs and StateStore on Failure TSManager 6/28/2016 1:01:07 PM 1512 (0x05E8)
Parsing step node: Emaill Failure of Build TSManager 6/28/2016 1:01:07 PM 1512 (0x05E8)
Failed to run the action: Confirmation to Partition Disk.
Incorrect function. (Error: 00000001; Source: Windows) TSManager 6/28/2016 1:01:09 PM 1512 (0x05E8)
The execution engine ignored the failure of the action (Confirmation to Partition Disk) and continues execution TSManager 6/28/2016 1:01:09 PM 1512 (0x05E8)
Failed to read filesystem from OSDPartitions2FileSystem, not formatting OSDDiskPart 6/28/2016 1:01:27 PM 2008 (0x07D8)
Failed to read filesystem from OSDPartitions2FileSystem, not formatting OSDDiskPart 6/28/2016 1:02:07 PM 1660 (0x067C)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 6/28/2016 1:02:58 PM 2244 (0x08C4)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 6/28/2016 1:03:41 PM 2604 (0x0A2C)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 6/28/2016 1:03:47 PM 3040 (0x0BE0)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 6/28/2016 1:03:49 PM 1596 (0x063C)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log. InstallSoftware 6/28/2016 1:03:50 PM 1104 (0x0450)
Failed to read filesystem from OSDPartitions2FileSystem, not formatting OSDDiskPart 6/28/2016 1:05:06 PM 712 (0x02C8)
Tuesday, June 28, 2016 7:05 PM
"Parsing step node: User Cancelled Wizard"
That means exactly what it says: It (the task sequence engine) is parsing (aka examining) the instructions for the task (aka node) titled "User Cancelled Wizard". The TS engine does this for every task in the task sequence, that's how it knows what to do. This line is not about it executing the task and thus the "Parsing step node" prefix.
What about my questions?
Jason | http://blog.configmgrftw.com | @jasonsandys
Thursday, July 14, 2016 6:43 PM
Great...Now that I'm trying to do this in production (the same way as in test), it's no longer working. Failing out right after I select the task sequence. The logs are less than helpful and only mention:
Failed to run the action: Confirmation to Partition Disk.
Incorrect function. (Error: 00000001; Source: Windows) TSManager 7/14/2016 2:15:12 PM 652 (0x028C)
It seems to be pointing to a problem with this test in my task sequence:
Confirmation to Partition Disk (where a "Run Command Line" is initiated before formatting and partitioning the disk)
cscript.exe X:\deploy\scripts\zticonfirmdiskpart.vbs
This script works fine for Windows 7 with legacy boot, and it worked in our test environment with Windows 10 with UEFI. So I am at a loss to why it isn't working now in our production environment. We are using SCCM 2012 R2 SP1 and MDT 2013 update 2.
Is it possible that I need to disable 64-bit file redirection? We have recently switched to a 64-bit boot wim when we switched to UEFI and Win10.
Friday, February 3, 2017 11:28 AM
In my testing it seems that MDT created sequence has "Set OSDDiskPart=TRUE" step
For UEFI boot (on physical Latitude) TS generates error
Failed to read filesystem from OSDPartitions2FileSystem, not formatting
and TS errors out (and dies)
The "supposed" fix was
https://www.ronnipedersen.com/2013/04/fix-deploy-windows-to-uefi-devices-using-mdt-sccm/
which is NOT the case as "Format and Partition Disk (UEFI)" sequence ALREADY sets variable OSDisk
So for me the UEFI TS to work was to disable the sequence : Set OSDDiskPart
Strangely the above was NOT needed when running the same TS on Hyper-V Gen2 VM
Seb