SCCM 2012 : No need to manually install WDS

ConfigMgr 2012 : No need to manually install WDS

   

Contrarily to Configuration Manager 2007, there is no need to install WDS before to enable PXE in Configuration Manager 2012. The distribution point installs it automatically when enabling PXE and this is the recommendation. Otherwise, WDS service will hung as in the following print screen and you’ll not able to to deploy OS.
1. WDS service in “Starting” status if it was installed manually before enabling PXE.

2. So don’t preinstall WDS, just enable PXE from ConfigMgr 2012 and it will be automatically installed.

3. You can monitor the installation from distmgr.log

      

SCCM 2012 WDS PXE-E32: TFTP open timeout

Ever get this message when PXE booting? I did again today. The PXE Server was running Windows Server 2008 R2 SP1, and PXE boot had been working perfectly until I applied some updates to the server last week. Following the server update, clients were unable to PXE boot, and the above error was displayed.

1st possible solution

• Open registry editor on the PXE server (regedit.exe)
• Locate HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\WDSServer\Parameters

• 

  • Right-click UdpPortPolicy, and then click Modify.

  

  • In the “Value data” field, change the value to 0, and then click OK.
  • Exit the Registry Editor.
  • From the Services console, restart the “Windows Deployment Services” service
  Problem solved! PXE boot is now working!

2nd possible solution - this fixed my problem for sure 
Well, to fix this, I tricked it.

 1) I made sure it was all off' in SCCM by right clicked DP point => proprietaries => PXE and disabled . And renamed the RemoteInstall folder

2) I installed WDS myself as a role. Then enabled the PXE stuff in SCCM. Rebooted.

3) Then, I disabled the PXE stuff again, and it correctly removed WDS. Rebooted

4) Enabled PXE again, went to Services & saw the Windows Deployment Services Server was not started => Right click and started it. At this point a new RemoteInstall folder is created

5) I basically copied the content of the RemoteInstall.old to the new RemoteInstall

6) PXE now can boot without error and is able to deploy OS.

WSUS 3.0 SP2 An unexpected error occurred, and this wizard must be closed mesage

Problem:
SCCM 2012 R2 SP2 on Windows Server 2008 R2 x64
Installed WSUS 3.0 successfully however at end of install (after pressing finish) an error message appears stating: An unexpected error occurred, and this wizard must be closed. you may restart the WSUS server configuration wizard from the options page in the wsus 3.0 console.
I installed WSUS in custom port: 8530
in event log
Error 7053, 12052, 12042, 12032, 12012
DDSAuthentication Web service is not working
SimpleAuthWeb, ClientWebService, Server Sync web service, API remoting web, and reporting web service is not working..


Solution:
Problem was in IIS Application Pool for WSUSPool. Had to change it from Network Service to Local System. WSUS worked immediately. Very strange.

My SCCM 2012 was synchronizing fine until I had the SP1 installed, which messed it up and I had to install KB2720211 + KB2734608  to fix the problems.