Re: This Computer has not reported status yet

PA Bear [MS MVP]

unread,

Jun 25, 2008, 8:09:13 PM6/25/08

to

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/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/

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

Thomas

unread,

Jun 25, 2008, 11:25:14 PM6/25/08

to

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]" <PABe...@gmail.com> wrote in message
news:%23bS4SEy...@TK2MSFTNGP06.phx.gbl...

mackdaddy315

unread,

Jun 29, 2008, 9:15:55 AM6/29/08

to

>
> 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.

Lawrence Garvin

unread,

Jun 30, 2008, 7:50:32 AM6/30/08

to

"mackdaddy315" <mackda...@hotmail.com> wrote in message
news:43933a5f-0f26-4b85...@34g2000hsf.googlegroups.com...

>> > 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/profile/Lawrence.Garvin

Rolf Lidvall

unread,

Jul 7, 2008, 9:58:29 AM7/7/08

to

> /reportnow is an invalid switch,

What about the post from "Cecil [MSFT]" in this thread?
http://groups.google.se/group/microsoft.public.windows.server.update_services/browse_thread/thread/ec9c50044da6374f/ef826189ae65925a?hl=en
or
http://tinyurl.com/5f9w32

Regards
Rolf Lidvall
Swedish Radio (Ltd)

Lawrence Garvin

unread,

Jul 8, 2008, 8:32:03 PM7/8/08

to

"Rolf Lidvall" <no_direct_email@me> wrote in message
news:%23w5hLmD...@TK2MSFTNGP04.phx.gbl...

>> /reportnow is an invalid switch,
>
> What about the post from "Cecil [MSFT]" in this thread?
> http://groups.google.se/group/microsoft.public.windows.server.update_services/browse_thread/thread/ec9c50044da6374f/ef826189ae65925a?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

jeps

unread,

Jul 30, 2008, 9:41:01 AM7/30/08

to

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

unread,

Jul 30, 2008, 5:35:58 PM7/30/08

to

"jeps" <je...@discussions.microsoft.com> wrote in message
news:5EBC6056-B9AD-49B8...@microsoft.com...

>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.

jwc...@gmail.com

unread,

Jul 31, 2008, 6:15:44 AM7/31/08

to

