locked
WDS won't start RRS feed

  • Question

  • Hi,

    I'm new to SCCM 2012 R2 SP1 and WDS.  But trying to get WDS to start after having reinstalled it because the remoteinstall\mngmnt folder is empty.  So uninstalled the role (rebooted) and reinstalled and configured it.

    sccm and dhcp ARE on separate servers.

    Error in the system log is:

    The description for Event ID 7024 from source Service Control Manager cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    Windows Deployment Services Server
    %%3238461708

    The locale specific resource for the desired message is not present

    Any ideas?

    Thursday, November 10, 2016 4:47 AM

All replies

  • You don't need to install WDS yourself. WDS is installed when you enable PXE on a DP. Try that method and report back.

    Cheers Paul | http://sccmentor.com

    Thursday, November 10, 2016 9:18 AM
  • PXE was selected, so deselected it and bounced the server.

    Re-enabled PXE in administration-disty point.

    Windows deployment server not installed - nothing in services either.

    Thursday, November 10, 2016 11:28 PM
  • I've seen that before when WDS does not get installed again. Try:

    1. Remove PXE (and multicast if installed). Check the logs and wait for the actual uninstall to finish. SCCM needs time after you uncheck PXE

    2. Aftet that, if WDS is still installed, uninstall it and delete remoteinstall. Restart 

    3. Install WDS role again. You may need to restart  (might as well restart in all cases)

    4. Enable PXE again on the DP and check logs again

    Friday, November 11, 2016 12:01 AM
  • Did all that, and configured it, but WDS fails to start properly.  Looked at the SMSPXE but nothing there since the 28th oct.

    Just to be sure, where exactly are the logs I should be looking at?

    thanks

    Friday, November 11, 2016 2:28 AM
  • You should not interact with WDS directly, all the configuration needed will be done when you enable PXE.

    You can check smsdpprov.log for PXE installation activity. You may also have two smspxe log files, one  sms_dp$\logs and one with the client logs.

    If you also use Multicast, there's the MCS log files.

    Friday, November 11, 2016 2:47 AM
  • Dear Sir,

    "Mgmt folder is empty " doesn't mean that WDS is not working properly. Did you face any problem during OSD?

    Check below for OSD in Configuration Manager:

    https://technet.microsoft.com/en-us/library/gg682018.aspx

    Best regards

    Frank


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 11, 2016 3:14 AM
  • this is driving me crazy!

    smsdpprov.log doesn't exist nor does sms_dp$

    I did net share.....but nothing there??

    Friday, November 11, 2016 3:24 AM
  • Hi Frank,

    Had a problem on the workstation PXE Booting.

    Error was:

    No responce from windows deployment server

    Launch PXE Boot

    Exiting intel boot agent

    Found this on technet and followed it, but remoteinstall folder is still empty and WDS does not start

    1: remove the boot images from the  SMSPXEIMAGES$

    2: remove the PSP Role from SCCM

    3: remove the WDS role from the server

    4: Delete the Remmoteinstall folder

    5: reboot the server

    6:Install the WDS role

    7:Configure WDS and Add a boot image from C:\Program Files\Windows AIK\Tools\PETools\x86\WINPE.WIM

    8:Make sure WDS is working with the WINPE.wim

    9: Once WDS is working on it's own, add the PSP role to SCCM

    10: Add boot images to  SMSPXEIMAGES$

    11. Wait 5 min, and boot to PSP

    Sorry, I'm new to SCCM

    Friday, November 11, 2016 3:47 AM
  • Didn't work:

    Error code: 0x41d

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

    Any other ideas?

    Monday, November 14, 2016 12:27 AM