none
WSUS and SCCM2007

    Question

  • Hi All

    I have one SCCM server in native mode.

    I'm trying to "integrate" WSUS, I already installed the WSUS role but I allways have the error at the Component Status.

    SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "APSSSCCM01".

    Possible cause: WSUS Server version 3.0 SP1 and above is not installed or cannot be contacted.
    Solution: Verify that the WSUS Server version 3.0 SP1 or greater is installed. Verify that the IIS ports configured in SMS are same as those configured on the WSUS IIS website.

    All WSUS configuration I've done at SCCM side.

    The WSUS Port are

    http - 8530

    htps - 8531

    and at SCCM component I've configured

    port number - 8530

    SSL port number - 8531

    Can anyone could help me please

    mercredi 18 avril 2012 15:01

Réponses

Toutes les réponses

  • Is WSUS installed on the ConfigMgr box or on a remote one [if it is on a remote one, make sure that you've already installed the WSUS console on the ConfigMgr box and that the ConfigMgr computer account is in the local admin group on the WSUS server] ? Is WSUS Website configured for SSL http://technet.microsoft.com/en-us/library/bb633246.aspx and are all requirements for SUP to use SSL done well http://technet.microsoft.com/en-us/library/bb693886.aspx ? Could you check in plus WCM.log

    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1



    mercredi 18 avril 2012 15:59
  • Hi

    thanks for your fast response.

    The WSUS is in the same server tha SCCM

    I've followed (before) the both links that you sent and still no work

    about WCM.log I get

    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111 SMS_WSUS_CONFIGURATION_MANAGER 19-04-2012 11:35:53 2872 (0x0B38)
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001 SMS_WSUS_CONFIGURATION_MANAGER 19-04-2012 11:35:53 2872 (0x0B38)
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226) SMS_WSUS_CONFIGURATION_MANAGER 19-04-2012 11:35:53 2872 (0x0B38)
    Using xxxxxxxx\administrator credentials for network connections SMS_WSUS_CONFIGURATION_MANAGER 19-04-2012 11:35:53 2872 (0x0B38)
    System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host~~   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)~~   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)~~   --- End of inner exception stack trace ---~~   at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)~~   at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)~~   at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)~~   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)~~   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)~~   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)~~   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)~~   at System.Net.TlsStream.CallProcessAuthentication(Object state)~~   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)~~   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)~~   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)~~   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)~~   at System.Net.ConnectStream.WriteHeaders(Boolean async)~~   --- End of inner exception stack trace ---~~   at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~   at Microsoft.UpdateServices.Administration.AdminProxy.GetUpdateServer(String serverName, Boolean useSecureConnection, Int32 portNumber)~~   at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) SMS_WSUS_CONFIGURATION_MANAGER 19-04-2012 11:35:53 2872 (0x0B38)
    Done using xxxxxxx\administrator credentials SMS_WSUS_CONFIGURATION_MANAGER 19-04-2012 11:35:53 2872 (0x0B38)
    Remote configuration failed on WSUS Server. SMS_WSUS_CONFIGURATION_MANAGER 19-04-2012 11:35:53 2872 (0x0B38)
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=APSSSCCM01 SITE=TOP PID=1920 TID=2872 GMTDATE=Thu Apr 19 10:35:53.428 2012 ISTR0="APSSSCCM01" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 19-04-2012 11:35:53 2872 (0x0B38)

     

    jeudi 19 avril 2012 11:09
  • So IIS has the ports set correctly and the ConfigMgr console is correct?

    Have you looked at the WSUSutil command as well?

    http://technet.microsoft.com/en-us/library/dd939838(v=ws.10).aspx

    configuressl

    checkhealth


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

    jeudi 19 avril 2012 13:36
  • Hi Mattew

    Yes the ports are set correctly

    The WSUS Port are

    http - 8530

    htps - 8531

    and at SCCM component I've configured

    port number - 8530

    SSL port number - 8531

    The commands:

    wsusutil configuressl servername.domain.pt

    return

    URL: https://servername.domain.pt:8531

    the event Viewer

    wsusutil checkhealth

    Error 19-04-2012 15:28:44 Windows Server Update Services 12052 9 - The DSS Authentication Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12042 9 - The SimpleAuth Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12022 9 - The Client Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12032 9 - The Server Synchronization Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12012 9 - The API Remoting Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12002 9 - The Reporting Web Service is not working

    jeudi 19 avril 2012 14:36
  • Error 19-04-2012 15:28:44 Windows Server Update Services 12052 9 - The DSS Authentication Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12042 9 - The SimpleAuth Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12022 9 - The Client Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12032 9 - The Server Synchronization Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12012 9 - The API Remoting Web Service is not working.
    Error 19-04-2012 15:28:44 Windows Server Update Services 12002 9 - The Reporting Web Service is not working


    These errors can be caused if the IIS configuration was incorrect or SSL has been enabled improperly on IIS virtual directories ! Please follow these links and confirm that all steps are done correctly http://technet.microsoft.com/en-us/library/bb633246.aspx then http://technet.microsoft.com/en-us/library/bb693886.aspx

    Bechir Gharbi | http://myitforum.com/myitforumwp/community/members/bgharbi/ | Time zone : GMT+1


    jeudi 19 avril 2012 14:52
  • Hi Bechir

    I've already re-checked the configurations for all VD's and everything is acording to the technet doc.

    I've cleaned that error when I configured the WebDav Authority Rule to:

    All content

    All Users

    Read

    but still have the 1st error that I Post

    jeudi 19 avril 2012 15:48
  • Hi Paulo,

    Have you add "Windows Authentication" service for your IIS?

    Check this technet document:

    How to Configure Windows server 2008 for SCCM

    Hope this will help.

    Thanks

    • Marqué comme réponse Sabrina Shen lundi 30 avril 2012 05:19
    mardi 24 avril 2012 08:28