On Jul 30, 10:35 pm, "Lawrence Garvin" <ons...@postalias.news> wrote:
> "jeps" <j...@discussions.microsoft.com> wrote in message

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\{FF08E068-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\{FF08E068-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\{FF08E068-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\{FF08E068-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

jwc...@gmail.com

unread,

Jul 31, 2008, 6:22:18 AM7/31/08

to

> WUStatusServer =http://xxxxxx

> UseWuServer is enabled. . . . . . . . . . . . . . . . . PASS
> Connection to server. . . . . . . . . . . . . . . . . . PASS

> SelfUpdate folder is present. . . . . . . . . . . . . . PASS- Hide quoted text -

>
> - Show quoted text -

The Client Diag show Wuaueng.dll version

5.4.3790.5512 . . . . . . . . . . . PASS
This version is WSUS 2.0

IS this coreect but I am using WSUS3.0

Jeremy

DaveMills

unread,

Jul 31, 2008, 11:55:31 AM7/31/08

to

--
Dave Mills
There are 10 type of people, those that understand binary and those that don't.

DaveMills

unread,

Jul 31, 2008, 12:02:44 PM7/31/08

to

Looks to me like the client is not talking to the server at all. Since you have
editing all the server name and ip addresses you may have edited out the cause
of the problem. Quite often the problem is because of an incorrect server
specification in the GPO, an extra dot or some other simple error like a
trailing \
It also looks like the WSUS client is trying to use a proxy. Is the bypass IP
mask correct.

The client has not updated to WSUS 3

On Thu, 31 Jul 2008 03:22:18 -0700 (PDT), jwc...@gmail.com wrote:

Harry Johnston [MVP]

unread,

Jul 31, 2008, 4:16:38 PM7/31/08

to

jwc...@gmail.com wrote:

> 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

Given these settings, the WUA will be trying to access the WSUS server via the
proxy. Might the proxy be blocking access?

Harry.

--
Boycott Beijing 2008 http://www.rsf.org/rubrique.php3?id_rubrique=174

jwc...@gmail.com

unread,

Jul 31, 2008, 7:11:02 PM7/31/08

to

On 31 Jul, 21:16, "Harry Johnston [MVP]" <ha...@scms.waikato.ac.nz>
wrote:

Hi Harry
The Wsus is also the proxy server. But isn't the proxy being by passed
for local networks. All the clients are showing up with the orange
triangle except for 2 showing the red round symbol with a cross when
hightlighted it says not reported status for 289 or more days and 189
or more days respectively. So they must be able to contact the wsus. I
do not understand why the proxy is blocking access.

Jeremy

jwc...@gmail.com

unread,

Jul 31, 2008, 7:21:46 PM7/31/08

to

> There are 10 type of people, those that understand binary and those that don't.- Hide quoted text -

>
> - Show quoted text -

Dear Dave

You can see they are all passes. The clients are showing up in the
WSUS as orange traiagles and red circles. SO they must be touching
base with WSUS.
The setup is WSUS 3 is runnig on a Windows 2003 Server Sp2. The Proxy
server is on the same server.

Thansk
Jeremy

Harry Johnston [MVP]

unread,

Jul 31, 2008, 8:02:38 PM7/31/08

to

jwc...@gmail.com wrote:

>>> 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

> The Wsus is also the proxy server. But isn't the proxy being by passed
> for local networks.

The ProxyBypass setting has nothing in it but :8080. I'm no expert in Winhttp
proxy settings, but that certainly doesn't look right if you're expecting it to
bypass the local network.

It would help if you could post the actual output. But perhaps if you look at
these settings, particularly if you compare them to one on a machine that is
working, the problem may be obvious.

... you realise the Winhttp settings are distinct from the user settings? For
everything to work properly, both have to be set correctly, but the Winhttp
settings are the ones relevant to the errors appearing in the log.

DaveMills

unread,

Jul 31, 2008, 11:08:37 PM7/31/08

to

On Thu, 31 Jul 2008 16:21:46 -0700 (PDT), jwc...@gmail.com wrote:

>> - Show quoted text -
>
>Dear Dave
>
>You can see they are all passes. The clients are showing up in the
>WSUS as orange traiagles and red circles. SO they must be touching
>base with WSUS.
>The setup is WSUS 3 is runnig on a Windows 2003 Server Sp2. The Proxy
>server is on the same server.

Will the Proxy server know that it should not forward HTTP requests to itself to
the Internet?
>
>Thansk

DaveMills

unread,

Jul 31, 2008, 11:14:52 PM7/31/08

to

On Thu, 31 Jul 2008 16:11:02 -0700 (PDT), jwc...@gmail.com wrote:

>On 31 Jul, 21:16, "Harry Johnston [MVP]" <ha...@scms.waikato.ac.nz>
>wrote:
>> jwc...@gmail.com wrote:
>> > 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
>>
>> Given these settings, the WUA will be trying to access the WSUS server via the
>> proxy. Might the proxy be blocking access?

If you are thinking of the IE setting "Bypass Proxy Server for local addresses"
then you need to be aware that "local" means addresses without a ".", i.e.
192.168.1.2 is NOT local because it has a dot.

>>
>> Harry.
>>
>> --
>> Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174
>
>Hi Harry
>The Wsus is also the proxy server. But isn't the proxy being by passed
>for local networks. All the clients are showing up with the orange
>triangle except for 2 showing the red round symbol with a cross when
>hightlighted it says not reported status for 289 or more days and 189
>or more days respectively. So they must be able to contact the wsus. I
>do not understand why the proxy is blocking access.
>
>Jeremy

jwc...@gmail.com

unread,

Aug 1, 2008, 8:49:28 PM8/1/08

to

I have run test below and passed test. There is conectivity to WSUS.

To check network connectivity on the WSUS client computer

1. Click Start, and then click Run.

2. In the Open box, type iexplore and then press ENTER

3. In the Internet Explorer Address bar, type:

http://WSUSServerName/iuident.cab

where WSUS server name is the name of your WSUS server. Ensure that
you are prompted to download or open Iuident.cab. This verifies
network connectivity from the WSUS client and the availability of the
Iuident.cab file on the WSUS server.

Jeremy

DaveMills

unread,

Aug 2, 2008, 5:44:11 AM8/2/08

to

Try resetting the winhttp proxy setting to those of IE using

cfgproxy -u

Harry Johnston [MVP]

unread,

Aug 3, 2008, 7:05:36 PM8/3/08

to

jwc...@gmail.com wrote:

> I have run test below and passed test. There is conectivity to WSUS.

This only tests connectivity in *your* context. It doesn't test connectivity in
the *WinHttp* context, which has different proxy settings configured per your
earlier post.

Dave's suggestion sounds like your best bet.

Joseph Rinaldi

unread,

Aug 4, 2008, 2:45:00 AM8/4/08

to

Hi All,

NOTE 1
~~~~~
I have had this problem and been at it for nearly three weeks,. MS has found
that there was a problem with a DDL in WSUS. Go to
http://support.microsoft.com/kb/954960. There you will find a hotfix that
replaces dll file
%ProgramFiles%\Update
Services\WebServices\ClientWebService\bin\Microsoft.UpdateServices.WebServices.Client.Dll.
Click the Version tab. The file version is 3.1.6001.66 is the new version.

NOTE 2
~~~~~
The clientdiag.exe tool does not work on a Windows x64 computer. To fix this
add the following subkey

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update

The tool will now work and allow you to troubleshoot any problems.

I tried all the recommendations in this post and many others. None worked
but this hotfix which was released only 5 days ago did the trick.

--
Joseph Rinaldi
Clarius Group Ltd

Harry Johnston [MVP]

unread,

Aug 5, 2008, 5:23:29 PM8/5/08

to

Joseph Rinaldi wrote:

> NOTE 1
> ~~~~~
> I have had this problem and been at it for nearly three weeks,. MS has found
> that there was a problem with a DDL in WSUS. Go to
> http://support.microsoft.com/kb/954960.

This isn't the same problem that jwchoo has.

Joseph Rinaldi

unread,

Aug 5, 2008, 6:03:02 PM8/5/08

to

Hi Harry,

Are you sure? The problem I was getting was that a few computers were
appearing in WSUS but getting "This computer has not reported status yet".
It had been ongoing for about 3 weeks. I installed the hotfix KB954960, and
then they all started to work.

jwchoo,

Can you please try the hotfix and see if it works for you?

Joseph Rinaldi

--
Joseph Rinaldi
Clarius Group Ltd

Harry Johnston [MVP]

unread,

Aug 5, 2008, 6:11:29 PM8/5/08

to

Joseph Rinaldi wrote:

> Are you sure?

Yes. The superficial symptoms may be the same, but jwchoo's Windows Update log
shows no evidence of the problem you were having - it's failing at an earlier
point in the process.

> jwchoo,
>
> Can you please try the hotfix and see if it works for you?

Well, it won't do any harm, assuming he is running WSUS 3 service pack 1.

jwc...@gmail.com

unread,

Aug 7, 2008, 7:03:27 PM8/7/08

to

On Aug 5, 11:03 pm, Joseph Rinaldi

> > Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174- Hide quoted text -

>
> - Show quoted text -

Hi Joseph/Harry/David

I am happy to report I have got it working. Clients are reporting and
getting updates. The only issue now is they are not populating the
WSUS Computer Groups as in GP OUs. I followed instructions from
http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-SelfUpdate-service-automatic-updates.aspx.
To summarise what I have done:-
1. check the correct level of permission, ISUR_IISserver user for all
the relevant folders. and anonynous user is checked on the Default
Website.
2. IP address is Unassign for Default website

Thank for all the help
Jeremy

jwc...@gmail.com

unread,

Aug 7, 2008, 7:32:07 PM8/7/08

to

On Aug 8, 12:03 am, jwc...@gmail.com wrote:
> On Aug 5, 11:03 pm, Joseph Rinaldi
>
>
>
>
>
> <JosephRina...@discussions.microsoft.com> wrote:
> > Hi Harry,
>
> > Are you sure? The problem I was getting was that a few computers were
> > appearing in WSUS but getting "This computer has not reported status yet".
> > It had been ongoing for about 3 weeks. I installed the hotfix KB954960, and
> > then they all started to work.
>
> > jwchoo,
>
> > Can you please try the hotfix and see if it works for you?
>
> > Joseph Rinaldi
>
> > --
> > Joseph Rinaldi
> > Clarius Group Ltd
>
> > "Harry Johnston [MVP]" wrote:
> > > Joseph Rinaldi wrote:
>
> > > > NOTE 1
> > > > ~~~~~
> > > > I have had this problem and been at it for nearly three weeks,. MS has found
> > > > that there was a problem with a DDL in WSUS. Go to
> > > >http://support.microsoft.com/kb/954960.
>
> > > This isn't the same problem that jwchoo has.
>
> > > Harry.
>
> > > --

> > > Boycott Beijing 2008http://www.rsf.org/rubrique.php3?id_rubrique=174-Hide quoted text -

>
> > - Show quoted text -
>
> Hi Joseph/Harry/David
>
> I am happy to report I have got it working. Clients are reporting and
> getting updates. The only issue now is they are not populating the

> WSUS Computer Groups as in GP OUs. I followed instructions fromhttp://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-S....

> To summarise what I have done:-
> 1. check the correct level of permission, ISUR_IISserver user for all
> the relevant folders. and anonynous user is checked on the Default
> Website.
> 2. IP address is Unassign for Default website
>
> Thank for all the help

> Jeremy- Hide quoted text -

>
> - Show quoted text -

I also started WHTTP web proxy service. I am not sure it is necessary.

Jeremy

DaveMills

unread,

Aug 8, 2008, 12:08:41 AM8/8/08

to

On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwc...@gmail.com wrote:

>I am happy to report I have got it working. Clients are reporting and
>getting updates. The only issue now is they are not populating the
>WSUS Computer Groups as in GP OUs.

Two possibilities:
1) The client is not being told which group to use in the GPO or the spelling of
the group does not match that is WSUS console.
2) The WSUS server is not set to use Client Side Targeting.

> I followed instructions from
>http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-SelfUpdate-service-automatic-updates.aspx.
>To summarise what I have done:-
>1. check the correct level of permission, ISUR_IISserver user for all
>the relevant folders. and anonynous user is checked on the Default
>Website.
>2. IP address is Unassign for Default website
>
>Thank for all the help
>Jeremy

jwc...@gmail.com

unread,

Aug 8, 2008, 9:58:08 AM8/8/08

to

On Aug 8, 5:08 am, DaveMills <DaveMi...@newsgroup.nospam> wrote:
> On Thu, 7 Aug 2008 16:03:27 -0700 (PDT), jwc...@gmail.com wrote:
> >I am happy to report I have got it working. Clients are reporting and
> >getting updates. The only issue now is they are not populating the
> >WSUS Computer Groups as in GP OUs.
>
> Two possibilities:
> 1) The client is not being told which group to use in the GPO or the spelling of
> the group does not match that is WSUS console.
> 2) The WSUS server is not set to use Client Side Targeting.
>
> > I followed instructions from

