I get that issue after deploying images on particular lenovo systems. I don't have the topic to link you to to explain what the switch does (and I don't remember), but for me the problem was solved by placing the /r switch at the end of the imaging command that comes up after saving the script.
That did not fix my problem. Thanks anyway.
As an Altitirs guy in a LanDesk shop, I understand. It would probably save you time and some frustration if you became familiar with MDT2012 and WAIK. You may prefer to use ImageX.exe (file based imaging, like RDeploy) as your Imaging tool, it doesn't use sector based images like (LanDesks) Imagew.exe. (FWIW - Sector Based images- this could be why your images are choking on bootup.) The disk functions executed by The LanDesk disk preparation tool is similar to the DISKPART.exe tool in MDT2012, it just works differently and its commands are awkward to follow.
1 of 1 people found this helpful
First, to be clear, diskpart.exe is standard Windows tooling, you can even open it on your Win7 device and get throught it's structure. It isnt hard to understand, if you look through the answer files LANDesk uses in the OSD process (the txt files after the /s of the diskpart command). ALternatively, use Provisioning and its Disk Actions. It does the same, but is GUI based to create the actions.
To get to the first questions:
1. It removes all volumes. Basically, a CD or SDcard can ahve a drive letter assigned that should be used for something different in OSD. This clears all driveletters, not partitions.
2. This will clean the disk. Basically it will remove all partitions from disk 0.
3. A image is deployed, but be careful! If it's a disk-image you should be fine. If you use a partition image, or a file based imaging tool like Imagex, you need to create the partitions first and (in case of Imagex, format them).
I dont know where the RMvollletter comes from at this point, but it shouldnt be necessary.
4.Assigning C: to the windows drive is only necessary if you have a Windows 7 installation with 2 partitions, 1 for boot, 1 for the OS. If you dont do anything at this point, C: is the boot, D: is the Windows drive. Nothing wrong with that, but can be confusing for some if you need to copy stuff now suddenly to D:\Windows (like the unattend.xml, drivers, etc.)
5. Yes, this fixes the MBR, and puts the active partitions straight.
Your best bet to troubleshoot is to remove the reboot at the end of the WinPE command sequence and get in there with Diskpart to see what the result is from the actions above. At this point, the boot partition should be active, the bootpartition without driveletter and the OS partition with driveletter C:
Your answer helped to figure out a few things.