RE: Reboot from Startup script--failing!
From: Jeff (jjb_at_news.postalias)
Date: 06/29/04
- Next message: Chriss3: "Re: Publishing Software"
- Previous message: mélanie paterson: "Hide Start menu"
- In reply to: Bob Qin [MSFT]: "RE: Reboot from Startup script--failing!"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 29 Jun 2004 09:23:06 -0700
>I would like to suggest that you use gpresult tool
>check if the client apply the group policy.
The client definitely does apply the group policy,
and the startup scripts run as expected. Here's
what we see, and the work-around that we've found:
Some of our local group policies do things that might
require a reboot. If a reboot is required, a particular
registry value (that we created) is set to 1.
The last group policy in the ordered list
has a startup script that checks the registry
value and reboots if it is set to 1.
We know from testing that the registry key *does*
get set, and more importantly, if we use the
"psshutdown" tool from SysInternals
psshutdown -r -f -t 00
the computer reboots, as expected. However,
shutdown -r -f -t 00
has no effect, and no error message is
logged on the client. Using the Reboot() method
in a WMI script doesn't work, either. The
shutdown/reboot request just gets ignored.
So, we've found that replacing "shutdown"
with "psshutdown" in the script fixes the problem,
but we still don't understand why there was any
problem--that is, we can't imagine why the
built-in shutdown mechanism doesn't work, or
what aspect of Group Policy might have broken
it from within a startup script. ??
- Next message: Chriss3: "Re: Publishing Software"
- Previous message: mélanie paterson: "Hide Start menu"
- In reply to: Bob Qin [MSFT]: "RE: Reboot from Startup script--failing!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
