locked
SCCM SUP and WSUS issues RRS feed

  • Question

  •  

     I would like to use SCCM to configure clients. I had SCCM installed on a serve, let’s say Server A. I then installed WSUS on another server, let’s say Server B. On Server B WSUS is installed using a custom website, port 8530, I configured no other options so that SCCM could configure WSUS. I then installed the WSUS Admin Console on Server A and connected it to the WSUS server on Server B. Next I Installed the SUP on Server B and configured options. SMS_WSUS_Sync_Manager is reporting

    SMS WSUS Synchronization failed.

    Message: WSUS server not configured.

    Source: CWSyncMgr::DoSync.

      The operating system reported error 2147500037: Unspecified error

    SMS_WSUS_Configuration_Manager is reporting

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


    Tom Power

    Friday, February 17, 2012 2:32 PM

Answers

All replies

  • Please check if there is any firewall issue & rights issue. Server A's computer account has admin right on Server B.


    Thanks & Regards, Prashant Patil

    Friday, February 17, 2012 2:41 PM
  • Yes Server A's computer account is a memeber of Server B's Builtin Administrators group. Firewall for the domain connection has been turned off.

    Tom Power

    Friday, February 17, 2012 2:56 PM
  •  

     I would like to use SCCM to configure clients. I had SCCM installed on a serve, let’s say Server A. I then installed WSUS on another server, let’s say Server B. On Server B WSUS is installed using a custom website, port 8530, I configured no other options so that SCCM could configure WSUS. I then installed the WSUS Admin Console on Server A and connected it to the WSUS server on Server B. Next I Installed the SUP on Server B and configured options. SMS_WSUS_Sync_Manager is reporting

    SMS WSUS Synchronization failed.

    Message: WSUS server not configured.

    Source: CWSyncMgr::DoSync.

      The operating system reported error 2147500037: Unspecified error

    SMS_WSUS_Configuration_Manager is reporting

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


    Tom Power

    Have you installed SUP on the server B?

    I think, you should go through the below guide to get the configuration correct.

    http://www.windows-noob.com/forums/index.php?/topic/812-install-a-sup-on-remote-server/


    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Friday, February 17, 2012 3:14 PM
  • Yes as stated above SUP is installed on Server B.

    Tom Power

    Friday, February 17, 2012 5:10 PM
  • Check these ... it could be a communication issue with Wrong configuration...

    Possible Solutions

    Following are possible solutions for the WSUS server not configured error:

    • Check the port settings configured for the active software update point, and make sure they are the same as the port settings configured for the Web site used by WSUS running on the active software update point. For more information, seeHow to Determine the Port Settings Used by WSUS.

    • Check to make sure the fully qualified domain name (FQDN) for the active software update point site system server is correct. For more information, see How to Verify the Fully Qualified Domain Name Settings Used By the Active Software Update Point.

    • When the Configuration Manager site is in native mode, the WSUS Web site and virtual directories must be configured for Secure Sockets Layer (SSL) because the active software update point is automatically configured to use SSL, but WSUS is not automatically configured. When a Configuration Manager site is in mixed mode, you have the option to configure the active software update point to use SSL. In both cases, you must manually configure the WSUS Web site and virtual directories. For more information, see How to Configure the WSUS Web Site to Use SSL.

    • Check to make sure that WSUS running on the active software update point for the child primary site is not configured to be a replica. The following procedure provides the steps to check whether WSUS is configured to be a replica.

      To check the update source settings in WSUS

      1. Open the WSUS console on the active software update point for the site.

      2. Click Options in the console tree pane.

      3. Click Update Source and Proxy Server in the display pane.

      4. Verify that This server is a replica of the upstream server is not selected unless you are in the WSUS console on the active software update point for a secondary site. Child primary sites should never be configured as a replica of the upstream server.

    • Check that Update Services is running on the WSUS server.


    This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. Click on "vote as Helpful" if you feel this post helpful to you. This can be beneficial to other community members reading the thread.

    Friday, February 17, 2012 6:19 PM
  • Check them all. Ports are good on both 8530, custom website. FQDN is good. Site is NOT in native mode. It is not configured as a replica. Still having issues

    Tom Power

    Friday, February 17, 2012 7:28 PM
  • this is a section of the WSUSCtrl log it lists port 80 but WSUS custom website is configured with port 8530??????

    Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.569 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.591 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.601 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226)~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.610 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Successfully connected to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.632 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.917 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Successfully connected to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.930 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    There are no unhealthy WSUS Server components on WSUS Server CATCH-S011~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.945 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Successfully checked database connection on WSUS server CATCH-S011~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.959 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    ~Waiting for changes for 57 minutes $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:00:19.968 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Timed Out...~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.343 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.0.6000.273, Major Version = 0x30000, Minor Version = 0x17700111~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.365 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Found WSUS Admin dll of assembly version Microsoft.UpdateServices.Administration, Version=3.1.6001.1, Major Version = 0x30001, Minor Version = 0x17710001~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.375 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    The installed WSUS build has the valid and supported WSUS Administration DLL assembly version (3.1.7600.226)~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.384 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Successfully connected to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.405 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Local WSUS Server Proxy settings are correctly configured as Proxy Name and Proxy Port 80 $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.637 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Successfully connected to local WSUS server $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.653 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    There are no unhealthy WSUS Server components on WSUS Server CATCH-S011~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.670 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    Successfully checked database connection on WSUS server CATCH-S011~ $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.687 2012 Eastern Standard Time><thread=14508 (0x38AC)>
    ~Waiting for changes for 57 minutes $$<SMS_WSUS_CONTROL_MANAGER><Fri Feb 17 13:57:29.698 2012 Eastern Standard Time><thread=14508 (0x38AC)>

    Tom Power

    Friday, February 17, 2012 7:53 PM
  • I don't know you had already gone through the website (windows-noob) link given above and confirm you've completed everysteps mentioned in that link.

    Anoop C Nair - @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    User Group:  ConfigMgr Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Saturday, February 18, 2012 2:13 AM
  • Yes Sir, I even tried a reinstall. SCCM is reporting that it can not configure the WSUS yet the WSUSlog does say it sees the WSUS server and the SUPlog says that SUP is installed.

    Tom Power

    Tuesday, February 21, 2012 2:06 PM
  • Could it be an IIS issue? WSUS is set to use a custom website port 8530 but there is a virtual directory for WSUS under the default website also

    Tom Power

    Wednesday, February 22, 2012 4:39 PM
  • You have probably gone too far with Server B and WSUS configuration. Now the SUP can't take over the WSUS.

    Delete SUP role from Server B.

    Remove server role WSUS

    reboot

    Add the role WSUS role back, install the WSUS but cancel the configuration of it.

    Add SUP and configure it again on port 8530

    Sunday, February 26, 2012 5:03 AM
  • Have reinstalled already both WSUS and SUP. NO configuration of WSUS still same problem.

    Tom Power

    Monday, February 27, 2012 2:03 PM
  • Check this link out. Maybe your SCCM server doesn't have the authority on that other server to configure it as SUP.

    Step 4. Make the SCCM computer account a member of local administrators on your WSUS server

    http://www.windows-noob.com/forums/index.php?/topic/812-install-a-sup-on-remote-server/


    Also on the Synchronization source make sure you select the option "Synchronize from Microsoft Update"
    • Edited by Brano Lukic Wednesday, February 29, 2012 5:30 AM
    • Proposed as answer by Sabrina Shen Wednesday, February 29, 2012 7:54 AM
    • Marked as answer by Garth JonesMVP Saturday, January 2, 2016 6:00 PM
    Wednesday, February 29, 2012 5:27 AM
  • SCCM server is a memeber of the other server's bulitin administrators group.


    Tom Power

    Wednesday, February 29, 2012 2:13 PM
  • Check the Software Update Component in ConfigMgr Console.

    the Server B should be selected as Active Software Update Point in the Remote Server and Port Should be 8530 and 8531.

    If it is correct, check the WCM.log for any issues.

    Saturday, March 17, 2012 6:41 PM