This Computer has not reported status yet

Hello, I am having problems with a few clients running XP Pro SP 2 that are
not reporting in into WSUS.

They show up as clients in WSUS but are not showing their Status Report. I
have tried all the following: disjoining the computer from the domain.
Renaming the computer, using the wsuaclt /resetauthorization /detectnow
commands (which do work) after removing the client and readding it.

I am running WSUS 3.0 SP1. This is only happening to a handful of clients.
All computers are receiving their group policy correctly etc. I have also run
the WSUS client diagnostic tool and every thing passes.

I am truly stumped on these machines. I can see other people out there have
had this problem but there seems no remedy to the issue.

Any ideas or help is greatly appreciated!

Regards,
Brandon

Does anyone know where to start troublshooting this issue? I have also done a

Right pew, wrong church. 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...pdate_services

In your newsreader:
news://msnews.microsoft.com/microsof...pdate_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/

bzumwalt99 wrote:
> Hello, I am having problems with a few clients running XP Pro SP 2 that
> are
> not reporting in into WSUS.
>
> They show up as clients in WSUS but are not showing their Status Report. I
> have tried all the following: disjoining the computer from the domain.
> Renaming the computer, using the wsuaclt /resetauthorization /detectnow
> commands (which do work) after removing the client and readding it.
>
> I am running WSUS 3.0 SP1. This is only happening to a handful of clients.
> All computers are receiving their group policy correctly etc. I have also
> run the WSUS client diagnostic tool and every thing passes.
>
> I am truly stumped on these machines. I can see other people out there
> have
> had this problem but there seems no remedy to the issue.
>
> Any ideas or help is greatly appreciated!
>
> Regards,
> Brandon
>
> Does anyone know where to start troublshooting this issue? I have also
> done
> a

I recommend looking at WindowsUpdate.log file in %WINDIR% on the clients
having problems.
As others have suggested before, if your machines have been cloned, run this
script: http://msmvps.com:80/blogs/athif/pages/66376.aspx

/Thomas


"PA Bear [MS MVP]" <> wrote in message
news:%...
> Right pew, wrong church. 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...pdate_services
>
> In your newsreader:
> news://msnews.microsoft.com/microsof...pdate_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/
>
> bzumwalt99 wrote:
>> Hello, I am having problems with a few clients running XP Pro SP 2 that
>> are
>> not reporting in into WSUS.
>>
>> They show up as clients in WSUS but are not showing their Status Report.
>> I
>> have tried all the following: disjoining the computer from the domain.
>> Renaming the computer, using the wsuaclt /resetauthorization /detectnow
>> commands (which do work) after removing the client and readding it.
>>
>> I am running WSUS 3.0 SP1. This is only happening to a handful of
>> clients.
>> All computers are receiving their group policy correctly etc. I have also
>> run the WSUS client diagnostic tool and every thing passes.
>>
>> I am truly stumped on these machines. I can see other people out there
>> have
>> had this problem but there seems no remedy to the issue.
>>
>> Any ideas or help is greatly appreciated!
>>
>> Regards,
>> Brandon
>>
>> Does anyone know where to start troublshooting this issue? I have also
>> done
>> a
>

>
> bzumwalt99 wrote:
> > Hello, I am having problems with a few clients running XP Pro SP 2 that
> > are
> > not reporting in into WSUS.
>
> > They show up as clients in WSUS but are not showing their Status Report. I
> > have tried all the following: disjoining the computer from the domain.
> > Renaming the computer, using the wsuaclt /resetauthorization /detectnow
> > commands (which do work) after removing the client and readding it.
>
> > I am running WSUS 3.0 SP1. This is only happening to a handful of clients.
> > All computers are receiving their group policy correctly etc. I have also
> > run the WSUS client diagnostic tool and every thing passes.
>
> > I am truly stumped on these machines. I can see other people out there
> > have
> > had this problem but there seems no remedy to the issue.
>
> > Any ideas or help is greatly appreciated!
>
> > Regards,
> > Brandon
>
> > Does anyone know where to start troublshooting this issue? I have also
> > done
> > a- Hide quoted text -
>
> - Show quoted text -
First make sure your policy says it is pointing to the correct wsus
box by running a rsop.
Try the following at the client end:

