MDT Error - "A connection to the deployment share could not be made. Connection ok. Possible cause: invalid credentials"

Question

Having this issue with Version 6.3.8456.1000. Have tried the fixes listed and still having the same error. Are there any other items I need to look at? Trying to capture build of Windows 10 version 21H2. Can deploy but cannot capture. File work when capture unit is on domain. but fails because it's on domain. Off domain I get the possible invalid credentials error.

Answer 1

Hi, @Anonymous

Thank you for posting in Microsoft Q&A forum.

What's the fixes have we tried? You may forget to list them.
Have we tried to access the deployment share with IP address instead of server name? After the replacement, remember to update the path everywhere it's used (bootstrap.ini, customsettings.ini) and regenerate new boot images.

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

I have always used the IP rather than server name. I made a few changes that caused the UNC path to change slightly and I adjusted it in most locations.
The only thing I had not done was change the UNC path in the Bootstrap.ini file. I am going to try that and regenerate new boot images and try again.
Still expecting failure, but we'll see.

Answer 3

I found another issue that may correct this. I notice that even though I update the bootstrap.ini file, the rules displayed still show the old deployment share. I went in and change it directly on rules and will re-try. I found this going through the log file after making the previous change.
Fingers crossed.

Answer 4

What I'm finding is that the UNC path to the deployment share has changed but there are still pointers to the old path even though I have regenerated the boot images over and over and changed all of the boot.ini and rules that I can find to reflect the new path. The unit is set with a 2nd drive as the holder for the deployment share, ( not C:) so the deployment share now has to contain \o\ in it ( the deployment is on O: ) it had been this way before, but when I updated MDT and the ADK files for the newest Windows, something changed and I now have to add the \o\ to path to the deployment share.

Answer 5

Ok Right now it looks to be trying to go to \server\deploymentShare$ but the folder is listed as \server\deploymentShare not the root folder. Is there a setting I missed? That seems to be the only thing left that is missing. When I try to path to it with the root sign on properties it tells me there is an error in the UNC path.

This all started when I had to re-install the programs for the newest updates of Windows. Most of my hair is now gone! LOL