Invalid Credential when imaging with WDS/MDT
This is really stumped me at the moment. I have 1 MDT server functioning as it should, deploying images etc.
A second MDT server on the same network but different site (geographically) has been built as per the above server.
When using a Client Desktop to PXE boot it seem the MDT server, finds the Boot Image, and then presents this:
-----------------------
A connection to the deployment share
(\\<MDTServer>.<OurDomain>
Connection OK. Possible cause: invalid credentials.
Retry: Try again to connect to the deployment share.
Cancel: Give up, cancelling any in-progress task sequence.
------------------------
I have Googled this and now of the second page of possible issues after trying the following so far:
(Initial second server setup, a Deployment Share Link was created and all deployment share data (images, files, drivers, etc) replicated)
Ensured that the Custom Settings File is exactly the same (copied over) as that found on the Primary MDT server (this server is working)
Double checked UserID/Admin credentials on both the Custom Settings and Boot Strap files to ensure they're correct
Updated the Deployment Share, on both servers
Removed the Boot Image from WDS, then imported the new boot image following saved changes from above Deployment Update
Ensured that both date & time on both the MDT server and target client were correct and the same
Cross-referenced ALL file & folder permissions to the Deployment Share ensuring that all permissions mirror exactly those on the Primary MDT server
I am fast running out of options so anything outside of the above would be great, Thanks
A second MDT server on the same network but different site (geographically) has been built as per the above server.
When using a Client Desktop to PXE boot it seem the MDT server, finds the Boot Image, and then presents this:
-----------------------
A connection to the deployment share
(\\<MDTServer>.<OurDomain>
Connection OK. Possible cause: invalid credentials.
Retry: Try again to connect to the deployment share.
Cancel: Give up, cancelling any in-progress task sequence.
------------------------
I have Googled this and now of the second page of possible issues after trying the following so far:
(Initial second server setup, a Deployment Share Link was created and all deployment share data (images, files, drivers, etc) replicated)
Ensured that the Custom Settings File is exactly the same (copied over) as that found on the Primary MDT server (this server is working)
Double checked UserID/Admin credentials on both the Custom Settings and Boot Strap files to ensure they're correct
Updated the Deployment Share, on both servers
Removed the Boot Image from WDS, then imported the new boot image following saved changes from above Deployment Update
Ensured that both date & time on both the MDT server and target client were correct and the same
Cross-referenced ALL file & folder permissions to the Deployment Share ensuring that all permissions mirror exactly those on the Primary MDT server
I am fast running out of options so anything outside of the above would be great, Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I made the changes outlined in the post and I have now got passed the Credentials Connection screen error and can now image the clients.
ASKER
I think we mean the same thing, the Bootstrap.ini file that can be edited on the MDT Deployment Share / Rules Tab.
I can confirm whilst logged onto the Secondary MDT server I can net use to the Deployment drive and DeploymentShare$ on that server
I'm going to double check the files that should be identical.