Em 6/1, um dos nossos Pontos de Atualização de Software perdeu a capacidade de se conectar ao seu Servidor 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.
O arquivo de log SMS_WSUS_CONFIGURATION_MANAGER sugere que o WSUS 3.0 SP2 não está instalado ou não pode ser contatado pelos serviços SMS SUP (SMS_WSUS_CONFIGURATION_MANAGER e 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.
Verifiquei que a função do WSUS ainda estava instalada no SCCM.ad.contoso.gov; no entanto, não parece ser saudável. Não consigo me conectar a ele usando o snap-in do MMC do Windows Server Update Services e o log de eventos é preenchido com os seguintes erros voltando para 6/1:
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 ...
Verifiquei que o WsusService estava em execução e verifiquei o IIS:
Hã.Issoprovavelmentenãoébom.OPooldeAplicativosWsusPoolprovavelmentedeveestaremexecução...SeeuiniciarmanualmenteoWsusPool,possoconectar-meaosWSUSWebServicesnavegandoatéhttp://SCCM.ad.contoso.gov:8530/Selfupdate...edepoisdeaproximadamente15minutos,oPooldeAplicativosseráinterrompido.
Tambémestárodandonasportaserradas(8530/8531)!Cercadeummêsatrás,comaassistênciadaPFE,configuramosessaSUPparaestardisponívelparaclientesbaseadosnaInternet.PartedessareconfiguraçãosignificouqueosserviçoswebdoWSUSprecisamserrealocadospara80/443,demodoqueelesestãodisponíveisatravésdonossofirewalldeperímetro.
Eunãotenhodocumentaçãosobreoscomandosexatosqueusamos,mastenhocertezadequeera WSUSUtil.exe usecustomwebsite false que deve mover o WSUS de seu IIS" Administração do WSUS "de volta para o Site Padrão, que está ligado sob *: 80 e *: 443.
novamente. Este não é o caso:
Bem,issonãoébom.ParecequeositedoWSUSmigroumagicamentedevoltaparaseusiteindependenteporque...DIVERSÃO!SeoSUPdoSCCMestiverprocurandopeloWSUSno80/443enãoestivermaislá,nãoédeadmirarquenãofuncione.
Seeuexaminarachavederegistro(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\UpdateServices\Server\Setup\PortNumbner)que WSUSUtil.exe está manipulando Eu vejo que ainda acha que o WSUS deveria estar rodando em 80.
Talvez eu precise executar WsusUtil.exe mais de uma vez para mais ... FUN?
C:\Program Files\Update Services\Tools>WsusUtil.exe usecustomwebsite false
Using port number: 80
Exceto ... nada no IIS muda. Eu não estou lembrando de uma etapa que fizemos anteriormente para mover o Site WSUS IIS ou algo está quebrado.
Eu realmente tenho dois problemas:
- O site do WSUS 'Administração do WSUS' retornou à sua configuração instalada como um site independente do IIS com *: 8530 e *: 8531, mas partes subjacentes do sistema acham que ele deve estar sendo executado no 'Site padrão' ligado a *: 80 e *: 443.
- O Pool de Aplicativos do WsusPool continua travando ou parando de me impedir de reconfigurar o ponto de SUP para usar o WSUS em suas portas *: 8530 e *: 8531 originais.
Neste ponto, estou com uma certa dificuldade sobre como continuar a solucionar esse problema. Eu realmente quero evitar a reinstalação da função do WSUS e / ou SUP, se possível, devido ao lançamento iminente das Atualizações da Microsoft amanhã.
Algum conselho sobre resolução de problemas?