1. Make sure that the server do not have PXE installed
a. Remove all bootimage images from the affected PXE server Distribution Point
b. From the console, remove the PXE service role.
c. Check the Program Files\Microsoft Configuration Manager\Logs\PXEsetup.log to verify that the role is removed successfully.
d. Remove the Windows Deployment Service.
e. Reboot the Configuration Manager site server, if WDS was installed on the site server.
2. Install WDS but do not configure it.
3. Assuming DHCP and WDS are installed on the same Configuration Manager server,
a. Make sure that DHCP Option 60 is set
i. NETSH
ii. NETHSH>DHCP server \\nameofserver
iii. add optiondef 60 PXEClient String 0 comment=”Option added for PXE Support”
iv. set optionvalue 60 STRING PXEClient
v. show optionvalue all
vi. exit
b. Enabled and choose don’t listen on port 67.
i. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE
ii. Set the UseDHCPPorts registry value to 0
4. Install the PXE service role from the console
5. Check the PXEsetup.log to verify that the role was installed successfully.
6. Update the PXE distribution points for the boot images now that the new role is installed.
7. The target client should now be able to PXE boot to the Configuration Manager server.
