Re: WSUS Not Yet Reported

Yep, both computers have been restarted (several times!) and one is running
XP Pro SP3 and the other is Windows Server 2003 R2 Standard. Both are fully
patched (just checked with Microsoft Update)

Waggers





"Costas" <cpstechgroup@xxxxxxxxx> wrote in message
news:uJgW%23389IHA.4892@xxxxxxxxxxxxxxxxxxxxxxx
I guess I have to ask the obvious.... did you restart the computers? Also,
what type of operating system are they running on? Are they fully patched
and up to date?

--
Costas
http://costas.cpstechgroup.com




"Waggers" <Waggers@xxxxxxxxxxxxxxxx> wrote in message
news:u5Ii2w89IHA.5928@xxxxxxxxxxxxxxxxxxxxxxx
Thanks Costas.

It looks OK, I can see the following listed under 'Computer Settings -
Applied Gruop Policy Objects'

Small Business Server Update Services Client Computers Policy
Small Business Server Update Services Common Settings Policy






"Costas" <cpstechgroup@xxxxxxxxx> wrote in message
news:Oe15mn89IHA.1192@xxxxxxxxxxxxxxxxxxxxxxx
Waggers,

I will start by making sure that Group Policy is properly applied to the
computers that present the issue. From the command prompt, run
'gpresult' and see if the Group Policy object that contains the Update
Services settings is applied



--
Costas
http://costas.cpstechgroup.com




"Waggers" <Waggers@xxxxxxxxxxxxxxxx> wrote in message
news:OGsX6079IHA.3612@xxxxxxxxxxxxxxxxxxxxxxx
Our SBS 2003 R2 Standard is running WSUS 3 SP1 and has been quite happy
updating the clients.

However, I've just noticed that two of the client machines (out of 14)
have started to show 'Not Yet Reported' These two clients have been
attached to the network for years and had no known previous update
problems.

I've found a few postings where no clients are reporting but nothing on
'some clients are reporting'

Could someone kindly point me in the right direction?

Many thanks
Waggers





.

Relevant Pages

  • Re: Deploying sp4 through Group policy (repost)
    ... Check the permissions on both the share and the directory. ... both SYSTEM and the group that the policy is applicable to (this requires ... Are these clients at a remote site and the files on a local server (that is, ... > the domain computers group. ...
    (microsoft.public.win2000.active_directory)
  • Re: Assign Domain Security Policy/Manage remote computer
    ... Given your policy it looks like you're also securing traffic from ... the clients to their DC/AD server. ... > I've just setup active direcotry, and added other computers to the new ...
    (microsoft.public.win2000.security)
  • Re: WSUS Not Yet Reported
    ... I can see the following listed under 'Computer Settings - Applied Gruop Policy Objects' ... Small Business Server Update Services Client Computers Policy ... I've just noticed that two of the client machines have started to show 'Not Yet Reported' These two clients have been attached to the network for years and had no known previous update problems. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS Not Yet Reported
    ... I can see the following listed under 'Computer Settings - Applied Gruop Policy Objects' ... Small Business Server Update Services Client Computers Policy ... I've just noticed that two of the client machines have started to show 'Not Yet Reported' These two clients have been attached to the network for years and had no known previous update problems. ... I've found a few postings where no clients are reporting but nothing on 'some clients are reporting' ...
    (microsoft.public.windows.server.sbs)
  • Re: Group Policy Not Applying to All Computers
    ... Howdy Richard! ... not apply to some computers. ... Having a look at the eventlog and tools like "gpresult" and "rsop.msc" should give you a hint if there is an error with Client Side Extensions that are responsible for policy application. ... Do all clients lie in the scope of the policy or does the policy just apply to "some" clients since all other clients belong to another OU? ...
    (microsoft.public.windows.group_policy)
Loading