> >http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-S....

> >To summarise what I have done:-
> >1. check the correct level of permission, ISUR_IISserver user for all
> >the relevant folders. and anonynous user is checked on the Default
> >Website.
> >2. IP address is Unassign for Default website
>
> >Thank for all the help
> >Jeremy
>
> --
> Dave Mills
> There are 10 type of people, those that understand binary and those that don't.

Dave

I have Client side targeting setup. The OUs are nested like
1. Client systems\XP\Workstations
2. Client systems\XP\Laptops

How do I name them in GP ?

Jeremy

DaveMills

unread,

Aug 9, 2008, 7:44:18 AM8/9/08

to

Use the setting in the WSUS policy settings
Computer\Windows Components\Windows Update\Target group name for this computer

You can either create a separate GPO for Laptops and Workstations with all the
setting you need for each.

or

Create a GPO for XP with all the settings for all sub OUs and then have other
GPO for Loptops OU etc which supply just the different settings such as
groupname etc.

You decide which, is it easier to have central setting for everything and
overwrite these with the exception or just have totally separate GPOs and have
to make change in all if something changes.
I would definitely have WSUS setting in a GPO or their own and not added to
Workstation Settings or Laptop Settings. It is too hard to maintain otherwise.

jwc...@gmail.com

unread,

