Hi

 

So I was updating the PXE certificate on our pxe service point, I followed all the documented steps, but after updating the boot image the WDS service on our pxe service point will not start and is stuck in "starting". So I proceeded to remove the boot images from the dp. But one of the boot images is failing at removal.

So I then changed the counters for default distmgr settings to a small number and it now has used up all its retries. The issue seems to be with my x86 boot image, as it is the only boot image that has prolems being removed.

 

What should I do to get the WDS service to start again? Should I go and delete the boot image that is still present on the psp server? I tried to upload the boot images again but I run into the same problem. Maybe if I delete the files off the server and then upload the boot images again?

hi Nico_

follow all the steps here to troubleshoot it

http://blogs.technet.com/b/oob/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx

I got it working again. Here is how I did it:

 

1. Set the WDS to not start at boot and then I booted the server(since the wds will not stop).

2. Since the package is allready gone from SCCM, due to exceeding the number of retries, see my previous post, I quickly removed the corrupt boot image from my smswpxeimages$\smspkg\ folder. 

3. Restarted the WDS, it will now start. Set WDS to start automatically

4. Boot the server

5. Uploaded the boot images to the  smswpxeimages$\smspkg\ folder

6. Set number of retries back to default value.

6. Pxe boot as usual.

 

Its now working as it should :)

• Marked as answer by Nico_ Thursday, January 12, 2012 1:27 PM

I got it working again. Here is how I did it:

 

1. Set the WDS to not start at boot and then I booted the server(since the wds will not stop).

2. Since the package is allready gone from SCCM, due to exceeding the number of retries, see my previous post, I quickly removed the corrupt boot image from my smswpxeimages$\smspkg\ folder. 

3. Restarted the WDS, it will now start. Set WDS to start automatically

4. Boot the server

5. Uploaded the boot images to the  smswpxeimages$\smspkg\ folder

6. Set number of retries back to default value.

6. Pxe boot as usual.

 

Its now working as it should :)

• Marked as answer by Nico_ Thursday, January 12, 2012 1:27 PM

I got it working again. Here is how I did it:

 

1. Set the WDS to not start at boot and then I booted the server(since the wds will not stop).

2. Since the package is allready gone from SCCM, due to exceeding the number of retries, see my previous post, I quickly removed the corrupt boot image from my smswpxeimages$\smspkg\ folder. 

3. Restarted the WDS, it will now start. Set WDS to start automatically

4. Boot the server

5. Uploaded the boot images to the  smswpxeimages$\smspkg\ folder

6. Set number of retries back to default value.

6. Pxe boot as usual.

 

Its now working as it should :)

• Marked as answer by Nico_ Thursday, January 12, 2012 1:27 PM

In our case, the issue was an wim-image file (4 GB) that was erroneous distributed to smspxeimages$\smspkg!
After housekeeping (manage distribution points), a folder rename of "C:\Windows\Temp\PXEBootFiles" and a server reboot the service "WDSServer" gets work fine.