No response from windows deployment services server
Thanks for posting in Microsoft TechNet forums.
Based on the situation, please check if this thread share some insight.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked as answer by Magon Liu Moderator Wednesday, March 30, 2011 3:22 AM
All replies
Thanks for posting in Microsoft TechNet forums.
Based on the situation, please check if this thread share some insight.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked as answer by Magon Liu Moderator Wednesday, March 30, 2011 3:22 AM
Thanks for posting in Microsoft TechNet forums.
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
This might have been addressed already but here’s what I did to fix this issue.
1. Stop the Windows Deployment Services Server service.
2. Navigate to the Mgmt directory under RemoteInstall. In my case D:\RemoteInstall\Mgmt
3. Create a directory called backup and move the contents of the Mgmt directory into the backups folder.
4. Restart the Windows Deployment Services Server service. This will regenerate the files that were in the Mgmt directory.
5. Once the service is back up and running test and make sure you do not receive the error any more.
Hope this helps.
- Proposed as answer by YoungMellow Friday, November 16, 2012 5:30 PM
- Marked as answer by Carey Frisch MVP, Moderator Tuesday, August 6, 2013 9:07 PM
I am running into this same issue, and I have spent a few days now trying to figure it out. When trying to PXE boot from a client, I get the «No response from Windows Deployment Services server.» Many of my servers (including DCs) are still running Server 2003, and I have SCCM2012 installed on a dedicated VM server running Server 2008 SP2.
I have turned off every validation/security option I could find (respond to all computers in WDS, turned off all encryption, turned off certs, or CRL checks, use HTTPS or HTTP, etc in CfgMgr). I created a x86 (from Win7 x86 ISO) and x64 (from Svr 2008 R2 ISO) boot images, and one generic Win7 install image (from Win7 ISO). I added option 66 and 67 to the DHCP scope, and manually created option 60 (since my FDL is still 2003) on my DHCP server. SCCM and WDS are on the same server, DHCP on another (the DC). The servers are on the same subnet, and the client is on another (hence the DHCP scope options).
I would sure appreciate any updated advice.
THANK you, YoungMellow! I’ve been working on this all day, going down blind alleys in forums. Regenerating the contents of the Mgmt folder fixed it!
No response from windows deployment services server
Thanks for posting in Microsoft TechNet forums.
Based on the situation, please check if this thread share some insight.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked as answer by Magon Liu Moderator Wednesday, March 30, 2011 3:22 AM
All replies
Thanks for posting in Microsoft TechNet forums.
Based on the situation, please check if this thread share some insight.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked as answer by Magon Liu Moderator Wednesday, March 30, 2011 3:22 AM
Thanks for posting in Microsoft TechNet forums.
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
This might have been addressed already but here’s what I did to fix this issue.
1. Stop the Windows Deployment Services Server service.
2. Navigate to the Mgmt directory under RemoteInstall. In my case D:\RemoteInstall\Mgmt
3. Create a directory called backup and move the contents of the Mgmt directory into the backups folder.
4. Restart the Windows Deployment Services Server service. This will regenerate the files that were in the Mgmt directory.
5. Once the service is back up and running test and make sure you do not receive the error any more.
Hope this helps.
- Proposed as answer by YoungMellow Friday, November 16, 2012 5:30 PM
- Marked as answer by Carey Frisch MVP, Moderator Tuesday, August 6, 2013 9:07 PM
I am running into this same issue, and I have spent a few days now trying to figure it out. When trying to PXE boot from a client, I get the «No response from Windows Deployment Services server.» Many of my servers (including DCs) are still running Server 2003, and I have SCCM2012 installed on a dedicated VM server running Server 2008 SP2.
I have turned off every validation/security option I could find (respond to all computers in WDS, turned off all encryption, turned off certs, or CRL checks, use HTTPS or HTTP, etc in CfgMgr). I created a x86 (from Win7 x86 ISO) and x64 (from Svr 2008 R2 ISO) boot images, and one generic Win7 install image (from Win7 ISO). I added option 66 and 67 to the DHCP scope, and manually created option 60 (since my FDL is still 2003) on my DHCP server. SCCM and WDS are on the same server, DHCP on another (the DC). The servers are on the same subnet, and the client is on another (hence the DHCP scope options).
I would sure appreciate any updated advice.
THANK you, YoungMellow! I’ve been working on this all day, going down blind alleys in forums. Regenerating the contents of the Mgmt folder fixed it!
No response from windows deployment services server
Thanks for posting in Microsoft TechNet forums.
Based on the situation, please check if this thread share some insight.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked as answer by Magon Liu Moderator Wednesday, March 30, 2011 3:22 AM
All replies
Thanks for posting in Microsoft TechNet forums.
Based on the situation, please check if this thread share some insight.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
- Marked as answer by Magon Liu Moderator Wednesday, March 30, 2011 3:22 AM
Thanks for posting in Microsoft TechNet forums.
As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish.
BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts.
TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
This might have been addressed already but here’s what I did to fix this issue.
1. Stop the Windows Deployment Services Server service.
2. Navigate to the Mgmt directory under RemoteInstall. In my case D:\RemoteInstall\Mgmt
3. Create a directory called backup and move the contents of the Mgmt directory into the backups folder.
4. Restart the Windows Deployment Services Server service. This will regenerate the files that were in the Mgmt directory.
5. Once the service is back up and running test and make sure you do not receive the error any more.
Hope this helps.
- Proposed as answer by YoungMellow Friday, November 16, 2012 5:30 PM
- Marked as answer by Carey Frisch MVP, Moderator Tuesday, August 6, 2013 9:07 PM
I am running into this same issue, and I have spent a few days now trying to figure it out. When trying to PXE boot from a client, I get the «No response from Windows Deployment Services server.» Many of my servers (including DCs) are still running Server 2003, and I have SCCM2012 installed on a dedicated VM server running Server 2008 SP2.
I have turned off every validation/security option I could find (respond to all computers in WDS, turned off all encryption, turned off certs, or CRL checks, use HTTPS or HTTP, etc in CfgMgr). I created a x86 (from Win7 x86 ISO) and x64 (from Svr 2008 R2 ISO) boot images, and one generic Win7 install image (from Win7 ISO). I added option 66 and 67 to the DHCP scope, and manually created option 60 (since my FDL is still 2003) on my DHCP server. SCCM and WDS are on the same server, DHCP on another (the DC). The servers are on the same subnet, and the client is on another (hence the DHCP scope options).
I would sure appreciate any updated advice.
THANK you, YoungMellow! I’ve been working on this all day, going down blind alleys in forums. Regenerating the contents of the Mgmt folder fixed it!