Aug 12, 2008, 12:20:15 PM8/12/08

to

> There are 10 type of people, those that understand binary and those that don't.- Hide quoted text -

>
> - Show quoted text -

I have done Computer\Windows Components\Windows Update\Target group
name for this computer
all the groups but still the same - not populating the groups as the
ones in Group Policy.

Jeremy

DaveMills

unread,

Aug 12, 2008, 4:51:06 PM8/12/08

to

What does WindowsUpdate.log say the client is getting for "Target Group"

Harry Johnston [MVP]

unread,

Aug 13, 2008, 8:18:08 PM8/13/08

to

jwc...@gmail.com wrote:

> I have Client side targeting setup. The OUs are nested like
> 1. Client systems\XP\Workstations
> 2. Client systems\XP\Laptops
>
> How do I name them in GP ?

I believe you should specify Workstations and Laptops respectively, i.e., ignore
the nesting entirely and only specify the last component. I may be
misremembering, I don't do this routinely - but it's worth a try. :-)

jwc...@gmail.com

unread,

Aug 18, 2008, 3:44:39 PM8/18/08

to

On Aug 14, 1:18 am, "Harry Johnston [MVP]" <ha...@scms.waikato.ac.nz>
wrote:

ok I will give it a try. Thanks
Jeremy