cd c:\windows\system32\
ipconfig /flushdns
ipconfig /registerdns
nbtstat -R
net stop "Automatic Updates"
net stop "BITS"
net start "Automatic Updates"
net start "BITS"
wuauclt /detectnow
wuauclt /reportnow

btw you can use psexec to run this from the server to the clients as a
batch process. handy script that solves alot of wsus related issues.

"mackdaddy315" <> wrote in message
news:43933a5f-0f26-4b85-a09b-...

>> > Hello, I am having problems with a few clients running XP Pro SP 2 that
>> > are
>> > not reporting in into WSUS.
>>
>> > They show up as clients in WSUS but are not showing their Status
>> > Report. I
>> > have tried all the following: disjoining the computer from the domain.
>> > Renaming the computer, using the wsuaclt /resetauthorization /detectnow
>> > commands (which do work) after removing the client and readding it.

> First make sure your policy says it is pointing to the correct wsus
> box by running a rsop.

Or using the Client Diagnostic Tool, which is the *correct* Step 1 in any
client-side diagnostic process..

Or inspecting the WindowsUpdate.log which logs the configured server about
every tenth line one way or another.

But we already know the server URL is correct, or they would not have even
=registered= with the WSUS Server, -- which they already did.

> Try the following at the client end:
>

As for this script, I'm not sure where it came from, but it's pretty much
trash.

> cd c:\windows\system32\
> ipconfig /flushdns

Flushing the DNS cache is pointless -- the clients have already registered
with the WSUS Server. DNS is correct.

> ipconfig /registerdns

Refreshing the DHCP lease and re-registering the client's hostname in DNS
does nothing to address this issue.

> nbtstat -R

Reloading the NetBios name cache is pointless. This is a TCP/IP application.

> net stop "Automatic Updates"
> net stop "BITS"
> net start "Automatic Updates"
> net start "BITS"

Restarting BITS is useless.
Restarting Automatic Updates only has benefit if the registry has been
edited and has new configuration values.

> wuauclt /detectnow
> wuauclt /reportnow

/reportnow is an invalid switch,

and the O.P. already stated that 'wuauclt /resetauthorization /detectnow'
was successfully executed.

> btw you can use psexec to run this from the server to the clients as a
> batch process. handy script that solves alot of wsus related issues.

Throw this script away. It does nothing of substance except initiate a
detection event.

The *CORRECT* next step based on the description provided is:
Inspect the %windir%\WindowsUpdate.log to determine why the client has
registered but is not reporting.

--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

> /reportnow is an invalid switch,

What about the post from "Cecil [MSFT]" in this thread?
http://groups.google.se/group/micros...ae65925a?hl=en
or
http://tinyurl.com/5f9w32


Regards
Rolf Lidvall
Swedish Radio (Ltd)

"Rolf Lidvall" <no_direct_email@me> wrote in message
news:%...
>> /reportnow is an invalid switch,
>
> What about the post from "Cecil [MSFT]" in this thread?
> http://groups.google.se/group/micros...ae65925a?hl=en
> or
> http://tinyurl.com/5f9w32

wuauclt /detectnow

will also send the events to the server.

There really seems to be no point to the /reportnow switch, assuming it even
actually does anything.

To my knowledge, it's still undocumented, either way



--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

I have the same problem "has not reported status yet". I have search all the
froums and no one has an answer. IS there an answer from Microsoft?

Thanks Jeremy

"Lawrence Garvin" wrote:

