Microsoft Deployment Toolkit give Wizard Error - A Connection to the deployment share could not be made
-
Monday, February 04, 2013 1:51 PM
Particulars MDT 2012 update 1 on 2008R2 server
I initially got it to work rather quickly using shares (deploymentshare$) on the C drive of my server. Great, but I wante to move the shares to my NetApp filer.
I tried repeatedly and I got the above error "A Connection to the deployment share could not be made "....even though the path was correct and the share and security perms were wide open (for testing).
In order to isolate I added a "D:\" drive to the MDT server and created a new deployment share on the D:\ drive respectively. I verified the UNC and local path and updated the deployment share.
Problem: When I booted from the newly updated "LiteTouchPE_x64.iso" it pointed to the old NAS path not the new path...not the new share path??? I updated the deployment share again (and verified the path was correct) and told it to completely regenerate the boot images and I even blew away the ISO files beforehand and it still gave me a A Connection to the deployment share could not be made because it was trying to point to the old NAS path.
I finally removed all of the shares and uninstalled MDT (and the Lenovo ThinInstaller...which shouldn't have factored into the problem) and deleted any reference to the MDT from the registry and file system. I then re-installed MDT, created new shares on the D:\ drive and it created new ISO files, but it still is pointing to the old NAS path. HOW CAN THIS BE?? Where is it getting this old path from?
David W King
All Replies
-
Monday, February 04, 2013 2:04 PMAlso....the Bootstrap.ini within D:\DeployementShare\Control has the correct path to the new share.
David W King
-
Monday, February 04, 2013 2:35 PM
Ok, so I click "Cancel" and it do a "net use \\server\deploymentshare$" and provide my credentials. I then do a "startnet" and I'm able to start the Lite Touch install.
BUT I STILL DON'T UNDERSTAND WHERE THE OLD NAS PATH IS COMING FROM.....I mean I completely un-installed and reinstalled MDT!!! Help...this is driving me nuts!
David W King
-
Monday, February 04, 2013 6:23 PM
Nobody has responded yet, but I wanted to save folks some time......on the 3rd PC this problem self corrected itself and connected to the new DeploymentShare$ without any help from me. I'm not sure why....very strange.
David W King
-
Monday, February 04, 2013 11:36 PMAfter you updated the bootstrap.ini, did you remember to update the deployment share to recreate the wim?
Blog: http://scriptimus.wordpress.com
-
Tuesday, February 05, 2013 12:50 PM
Actually the bootstrap.ini was correct after I reinstalled MDT and updated the deployment share....so no need to do it twice. Anyhow it's inexplicably working now...I wish I could explain why, but I'm going with it. Thanks.David W King
- Marked As Answer by Alex ZhaozxMicrosoft Contingent Staff, Moderator Wednesday, February 06, 2013 1:33 AM

