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.

We may also need to go to \servername\deploymentshare$\control\<Task sequence>\ > Edit Unattend.xml > Do a find a for the old path and replace with the new one.

Answer 2

Folder Path replaced or repaired. Boot images re-re-re built I can see the new unit in monitor tab, but the new boot images don't seem to be running once I PXE boot the new computer I want to image. I was noticing the file path it is looking for to run the litetouch x64 wim file and I did not recognize a folder in the middle. it's going to boot\x64\images\litetouchPEx64 but there was no images folder inside of the x64 folder. I don't believe there ever was before. I am adding one and copying the litetouchPEx64 wim into it to try again. (why not? stranger things have happened!) This is all in my DeploymentShare path but that isn't listed in the path, just \server\boot\x64\ etc.....

I am able to path to the file from the off domain unit and sysprep that unit now without the invalid credentials error. I am believing the issue was the UNC path was not including the $ at the end to represent hiding the file on the windows network. ( at least that's what the Install article stated, I always thought $ signified root access folder)

Answer 3

Ok I am able to get the deployment to run finally by creating a boot\x64\images\lightTouchPEx64.wim on the C: of the server. Even thought the DeploymentShare$ is on O: of the server. It's a VM and so they created a secondary drive to house all of the MDT Deployment items. This has been way more fun than expected, NOT!. Currently it has not failed, however I did try to run the LiteTouchPEx64.iso from a new VM on my desktop and it failed with the invalid credentials error, so not sure if it's completely repaired or not. As I am writing this, the image has completed deployment to the new laptop. I will attempt to complete the set up of this device and capture an image for use on other devices. That will be the next test.
Where I believe my error started was, when I was updating the MDT and ADK programs on the server to account for the newest version of Windows, these require uninstall/reinstall, rather than upgrade. My settings where lost or slightly off because of this. I was able to save my old DelpoymentShare folder and then "trick" the new system into using it by creating a new deployment share in the same location, (after renaming the old one) then renaming the new one and changing the name of the old one back to the original form, (Eventually deleting the new one) thus tricking the system into thinking the existing folder was the newly created folder. While I'm sure there is a better way to do this, I really don't have the time to devote to weeks of research into how to "start over" and just had to improvise. Since most likely no one else will make the bone-headed moves I did trying to update their system, but just in case. This worked for me. My deployment share has all the drivers and several versions of Windows needed for our environment.
If you have any better solutions, I'd love to hear them as I am going to have to stay with MDT as long as I'm at this location.