+ Post New Thread
Page 2 of 2 FirstFirst 12
Results 16 to 19 of 19
O/S Deployment Thread, "remote" SUP not syncing (head bleeding profusely from banging against wall) in Technical; Originally Posted by FN-GM Just migrated mine onto a new server and worked first time. There must be something wrong. ...
  1. #16
    basicchannel's Avatar
    Join Date
    May 2010
    Location
    Norfolk, UK
    Posts
    279
    Thank Post
    36
    Thanked 22 Times in 14 Posts
    Blog Entries
    1
    Rep Power
    23
    Quote Originally Posted by FN-GM View Post
    Just migrated mine onto a new server and worked first time. There must be something wrong. I would try reinstalling your SUP role.

    Is your SCCM install and server fully patched up?
    Yes, I'm pretty sure everything is up to date, although I will check this.

    What I'm going to do is uninstall re-install WSUS role, and install it under the default IIS website and ports 80/443 (basically follow these win-noob isntructions. I'll then try adding the SUP role again on my SCCM server and try syncing. I'll report back on how it went.

    Cheers

  2. #17
    basicchannel's Avatar
    Join Date
    May 2010
    Location
    Norfolk, UK
    Posts
    279
    Thank Post
    36
    Thanked 22 Times in 14 Posts
    Blog Entries
    1
    Rep Power
    23
    I'm completely on the verge of giving this up (and I don't give up very easily). I uninstalled and re-installed the WSUS role (which was a pain in itself as something always goes wrong) uninstalled and re-installed the SUP role, made sure the WSUS server was all patched up and that my SCCM server was. I also changed the WSUS ports to 80 443 and it still is saying WSUS config failed. My elation at finally getting SCCM up and running and working has now been eclipsed by this. I'm now going to install SCCM on the WSUS server which a lot of people said should happen in the first place, but what annoys me is that it shouldn't be this difficult to get a Microsoft SCCM server and a WSUS server to talk to each other.

  3. #18
    basicchannel's Avatar
    Join Date
    May 2010
    Location
    Norfolk, UK
    Posts
    279
    Thank Post
    36
    Thanked 22 Times in 14 Posts
    Blog Entries
    1
    Rep Power
    23
    OK, determined not to give up now. I went away and had a breather and feel better about it. I'm going to put WSUS on a VM as it's dedicated server with a completely clean install of Server 2008 R2 and try that way. I'm a bit concerned our current WSUS server might be a bit worse for wear, or at least SCCM doesn't like it. I was getting all sorts of errors on my current WSUS server and it wasn't uninstalling cleanly it seemed so perhaps that was half the problem.

  4. #19
    basicchannel's Avatar
    Join Date
    May 2010
    Location
    Norfolk, UK
    Posts
    279
    Thank Post
    36
    Thanked 22 Times in 14 Posts
    Blog Entries
    1
    Rep Power
    23
    Just wanted to say I managed to fix this after hours of re-installing and head banging. The main issue was the WSUS version errors I was receiving in my WCM.log which I couldn't get my head around because I was certain the KB updates WSUS-KB2720211-x64.exe and WSUS-KB2734608-x64.exe had been installed. The errors in my WCM log were:

    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) 11/06/2013 17:16:44 5024 (0x13A0)
    Checking runtime v2.0.50727... 11/06/2013 17:16:44 5024 (0x13A0)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration. 11/06/2013 17:16:44 5024 (0x13A0)
    Checking runtime v4.0.30319... 11/06/2013 17:16:44 5024 (0x13A0)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration. 11/06/2013 17:16:44 5024 (0x13A0)
    Supported WSUS version not found 11/06/2013 17:16:44 5024 (0x13A0)
    STATMSG: ID=6607 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=sccm.server.local SITE=XXX PID=2924 TID=5024 GMTDATE=Tue Jun 11 16:16:44.956 2013 ISTR0="wsus.server.local" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 11/06/2013 17:16:44 5024 (0x13A0)
    Remote configuration failed on WSUS Server. 11/06/2013 17:16:44 5024 (0x13A0)
    STATMSG: ID=6600 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=sccm.server.local SITE=XXX PID=2924 TID=5024 GMTDATE=Tue Jun 11 16:16:44.957 2013 ISTR0="wsus.server.local" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 11/06/2013 17:16:44 5024 (0x13A0)
    Setting new configuration state to 3 (WSUS_CONFIG_FAILED) 11/06/2013 17:16:44 5024 (0x13A0)
    What I didn't realise was the WSUS it was referring to was the admin console on my SCCM 2012 server, not the WSUS server. I also applied the updates to my SCCM server and reinstalled the SUP role and bingo.

    So for anyone else getting these errors, try this out.

SHARE:
+ Post New Thread
Page 2 of 2 FirstFirst 12

Similar Threads

  1. smartcache not syncing
    By IanT in forum Wireless Networks
    Replies: 3
    Last Post: 15th January 2010, 10:55 PM
  2. REMOTE DESKTOP WILL NOT LOAD
    By bart21 in forum Windows
    Replies: 7
    Last Post: 10th November 2009, 09:47 PM
  3. DC Servers not Sync'ing
    By Nick_Parker in forum Windows Server 2008
    Replies: 6
    Last Post: 19th May 2009, 04:42 PM
  4. user not syncing with time server
    By techie211 in forum Windows Server 2000/2003
    Replies: 5
    Last Post: 19th March 2009, 07:28 PM
  5. Clock on PC's not syncing
    By dezt in forum Wireless Networks
    Replies: 11
    Last Post: 6th November 2006, 10:09 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •