WSUS 3 SP1 Upgrade - Clients Not Yet Reported?

Hi Guys

Apologies if this issue has already been resolved in an earlier posting but
I'm stuffed if I can find a definitive answer yet.

Got an SBS2k3 standard server running like a dream. (workshop setup with no
clients at this stage.) It had WSUS 2 installed which worked fine. WSUS 2
advised us that WSUS 3 was available for download so we diligently approved
the download and let it install. The upgrade proceeded without issue and it
ended with the WSUS 3 wizard cranking up. (Have since learnt one is not
suppose to run the wizard on SBS platforms but it seemed like the right
thing to do at the time - lol) Ran the wizard and all appeared fine. The
SBS2k3 box continued to check for updates via WSUS 3 and advised us of any
downloads...

At this point we joined a new Win2k3 server to the domain. The Win2k3 box
joined the domain without issue and we could see in WSUS 3 that the machine
was added to the list of computers to include in updates etc. But,.... no
updates were recommended for the new Win2k3 box...? I could manually run
Windows Updates on the new Win2k3 box and see there were 30 plus updates
needed....? (As you'd expect with a brand new Microsoft product - grin)

Cranking up the new WSUS 3 program from Administrative Tools we could see
that the Win2k3 machine had a status of " Not yet reported"....?

Wading through the web (as you do), we learnt all about WSUS woes....
Checked out our Win2k3 Windowsupdate.log file and found this. (Have just
included the juicy stuff)

Server URL = http://ET2SBS2K3:8530/SimpleAuthWebS...impleAuth.asmx
2008-06-18 11:14:34:298 796 c18 PT WARNING: SyncUpdates failure, error =
0x8024400E, soap client error = 7, soap error code = 400, HTTP status code =
200
2008-06-18 11:14:34:298 796 c18 PT WARNING: SOAP Fault: 0x000190
2008-06-18 11:14:34:298 796 c18 PT WARNING: faultstring:Fault occurred
2008-06-18 11:14:34:298 796 c18 PT WARNING:
ErrorCode:InternalServerError(5)
2008-06-18 11:14:34:298 796 c18 PT WARNING: Message:(null)
2008-06-18 11:14:34:298 796 c18 PT WARNING:
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2008-06-18 11:14:34:298 796 c18 PT WARNING:
ID:539191b7-9c03-4aa0-81fe-03027373993c
2008-06-18 11:14:34:298 796 c18 PT WARNING: PTError: 0x8024400e
2008-06-18 11:14:34:298 796 c18 PT WARNING: SyncUpdates_WithRecovery
failed.: 0x8024400e
2008-06-18 11:14:34:298 796 c18 PT WARNING: Sync of Updates: 0x8024400e
2008-06-18 11:14:34:298 796 c18 PT WARNING: SyncServerUpdatesInternal
failed: 0x8024400e
2008-06-18 11:14:34:298 796 c18 Agent * WARNING: Failed to synchronize,
error = 0x8024400E
2008-06-18 11:14:34:361 796 c18 Agent * WARNING: Exit code = 0x8024400E

More searching on the error message has just left us more baffled than
ever....Looks like some kind of authentication issue with Internet
Information services on the SBS box....?

That install guide SBSWSUSv3.doc tells us not to run the WSUS 3 wizard but
it doesn't tell us what to do if you do...? Can anyone enlighten us on what
changes to WSUS 3 when you run the wizard. I would have thought there would
be a simple tweak we need to do. Reinstalling WSUS 3 as some people suggest
sounds like such a sledge hammer approach.

Thanks in advance
Mike

Mike Nash wrote:
> Hi Guys
>
> Apologies if this issue has already been resolved in an earlier posting but
> I'm stuffed if I can find a definitive answer yet.
>
> Got an SBS2k3 standard server running like a dream. (workshop setup with no
> clients at this stage.) It had WSUS 2 installed which worked fine. WSUS 2
> advised us that WSUS 3 was available for download so we diligently approved
> the download and let it install. The upgrade proceeded without issue and it
> ended with the WSUS 3 wizard cranking up. (Have since learnt one is not
> suppose to run the wizard on SBS platforms but it seemed like the right
> thing to do at the time - lol) Ran the wizard and all appeared fine. The
> SBS2k3 box continued to check for updates via WSUS 3 and advised us of any
> downloads...
>
> At this point we joined a new Win2k3 server to the domain. The Win2k3 box
> joined the domain without issue and we could see in WSUS 3 that the machine
> was added to the list of computers to include in updates etc. But,.... no
> updates were recommended for the new Win2k3 box...? I could manually run
> Windows Updates on the new Win2k3 box and see there were 30 plus updates
> needed....? (As you'd expect with a brand new Microsoft product - grin)
>
> Cranking up the new WSUS 3 program from Administrative Tools we could see
> that the Win2k3 machine had a status of " Not yet reported"....?
>
> Wading through the web (as you do), we learnt all about WSUS woes....
> Checked out our Win2k3 Windowsupdate.log file and found this. (Have just
> included the juicy stuff)
>
> Server URL = http://ET2SBS2K3:8530/SimpleAuthWebS...impleAuth.asmx
> 2008-06-18 11:14:34:298 796 c18 PT WARNING: SyncUpdates failure, error =
> 0x8024400E, soap client error = 7, soap error code = 400, HTTP status code =
> 200
> 2008-06-18 11:14:34:298 796 c18 PT WARNING: SOAP Fault: 0x000190
> 2008-06-18 11:14:34:298 796 c18 PT WARNING: faultstring:Fault occurred
> 2008-06-18 11:14:34:298 796 c18 PT WARNING:
> ErrorCode:InternalServerError(5)
> 2008-06-18 11:14:34:298 796 c18 PT WARNING: Message:(null)
> 2008-06-18 11:14:34:298 796 c18 PT WARNING:
> Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
> 2008-06-18 11:14:34:298 796 c18 PT WARNING:
> ID:539191b7-9c03-4aa0-81fe-03027373993c
> 2008-06-18 11:14:34:298 796 c18 PT WARNING: PTError: 0x8024400e
> 2008-06-18 11:14:34:298 796 c18 PT WARNING: SyncUpdates_WithRecovery
> failed.: 0x8024400e
> 2008-06-18 11:14:34:298 796 c18 PT WARNING: Sync of Updates: 0x8024400e
> 2008-06-18 11:14:34:298 796 c18 PT WARNING: SyncServerUpdatesInternal
> failed: 0x8024400e
> 2008-06-18 11:14:34:298 796 c18 Agent * WARNING: Failed to synchronize,
> error = 0x8024400E
> 2008-06-18 11:14:34:361 796 c18 Agent * WARNING: Exit code = 0x8024400E
>
> More searching on the error message has just left us more baffled than
> ever....Looks like some kind of authentication issue with Internet
> Information services on the SBS box....?
>
> That install guide SBSWSUSv3.doc tells us not to run the WSUS 3 wizard but
> it doesn't tell us what to do if you do...? Can anyone enlighten us on what
> changes to WSUS 3 when you run the wizard. I would have thought there would
> be a simple tweak we need to do. Reinstalling WSUS 3 as some people suggest
> sounds like such a sledge hammer approach.
>
> Thanks in advance
> Mike
>
>
see if that works?

The WSUS Support Team Blog : Clients stop reporting after WSUS 3.0 is
upgraded to SP1:
http://blogs.technet.com/sus/archive...ed-to-sp1.aspx

Hi Susan

Thanks for your prompt reply.

Had a look at that link. We weren't missing any virtual directories that I
could see but I ran that script regardless. (Thought I did pretty well
having never run a vbs script before...... ) Copied that example into a txt
file then renamed it rerunSelfupdateSetup.vbs From the command prompt we
navigated to the c:\program files\update services\setup folder. Then ran the
line cscript rerunSelfupdateSetup.vbs . Hope that's how you do it...? It
sure took off with zillions of files flashing past my eyes. Finished ok - I
think - grin. Well, the server still works anyway. Restarted IIs for good
luck and on the Win2k3 box ran that wuauclt /detectnow command.
Unfortunately the Win2k3 Windowsupdate.log is just the same - sniff.

Any more bright ideas out there...?
Thanks in advance

Mike

First, the wizard can be be run on SBS2k3 without problem. It *does* break
the built-in reporting in SBS2k3 R2...but if you aren't running R2 the no
worries. If you are...well, that'd break the snap-in in Server Management,
but not WSUS itself...so don't kick yourself too hard there...and don't
spend too much time figuring out if that broke anything in yuor setup. It
didn't. :)

With that said, check the WSUS documentation for the group policy settings
for WSUS3. Note that they *HAVE* changed since WSUS2, so your WSUS2
settings are very likely monkeying with you. Based on the log file, I
believe that is the problem you are having. It is still trying to connect
to some IIS tidbits that don't exist in WSUS3. It is also important to note
that you'll want to make sure your GPO is being applied to the server. Most
people set up WSUS on a domain client OU so the server never gets the proper
settings. Group Policy Results can be a real timesaver in troubleshooting
this as well.

Hope that helps,

-Cliff

"Mike Nash" <infinity.hastings@xtra.co.nz> wrote in message
news:OFCb0eO0IHA.4500@TK2MSFTNGP03.phx.gbl...
> Hi Susan
>
> Thanks for your prompt reply.
>
> Had a look at that link. We weren't missing any virtual directories that I
> could see but I ran that script regardless. (Thought I did pretty well
> having never run a vbs script before...... ) Copied that example into a
> txt file then renamed it rerunSelfupdateSetup.vbs From the command prompt
> we navigated to the c:\program files\update services\setup folder. Then
> ran the line cscript rerunSelfupdateSetup.vbs . Hope that's how you do
> it...? It sure took off with zillions of files flashing past my eyes.
> Finished ok - I think - grin. Well, the server still works anyway.
> Restarted IIs for good luck and on the Win2k3 box ran that wuauclt
> /detectnow command. Unfortunately the Win2k3 Windowsupdate.log is just the
> same - sniff.
>
> Any more bright ideas out there...?
> Thanks in advance
>
> Mike
>

Cliff Galiher wrote:
> First, the wizard can be be run on SBS2k3 without problem. It *does*
> break the built-in reporting in SBS2k3 R2...but if you aren't running R2
> the no worries. If you are...well, that'd break the snap-in in Server
> Management, but not WSUS itself...so don't kick yourself too hard
> there...and don't spend too much time figuring out if that broke
> anything in yuor setup. It didn't. :)
>
> With that said, check the WSUS documentation for the group policy
> settings for WSUS3. Note that they *HAVE* changed since WSUS2, so your
> WSUS2 settings are very likely monkeying with you. Based on the log
> file, I believe that is the problem you are having. It is still trying
> to connect to some IIS tidbits that don't exist in WSUS3. It is also
> important to note that you'll want to make sure your GPO is being
> applied to the server. Most people set up WSUS on a domain client OU so
> the server never gets the proper settings. Group Policy Results can be
> a real timesaver in troubleshooting this as well.
>
> Hope that helps,
>
> -Cliff
>
> "Mike Nash" <infinity.hastings@xtra.co.nz> wrote in message
> news:OFCb0eO0IHA.4500@TK2MSFTNGP03.phx.gbl...
>> Hi Susan
>>
>> Thanks for your prompt reply.
>>
>> Had a look at that link. We weren't missing any virtual directories
>> that I could see but I ran that script regardless. (Thought I did
>> pretty well having never run a vbs script before...... ) Copied that
>> example into a txt file then renamed it rerunSelfupdateSetup.vbs From
>> the command prompt we navigated to the c:\program files\update
>> services\setup folder. Then ran the line cscript
>> rerunSelfupdateSetup.vbs . Hope that's how you do it...? It sure took
>> off with zillions of files flashing past my eyes. Finished ok - I
>> think - grin. Well, the server still works anyway. Restarted IIs for
>> good luck and on the Win2k3 box ran that wuauclt /detectnow command.
>> Unfortunately the Win2k3 Windowsupdate.log is just the same - sniff.
>>
>> Any more bright ideas out there...?
>> Thanks in advance
>>
>> Mike
>>
>
Run the wizard, don't change the categories.

There's a specific way to run the wizard and NOT break the R2 reporting.

Hi Guys

Thanks for all your replies. Yes, it is SBS2k3 R2.

You'll probably hate me for this but I ended up restoring a ghost snap shot
of SBS system before WSUS 3 got installed. I was mucking about with
permissions in IIs and things went from bad to worse - lol. Still in the
process of downloading all the updates now. I'll run the WSUS 3 upgrade
again without the running the wizard and see what happens this time. Being
a workshop server it's a bit of a luxury to be able to mess about with these
things.

But,.... I did have another production server out there which had the exact
symptoms highlighted in that web document
http://blogs.technet.com:80/sus/arch...ed-to-sp1.aspx
It was another SBS2k3 R2 box with 30 or so clients. Both server and clients
had not reported since the WSUS 3 upgrade and the Selfupdate virtual
directory was missing in the IIs WSUS Administration web site. I was too
chicken to run that vbs script on a production server (laugh it up), so we
manually created a Selfupdate virtual directory. Presto, the SBS2k3 server
reported in immediately - woohooo. Hopefully by tomorrow all the clients
will have followed suit.

Cheers
Mike

I had this problem which was extremely frustrating on one of the pc's. I had found a fix for another problem that the pc's would not show up in WSUS if that pc had a complete reload from an image file or in this instance from a reload off the server. I found a load of commands that you can type out manually or what i done was put the commands into a .cmd file and run it off a memory stick.

I gave it a try as i had tried everything else and low and behold the problem was fixed. I hope it helps someone else. Below are the commands i put into the cmd file.

The above problem occurs when a clone is restored and the SID number remains the same from this clone. Yet when i ran the .cmd file it fixed the problem almost immediately of the pc not reporting status.


@echo off
Echo Save the batch file "AU_Clean_SID.cmd". This batch file will do the following:
Echo 1. Stop the wuauserv service
Echo 2. Delete the AccountDomainSid registry key (if it exists)
Echo 3. Delete the PingID registry key (if it exists)
Echo 4. Delete the SusClientId registry key (if it exists)
Echo 5. Restart the wuauserv service
Echo 6. Resets the Authorization Cookie
Pause
@echo on
net stop wuauserv
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v AccountDomainSid /f
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v PingID /f
REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate" /v SusClientId /f
net start wuauserv
wuauclt /resetauthorization /detectnow
Pause

Thanks, Bruce.

As far as I know, the wuaucalt /resetauthorization /detectnow alone should
work.

--
Les Connor [SBS-MVP]


____________________________
"Bruce Van Essen" wrote in message
news:20081023163419bvanessen@abbotsford.school.nz...
>I had this problem which was extremely frustrating on one of the pc's. I
>had found a fix for another problem that the pc's would not show up in WSUS
>if that pc had a complete reload from an image file or in this instance
>from a reload off the server. I found a load of commands that you can type
>out manually or what i done was put the commands into a .cmd file and run
>it off a memory stick.
>
> I gave it a try as i had tried everything else and low and behold the
> problem was fixed. I hope it helps someone else. Below are the commands i
> put into the cmd file.
>
> The above problem occurs when a clone is restored and the SID number
> remains the same from this clone. Yet when i ran the .cmd file it fixed
> the problem almost immediately of the pc not reporting status.
>
>
> @echo off
> Echo Save the batch file "AU_Clean_SID.cmd". This batch file will do the
> following:
> Echo 1. Stop the wuauserv service
> Echo 2. Delete the AccountDomainSid registry key (if it exists)
> Echo 3. Delete the PingID registry key (if it exists)
> Echo 4. Delete the SusClientId registry key (if it exists)
> Echo 5. Restart the wuauserv service
> Echo 6. Resets the Authorization Cookie
> Pause
> @echo on
> net stop wuauserv
> REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"
> /v AccountDomainSid /f
> REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"
> /v PingID /f
> REG DELETE "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate"
> /v SusClientId /f
> net start wuauserv
> wuauclt /resetauthorization /detectnow
> Pause