Re: Question to Restart After Win Updates Installed - No Button Greyed

Hi !

We experience the excapt same problem, only on a Terminal Server (and wsus
server)
All the settings seems correct, among others the RebootRelaunchTimeout is
set to 0 and
the ElevatedNonAdmins are also set to 0. The AUOptions is set to 4.
As far as I understand, this should download and install updates set to
"install" automatically and
inform ONLY ADMINISTRATORS logging on to the terminal-server.
But, all of our users keep getting the popup message regarding restart, and
both the "Restart Now"
and "Restart Later" buttens are disabled. The only way of getting rid of
this is to stop the "Automatic Update" service,
this "kills" the windows in every session.

The wuaueng.dll file is in version 5.8.0.2468 which seems farly recent.

So, does anyone have any idea on how to avoid the AU service in
presenting/informing ordinary users of reboot?
I've soon google'd the entire net in search of answers, but can't find much
information about using AU client
on terminal servers (w2k ts that is)

Thanks in advance!
brdgs,
Stig A Sunde



"deesully" <deesully@xxxxxxxxxxxxxxxxxxxxxxxxx> skrev i melding
news:10CA7F62-007B-43E9-8770-E2E74BD5EA7E@xxxxxxxxxxxxxxxx
> Pat,
>
> I too am experiencing this issue. As I cannot be guaranteed all of my PCs
> will be on at 3am I prefer to run my updates during the day so I know my
> users are here and their computers are turned on.
>
> I understand this issue is "by design", however I feel the feature of not
> having the computers automatically reboot is negated by this button being
> greyed out. the only option is to put up with a window still partially on
> your screen, or hit yes and restart anyway. I'm sure there are MANY
> admins
> out here that really don't mind if their users wait to reboot their PCs.
> Can
> this option be written into a Group Policy?
>
> In your reply #2 states the user does not have high enough privileges to
> say
> "NO", per your own domain policy. Are you referring to the fact that
> users
> are not admins? If so then nobody but admins would have rights to NOT
> restart the PC and if that is the case, what is the point in having the
> button?
>
> Sorry if I sound a bit harsh. It's just frustrating to have this feature
> and not really have it work like it sounds like it should. I get multiple
> calls from users when I push out updates and all I can say is " I don't
> know
> why"
>
> David
>
> "Pat Walters [MSFT]" wrote:
>
>> Louis,
>>
>> This is "by-design" behavior. The following facts are
>> true:
>>
>> 1. The machine does NOT automatically reboot after the
>> install, per the No Auto-Restart for Scheduled Automatic
>> Updates Installations policy.
>>
>> 2. The user does not have high enough privileges to
>> say "No," per your own domain policy.
>>
>> 3. The user apparently has elevated enough privileges to
>> say "Yes" to rebooting.
>>
>> There is a small delay you can use. The policy
>> RescheduleWaitTime can be set anywhere from 1 to 60 (in
>> minutes).
>>
>> This is just a suggestion from me, but if it were possible
>> for you to set the install time to a more convenient hour
>> for your students--such as 3am--then your students could
>> walk into the lab and reboot the machines after they log
>> on. Their work time would be minimally hindered by a
>> reboot, unless they were trying to print their term paper
>> at 7:30am for an 8am deadline!
>>
>> Please let me know if this helps.
>>
>> Sincerely,
>>
>> Pat Walters [MSFT]
>>
>> >-----Original Message-----
>> >Hello,
>> >
>> >I'm experimenting automating Windows Update for computer
>> lab clients at the
>> >university I work for. The clients are Windows XP SP1,
>> and Windows XP SP2,
>> >and they all login to Windows Server 2003 Active
>> Directory.
>> >
>> >I'm forcing the updates via Group Policy in the Group
>> Policy Management
>> >Console Snapin. I've configured the following Policy
>> settings and applied
>> >them towards a test OU:
>> >
>> >* Configure Windows Updates - Enabled, with Option #4
>> (Automatically
>> >download and Install the Updates based on the Specified
>> Schedule - which is
>> >daily at 4:00pm). This seems to work OK.
>> >
>> >* Specify Intranet Microsoft Update Service Location -
>> Enabled, and a server
>> >designated for retrieving and catalogging updates is
>> specified as both the
>> >detecting server and the statistics server. This seems to
>> work OK.
>> >
>> >* No Auto Restart for Scheduled Automatic Updates
>> Installations - Enabled.
>> >This is where I seem to be having my problem. I enable
>> this policy because I
>> >don't want to force the reboot at the exact moment in
>> time the updates are
>> >installed. It is acceptable in our environment to wait
>> until the machine gets
>> >rebooted by an intervening user naturally (this happens
>> often). However, even
>> >though I've enabled this policy, after the updates
>> install, the client
>> >exhibits a strange behavior and says:
>> >
>> >"Your updates have been installed successfully. To
>> Complete Installation,
>> >you must restart your computer. Do you want to Restart
>> your Computer Now?"
>> >and displays a "YES" and "NO" button. Here's the problem:
>> THE NO BUTTON IS
>> >GREYED OUT, so the user can't click it. They are forced
>> to say yes, since the
>> >message screen cannot be closed or moved and is right in
>> the middle of the
>> >screen.
>> >
>> >I didn't expect to see this prompt because I have the "No
>> Auto-Restart for
>> >Scheduled Automatic Updates Installations" policy enabled.
>> >
>> >What can I do to fix this? Has anyone else experienced
>> this problem?
>> >
>> >
>> >
>> >Thanks in Advance and HELP,
>> >Louis
>> >.
>> >
>>


.

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: SUS
    ... > I have setup a SUS Server on win2k. ... 0-2.reg will not configure your machine to automatically download updates from ... critical updates or service packs that your machine needs. ... It will also ask you if you want to install them, ...
    (microsoft.public.windows.server.general)
  • Re: Disaster Restore SBS2003
    ... If you had the server set to download updates automatically (never ... then install any service packs to return the server to the same service pack ... have the correct version of NTBackup prior to the restore. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... the old array was a raid 5 that should not have become so rooted but the twit who built the server did not actually enable the spare drive to act as a spare!! ... The problem is SBS is unique and I've rarely if ever seen it work. ... The server has been chugging away in a small business environment for several years and I have administered it for them for about a year making sure that the updates were installed and their mailboxes were managed etc etc. ... My main reason for slipstreaming the install is because I cannot get the original 2003 server install to cope with the new hardware and it falls over part way into the install - BSOD bit. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot activate SBS 2003 SP2
    ... everywhere and sitting on the case of the server is the old board - balanced ... slip stream SBS you would have had it ages ago. ... My main reason for slipstreaming the install is because I cannot get ... updates that need to be applied if one is to have a succesful outcome ...
    (microsoft.public.windows.server.sbs)