[sccm 2012] "remote" SUP not syncing (head bleeding profusely from banging against wall)

[basicchannel]

Hi,

I do love making life difficult for myself so I decided to install SCCM 2012 on a separate server to our WSUS server. Obviously this was fine as how frickin hard can it be for two microsoft servers to talk to each other? I've installed the WSUS server on SCCM as an SUP, made sure the ports are all correct and even installed the WSUS admin console on my SCCM server which is talking to WSUS without issue. Still I'm getting errors in my WCM.log saying "remote configuration failed on WSUS server" and "Setting new configuration state to 3 (WSUS_CONFIG_FAILED)". Has anyone successfully managed to set up this kind of thing on their production environment? I could move SCCM over to our WSUS server but that'd be too easy, and I can't believe it's this hard to use WSUS on a separate server.

 

Any ideas?

 

Many thanks

 

Update: Also forgot to mention that I have tried uninstalling and reinstalling WSUS on the SUP as suggested by other posts on the subject

Edited June 7, 2013 by basicchannel

[FN-GM]

Can you send a screen shot of the first tab on the Software Update Point Component properties.

 

Thanks

[basicchannel]

Is this the one?

[basicchannel]

I may have just found where I'm going wrong. I'll report back with updates

[basicchannel]

Nope, still failing miserably

[sparker]

Sorry to piggy back on your thread but I am trying to run SCCM on server 2012 as well but keep getting this pre req error - Configuration Manager software update points require at least Windows Server Update Services (WSUS) version 3.0 SP2. If using a remote software update point, the WSUS administration console must be installed on the site server. For more information on WSUS installation see Windows Server Update Services Home.

Gotta be a simple thing but is defeating me at the moment

 

If i try to install Admin console i just an incompatibility warning - any ideas?

[FN-GM]

Have you tried without SSL? Are you using those ports or 80 & 443?

[basicchannel]

Sorry to piggy back on your thread but I am trying to run SCCM on server 2012 as well but keep getting this pre req error - Configuration Manager software update points require at least Windows Server Update Services (WSUS) version 3.0 SP2. If using a remote software update point, the WSUS administration console must be installed on the site server. For more information on WSUS installation see Windows Server Update Services Home.

Gotta be a simple thing but is defeating me at the moment

 

If i try to install Admin console i just an incompatibility warning - any ideas?

 

Funnily I didn't get this error and the admin console wasn't installed on my server either. I got WSUS warnings but not errors. I installed the console afterwards by downloading the latest version of WSUS 3.0 and selecting the "administration console only" radio button.

[basicchannel]

Have you tried without SSL? Are you using those ports or 80 & 443?

 

Yes, done this. Definitely using 8530 and 31 on our WSUS server - this surely can't be causing issues?

 

Also in the wsyncmgr.log I'm getting the stat error

 

STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=sccm.domain.local SITE=XXX PID=2752 TID=2204 GMTDATE=Fri Jun 07 11:31:41.353 2013 ISTR0="getSiteUpdateSource" ISTR1="WSUS update source not found on site XXX. Please refer to WCM.log for configuration error details." ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0

 

I've checked the WCM.log but there's nothing useful in it

[sparker]

Actually mine is just a warning so I shall push on . I didi try to install the console but got an incompatibility notice ( Im installing on 2012) . Ill see if I can sort out my database Collation

[FN-GM]

Right, had a very similar error. Is your WSUS on Server 2012 there is a bug if you are.

[sparker]

Yes supposed to be installed as a feature so not sure why its giving me grief

[FN-GM]

Yes supposed to be installed as a feature so not sure why its giving me grief

 

Is the WSUS service running?

[basicchannel]

I'd just like to say, for the benefit of the original post, that my WSUS server is not on a 2012 box and it's still getting on my proverbials. Seriously Microsoft, how hard can this be?

[FN-GM]

I'd just like to say, for the benefit of the original post, that my WSUS server is not on a 2012 box and it's still getting on my proverbials. Seriously Microsoft, how hard can this be?

 

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?

[basicchannel]

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

[basicchannel]

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.

[basicchannel]

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.

[basicchannel]

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.