4

I recently ran into an issue where my Windows Deployment Services server stopped working after changing the name of the server. After looking around, I didn't really find a good answer for what settings need to be updated if you change the name of your WDS server.

Answering this below per the comment.

2
  • This is great, except that you shouldn't format it the way that you did. You should ask the question in the question field and then answer your own question. Then accept that answer when the system allows you to. If you just leave it as-is, it will constantly be bumped and will be marked as "unanswered", which is bad. – MDMarra May 3 '12 at 19:21
  • Plus, you get double rep this way :) – MDMarra May 3 '12 at 20:35
5

I found all the different places that it needs to be updated but wanted to document them here incase anybody else ever runs into a similar issue.

  • DeploymentWorkbench > Deployment Shares > Share Name > right-click > Properties > General > Network (UNC) path
  • DeploymentWorkbench > Deployment Shares > Share Name > right-click > Properties > Rules > Edit Bootstrap.ini > DeployRoot=\servername\directorylocation
  • \servername\deploymentshare$\control > Edit CustomSettings.ini > If the server name is included anywhere in this file, update it
  • \servername\deploymentshare$\control\deployment\ > Edit Unattend.xml > Do a find a for the old server name and replace with the new one

After this, update the package, redeploy a new image to it, and everything should be up and running!

2
  • You might have to change the "Monitoring host:" too in the deployment share properties. – js2010 Aug 14 '19 at 14:55
  • Also you need to replace the boot wim in WDS. – js2010 Aug 17 '19 at 14:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.