olufisademidun

unread,

Feb 1, 2010, 9:37:19 AM2/1/10

to

Hi all,

I have similar problem but running WSUS Sp2, the patch cannot run on my system any help please

"This computer has not reported status yet"

Log file in one of the server:
Service ** START ** Service: Service startup
2010-02-01 14:03:03:140 1208 9c4 Service *********
2010-02-01 14:03:04:484 1208 9c4 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups.dll"
2010-02-01 14:03:05:796 1208 9c4 Misc Registering binary: C:\WINDOWS\system32\regsvr32.exe /s "C:\WINDOWS\system32\wups2.dll"
2010-02-01 14:03:07:140 1208 9c4 Agent * WU client version 7.4.7600.226
2010-02-01 14:03:07:140 1208 9c4 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2010-02-01 14:03:07:218 1208 9c4 Agent * Access type: No proxy
2010-02-01 14:03:07:250 1208 9c4 Agent * Network state: Connected
2010-02-01 14:03:55:796 1208 9c4 Agent *********** Agent: Initializing Windows Update Agent ***********
2010-02-01 14:03:55:796 1208 9c4 Agent *********** Agent: Initializing global settings cache ***********
2010-02-01 14:03:55:796 1208 9c4 Agent * WSUS server: http://RGMHSCCM1:8530
2010-02-01 14:03:55:796 1208 9c4 Agent * WSUS status server: http://RGMHSCCM1:8530
2010-02-01 14:03:55:796 1208 9c4 Agent * Target group: (Unassigned Computers)
2010-02-01 14:03:55:796 1208 9c4 Agent * Windows Update access disabled: No
2010-02-01 14:03:55:812 1208 9c4 DnldMgr Download manager restoring 0 downloads
2010-02-01 14:03:55:843 1208 9c4 AU ########### AU: Initializing Automatic Updates ###########
2010-02-01 14:03:55:843 1208 9c4 AU AU setting next sqm report timeout to 2010-02-01 14:03:55
2010-02-01 14:03:55:859 1208 9c4 AU # WSUS server: http://RGMHSCCM1:8530
2010-02-01 14:03:55:859 1208 9c4 AU # Detection frequency: 22
2010-02-01 14:03:55:859 1208 9c4 AU # Approval type: Scheduled (Policy)
2010-02-01 14:03:55:859 1208 9c4 AU # Scheduled install day/time: Every day at 3:00
2010-02-01 14:03:55:859 1208 9c4 AU # Auto-install minor updates: Yes (User preference)
2010-02-01 14:03:55:859 1208 9c4 AU Setting AU scheduled install time to 2010-02-02 03:00:00
2010-02-01 14:03:55:890 1208 9c4 AU Initializing featured updates
2010-02-01 14:03:55:906 1208 9c4 AU Found 0 cached featured updates
2010-02-01 14:03:55:906 1208 9c4 AU AU finished delayed initialization
2010-02-01 14:03:56:218 1208 9c4 Report *********** Report: Initializing static reporting data ***********
2010-02-01 14:03:56:218 1208 9c4 Report * OS Version = 5.1.2600.2.0.65792
2010-02-01 14:03:56:281 1208 9c4 Report * Computer Brand = Hewlett-Packard
2010-02-01 14:03:56:281 1208 9c4 Report * Computer Model = HP Compaq dc7900 Small Form Factor
2010-02-01 14:03:56:281 1208 9c4 Report * Bios Revision = 786G1 v01.16
2010-02-01 14:03:56:281 1208 9c4 Report * Bios Name = Default System BIOS
2010-02-01 14:03:56:281 1208 9c4 Report * Bios Release Date = 2009-03-05T00:00:00
2010-02-01 14:03:56:281 1208 9c4 Report * Locale ID = 2057

