Windows Deployment Services won't start after server name/IP change

Question

I'll start by saying I know little to nothing about MDT.

I had to rename a server in a remote office and change its IP as well. After doing so, Windows Deployment Services will not start the service. Note that nothing has changed on the server other than its name and IP--the deployment share folder is still there, still shared, etc.

• When trying to start the server in the WDS management console I get "The service did not respond to the start or control request in a timely fashion.
• Event 7024 is logged in the System Event Viewer, indicating that the Windows Deployment Server service terminated with the following service-specific error: %%4294966768
• Running sc start wdsserver I get the following error:

H:>sc start wdsserver

SERVICE_NAME: wdsserver

    TYPE               : 30  WIN32

    STATE              : 2  START_PENDING

                            (NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)

    WIN32_EXIT_CODE    : 0  (0x0)

    SERVICE_EXIT_CODE  : 0  (0x0)

    CHECKPOINT         : 0x0

    WAIT_HINT          : 0x7d0

    PID                : 6792

    FLAGS              :

• I found a post indicating that possibly updating the deployment share would fix it, so I went into DeploymentWorkbench -> Deployment Shares, right-clicked on my share and selected Update Deployment Share. I've tried both Optimizing the boot image updating process and completely regenerating the boot images, but either way the process fails:

=== Processing LiteTouchPE (x64) boot image ===

Building requested boot image profile.

System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the path specified

   --- End of inner exception stack trace ---

   at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)

   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)

   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()

   at System.Management.Automation.CommandProcessor.ProcessRecord()

   --- End of inner exception stack trace ---

   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)

   at Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()

   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

I'm not sure what to look at here. I'd like to see if it's something I can resolve before having to tell someone else that I made more work for them, heh.

Answer 1

Hi Joe,

A couple of config files still might refer to the old name, check the following locations:

DeploymentWorkbench -> Deployment Shares -> right-click your share -> Properties -> Rules -> Edit Bootstrap.ini replace the DeployRoot=\NewServerName\directorylocation

\NewServerName\deploymentshare$\Dontrol\CustomSettings.ini - replace any references to teh old servername to the new one in this file

\NewServerName\Deploymentshare$\Control\Deployment\Unattend.xml - search & replace the old servername with the new one here too

Hope this helps,

Answer 2

Well, it would seem that it just needed time. I logged in to start looking at the posted suggestions, and when going to check the service I saw it was now running. I opened up the WDS console and the server shows it's online now. :/

Answer 3

Hi,

Thanks very much for your feedback and sharing. We're glad that the issue is gone 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:

Windows Deployment Services won't start after server name/IP change of MDT server with below error:

"The service did not respond to the start or control request in a timely fashion."

Solution/Workaround:

Update the deployment share and wait some time.

Thanks again for your time. Have a nice day!

Best regards,

Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.