SOLVED WSUS on Server 2. R2 stopped working and cannot load WSUS Admin Console. In the Computer section, WSUS displays the update status of each computer with a red X if an update has failed. You can run a report on such computer by. In this tutorial, we will implement one of Server 2012s newest features, DHCP Failover. Before Server 2012, DHCP failover was achieved through Windows Failover. Brian Tate wrote Gabrielle. L wrote Patch KB3. KB3. 15. 97. 06 was another https community. My first guess if the patches above dont pan out is that something is indeed amiss with the port numbers, as you mentioned. WSUS on Server 2. R2, so someone would have had to change it to 8. Give me a few minutes to dig out a few easy things you can test. Thanks Gabrielle. L Thats exactly what is what indeed that did it. However this is a major issue now, because we do NOT use the Windows Internal Database with WSUS and are using an external SQL database for use with SCCM and all of its features. According to this update, its required for WSUS and SCCM since it uses its components to push out updates to Windows 1. Thats a serious issueSo what exactly are we supposed to do here These two threads I correlated the event IDs with the stack trace connections in Software. Distribution. log and other places and found it must be a connection to SQL in some manner. One person tested it by moving back to using the WID with WSUS and it worked with the update, but we however cannot do that. Other than calling Microsoft after reading these two articles, has anyone found a way to work around this and get the updates to deploy out with WSUS and SCCM after the use the OSD for new Windows 1. There have been some great guides through the years on configuring WSUS with SCCM from the ground up, but i felt it was time for me to add to the library with an. Evjls Rain You can chose what types of updates you want C Runtimes. net etc also you can deselect certain updates by adding the KB to exclude list in WSUS. Enterprise deployments Forumsen US9. 25abf. Forumswindowsserveren USd. Thank you all to who commented as this was really making no sense when I could access the database with SMSS from my workstation, but the real oddity was the netstat on the WSUSSCCM server and the stack trace logs. Im not sure Microsoft has figured out a way to fully resolve this and are doing it on a case by case support basis I bet with a call or ticket to them based on these Tech. Net Social posts. What a total mess and if anyone still has any comments on how they worked around it yet Im open to suggestions hereAh ha I bet that the person before me did not bother to follow the prereqs firstOne of them is a Windows Update that you pretty much have to manually install or at least I didnt see it in Windows Update anywhere, even optional. Then after that update, you must follow the instructions below to install each update itselft if they do not automatically install and IN that order as listed from here https support. Step One DO THE PREREQSYou must manually download the update 2. KB article above. Then you can do the rest listed as more information AND THEN FINALLY APPLY THE 3. UPDATE THAT KILLS WSUS and it should work, EVEN WITH A REMOTE SQL DB INSTANCE AS OURS IS Prerequisites. To apply this update in Windows Server 2. R2, you must have April 2. Windows RT 8. 1, Windows 8. Windows Server 2. R2 2. 91. 93. 55 installed. Registry information. To apply this update, you dont have to make any changes to the registry. Restart requirement. You may have to restart the computer after you apply this update. Update replacement information. This update can be installed on top or in place of KB3. STEP TWO MORE INFORMATION FOLLOW THESE INSTRUCTIONS OR WSUS WILL NOT WORK More information. Manual steps required to complete the installation of this update. Open an elevated Command Prompt window, and then run the following command case sensitive, assume C as the system volume      C Program FilesUpdate ServicesToolswsusutil. Select HTTP Activation under. NET Framework 4. 5 Features in the Server Manager Add Roles and Features wizard. Restart the WSUS service. If SSL is enabled on the WSUS server. Assign ownership of the Web. Config file to the administrators group run at an elevated command prompt   takeown f web. C Program FilesUpdate ServicesWeb. ServicesClient. Web. ServiceWeb. config grant administrators f. Locate the Web. Config file in the following path   C Program FilesUpdate ServicesWeb. ServicesClient. Web. ServiceWeb. Config. Make the following changes in the file. Note. This code sample represents a single text block. The line spacing is used only to emphasize the text changes, which are shown in bold. lt services. Microsoft. Update. Services. Internal. Client. behavior. ConfigurationClient. Web. Service. Behaviour               lt. These 4 endpoint bindings are required for supporting both http and https. Http. Binding. binding. ConfigurationSSL. Microsoft. Update. Services. Internal. IClient. Web. Service. Http. Binding. binding. ConfigurationSSL. Microsoft. Update. Services. Internal. IClient. Web. Service               lt endpoint address. Http. Binding. binding. ConfigurationClient. Web. Service. Binding. Microsoft. Update. Services. Internal. IClient. Web. Service. Http. Binding. binding. ConfigurationClient. Web. Service. Binding. Microsoft. Update. Services. Internal. IClient. Web. Service. Add the multiple. Site. Bindings. Enabledtrue attribute to the bottom of the Web. Config file, as shown lt bindings. Hosting. Environment asp. Net. Compatibility. Enabledtrue multiple. Site. Bindings. Enabledtrue.