Re: Clients not updating with WSUS 3.0



"Costas" wrote:

That yellow triangle on the client, means that there are updates waiting to
be installed. Click on it and you'll initiate the process. When the process
completes, the WSUS console will update and it will show you that the
computer has been updated.

I'm sorry, but when i doubleclick this it gives a report. This is when i'm
sitting at the server, in Update Services console, looking at the computers.


The process, in general, is as follows. At certain, configurable, time
intervals (once a day) WSUS synchronizes with Microsoft and downloads the
information about the available updates. When you approve the updates (on
the server), the updates are downloaded and then based on the GPO settings,
are being pushed out to the clients. When the client receives the
notification from the server that there are updates waiting (in your case
"Auto download and notify for install") it downloads the updates and the
yellow triangle notifies the user for installing the updates.

Do you mean the yellow shield here or is it now a triangle since i'm using
the WSUS server?


If the user does not click on the yellow triangle, WSUS will not show that
the updates have been installed. It will be showing a percentage which will
mean 'something' is missing. When the user finally goes through the process
of installing the updates, the WSUS console will update, and show that
everything have been updated. Sometimes a reboot is required on the client
machine, and if the users does not go through it, WSUS on the server will
still be showing that 'something' is missing (by showing 97% complete or
something like that)

Hope that clarifies things.


Yes that clears up a lot. I now have a better overall concept of how things
should work. I guess i should have asked that to begin with.

Thanks for all of your help with this. It is very much appreciated.
Tony

--
Costas


"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:D562A5C9-9BB6-4313-9492-D29C3E3C165C@xxxxxxxxxxxxxxxx
I guess i just don't understand this whole WSUS 3.0 thing. I have one
laptop
that shows in the Update Services snapin with the following information
for 2
days now. Te Update Services snapin, for that client, shows a little
yellow
triangle with an exclamation point in it.

Updates with errors: 0
Updates needed: 5
Updates installed/not applicable: 6181
Updates with no status: 0

I don't know if the other clients were updated from me installing updates
at
the clients workstation (because the little yellow shield showed in the
systray) or if they were updated from the WSUS server.

When i sit in front of a client workstation, can the clients do anything
to
say update now?

When updates are available from the WSUS server, do the clients see the
little yellow shield in the systray?

Thanks,
Tony

"Costas" wrote:

Tony,

The settings of the GPO you posted are correct but I don't understand the
part about the clients not updating. You posted that the WSUS report
shows
successful update, but the client do not update. How do you come to that
conclusion?

Judging from the settings of the GPO, only two things come to mind.
Either
the computers are not running when at the scheduled install time, or the
computers haven't been assigned to the "LakeSide Server Computers" group
from within the WSUS management console

--
Costas


"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:DF43A52B-189C-4A64-B306-616B281F94CF@xxxxxxxxxxxxxxxx
Hello Costas.

Actually, i only saw that event error one more time after posting this
question. However the clients are still not updating.

Is there a way for the clients to contact the wsus server?

Thanks,
Tony

"Costas" wrote:

The clients can't go to 'localhost' on the server because 'localhost'
is
the
server (if any) that runs on the computer from which the command was
issued,
in your case, the actual client computer. Based on your opening post,
the
problem is with drive E on the server.

--
Costas


"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:A78D9560-FFC1-45F5-B206-C9AF1C131636@xxxxxxxxxxxxxxxx
Hello Costas.

I checked all of those settings. Here is what i have. I tried to
follow
the install instructions.

Configure Automatic updates = 3-Auto download and notify for
install"
Specify intranet Microsoft update service location =
"http://lakeside:8530";
(both fields)
Enable client-side targeting = "Lakeside Server Computers"
Reschedule Automatic Updates scheduled installations = "1"
Automatic Updates detection frequency = "22"

Is a client supposed to be able to go to "http://localhost/SUSAdmin";
and
be
able to got to Microsoft Software Update Services on the intranet?

Thanks,
Tony

"Costas" wrote:

Tony,

Clients connect to the WSUS via Group Policy. If you go to the
Group
Policy
Management on the server and edit the 'Update Services for Client
Computers
and Server policy' GPO, then go to 'Computer Configuration |
Administrative
Templates | Windows Components | Windows Update' you'll see to the
right
all
the settings that have been enabled and if you edit each one of
them,
you'll
see their properties

--
Costas


"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:30A32582-18AD-476F-80C5-13318CB66281@xxxxxxxxxxxxxxxx
Hello Costas.

Thanks for finding that. I tried those changes and it did not
help.

I keep reading documents that say "when the client connects to
the
SUS
server, the updates will be downloaded". How does a client
connect
to
the
SUS server?

Thanks,
Tony

"Costas" wrote:

Take a look at the following link

http://technet2.microsoft.com/windowsserver/en/library/a7a947d7-c2db-45e4-9495-70aba6d059fe1033.mspx?mfr=true

The paragraph under "Downloads from a WSUS server are failing"
describes
the
permissions that need to be set

--
Costas


"Tony Girgenti" <tony(nospam)@lakesideos.com> wrote in message
news:7F5D34AA-1892-4CB3-AA77-062812CFA5B5@xxxxxxxxxxxxxxxx
Hello.

I tried asking questions in the Software Update Services
newsgroup,
but
never got a reply.

We have an SBS2003, SP2 server with IIS6.0, ISA 2004, Exchange
with
POP3
Connector, .Net Framework 1.1 and 2.0.

We installed WSUS3.0. The synchronization is working. The
computers
in
the
Target group for updating show as being updated every day
under
the
"Last
Status Report" column, but the computers never get updated
with
the
latest
updates.

Every day there is an entry in the Application event log with
Event
ID:10012, The permissions on directory E:\sw\ms are incorrect.
I
tried
giving that folder every permission i could think of but we
still
keep
getting the event error.

Does anybody have ideas on how to fix that?

Any help would be gratefully appreciated.

Thanks,
Tony





.

Relevant Pages

  • Re: FYI for eTrust AV 7.x Users
    ... When I just had my little incident with the redistribution settings on the SBS, my clients were logging successful checks for updates, and the logs indicated that no updates were found. ... That turned out to be because I had not gone back and checked the redistribution server box for 8.x after reinstalling the redistribution server. ... installed the new remote install utility which works the same as v7 did - just edited the .ICF file the way I wanted it and ran the client upgrades from the server. ... I can't remember if it's a separate install, or if you have to click a box when you do the Agent install, but redistribution server is not installed by default. ...
    (microsoft.public.windows.server.sbs)
  • Re: WSUS Client not yet reported
    ... The root cause can be at either the server side or the client side. ... please check if it works with WSUS. ... any updates in your thread. ...
    (microsoft.public.windows.server.sbs)
  • Re: FYI for eTrust AV 7.x Users
    ... installed the new remote install utility which works the same as v7 did - ... from the server. ... I think my issues had to do with my first client upgrade - our Windows 2003 ... I think this is why the updates did not go through (although you'd think ...
    (microsoft.public.windows.server.sbs)
  • RE: Where does SBS store its client updates?
    ... Thanks for updates. ... I am sorry to hear that SP2 have bring you some inconvenience, ... from the client application. ... You have to remove it manually after install ...
    (microsoft.public.windows.server.sbs)
  • Re: FYI for eTrust AV 7.x Users
    ... got it on the server & exchange no problem. ... Installed it manually on the first client and it runs, but I can't get it to ... getting through ISA for updates. ... I have not tried the remote install. ...
    (microsoft.public.windows.server.sbs)
Loading