WSUS - Missing update icon to apply updates
I use the WSUS server to manage and apply all of my updates for the XP workstations and Windows 2003 Servers. My primary access to the Windows 2003 Servers is through the windows remote desktop application. I have noticed recently that on RDP connection to the servers, the Windows Update icon that typically appears in the task bar adjacent to the clock no longer appears to apply the updates. (See attached image). According to my WSUS server, there are 15+ updates ready to install on these servers. I have tried to force the update (wuauclt.exe /detectnow) with no success. Is there a way to start the updates without going through the icon on the taskbar?
(Note: I am experiencing this only on my 2003 servers that I access through RDP, the XP workstations are fine.)
Windows-Update-Icon.jpg
(Note: I am experiencing this only on my 2003 servers that I access through RDP, the XP workstations are fine.)
Windows-Update-Icon.jpg
ASKER
Yes the server are seeing the WSUS server. One the servers is actually the WSUS server itself. I'm not sure what WSUS client dialog you are refering.
ASKER
ChiefIT,
Ignore my precious comment. I had a mind block for a moment. I forgot about the WSUS Diagnostic tool. Anyway, I ran it and everything passed. Still no icon to install the updates.
Ignore my precious comment. I had a mind block for a moment. I forgot about the WSUS Diagnostic tool. Anyway, I ran it and everything passed. Still no icon to install the updates.
go to the command prompt and type:
wuauclt /r /refreshnow
what happens?
wuauclt /r /refreshnow
what happens?
ASKER
ChiefIT,
I ran the command, it ran and returned back to the command prompt. Still no icon on the taskbar to apply the updates. Is there a flag in the 'wuauclt' that can force the update?
Jed
I ran the command, it ran and returned back to the command prompt. Still no icon on the taskbar to apply the updates. Is there a flag in the 'wuauclt' that can force the update?
Jed
OK, here's what I am thinking:
Your servers see the WSUS server. This means your server's GPO to link up to the WSUS server is good. We tried to force it to resynch. Still no updates. All XP clients are getting updates.
This leads me to the conclusion that the XP machines have a rule to automatically APPROVE updates, but the 2003 servers do not. (Good practice, by the way).
You will have to go in to the WSUS console and manually approve needed updates to your 2003 servers. Then, I think all will be happy.
Your servers see the WSUS server. This means your server's GPO to link up to the WSUS server is good. We tried to force it to resynch. Still no updates. All XP clients are getting updates.
This leads me to the conclusion that the XP machines have a rule to automatically APPROVE updates, but the 2003 servers do not. (Good practice, by the way).
You will have to go in to the WSUS console and manually approve needed updates to your 2003 servers. Then, I think all will be happy.
ASKER
Yes I have the servers set to notify prior to install. I have approved these updates on the WSUS server console, they are all ready to install. The problem is that I don't get a notification (the icon in the taskbar) on the servers to install. Am I missing something here? Is it something within RDP that is preventing me seeing the update icon?
(BTW: It has been working perfect for 2 years now, this is only recently, within the last 2 weeks that I have not seen any icon to apply the updates on the servers.)
(BTW: It has been working perfect for 2 years now, this is only recently, within the last 2 weeks that I have not seen any icon to apply the updates on the servers.)
OK, updates come in stages. You might need to reboot for the next stage to be downloaded.
In other words, you can't install the SP1 update and the SP2 update without a reboot, right.
So, your servers are waiting for a reboot to finalize the updates that are all ready installed.
In other words, you can't install the SP1 update and the SP2 update without a reboot, right.
So, your servers are waiting for a reboot to finalize the updates that are all ready installed.
ASKER
You may have a point here. Interesting. Let me try to reboot a non critical server. Stand by.
If there is a pending reboot, further updates wont notify until a reboot
ASKER
I have rebooted the server, logged in with RDP and waited 3-5 minutes for an icon to appear in the corner. Nothing. I also ran wuauclt /r /refreshnow, still nothing.
Any ideas?
Any ideas?
you need to run wuauclt /detectnow, wuauclt /r /refreshnow is not a valid command and wuaclt doesnt report errors
@ dstewartjr:
LOL:
It doesn't report the switch syntax either, when you type:
wuauclt /?
or
wuauclt help
LOL:
It doesn't report the switch syntax either, when you type:
wuauclt /?
or
wuauclt help
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Finally...it was wuauclt /r /reportnow that worked. That was fun. Thank you.
BTW: What does the /r switch do? I did not see it in the switch list.
BTW: What does the /r switch do? I did not see it in the switch list.
Good question, I just followed technet when /detectnow didn't seem to work and everything was good, (as in your case).
destewartjr:
Do you know what the /r means???
Destewart is probably the best WSUS techs I have seen. He taught me a lot.
Do you know what the /r means???
Destewart is probably the best WSUS techs I have seen. He taught me a lot.
Its actually just short for reportnow
wuauclt /reportnow
=or=
wuauclt /r
but not both parameters together.
wuauclt /reportnow
=or=
wuauclt /r
but not both parameters together.
ASKER
So to be clear:
wuauclt /r /reportnow
is the same as
wuauclt /r
?
wuauclt /r /reportnow
is the same as
wuauclt /r
?
yup
I think, (as dstewartjr and I pointed out), the root problem was a reboot was needed to finalize updates.
--the /detectnow didn't work for me either. /reportnow did.
All these switches do is forgo the automated reporting period. So, those switches do not resolve the root problem.
As you go to your domain servers and try to fix them, remember they will require a reboot before you tell them to reportnow.
--the /detectnow didn't work for me either. /reportnow did.
All these switches do is forgo the automated reporting period. So, those switches do not resolve the root problem.
As you go to your domain servers and try to fix them, remember they will require a reboot before you tell them to reportnow.
ASKER
ChiefIT,
Actually 2 of my servers did not need to be rebooted. I simply did the following:
wuauclt /reportnow
wuauclt /detectnow
-Jed
Actually 2 of my servers did not need to be rebooted. I simply did the following:
wuauclt /reportnow
wuauclt /detectnow
-Jed
your welcome
Nevertheless, dstewart helped us clarify a couple things and deserves and assist at bare minimum.
Will you open this up and throw him a bone for his help, maybe split the points? (LOL)
All you have to do is push the request attention and ask this be opened again.
Thanks.
Will you open this up and throw him a bone for his help, maybe split the points? (LOL)
All you have to do is push the request attention and ask this be opened again.
Thanks.
ASKER
Sorry guys, I screwed up with the point allocation. Let me redo this.
no prob ; ^ )
Use the WSUS client diag on the 2003 servers to see what's wrong.