Disabling automatic reboot after automatic updates

Is there a way to disable the automatic reboot after an XP machine performs
an automatic update? Unfortunately we are still running on a NT network so
we're not updating via the network. All XP machines have auto update turned
on but since the users log on as Power Users, it won't give them the choice
to reboot at a later time (or cancel the restart).

Any suggestions?

Thanks in advance.

Patrick

"Mokupono" <> wrote in message
news:38F3769B-44C2-42E9-B4D8-...
> Is there a way to disable the automatic reboot after an XP machine performs
> an automatic update? Unfortunately we are still running on a NT network so
> we're not updating via the network. All XP machines have auto update turned
> on but since the users log on as Power Users, it won't give them the choice
> to reboot at a later time (or cancel the restart).
>
> Any suggestions?


Why not give them full control, e.g. at least prompt to install?
Then if a reboot is required it is their responsibility because
they allowed the install.


>
> Thanks in advance.
>
> Patrick


HTH

Robert Aldwinckle
---

Because that would give the user the ability to install anything they want on
company machines, which is what we are trying to avoid.

"Robert Aldwinckle" wrote:

> "Mokupono" <> wrote in message
> news:38F3769B-44C2-42E9-B4D8-...
> > Is there a way to disable the automatic reboot after an XP machine performs
> > an automatic update? Unfortunately we are still running on a NT network so
> > we're not updating via the network. All XP machines have auto update turned
> > on but since the users log on as Power Users, it won't give them the choice
> > to reboot at a later time (or cancel the restart).
> >
> > Any suggestions?
>
>
> Why not give them full control, e.g. at least prompt to install?
> Then if a reboot is required it is their responsibility because
> they allowed the install.
>
>
> >
> > Thanks in advance.
> >
> > Patrick
>
>
> HTH
>
> Robert Aldwinckle
> ---
>
>
>
>

If the users do not have local administrator privileges, then the /only/ way
you can 'control' the restart of the machine is to not install the updates
while they're trying to use the machine.

There's a reason why the default installation time is set to 3am. :-)

btw... there's an inconsistency in what you've posted. If you're concerned
about users having the ability to "install anything they want", then you
might want to review the authority of a "Power User" vis a vis the ability
to install software, specifically:

Power Users can:
a.. Run legacy applications, in addition to Windows 2000 or Windows XP
Professional certified applications.
b.. Install programs that do not modify operating system files or install
system services.
c.. Customize systemwide resources including printers, date, time, power
options, and other Control Panel resources.
d.. Create and manage local user accounts and groups.
e.. Stop and start system services which are not started by default.
Note the second item..: "Install programs that do not modify operating
system files, or install system services." I tell you.. there's a lot of
that out there, and the more typical stuff you don't want installed on those
systems falls right into that classification!


"Mokupono" <> wrote in message
news:3C79A693-0472-41D1-8852-...
> Because that would give the user the ability to install anything they want
> on
> company machines, which is what we are trying to avoid.
>
> "Robert Aldwinckle" wrote:
>
>> "Mokupono" <> wrote in message
>> news:38F3769B-44C2-42E9-B4D8-...
>> > Is there a way to disable the automatic reboot after an XP machine
>> > performs
>> > an automatic update? Unfortunately we are still running on a NT network
>> > so
>> > we're not updating via the network. All XP machines have auto update
>> > turned
>> > on but since the users log on as Power Users, it won't give them the
>> > choice
>> > to reboot at a later time (or cancel the restart).
>> >
>> > Any suggestions?
>>
>>
>> Why not give them full control, e.g. at least prompt to install?
>> Then if a reboot is required it is their responsibility because
>> they allowed the install.
>>
>>
>> >
>> > Thanks in advance.
>> >
>> > Patrick
>>
>>
>> HTH
>>
>> Robert Aldwinckle
>> ---
>>
>>
>>
>>

"Mokupono" <> wrote in message news:3C79A693-0472-41D1-8852-
....
> "Robert Aldwinckle" wrote:
>> Why not give them full control, e.g. at least prompt to install?

> Because that would give the user the ability to install anything they want on
> company machines, which is what we are trying to avoid.


I don't see that. AU shows them only what is being offered for download.
You could say it would give the user the ability to *avoid* installing anything
you want them to install and be more accurate I think. That would be
especially true if you were having them connect to your own WSUS
instead of Microsoft's WU or MU.


Robert
---