Thanks,

jwcho wrote:

Re: This Computer has not reported status yet
09-Aug-08

On Aug 5, 11:03=A0pm, Joseph Rinaldi
<JosephRina...@discussions.microsoft.com> wrote:
..
nd
s found
Hide quoted text -

Hi Joseph/Harry/David

I am happy to report I have got it working. Clients are reporting and
getting updates. The only issue now is they are not populating the
WSUS Computer Groups as in GP OUs. I followed instructions from

http://kbalertz.com/920659/Microsoft-Windows-Server-Update-Services-SelfUpd=

ate-service-automatic-updates.aspx.
To summarise what I have done:-
1. check the correct level of permission, ISUR_IISserver user for all
the relevant folders. and anonynous user is checked on the Default
Website.
2. IP address is Unassign for Default website

Thank for all the help
Jeremy

Previous Posts In This Thread:

On Wednesday, June 25, 2008 7:17 PM
bzumwalt9 wrote:

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

On Wednesday, June 25, 2008 8:09 PM
PA Bear [MS MVP] wrote:

Right pew, wrong church. Forwarded to WSUS newsgroup (microsoft.public.
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/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/

bzumwalt99 wrote:

On Wednesday, June 25, 2008 11:25 PM
Thomas wrote:

I recommend looking at WindowsUpdate.
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]" <PABe...@gmail.com> wrote in message
news:%23bS4SEy...@TK2MSFTNGP06.phx.gbl...

On Monday, June 30, 2008 3:25 AM
mackdaddy315 wrote:

First make sure your policy says it is pointing to the correct wsusbox by
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.

On Monday, June 30, 2008 7:50 AM
Lawrence Garvin wrote:

Re: This Computer has not reported status yet
"mackdaddy315" <mackda...@hotmail.com> wrote in message
news:43933a5f-0f26-4b85...@34g2000hsf.googlegroups.com...