question

HeathDurrett avatar image
0 Votes"
HeathDurrett asked saldana-msft edited

SCCM Current branch remove WDS

Hi All,

We have upgraded out MEMCM platform to 2002 successfully, since then PXE booting for OSD has been very hit and miss.

I'd like to know more about dropping WDS and enabling the now built in PXE responder.

Can we simply enable the PXE responder on DPs now and uninstall WDS?

Are there any other additional requirements to "migrate away" from WDS requirements on a system that is currently using WDS for PXE boot response.

Thanks in advance,
durrie.

mem-cm-generalmem-cm-osd
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HeathDurrett avatar image
1 Vote"
HeathDurrett answered

It's a strange series of events but I managed to resolve this by.

1) Again disabling PXE entirely - for a second time!
2) Enable only the PXE Responder again.
3) Re-created my Boot Images.
4) Deleted all deployments on Task Sequences.
5) Redeployed all Task sequences to the "Unknown Computers Collection"

Seems to be stable now...and as an added bonus seems to deploy a lot faster than before too!?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

FionaYan-MSFT avatar image
0 Votes"
FionaYan-MSFT answered HeathDurrett edited

@HeathDurrett

Thank you for posting in Microsoft Q&A forum.

  1. Please check your sms.pxe log on our site server to see if there is any related errors in it. And ensure that all of our site components are healthy after the upgrade.

  2. When enabling the PXE responder server does not uninstall WDS, it also simply disables it.Drop WDS and enable our PXE is the same way like this,so maybe we need to check the log first to see if any details in it.


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@FionaYan-MSFT

Thank you - realized the removal of WDS was not automatic so what I did was entirely disable the PXE option then I manually removed WDS and I rebooted.

Then I enabled PXE again with the PXE responder option.

I can see requests in the PXE log but I do not really see any errors jumping out at me, with that said I'm not well versed is reading this log so don't know what to look for?

44250-pxe.png




P.S. Site health status is all green ticks - OK

0 Votes 0 ·
pxe.png (105.8 KiB)
RahulJindal-2267 avatar image
0 Votes"
RahulJindal-2267 answered HeathDurrett edited

Hi,

Are you facing issues after enabling pxe responder?

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@RahulJindal-2267

No I have now managed to entirely remove WDS and PXE configuration, I then re-enabled PXE responder ONLY and the PXE boot is now working but not for all architecture types.

I'm using DHCP vendor classes and policy to specify PXE options in my DHCP. A lot of MEMCM reading suggests not to use these and use DHCP helper addresses.

Is that true even when the DP,DHCP and clients are all in the same subnet?

0 Votes 0 ·
FionaYan-MSFT avatar image
0 Votes"
FionaYan-MSFT answered HeathDurrett edited

@HeathDurrett

Thank you for the quickly response.

I have reviewed the case again and let us sort out our ideas.The issue we faced currently is that sometimes our pxe guidance is good, and sometimes it is not,is that right?(please correct me if I'm incorrectly)

If so,the first thing we need to know which step we are facing issues?It would be greatly appreciated that if we provide a failed screen shoot or we could described the failed scenario.

Have a good day!


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@FionaYan-MSFT

Thanks for the help so far, as requested, a quick round up and explanation of outstanding issue.

After completely removing PXE config and WDS, rebooting and then enabling only the PXE Responder service I am able to now boot but not ALL architecture types?

I use DHCP vendor classes and policies for PXE configuration because all my deployments happen in the same subnet no IP helpers configured nor required.

When I boot from legacy BIOS it all works fine - but asks me to press F12 to network boot.

However, now when I boot UEFI systems I now get prompted to approve the PXE request?

This seems like legacy WDS config hanging around to me? Where do you configure these options when using the PXE Responder service?


45792-pxe2.png


0 Votes 0 ·
pxe2.png (30.1 KiB)
FionaYan-MSFT avatar image
0 Votes"
FionaYan-MSFT answered FionaYan-MSFT edited

@HeathDurrett

Thank you for the kindly reply.

Have we checked the option of respond on a specific network interfaces on our DP? Sometimes it may cause the similar issue if we choose this option,please change the option to "all network interface".
46067-pxe-settings.png

Have a good day!


If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.



pxe-settings.png (29.5 KiB)
pxe-settings.png (29.4 KiB)
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@FionaYan-MSFT - thanks for the advice - my settings were already to listen on ALL network interfaces.

It's a strange series of events but I managed to resolve this by.

1) Again disabling PXE entirely - for a second time!
2) Enable only the PXE Responder again.
3) Re-created my Boot Images.
4) Deleted all deployments on Task Sequences.
5) Redeployed all Task sequences to the "Unknown Computers Collection"

Seems to be stable now...and as an added bonus seems to deploy a lot faster than before too!?

Thanks for the help.

1 Vote 1 ·

@HeathDurrett

Thank you very much for the update and sharing the solution here. Could we post as a separate response and then "accept answer" by yourself. I believe this should be useful for someone who has similar issue in the future.

Have a nice day!

0 Votes 0 ·