Comments on: SCCM and WSUS issues

By: Matt

Matt — Tue, 24 Nov 2009 01:24:58 +0000

I had this issue with the Unspecified Error. This server is a SCCM 2007 R2 box with all of the roles installed on the same box. To resolve this issue I needed to do the following two things: Install an SSL certificate on the WSUS IIS Site with the Primary Name set to the FQDN of my server and then configure the proxy settings of the SCCM Software Update Point to be the FQDN of my server with a port of 8531.

Microsoft has made SCCM overly complicated for no reason. This whole product could be so much simpler…

By: Laljeev M

Laljeev M — Tue, 30 Dec 2008 12:22:16 +0000

Above document helped me to troubleshoot, in my case what I did was removed SSL port (8531)from IIS SUS website and it started working fine.

Thanks

By: EBE

EBE — Tue, 09 Sep 2008 15:14:42 +0000

Hello

I had the same problems.. but different solution which other founds usefull also

-> add a IIS certificate for 8531 port.
-> REBOOT (REBOOT ! don’t hesitate:)

start a Run synch from Software update repository..

Look at Wsyncmgr.log.. to my lab it’s started working !

Hope this will help

EBE

By: Mark Raybone

Mark Raybone — Thu, 07 Aug 2008 15:19:59 +0000

I'm suffering from a similar problem, but can't get my head around what's going on. I've followed the guides and the links that were pasted. My WSYNCMGR.LOG shows the following: (I've altered some details but they are consistent throughout the logs)

Found local sync request in site contol file
Performing sync on local request
STATMSG: ID=6701 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SERVER SITE=SMS PID=2912 TID=2556 GMTDATE=Thu Aug 07 14:56:15.520 2008 ISTR0="" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Sync failed: WSUS server not configured. Source: CWSyncMgr::DoSync
STATMSG: ID=6703 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_SYNC_MANAGER" SYS=SERVER SITE=SMS PID=2912 TID=2556 GMTDATE=Thu Aug 07 15:01:15.606 2008 ISTR0="CWSyncMgr::DoSync" ISTR1="WSUS server not configured" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
Sync failed. Will retry in 60 minutes
Sync time: 0d00h04m59s
Waiting 60 minutes for requests...

I'm seeing this in my IIS log...

2008-08-07 15:04:26 W3SVC1045235440 1.1.1.1 POST /ApiRemoting30/WebService.asmx - 8530 - 1.1.1.1 Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+2.0.50727.1433) 401 1 0

I'm not sure what I should be looking for in my Security logs, they aren't making much sense to me. Any ideas? :-| Cheers, MRaybone.

By: Jarvis

Jarvis — Wed, 16 Jul 2008 13:04:19 +0000

You are correct Christian…and thanks for the plug for my “cmd prompt as system” post!

Also…if you are running on Server 2008, you will be better off looking at the other post that is referenced on the first line of this post…it is much more relevant.

By: Christian

Christian — Wed, 16 Jul 2008 12:25:47 +0000

We had a similar issue, Proxy authentication failed error 407.

We had to remove “automatically detect settings” from IE connection, for the system settings. -> Launch Internet Explorer as system, remove “Automatically detect settings” from the IE connenction settings. We had to do this to prevent WPAD configuration being applied

If you are running SCCM on Server 2008 check this out for how to launch IE as system: http://verbalprocessor.com/2007/12/05/running-a-cmd-prompt-as-local-system/

By: Nag

Nag — Fri, 27 Jun 2008 01:12:01 +0000

Today I had the same issue(SMS WSUS Synchronization failed.
Message: WSUS server not configured.
Source: CWSyncMgr::DoSync.
The operating system reported error 2147500037: Unspecified error ) I was able to overcome this. The name in the proxy was not matching (FQDN) what was in DNS ( I pinged the proxy name from the command prompt). Later, I added an entry in the host file which had the host name (present in proxy) and IP address ( from the ping result). That worked. Now, SCCM server is able to sync.

By: Jarvis

Jarvis — Fri, 30 May 2008 14:45:14 +0000

That has potential. If that works…and is that easy…I feel like a bit of a dope for not trying it myself already.

By: Shanti Lindström

Shanti Lindström — Fri, 30 May 2008 14:34:54 +0000

The host file was a creative work around, if you don´t want to use the host file.

1. Open the IIS Manager go to the folder “Web Sites” look at “Administration of WSUS”. HTTP port 8530 and HTTPS (SSL) port is 8531.

After that, change the IP Address from *All Unassigned* to the server Address.
2. Right click on the “Administration of WSUS” and chose Properties. Chose the IP from the list box.

And you’re done.

HTH
God luck

By: jrensink78

jrensink78 — Wed, 09 Jan 2008 17:31:30 +0000

I’m having the same problem myself. I’m not sure that I can implement this solution, since the autoproxy wpad.dat file specifies the IP of our proxy server and not the name. So I don’t think there’s a way to trick the SCCM/WSUS server using the HOSTS file.

Does anyone know a workaround for a situation like this?

Maybe see if I can get the OK to create a separate WPAD file for the atuoproxy entry on this subnet and use hosts names in that one. Than I should be able to use the HOSTS file trick. Otherwise, possibly get rid of the autoproxy entry altogether. We are pushing out proxy settings to clients using a GPO anyways. This shouldn’t really need to be there. Especially since it’s a server-only subnet.