SCCM SUP无法连接到WSUS服务器 – 未安装WSUS服务器版本3.0 SP2或更高版本

在6/1上，我们的软件更新点失去了连接到其WSUS服务器的能力：

WSUS Control Manager failed to monitor WSUS Server "SCCM.ad.contoso.gov". Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted.

SMS_WSUS_CONFIGURATION_MANAGER日志文件build议WSUS 3.0 SP2未安装或不能与SMS SUP服务（SMS_WSUS_CONFIGURATION_MANAGER和SMS_WSUS_CONTROL_MANAGER）联系：

 Error Milestone 004 6/8/2015 5:01:30 AM SCCM.ad.contoso.gov SMS_WSUS_CONTROL_MANAGER 7003 WSUS Control Manager failed to monitor WSUS Server "SCCM.ad.contoso.gov". Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website. Error Milestone 004 6/8/2015 5:01:30 AM SCCM.ad.contoso.gov SMS_WSUS_CONTROL_MANAGER 7000 WSUS Control Manager failed to configure proxy settings on WSUS Server "SCCM.ad.contoso.gov". Possible cause: WSUS Server version 3.0 SP2 or above is not installed or cannot be contacted. Solution: Verify that the WSUS Server version 3.0 SP2 or greater is installed. Verify that the IIS ports configured in the site are same as those configured on the WSUS IIS website.You can receive failure because proxy is set but proxy name is not specified or proxy server port is invalid. Information Milestone 004 6/8/2015 4:01:39 AM SCCM.ad.contoso.gov SMS_WSUS_CONTROL_MANAGER 4609 Component Status Summarizer set the status of component "SMS_WSUS_CONTROL_MANAGER", running on computer "SCCM.ad.contoso.gov", to Critical. Possible cause: The component is experiencing a problem. Solution: Diagnose and fix the problem by: 1. Examining the status messages that the component reports. 2. Correcting the problem. 3. Instructing Component Status Summarizer to reset the counts of Error, Warning, and/or Informational status messages reported by the component. To reset the counts, right-click Reset Counts on the component in the Component Status summary in the Configuration Manager Console. When the counts are reset, Component Status Summarizer will change the status of the component to OK. This might take some time if site "004" is a child site. 4. Delete any unwanted status messages from the site database, if necessary. 5. Monitor the component occasionally to verify that the problem does not reoccur. Possible cause: The component is OK and you were unnecessarily alerted because the Component Status Thresholds are set too low for the component. Solution: Increase the Component Status Thresholds for the component using the Thresholds tab of the Component Status Summarizer Properties dialog box in the Configuration Manager Console. Possible cause: The component is flooding the status system by rapidly reporting the same message repeatedly. Solution: Diagnose and control the flood of status messages by: 1. Verifying that the component is actually flooding the status system. View the status messages reported by the component and verify that the same message is continually reported every several minutes or seconds. 2. Noting the Message ID of the flooded status message. 3. Creating a Status Filter Rule for site "004" that instructs Status Manager to discard the flooded status message when component "SMS_WSUS_CONTROL_MANAGER" on computer "SCCM.ad.contoso.gov" reports it. 4. Verifying that your sites' databases were not filled up by the flooded status message. Del Information Milestone 004 6/8/2015 4:01:39 AM SCCM.ad.contoso.gov SMS_WSUS_CONTROL_MANAGER 4605 Component Status Summarizer detected that component "SMS_WSUS_CONTROL_MANAGER", running on computer "SCCM.ad.contoso.gov", has reported 5 or more Error status messages during the Component Status Threshold Period. Possible cause: The count equals or exceeds the Component Status Critical Threshold (5 status messages) for Error status messages for the component. Solution: Component Status Summarizer will set the component's status to Critical in the Component Status summary in the Configuration Manager Console. 

我证实WSUSangular色确实仍安装在SCCM.ad.contoso.gov; 然而它看起来并不健康。 我无法使用Windows服务器更新服务MMCpipe理单元连接它，并且事件日志中填充以下错误返回到6/1：

• Splunk UniversalForwarder失败，并显示“DetermineContextForAllProducts failed witht：0x65b”
• Windows Defender与Windows Intune Endpoint Protection和SCCM Endpoint Protection有什么区别？
• 针对小型networking运行所有Microsoft产品与VMWare / backup / AV
• 如何在SCCM 2012 SP1的任务序列中运行任务序列
• SCCM：Zoinks …神秘维护窗口

 PS C:\Windows\system32> Get-EventLog -LogName Application -Source "Windows Server Update Services" -After $(Date -Month 06 -Day 07) Index Time EntryType Source InstanceID Message ----- ---- --------- ------ ---------- ------- 267564 Jun 08 04:14 Error Windows Server Up... 12052 The DSS Authentication Web Service is not working. 267563 Jun 08 04:14 Error Windows Server Up... 12042 The SimpleAuth Web Service is not working. 267562 Jun 08 04:14 Error Windows Server Up... 12022 The Client Web Service is not working. 267561 Jun 08 04:14 Error Windows Server Up... 12032 The Server Synchronization Web Service is not w... 267560 Jun 08 04:14 Error Windows Server Up... 12012 The API Remoting Web Service is not working. 267559 Jun 08 04:14 Error Windows Server Up... 12002 The Reporting Web Service is not working. 267558 Jun 08 04:14 Warning Windows Server Up... 10021 The catalog was last synchronized successfully ... 

我validation了WsusService实际上正在运行，然后检查IIS：

呵呵。 这可能不好。 WsusPool应用程序池应该可能正在运行…如果我手动启动WsusPool，则可以通过浏览到http://SCCM.ad.contoso.gov:8530/Selfupdate …来连接WSUS WebServices，然后App Pool停止15分钟。

另外它运行在错误的端口（8530/8531）！ 大约一个月前，在PFE的帮助下，我们将这个SUPconfiguration成可供基于互联网的客户使用。 部分重新configuration意味着WSUS Web服务需要重新定位到80/443，以便通过我们的外围防火墙提供。

我没有关于我们使用的确切命令的文档，但我确信它是WSUSUtil.exe usecustomwebsite false ，它应该将WSUS从其“WSUSpipe理”IIS移回默认网站，该网站绑定在*：80和* ：443。

再次。 不是这种情况：

那么这不好。 看起来WSUS网站神奇地迁移回到它的独立站点，因为…好玩！ 如果SCCM SUP正在寻找80/443上的WSUS并且不再存在，那么难怪它不起作用。

如果我看一下WSUSUtil.exe正在操作的registry项（ HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup\PortNumbner ），我看到它仍然认为WSUS应该在80上运行。

也许我只需要运行WsusUtil.exe不止一次额外的… WsusUtil.exe吗？

 C:\Program Files\Update Services\Tools>WsusUtil.exe usecustomwebsite false Using port number: 80 

除了… IIS中没有任何变化。 我要么不记得我们之前做过的移动WSUS IIS站点的步骤，

我真的有两个问题：

• WSUS网站“WSUSpipe理”已经作为绑定到*：8530和*：8531的独立IIS网站返回到它的原始configuration，但系统的底层部分认为它应该在绑定到*的默认网站下运行。 ：80和*：443。
• WsusPool应用程序池不断崩溃或停止，使我无法重新configurationSUP点以在其原始*：8530和*：8531端口上使用WSUS。

在这一点上，我对如何继续解决这个问题感到不知所措。 我真的想避免重新安装WSUSangular色和/或SUP，如果可能的话，由于即将发布的微软明天更新。

有关进一步故障排除的build议