No response from Windows Deployment Services server

Last week has been pretty much busy in fixing the distribution point issues. Most of the time was spent on troubleshooting the client agent installs on distribution points. I always record the issues and solutions and publish it. So this will also help others who come across same issues. For the organization that I work for, there are many distribution points at various locations. One of the issues that I came across was related to windows deployment services. The error was no response from windows deployment services server. Looking at the errors, one would probably check the WDS service. Seems like the issue required more troubleshooting.

Post configuring the distribution point, the PXE client showed a BCD error 0xc000000f. While the solution for this error has been already documented, however there was something more to be done. Let’s take a look at the issue and steps to resolve this.

Issue – After setting up the DP correctly, the PXE client showed the following details.

Downloaded WDSNBP from

WDSNBP started using DHCP Referral.
Contacting Server: (Gateway:
No response from Windows Deployment Services server.
Press F12 for network service boot

No response from Windows Deployment Services server

Pressing F12 key shows the below message.

The boot configuration data for your PC is missing or contains errors.
File: \boot\bcd
Error code:0xc000000f

No response from Windows Deployment Services server

No response from Windows Deployment Services server

If you are seeing no response from windows deployment services server, you could try the below steps to fix this issue. If there is something else that worked for you, please post it in comments section.

  • Login to the distribution point server. Open the services console and stop the “Windows Deployment Services Server” service.
  • On the SCCM content drive, navigate to the Mgmt folder under RemoteInstall.
  • Create a new folder, name it as backup (or any other name). Move the contents of the Mgmt directory to the backup folder.
  • Now restart the Windows Deployment Services Server service. This will recreate the files that were in the Mgmt directory.
  • PXE boot the client and you shouldn’t see the no response from windows deployment services server error.

12 thoughts on “No response from Windows Deployment Services server”

  1. I discovered my self signed certificate was set to expire last month on the distribution point.
    I went into properties on the DP under the general tab and adjusted the date. Works now.

  2. Hello Prajwal Desai
    Hope you could help,
    I currently having issue as exactly same message error from your post: No Response from Windows Deployment Services server. Launching………
    I have already followed and tried as your advised instruction above BUT still did not solved the problem.
    Do you have any more suggestion?
    Thank You

  3. Hi , i have same issue and i tried many ways … still not working …. i change DP , Try to disable /Enable Pxe boot on DP ,
    Change Windows Image , Try to Distribute both x86 /x64 boot file , Update SCCM to 1710 , i try to boot winodws 7 ,8.1 ,10 but all of them fail … i cant capture or install …. i changed DHCP bootfilename to \smsboot\x86\

    what you suggest ?

  4. I have been trying to resolve this exact issue for a couple of days and have finally discovered the reason – my SCCM server and Distribution Point (on the same server) is hosted in Microsoft Azure….. and I have finally realised that WDS is not currently supported in Azure!

    It’s been driving me mad trying to troubleshoot this but at least now I know the reason which PXE boot is failing for me. On the plus side, I feel like I have learnt a lot about SCCM whilst digging in to the log files etc.

    It suppose it makes sense given the nature and volume of the data transfers.

  5. Hi Prajwal:

    I have the same problem. After I installed WDS, I Install WDS automatically by enabling PXE and multicast, but there is a error when finish installed .When I tried to provide C:\Windows\system32\wdsmdmgr.dll an intialization the provider WDSMDMGR , it come to an error. The Windows deployment service server will be closed. Error information : 0x3.

  6. We had a similar issue, what we had was multiple Boot Images deployed from the PXE-enabled point.
    once we unticked this option and only I had one boot imaged deployed it seemed to come work again

    Hope this helps

Comments are closed.