thanks for the replies, guys. tripedacus: Mapping a network drive is not a good solution for me, because I would have to have a vbscript to map / unmap the network drives anyways. Remember, the MDT won't pass UNC thru CMD, so I couldn't just add like a 'net use' to my batch file. Also, my deployment task sequence contains many reboots, and the mapped drives won't reconnect after reboot, and that is another issue entirely I think. cluberti: I have to look into this application bundle, the solution sounds like it will work - but doesn't sound very modular. I need to repeat this with possibly many other installs, and keeping track of all the dependencies would get messy. The goal is to get rid of all of the .bat files and .vbs scripts that I have to keep track of and condense them into one script. Also, I have other commands and administrative tasks I would like to add to some of my program installs, so I'm still on the look out for a working .vbs.