locked
Remote configuration Failed on Remote WSUS Server RRS feed

  • Question

  • Good Afternoon - 

    I recently rebuild our SCCM environment and it is currently at 2012 R2 SP1 CU3. The design (which I didn't create) called for the WSUS server to be a separate server.  When I deploy the SUP role to it and schedule an initial sync, it does not work.  Below are some environment details, errors / logs, and what I've tried so far.

    Environment Details

    • SCCM 2012 R2 SP1 CU3
    • x5 Separate Site Servers: Primary, x2 Secondaries (off-site), Database, & WSUS
    • All Site Servers run Windows Server 2012 R2
    • Database: SQL 2014
    • WSUS uses it's own SQL instance - not WID
    • All site servers have full control of Systems Management Container
    • All Site Servers are in a single security group which are set as local admins on each server

    Errors / Logs

    After deploying the SUP role, I get the following in wsyncmgr.log and WCM.log

    SCCM Console Status Messages

    • WSUS Configuration Manager failed to configure upstream server settings on WSUS Server "PrimaryFQDN".
    • WSUS Configuration Manager will not be able to configure WSUS Server "PrimaryFQDN" as the WSUS Server remoting API's of version 3.0 SP2 or greater are not installed on this site server.
      Solution: WSUS Server configuration on the WSUS Site System requires WSUS Server remoting API of version 3.0 SP2 or greater to be installed on the site server. To install the remoting API for version 3.0 SP2 run "WSUSSetup.exe console_install=1" on the site server or refer to the documentation.

    wsyncmgr.log

    WCM.log

    What I've Tried to Resolve

    • Uninstalling SUP role, had new DB instance created, and returned WSUS server back to snapshot taken after it was initially built.  Reinstalled all from beginning. (Tried this a few times)  No go
    • Verified that credentials were all correct
    • Verified that I could visit http://wsusserver:8530 - I could and received blank page - no error, though
    • Tried installing pre-reqs manually (.NET 3.5, .Net 4.5, & IIS with default features)
    • Heard that even though remote WSUS server, should have WSUS console / services installed on Primary, too.  Never heard of that, but then again never used a remote SUP server.  Trying that now.

    Any suggestions?  Thanks!


    Ben K.


    Monday, April 11, 2016 7:00 PM

Answers

  • Hi,

    Yes you must have the WSUS admin console on the Primary Site server when using a remote SUP, Configuration Manager uses the components of the WSUS admin console to configure the WSUS Server.

    And that is what is stated in the WCM.log file above as well.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    • Proposed as answer by Frank Dong Saturday, April 23, 2016 9:12 AM
    • Marked as answer by Frank Dong Monday, May 9, 2016 9:47 AM
    Monday, April 11, 2016 8:25 PM
  • Looks like the WSUS role is not past post-setup on the server you're installing the role on.

    You need to launch the WSUS console by using run as administrator and continue through the prompts to complete the post setup task. There is no need to configure WSUS, just choose the WSUS folder location and enter the SQL Server\Instance. This will complete the setup of the SUSDB on the server.

    • Proposed as answer by Frank Dong Saturday, April 23, 2016 9:12 AM
    • Marked as answer by Frank Dong Monday, May 9, 2016 9:47 AM
    Monday, April 11, 2016 11:23 PM

All replies

  • Hi,

    Yes you must have the WSUS admin console on the Primary Site server when using a remote SUP, Configuration Manager uses the components of the WSUS admin console to configure the WSUS Server.

    And that is what is stated in the WCM.log file above as well.

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    • Proposed as answer by Frank Dong Saturday, April 23, 2016 9:12 AM
    • Marked as answer by Frank Dong Monday, May 9, 2016 9:47 AM
    Monday, April 11, 2016 8:25 PM
  • Looks like the WSUS role is not past post-setup on the server you're installing the role on.

    You need to launch the WSUS console by using run as administrator and continue through the prompts to complete the post setup task. There is no need to configure WSUS, just choose the WSUS folder location and enter the SQL Server\Instance. This will complete the setup of the SUSDB on the server.

    • Proposed as answer by Frank Dong Saturday, April 23, 2016 9:12 AM
    • Marked as answer by Frank Dong Monday, May 9, 2016 9:47 AM
    Monday, April 11, 2016 11:23 PM