WSUS Still No Status **Fixed**

Windowsupdate.log file I had several of the following errors:

WARNING: SyncUpdates failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200

WARNING: SOAP Fault: 0x00012c
WARNING: faultstring:Fault occurred
WARNING: ErrorCode:ConfigChanged(2)
WARNING: Message:(null)


With some research I stumbled across this having to do with SCCM being setup with SUP. Now if you've gone through my older posts you'd see that I had that role at one point and removed it. Well it apparently set the WSUS reporting to none so here is a link to the tool that will fix it.

WSUS Reporting Level

Basically run it at command prompt and select 1 for All. After I did this

WSUS Can't connect to Server:Port

Well This post should be before the one below this but the way WSUS was setup here before me was to use port 80. After the crash and the reinstall I had to run the following Script from cmd or run.: cscript c:\Program Files\Update Services\InstallSelfUpdateOnPort80.vbs

After that I was able to connect to http://My-WSUS-Server/iuident.cab and download the file.

WSUS Clients status not yet reported

Well about two days ago our WSUS server had crashed and I pretty much had to reload it. Now the problem I'm having is that all of the clients show as not yet reported. I've checked a couple things and first problem I found was the Virtual Directory named Selfupdate was not in IIS. I had to create that myself and set the rights and paths as follows:

Directory: %ProgramFiles%Update Services\SelfUpdate

Security: Anonymous Access Enabled

Now that is all that I found and it seems there is more to it. You also have to set

Security: Like above but also set Integrated Windows Authentication.

Execute Permissions: Scripts Only

From a client Computer I ran the folowing command:

wuauclt /resetauthorization /detectnow

Before I did the above the log file c:\windows\windowsupdate.log had the following errors/warnings

Cached cookie has expired or a new PID is available

Once I set all the above my client had connected and downloaded new updates. A good link to follow is

IIS Settings For WSUS

SUP Role In SCCM 2007 Sync Error

Ok now maybe I over looked some steps but I have gone back and forth with tons of trys/fixes and I think I finally found the answer. My site is setup like this: Already in place WSUS and a new SCCM2007 server. Here is what I have found and it seems like that is how I was trying to set it up

Server 1 (SCCM) is the server server with WSUS admin console

Server 2 (WSUS) is the WSUS server

On WSUS, add SCCM as a local admin (don't need to do anything else)

On SCCM, ADD a NEW server:

* Name is WSUS

* Specify the WSUS server FQDN

* The only role is SUP

* Make it an active SUP

* Sync with Microsoft Update

* Set the rest of the parameters as desired


So It seems I was trying to add the role to my site server instead of the WSUS server. I never thought to add another server under the site systems. ::Slaps face::
Anyway I'm checking my log file now and its at 96% synching!! woo hoo!