WSUS clients not registering

Hi,

Fresh install of Windows 2003 Server, installed and configured WSUS 3 with
no issues. All updates are installed and the console looks fine. I setup a
GPO to get clients to detect and report to server and then refreshed policy
on a client. No clients are detecting in the console. THere is no firewall
between the clients and the server. I have done a wuauclt /detectnow
/reportnow on a client and this is a snip of the logentry in the
<systemroot>/windowsupdate.log file:

2008-03-25 06:35:43:800 1032 9b4 PT WARNING:
CAgentUpdateManager::DetectForAllUpdates failed: 0x8024000b
2008-03-25 06:35:43:800 1032 9b4 PT WARNING: Sync of Updates: 0x8024000b
2008-03-25 06:35:43:800 1032 9b4 PT WARNING: SyncServerUpdatesInternal
failed: 0x8024000b
2008-03-25 06:35:43:800 1032 9b4 Agent * WARNING: Failed to synchronize,
error = 0x8024000B
2008-03-25 06:35:43:816 1032 9b4 Agent * WARNING: Exit code = 0x8024000B
2008-03-25 06:35:43:816 1032 9b4 Agent *********
2008-03-25 06:35:43:816 1032 9b4 Agent ** END ** Agent: Finding updates
[CallerId = WindowsUpdate]
2008-03-25 06:35:43:816 1032 9b4 Agent *************
2008-03-25 06:35:43:816 1032 9b4 Agent WARNING: WU client failed Searching
for update with error 0x8024000b
2008-03-25 06:35:43:816 1032 a28 Agent WARNING: WU client fails to call back
to search call {805A8F5E-9910-4B2F-8DB5-544230E76672} with error 0x8024000c
2008-03-25 06:36:57:922 1032 4c0 AU Triggering AU detection through
DetectNow API
2008-03-25 06:36:57:922 1032 4c0 AU Can not perform non-interactive scan if
AU is interactive-only
2008-03-25 06:43:18:524 1032 45c AU Triggering AU detection through
DetectNow API
2008-03-25 06:43:18:524 1032 45c AU Can not perform non-interactive scan if
AU is interactive-only
2008-03-25 06:54:03:151 1032 920 AU AU received policy change subscription
event
2008-03-25 06:54:15:037 1032 a48 AU Triggering AU detection through
DetectNow API
2008-03-25 06:54:15:037 1032 a48 AU Can not perform non-interactive scan if
AU is interactive-only


If anyone can help that would be appreciated, I did see a post that said the
clients will not show up in the console of the IIS website for at least 24
hours but I am not sure that is correct, reportnow and detectnow should put
them in imediately correct?

Thanks for any help

Ted

PA
Tue Mar 25 07:16:04 PDT 2008

Forwarded to WSUS newsgroup
(microsoft.public.windows.server.update_services) via crosspost as a
convenience to OP.

On the web:
http://www.microsoft.com/communities/newsgroups/list/en-us/default.aspx?dg=microsoft.public.windows.server.update_services

In your newsreader:
news://msnews.microsoft.com/microsoft.public.windows.server.update_services
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


Ted wrote:
> > Fresh install of Windows 2003 Server, installed and configured WSUS 3
> > with
> no issues. All updates are installed and the console looks fine. I setup
> a
> GPO to get clients to detect and report to server and then refreshed
> policy
> on a client. No clients are detecting in the console. THere is no
> firewall
> between the clients and the server. I have done a wuauclt /detectnow
> /reportnow on a client and this is a snip of the logentry in the
> <systemroot>/windowsupdate.log file:
>
> 2008-03-25 06:35:43:800 1032 9b4 PT WARNING:
> CAgentUpdateManager::DetectForAllUpdates failed: 0x8024000b
> 2008-03-25 06:35:43:800 1032 9b4 PT WARNING: Sync of Updates: 0x8024000b
> 2008-03-25 06:35:43:800 1032 9b4 PT WARNING: SyncServerUpdatesInternal
> failed: 0x8024000b
> 2008-03-25 06:35:43:800 1032 9b4 Agent * WARNING: Failed to synchronize,
> error = 0x8024000B
> 2008-03-25 06:35:43:816 1032 9b4 Agent * WARNING: Exit code = 0x8024000B
> 2008-03-25 06:35:43:816 1032 9b4 Agent *********
> 2008-03-25 06:35:43:816 1032 9b4 Agent ** END ** Agent: Finding updates
> [CallerId = WindowsUpdate]
> 2008-03-25 06:35:43:816 1032 9b4 Agent *************
> 2008-03-25 06:35:43:816 1032 9b4 Agent WARNING: WU client failed Searching
> for update with error 0x8024000b
> 2008-03-25 06:35:43:816 1032 a28 Agent WARNING: WU client fails to call
> back
> to search call {805A8F5E-9910-4B2F-8DB5-544230E76672} with error
> 0x8024000c
> 2008-03-25 06:36:57:922 1032 4c0 AU Triggering AU detection through
> DetectNow API
> 2008-03-25 06:36:57:922 1032 4c0 AU Can not perform non-interactive scan
> if
> AU is interactive-only
> 2008-03-25 06:43:18:524 1032 45c AU Triggering AU detection through
> DetectNow API
> 2008-03-25 06:43:18:524 1032 45c AU Can not perform non-interactive scan
> if
> AU is interactive-only
> 2008-03-25 06:54:03:151 1032 920 AU AU received policy change subscription
> event
> 2008-03-25 06:54:15:037 1032 a48 AU Triggering AU detection through
> DetectNow API
> 2008-03-25 06:54:15:037 1032 a48 AU Can not perform non-interactive scan
> if
> AU is interactive-only
>
>
> If anyone can help that would be appreciated, I did see a post that said
> the
> clients will not show up in the console of the IIS website for at least 24
> hours but I am not sure that is correct, reportnow and detectnow should
> put
> them in imediately correct?
>
> Thanks for any help
>
> Ted

