While this approach involves modifying your task sequences, it is MDT version agnostic and does not require reapplying your code modifications with each Microsoft Deployment Toolkit update. Finally - and this is the solution I opted for - you could use a PowerShell script to query hard drive configuration.You could modify the ZTIDiskPart script - which creates the disk partitions on the target computer by calling the Diskpart utility - as demonstrated by Keith Garner on multiple occasions by dynamically altering the OSDDiskIndex variable.Personally, I would not go down this path as it makes a few assumptions and things typically change down the road. Assuming that all HP ProDesk 600 MT G3 models come with the same fixed disk configuration, one could simply duplicate the " Format and Partition (UEFI)" disk step, change the disk index to 1 and test for " HP ProDesk 600 MT G3" in order to use the modified step just for this particular model.There are actually multiple ways to achieve this: My goal now was to identify a workaround which would allow the customer to dynamically determine if the internal SSD was enumerated as the first or second boot device and adjust disk number for the Format and Partition (UEFI) task sequence step accordingly.
This is the expected behavior as by default each task sequence assumes that the first enumerated fixed disk should be used during the Format and Partition Disk step. Running diskpart clean on the SSD in order to remove the factory image would only solve part of the problem: MDT (and Configuration Manager for that matter) would still pick the slower HDD for the OS installation. My assumption, therefore, was that the existing Windows 10 installation broke MDT function that creates a new boot entry for the new OS using BCDBoot.exe. However, when looking at the attached disks I noticed that there were two Windows installations: one on the HDD (performed by the Microsoft Deployment Toolkit) and one on the SSD (HP's Windows 10 factory image). I verified the issue, checked the log files, but could not find anything that would explain the problem right away. After applying the OS image, an attempt to create BCD entries will fail at the Verify BCDBootEx step with the following exit code: 15250.MDT picks the HDD as the first boot device and uses it during the "Format and Partition" step.The problem: the SSD is being identified as Disk 1, which leads to two issues: These computers (at least the top tier configuration with Intel Core i7 and 16 GB RAM) have a somewhat unique hard drives configuration: on the inside, there are actually two disks: an HDD and an SSD. The other day, as I was working with a customer on implementing a Windows 10, version 1803 based MDT task sequence, one of IT technicians mentioned that they had issues installing newly received HP ProDesk 600 MT G3 computers.
0 kommentar(er)
