I ran into this problem too, but only in a production environment installing SP 2013 on Windows 2012 Servers.
Windows Server 2012 uses Windows Update to install some features needed for the Web Server role. Im my case, a GPO to configure WSUS for windows updates actually broke Windows Update instead of disabling it throwing one of the remote WFE servers into an infinite loop of reboots.
Not sure why the GPO had only affected one of the servers. When I tried to run Windows Update by clicking check for updates I get a Windows Update error 800b0001. I fixed Windows Update by removing certain registry entries identified in the Technet article "Configure Automatic Updates using Registry Editor".
When the script fails during the second remote install - what is the best course of action? I hit enter at the prompt and the script continued with the third remote install...
Joe
Windows Server 2012 uses Windows Update to install some features needed for the Web Server role. Im my case, a GPO to configure WSUS for windows updates actually broke Windows Update instead of disabling it throwing one of the remote WFE servers into an infinite loop of reboots.
Not sure why the GPO had only affected one of the servers. When I tried to run Windows Update by clicking check for updates I get a Windows Update error 800b0001. I fixed Windows Update by removing certain registry entries identified in the Technet article "Configure Automatic Updates using Registry Editor".
When the script fails during the second remote install - what is the best course of action? I hit enter at the prompt and the script continued with the third remote install...
Joe