Troubleshooting: Moving a Deployment Share to a Remote Site

by Mitch Tulloch [Published on 8 March 2012 / Last Updated on 8 March 2012]

How can you make sure MDT 2010 deployments still work if you move your deployment share to another site?

Problem: You are using MDT 2010 installed in a virtual machine on Hyper-V to deploy Windows 7 to target machines at headquarters.  You've finished deployment there, and your next deployment job is at a branch office of the same company. So you export your MDT 2010 virtual machine to USB drive and take that drive to the remote site where you import it into a Hyper-V host at that location.  You spin up the VM and try deploying Windows from it but it doesn't work. What went wrong?

Solution: Assuming you haven’t defined any applications in your image that refer to UNC paths, the only thing you will need to change is the path in the Bootstrap.ini file so that target computers can locate and authenticate with MDT 2010.


The Author — Mitch Tulloch

Mitch Tulloch is a widely recognized expert on Windows administration, networking, and security. He has been repeatedly awarded Most Valuable Professional (MVP) status by Microsoft for his outstanding contributions in supporting users who deploy and use Microsoft platforms, products and solutions. Mitch has published over two hundred articles on different IT websites and magazines, and he has written or contributed to almost two dozen books and is lead author for the Windows 7 Resource Kit from Microsoft Press. For more information, see .

Latest Contributions

Featured Links