Harry
Tue Mar 25 10:30:02 PDT 2008

Ted wrote:

> > Fresh install of Windows 2003 Server, installed and configured WSUS 3 > with
> no issues. All updates are installed and the console looks fine. I setup a
> GPO to get clients to detect and report to server and then refreshed policy
> on a client. No clients are detecting in the console.

Run the Client Diagnostics Tool on one of the clients and post the output here.

<http://technet.microsoft.com/en-us/wsus/bb466192.aspx>

Harry.

Ted
Tue Mar 25 17:08:00 PDT 2008

Hi Harry,

THanks for helping, this is the output of the client tool:

WSUS Client Diagnostics Tool

Checking Machine State
Checking for admin rights to run tool . . . . . . . . . PASS
Automatic Updates Service is running. . . . . . . . . . PASS
Background Intelligent Transfer Service is running. . . PASS
Wuaueng.dll version 7.0.6000.381. . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 0: Not Configured. . . . . . . . . . . . . FAIL
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Direct Connection>
Winhttp local machine Proxy. . . . . . . . . . PASS
Winhttp local machine ProxyBypass. . . . . . . PASS
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy. . . . . . . . . . . . . . . . . PASS
User IE ProxyByPass. . . . . . . . . . . . . . PASS
User IE AutoConfig URL Proxy . . . . . . . . . PASS
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
AU does not have Policy Set
AU does not have Policy Set
UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL


Thanks

"Harry Johnston [MVP]" wrote:

> Ted wrote:
>
> > > Fresh install of Windows 2003 Server, installed and configured WSUS 3 > with
> > no issues. All updates are installed and the console looks fine. I setup a
> > GPO to get clients to detect and report to server and then refreshed policy
> > on a client. No clients are detecting in the console.
>
> Run the Client Diagnostics Tool on one of the clients and post the output here.
>
> <http://technet.microsoft.com/en-us/wsus/bb466192.aspx>
>
> Harry.
>

Harry
Tue Mar 25 17:16:49 PDT 2008

Ted wrote:

> THanks for helping, this is the output of the client tool:

> Checking AU Settings
> AU Option is 0: Not Configured. . . . . . . . . . . . . FAIL
> Option is from Policy settings

> Checking Connection to WSUS/SUS Server
> AU does not have Policy Set
> AU does not have Policy Set
> UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL

Either you haven't configured the necessary group policy settings in the GPO, or
the GPO isn't being applied to the client.

You can type gpresult at the command line to see which GPOs are being applied.

Harry.

Ted
Tue Mar 25 20:07:01 PDT 2008

Harry,

Thanks so much the link wasnt enabled on the policy...it is pulling back
clients and registering them now....thanks for the great troubleshooting
tools link...sorry to be such a bonehead :)

Ted

"Harry Johnston [MVP]" wrote:

> Ted wrote:
>
> > THanks for helping, this is the output of the client tool:
>
> > Checking AU Settings
> > AU Option is 0: Not Configured. . . . . . . . . . . . . FAIL
> > Option is from Policy settings
>
> > Checking Connection to WSUS/SUS Server
> > AU does not have Policy Set
> > AU does not have Policy Set
> > UseWuServer is disabled . . . . . . . . . . . . . . . . FAIL
>
> Either you haven't configured the necessary group policy settings in the GPO, or
> the GPO isn't being applied to the client.
>
> You can type gpresult at the command line to see which GPOs are being applied.
>
> Harry.
>

Harry
Wed Mar 26 11:55:24 PDT 2008

Ted wrote:

> Thanks so much the link wasnt enabled on the policy...it is pulling back
> clients and registering them now....thanks for the great troubleshooting
> tools link...sorry to be such a bonehead :)

You're welcome. Thanks for letting us know the problem has been resolved.

Harry.