locked
MDT 8456 + ADK 1809 - ztidiskpart.vbs is assigning the incorrect drive letter. It's assigning the OSDisk as D: rather than C: RRS feed

  • Question

  • Update:  I was able to resolve this by not using my reference image and by creating a new task sequence.  I believe I had a combination of my reference image being bad and the unattend file being bad as well.  As soon as I used a plain Win10 image and in a brand new task sequence, it worked great for my needs.

    The issue this is creating is that when the machine starts up for the first time, it's expecting to find the ltibootstrap.vbs in D:\, however, when Win10 starts up, the drive letter is reassigned to C:\, so the task sequence doesn't resume automatically and it loses some of the information it gathered earlier in the TS.   Could I get some guidance on how to fix this or bypass it?  Thanks so much in advance!

    • Edited by GreyFoxNK Tuesday, August 13, 2019 2:06 PM
    Thursday, August 8, 2019 4:41 PM

All replies

  • The drive letter sounds normal to me...

    Before the system boots up for the first time the drive letters can vary depending on if you have a flash drive plugged in, if there's an optical drive, partition scheme due to encryption, etc. You should see diskpart information and then something that says:

    Found: DestinationOSVariable: D:	ZTIDiskpart	8/8/2019 1:05:55 PM	0 (0x0000)
    

    Did you hard code something or modify the template, maybe remove gather local only? MDT is designed to deal with this and during StateRestore scan the drives again

    Microsoft Deployment Toolkit version: 6.3.8456.1000	LiteTouch	8/8/2019 1:14:05 PM	0 (0x0000)
    ZTIUtility!GetAllFixedDrives (False)	LiteTouch	8/8/2019 1:14:05 PM	0 (0x0000)
    New ZTIDisk : \\COMPUTER\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"	LiteTouch	8/8/2019 1:14:05 PM	0 (0x0000)
    New ZTIDiskPartition : \\COMPUTER\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"    \\COMPUTER\root\cimv2:Win32_LogicalDisk.DeviceID="C:"	LiteTouch	8/8/2019 1:14:05 PM	0 (0x0000)
    New ZTIDisk : \\COMPUTER\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"	LiteTouch	8/8/2019 1:14:05 PM	0 (0x0000)
    New ZTIDisk : \\COMPUTER\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"	LiteTouch	8/8/2019 1:14:05 PM	0 (0x0000)
    ZTIUtility!GetAllFixedDrives =   C: 	LiteTouch	8/8/2019 1:14:05 PM	0 (0x0000)
    Found existing task sequence state information in C:\_SMSTaskSequence, will continue	LiteTouch	8/8/2019 1:14:05 PM	0 (0x0000)
    


    Daniel Vega

    Friday, August 9, 2019 1:40 PM
  • As far as I can tell, I didn't make any changes related to that.  However, I was able to get it to assign itself C: by disabling the two default format and partition tasks and then creating my own task to do it.  However, the ltibootstrap.vbs still isn't loading after the first restart.  I'm looking at my unattend.xml now, which was also unmodified.
    Friday, August 9, 2019 4:04 PM