locked
"Unable to determine destination partition, disk or drive" when Media deployment is used RRS feed

  • Question

  • We are heavy users of MDT 2013's "media" deployments -- in fact, once we finish testing a new image build on our lab server, media is created and is the sole method we use to deploy new systems due to many limitations.

    We ran into the following issue lately when using USB sticks or hard drives for our deployment media. Deployment of an OS image fails at the "Inject Drivers" stage. The hard disk inside the computer is formatted properly, but the TS fails with the error "Unable to determine destination partition, disk or drive".

    I dug into the logs, and it appears that "Inject drivers" does a check for where the \Drivers folder should be placed. The problem is that most USB hard disks and many higher-end USB sticks show up as "hard drives" rather than "removable media" when plugged into the machine. Adding another physical disk that appears as a fixed disk with an NTFS partition apparently confuses MDT and you get this error message. I think any "ReadyBoost enabled" USB stick has to show up on the system as a fixed disk rather than removable, so if you use these you might have this problem.

    The only workaround is to explicitly specify the disk number and partition number to use when you invoke "Install Operating System." The drivers step must take this information when determining where to put the driver store.

    Is there any other explanation for why this would be happening? We're stuck with media deployment for the foreseeable future, and until Microsoft fixes the problem with handling of split WIM files, we have to use NTFS formatted disks/sticks...this might be making it harder for the MDT logic to determine where to put the OS.

    Monday, February 23, 2015 8:13 PM

All replies

  • MDT should be smart enough to know that it should Skip USB drives.

    However if you have a USB 3 Hard DIsk (not a USB Flash Disk), that might be the problem

    1. Try using only Flash Drives.

    2. Try plugging the USB Hard Drive into a USB 2.0 port

    3. Additionally try not to use USB Hard Drives that are *Larger* that the internal hard drive.

    If you still have problems, can you copy your Bdd.log file to a public site like OneDrive and share the link?


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Tuesday, February 24, 2015 7:23 AM