Hi Luke, I don't have answers to your questions, but I do have the same issues. I am using MDT to deploy a server image from USB, after the image is done, the only drive that was correct was the OS on C:, the other drives were assigned like this: D: -> USB, E: -> DataDisk, F: -> DVD ; I could not get my scripts to work consistently during the TS, I had to let the image get installed, and after it was done, then I could run my scripts without issues, I ended up with 3 batch files, running them in this order: Set USB to R, Set DataDisk to D, and Set DVD to E. I did find one PosH script, but I can crank out batch code much quicker than PoSH code, so that is why I used batch files. The first link below is the one I am using, the 2nd one works also.
MDT 2013 - USB Boot and drive letter management http://blog.apps.id.au/?p=711 Script to Change the Drive Letter of all CDROM and DVD Drives http://www.jhouseconsulting.com/2015/01/04/script-to-change-the-drive-letter -of-all-cdrom-and-dvd-drives-1537 From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, May 14, 2015 1:24 PM To: [email protected] Subject: [mssms] CM12 OSD Deployment - Drive Letter Assignment Hello For those responsible for OSD, how are you going about assigning Drive letters in the Task Sequence? My scenario is that in my Deployment Task Sequence, I'm deploying my .wim that was generated from a Build & Capture MDT TS (which only had 1 disk) and I want specific volumes to have specific drive letters. My destination systems have 2 separate disks, as well as a DVD-ROM & USB drive. I'm using a TS Variable to assign C: to my OS disk successfully, but I'm having issues assigning specific Drive letters to the secondary disk & DVD-ROM. The closest I've come is by creating a Powershell script that parses diskpart output and assigns letter based on DriveType(ex: CD-ROM), & also assigns a drive letter based on Label(assigned during the Format & partition TS step). That works fine while in the OS, but the script doesn't behave the same while executed in the Task Sequence build process. When I deploy the same package/script to an OS in use (even via Task Sequence), it works as intended. In summary, 2 issues here: 1. How do you recommend assigning specific drive letters to specific volumes while in the Task Sequence? 2. Can you explain why a powershell diskpart script might operate differently in TS during build vs. while in the OS? Thanks for your time. Luke The preceding email message may be confidential or protected by the attorney-client privilege. It is not intended for transmission to, or receipt by, any unauthorized persons. If you have received this message in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the message. Legal advice contained in the preceding message is solely for the benefit of the Foley & Lardner LLP client(s) represented by the Firm in the particular matter that is the subject of this message, and may not be relied upon by any other party.
