MDT Move to new building caused error says "Connection OK. Possible cause: invalid credentials.

Question

We used to deploy Windows 10 image by connecting a PC onto a direct network connection using a bootable USB. Once image is deployed we used to join to the domain. We recently moved MDT server to a different building. The MDT physical server is next to us and we are trying to use it locally. We change its name with the new IP it and did a minor configuration on it's bootstrap ini file with its new user name and password then server update is done. Then created a new bootable USB but we still got the error as "invalid Credentials" and rebuilding PC cannot connect to the Task Sequence. We may have missed something here. What else do we need to configure to the MDT Deployment Share to make it fully functional again as before. Need some details on when physically moved from a domain account to a local account. As we are new to it some detail is expected. And we are also thinking of using the same server for PXE boot in future, some insight on PXE boot from the same physical server would also be great. Thanks in advance

Answer 1

Hi, @Sushil Gautam Thank you for posting in Microsoft Q&A forum. After you update the credentials under the BootStrap.ini file, did you update deployment share again to generate the new boot image?

---

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 "Add comment".

Answer 2

Thanks for your reply. Actually we have brought it back, rebuild few Win 10 machines and manually installed Firefox and missing device drivers. However, now we have two issues first one the error says - Invalid driver path & the second one Firefox command line "Firefax Quantum Installer.exe" -ms won't install Firefox. Even I change new Firefox msi or exe installer and update task sequence it won't install it. Rest of the applications installs normally including Chrome. It would be great if you have any thoughts on these two issues.

Answer 3

Hi there,

Not sure if my previous question is posted , re typing here

Got a new issue as below-

Newly created bootable USB stick only works for recently added device model but not the device model I have added yesterday. However, I have a bootable USB from yesterday works fine but only with the models I had added yesterday. On the client machine the error message is BSOD. Any advice ?

I have added driver packs on MDT from the following source

http://ftp.hp.com/pub/caps-softpaq/cmit/HP_Driverpack_Matrix_x64.html