> "Rolf Lidvall" <no_direct_email@me> wrote in message
> news:%...
> >> /reportnow is an invalid switch,
> >
> > What about the post from "Cecil [MSFT]" in this thread?
> > http://groups.google.se/group/micros...ae65925a?hl=en
> > or
> > http://tinyurl.com/5f9w32
>
> wuauclt /detectnow
>
> will also send the events to the server.
>
> There really seems to be no point to the /reportnow switch, assuming it even
> actually does anything.
>
> To my knowledge, it's still undocumented, either way
>
>
>
> --
> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> Senior Data Architect, APQC, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2008)
>
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin
>

"jeps" <> wrote in message
news:5EBC6056-B9AD-49B8-85EE-...
>I have the same problem "has not reported status yet". I have search all
>the
> froums and no one has an answer. IS there an answer from Microsoft?

"Has not reported status yet" generally means that something is broken on
the client side.

Next step is to inspect the WindowsUpdate.log for error messages that
provide additional details.


--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Senior Data Architect, APQC, Houston, Texas
Microsoft MVP - Software Distribution (2005-2008)

MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin

On Jul 30, 10:35*pm, "Lawrence Garvin" <ons...@postalias.news> wrote:
> "jeps" <j...@discussions.microsoft.com> wrote in message
>
> news:5EBC6056-B9AD-49B8-85EE-...
>
> >I have the same problem "has not reported status yet". I have search all
> >the
> > froums and no one has an answer. IS there an answer from Microsoft?
>
> "Has not reported status yet" generally means that something is broken on
> the client side.
>
> Next step is to inspect the WindowsUpdate.log for error messages that
> provide additional details.
>
> --
> Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
> Senior Data Architect, APQC, Houston, Texas
> Microsoft MVP - Software Distribution (2005-2008)
>
> MS WSUS Website:http://www.microsoft.com/wsus
> My Websites:http://www.onsitechsolutions.com;htt...hsolutions.com
> My MVP Profile:http://mvp.support.microsoft.com/pro...awrence.Garvin


HEreis the log

