Microsoft MDT - Wrong server in boostrap.ini on clients

Question

Microsoft MDT server.
All of a sudden, some classes of laptops were failing with invalid task sequence when applying the OS image and Applications.
After various attempts, I figured I'd recreate the Deployment share, - closed old, build new one..
Now authentication fails because cannot connect to a server (which doesn't exist.)
I've right clicked on the deployment share properties and verified the path is correct and as well in the bootstrap.ini
For some reason the laptops are getting the wrong server's name.

In the attached, it's \ny-mdt-01\whatever, whereas in reality it's \ny-mdt\whatever.

How can i edit this? I must've spent 3 or 4 hours looking through each script and ini in the deployment folder and in registry for a clue and found nothing...

Any help would be appreciated, Not looking forward to a wipe and redo...

Answer 1

Hi @Brett Flagg,

Thanks for your feedback. We're glad that the question is fixed now. It's appreciated that you could click "Accept Answer" to the helpful reply, this will help other users to search for useful information more quickly. Here's a short summary for the problem.

Problem/Symptom:
MDT PXE boot to wrong deployment share path after recreating the Deployment share.

Solution/Workaround:
Add a DNS alias of NY-MDT-01 to the NY-MDT box.

Thanks again for your time! Have a nice day!

Best regards,
Cherry

Answer 2

Hi @Brett Flagg, 

1, Are there multiple MDT servers in your environment?

2, Please help confirm that the correct MDT boot image is mounted on the WDS server. The screenshot for your reference:

3, Have you configured the DHCP Server Option 066 and 067 or IP helper use for boots from the network? For DHCP Server Option, the screenshot for your reference:

4, Can client find the correct WDS server and boot.wim when the client boots from the network? (In my environment, 192.168.98.102 is the IP of the WDS server and WDS is installed on the same server as MDT) The screenshots for your reference:

Looking forward to your feedback.

Best regards,
Cherry