|
|
There is a server that needs Windows updates. I can see that in the
WSUS console it says they have downloaded and are ready to be
installed. Going to that server's windowsupdates.log file shows many
updates detected and ready to install.
However, when I log into the the machine, there is no way to launch
the installation because the shield and balloon prompts are not
displayed.
I tried running the wuauclt /detectnow command, but the prompt never
appears and there are no error messages,.
Is there any way to get the shield back or launch the installation
another way so we do not have to download the updates manually?
|
|
Hi , did you check the windowsupdate.log for errors ?
Osman Shener
"MyGposts" <mygposts[ at ]gmail.com> wrote in message
news:d5600c59-f6b0-426e-be76-6c844caf3300[ at ]i18g2000prf.googlegroups.com...
[Quoted Text] > There is a server that needs Windows updates. I can see that in the
> WSUS console it says they have downloaded and are ready to be
> installed. Going to that server's windowsupdates.log file shows many
> updates detected and ready to install.
>
> However, when I log into the the machine, there is no way to launch
> the installation because the shield and balloon prompts are not
> displayed.
>
> I tried running the wuauclt /detectnow command, but the prompt never
> appears and there are no error messages,.
>
> Is there any way to get the shield back or launch the installation
> another way so we do not have to download the updates manually?
|
|
"MyGposts" <mygposts[ at ]gmail.com> wrote in message
news:d5600c59-f6b0-426e-be76-6c844caf3300[ at ]i18g2000prf.googlegroups.com...
[Quoted Text] > Is there any way to get the shield back or launch the installation
> another way so we do not have to download the updates manually?
The most likely cause of this issue is that somebody has configured a policy
to block access to WU features.
Start by inspecting the applied policies on the machine.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
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
|
|
On Tue, 25 Nov 2008 10:30:08 -0600, "Lawrence Garvin \(MVP\)"
<lawrence[ at ]news.postalias> wrote:
[Quoted Text] >"MyGposts" <mygposts[ at ]gmail.com> wrote in message
>news:d5600c59-f6b0-426e-be76-6c844caf3300[ at ]i18g2000prf.googlegroups.com...
>
>> Is there any way to get the shield back or launch the installation
>> another way so we do not have to download the updates manually?
>
>The most likely cause of this issue is that somebody has configured a policy
>to block access to WU features.
>
>Start by inspecting the applied policies on the machine.
There is another very likely cause. Accessing a w2003 server using RDP 6 while
the same user is still logged on to the console session. To get the shield I
usually have to first ensure that there is no locally logged on session and then
connect via RDP. Even then I usually have to run wuauclt /detectnow and wait a
minute or two.
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
|
|
"DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message
news:isspi4p47a358niovhr7p20mde6m2qbpp5[ at ]4ax.com...
[Quoted Text] >>> Is there any way to get the shield back or launch the installation
>>> another way so we do not have to download the updates manually?
>>The most likely cause of this issue is that somebody has configured a
>>policy
>>to block access to WU features.
>>
>>Start by inspecting the applied policies on the machine.
> There is another very likely cause. Accessing a w2003 server using RDP 6
> while
> the same user is still logged on to the console session. To get the shield
> I
> usually have to first ensure that there is no locally logged on session
> and then
> connect via RDP. Even then I usually have to run wuauclt /detectnow and
> wait a
> minute or two.
Good point, Dave.
In fact, I had an extended discussion with the WSUS Product Team a couple of
MVP Summits ago about this very issue -- behavior of the notification icon
in a Remote Desktop Session.
Your observations are entirely accurate with how the process was described
to me. Because the notification icon is a user-directed feature (and not
dependent on whether the session is a console session), but only one
"notification" can be active at a time, any subsequent logons (whether by
RDC or directly at the console) will not see the icon if it's already active
in a preexisting session.
If, when the O.P. logs onto the console of the server, there is still
another active session (possibly disconnected) using the Administrator
account, then the notification icon will be active in that pre-existing
session, and not available for display, even at the new physical console
session.
For those who might think they may be experiencing this scenario, you can
use the Terminal Services Manager to view the active sessions connected to
that server, and terminate any unneeded active sessions.
--
Lawrence Garvin, M.S., MCITP(x2), MCTS(x5), MCP(x7), MCBMSP
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)
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
|
|
On Wed, 26 Nov 2008 11:06:47 -0600, "Lawrence Garvin \(MVP\)"
<lawrence[ at ]news.postalias> wrote:
[Quoted Text] >"DaveMills" <DaveMills[ at ]newsgroup.nospam> wrote in message
>news:isspi4p47a358niovhr7p20mde6m2qbpp5[ at ]4ax.com...
>
>>>> Is there any way to get the shield back or launch the installation
>>>> another way so we do not have to download the updates manually?
>
>>>The most likely cause of this issue is that somebody has configured a
>>>policy
>>>to block access to WU features.
>>>
>>>Start by inspecting the applied policies on the machine.
>
>> There is another very likely cause. Accessing a w2003 server using RDP 6
>> while
>> the same user is still logged on to the console session. To get the shield
>> I
>> usually have to first ensure that there is no locally logged on session
>> and then
>> connect via RDP. Even then I usually have to run wuauclt /detectnow and
>> wait a
>> minute or two.
>
>Good point, Dave.
>
>In fact, I had an extended discussion with the WSUS Product Team a couple of
>MVP Summits ago about this very issue -- behavior of the notification icon
>in a Remote Desktop Session.
>
>Your observations are entirely accurate with how the process was described
>to me. Because the notification icon is a user-directed feature (and not
>dependent on whether the session is a console session), but only one
>"notification" can be active at a time, any subsequent logons (whether by
>RDC or directly at the console) will not see the icon if it's already active
>in a preexisting session.
Thanks L, this single instance description does clarify one or two odd
observations I have seen. Much clearer now.
>
>If, when the O.P. logs onto the console of the server, there is still
>another active session (possibly disconnected) using the Administrator
>account, then the notification icon will be active in that pre-existing
>session, and not available for display, even at the new physical console
>session.
>
>For those who might think they may be experiencing this scenario, you can
>use the Terminal Services Manager to view the active sessions connected to
>that server, and terminate any unneeded active sessions.
I have only found out how to disconnect a remote session and not logoff. Also I
cannot remotely hit the console session. I may be doing something wrong but I
have some VBA that can log off the remote console which I use. Or Shutdown.exe
may do it but last time I tried I shut down my own workstation instead so I tend
to use my own app.
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
|
|
|