2008-07-31 10:28:21+0100 1176 4a8 PT: Using serverID {3DA21691-
E39D-4DA6-8A4B-B43877BCB1B7}
2008-07-31 10:28:21+0100 1176 4a8 Failed to obtain cached cookie with
hr = 80248008.
2008-07-31 10:28:21+0100 1176 4a8 Failed to upload events with hr =
80248008.
2008-07-31 10:33:21+0100 3252 63c Out of proc datastore is shutting
down
2008-07-31 10:33:22+0100 3252 63c Out of proc datastore is now
inactive
2008-07-31 10:38:21+0100 1176 bf4 Successfully opened event cache file
at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E0 68-2F58-4EE1-8D01-
DA9354B01DE5}.bin for reading.
2008-07-31 10:38:21+0100 132 404 Trying to make out of proc datastore
active
2008-07-31 10:38:22+0100 132 404 Out of proc datastore is now active
2008-07-31 10:38:22+0100 1176 bf4 PT: Using serverID {3DA21691-
E39D-4DA6-8A4B-B43877BCB1B7}
2008-07-31 10:38:22+0100 1176 bf4 Failed to obtain cached cookie with
hr = 80248008.
2008-07-31 10:38:22+0100 1176 bf4 Failed to upload events with hr =
80248008.
2008-07-31 10:40:10+0100 1176 49c Service received connect
notification
2008-07-31 10:40:10+0100 1176 cc8 AU received event of 3
2008-07-31 10:40:18+0100 1176 49c Service received disconnect
notification
2008-07-31 10:40:18+0100 1176 cc8 AU received event of 3
2008-07-31 10:40:18+0100 1176 49c Service received connect
notification
2008-07-31 10:40:18+0100 1176 cc8 AU received event of 3
2008-07-31 10:40:19+0100 1176 49c Service received logon notification
2008-07-31 10:40:19+0100 1176 cc8 AU received event of 3
2008-07-31 10:40:53+0100 3376 808 CreateObject for
Microsoft.Update.AgentInfo failed: error 0x800401f3
2008-07-31 10:40:53+0100 1176 544 WU client succeeds
CClientCallRecorder::EnumerateService
2008-07-31 10:45:53+0100 132 404 Out of proc datastore is shutting
down
2008-07-31 10:45:54+0100 132 404 Out of proc datastore is now
inactive
2008-07-31 10:48:22+0100 1176 77c Successfully opened event cache file
at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E0 68-2F58-4EE1-8D01-
DA9354B01DE5}.bin for reading.
2008-07-31 10:48:22+0100 2096 4ac Trying to make out of proc datastore
active
2008-07-31 10:48:22+0100 2096 4ac Out of proc datastore is now active
2008-07-31 10:48:22+0100 1176 77c PT: Using serverID {3DA21691-
E39D-4DA6-8A4B-B43877BCB1B7}
2008-07-31 10:48:22+0100 1176 77c Failed to obtain cached cookie with
hr = 80248008.
2008-07-31 10:48:22+0100 1176 77c Failed to upload events with hr =
80248008.
2008-07-31 10:53:22+0100 2096 4ac Out of proc datastore is shutting
down
2008-07-31 10:53:24+0100 2096 4ac Out of proc datastore is now
inactive
2008-07-31 10:58:22+0100 1176 77c Successfully opened event cache file
at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E0 68-2F58-4EE1-8D01-
DA9354B01DE5}.bin for reading.
2008-07-31 10:58:23+0100 3688 ddc Trying to make out of proc datastore
active
2008-07-31 10:58:23+0100 3688 ddc Out of proc datastore is now active
2008-07-31 10:58:23+0100 1176 77c PT: Using serverID {3DA21691-
E39D-4DA6-8A4B-B43877BCB1B7}
2008-07-31 10:58:23+0100 1176 77c Failed to obtain cached cookie with
hr = 80248008.
2008-07-31 10:58:23+0100 1176 77c Failed to upload events with hr =
80248008.
2008-07-31 11:03:23+0100 3688 ddc Out of proc datastore is shutting
down
2008-07-31 11:03:24+0100 3688 ddc Out of proc datastore is now
inactive
2008-07-31 11:08:23+0100 1176 da4 Successfully opened event cache file
at C:\WINDOWS\SoftwareDistribution\EventCache\{FF08E0 68-2F58-4EE1-8D01-
DA9354B01DE5}.bin for reading.
2008-07-31 11:08:23+0100 4060 ab4 Trying to make out of proc datastore
active
2008-07-31 11:08:24+0100 4060 ab4 Out of proc datastore is now active
2008-07-31 11:08:24+0100 1176 da4 PT: Using serverID {3DA21691-
E39D-4DA6-8A4B-B43877BCB1B7}
2008-07-31 11:08:24+0100 1176 da4 Failed to obtain cached cookie with
hr = 80248008.
2008-07-31 11:08:24+0100 1176 da4 Failed to upload events with hr =
80248008.

here is Client Diag
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 5.4.3790.5512 . . . . . . . . . . . PASS
This version is WSUS 2.0

Checking AU Settings
AU Option is 3 : Notify Prior to Install. . . . . . . . PASS
Option is from Policy settings

Checking Proxy Configuration
Checking for winhttp local machine Proxy settings . . . PASS
Winhttp local machine access type
<Using Proxy>
Winhttp local machine Proxy
xxxxxxxx
Winhttp local machine ProxyBypass
:8080
Checking User IE Proxy settings . . . . . . . . . . . . PASS
User IE Proxy
http=192.xxx.x.xx:8080;https=192.xxx.x..xx:
8080;ftp=192.xxx.x.
8080;gopher=192.xxx.x.xx:8080
User IE ProxyByPass
192.168.0.*;<local>
User IE AutoConfig URL Proxy . . . . . . . . . NONE
User IE AutoDetect
AutoDetect not in use

Checking Connection to WSUS/SUS Server
WUServer = http://xxxxxxx
WUStatusServer = http://xxxxxx
UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
Connection to server. . . . . . . . . . . . . . . . . . PASS
SelfUpdate folder is present. . . . . . . . . . . . . . PASS