Close Menu
    Facebook X (Twitter) Instagram
    Tuesday, May 20
    X (Twitter) LinkedIn
    All about Endpoint Management
    • Home
    All about Endpoint Management
    Home»OS Deployment»Configuration Manager 2007 PXE Service Point causes the Windows Deployment Services Server service to crash and hang

    Configuration Manager 2007 PXE Service Point causes the Windows Deployment Services Server service to crash and hang

    Eswar KonetiBy Eswar KonetiMarch 01, 5:58 pm2 Mins Read OS Deployment 449 Views
    Share
    Facebook Twitter LinkedIn Reddit

    Frequently we see some issues with sccm clients when PXE boot for OS deployment with some locations(WDS servers) because of IP helpers and to identify the issue is caused because of this,it took some days because we have to check from server side if there are any issues running around.

    When attempting PXE boots via a System Center Configuration Manager 2007 PXE Service Point, PXE boots will initially work and succeed but then all of a sudden stop working.  Examining the server where the PXE Service Point and Windows Deployment Services (WDS) are installed reveals that the Windows Deployment Services Server service has crashed and is in a hung state. Attempting to restart the Windows Deployment Services Server service on the WDS server does not resolve the issue. Restarting both the Windows Management Instrumentation and the Windows Deployment Services Server services or restarting the server may temporarily resolve the problem, but the issue will eventually reoccur and WDS will eventually crash again.

    Trying to reproduce the issue by continually attempting to PXE boot PCs reveals that although the issue may happen frequently, the issue cannot be reproduced on a consistent basis and that the crashes will happen randomly.

    Examining the WDS server where the ConfigMgr 2007 PXE Service Point is installed reveals the following errors in Event Viewer

    System Event Log:
    <Date> <Time>  Error         <WDS_Server>    Service Control Manager          N/A             N/A                                The Windows Deployment Services Server service terminated unexpectedly.  It has done this <x> time(s).  The following corrective action will be taken in 120000 milliseconds: Restart the service.

    Continue in reading the rest of the post Via http://support.microsoft.com/default.aspx?scid=kb;EN-US;2510665

    configMgr PXE issues configMgr.SCCM PXE Issues Configuration Manager 2007 PXE Service Point causes the Windows Deployment Services Server service to crash and hang Microsoft SCCM System center configuration Manager WDS WDS service crashing.SCCM
    Share. Twitter LinkedIn Email Facebook Reddit

    Related Posts

    How to detect the source of registry key modifications on windows devices – Intune

    November 21, 8:49 pm

    Identifying devices managed by Intune but not reporting to WUfB using KQL

    November 09, 10:28 am

    Application Deployment with Hybrid Joined Requirement Rules in Intune

    October 06, 8:59 pm

    1 Comment

    1. openfurnace on February 24, 2017 9:05 PM

      HI Anoop ,

      We are getting the following error while imaging a bare metal using PXE . “No response from Windows Deployment Services Server”
      1)IP Helper settings
      2)Option 66 and Option 67 in DHCP server (As the DHCP and DP are not on the same server)
      3)Distribution of the boot image
      4)Reinstallation of WDS is already done and reconfiguration of PXE is already performed
      5)Certificates are imported
      6)DP is added to admin group in the site server , MP and vice versa

      I have also attached the logs from the Distribution Point

      Logs from SMSPXE
      010.020.001.143:4011] Recv From:[010.020.002.094:68] Len:291 123d570 SMSPXE 2/24/2017 12:35:42 PM 6660 (0x1A04)
      08:00:27:7F:DC:19, CF838C06-DB59-1843-94E2-772B6D8A699C: Received DHCP Request SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Set enterpirse certificate in transport SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Set media certificate in transport SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Set authenticator in transport SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Set authenticator in transport SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      reply has no message header marker SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      PXE::MP_LookupDevice failed; 0x80004005 SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Set enterpirse certificate in transport SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Set media certificate in transport SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Set authenticator in transport SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Set authenticator in transport SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      reply has no message header marker SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Failed to send status message (80004005) SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      Failed to send the status message SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      PXE::MP_ReportStatus failed; 0x80004005 SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      PXE Provider failed to process message.
      Unspecified error (Error: 80004005; Source: Windows) SMSPXE 2/24/2017 12:35:42 PM 3480 (0x0D98)
      08:00:27:7F:DC:19, CF838C06-DB59-1843-94E2-772B6D8A699C: Not serviced. SMSPXE 2/24/2017 12:35:42 PM

      Let us know what else we can try to fix the issue

      Reply

    Leave a ReplyCancel reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Sign Up

    Get email notifications for new posts.

    Author

    I’m Eswar Koneti ,a tech enthusiast, security advocate, and your guide to Microsoft Intune and Modern Device Management. My goal? To turn complex tech into actionable insights for a streamlined management experience. Let’s navigate this journey together!

    Support

    Awards

    Archives

    © Copyright 2009-2024 Eswar Koneti, All rights reserved.

    Type above and press Enter to search. Press Esc to cancel.