Using the Shutdown command over a network

We have command scripts that are scheduled on our server to shut down all
the PCs in specific places using the Shutdown command.

These stopped working recently and all the PCs that are online return
"Access is denied" instead of shutting down.

The script still works if I execute it on a Windows XP desktop.

The only thing I can think of is that we installed Service Pack 2 of WS2003
on that server recently. Any ideas?

hi,
the user is the same ?
--
Dragos CAMARA
MCSA Windows 2003 server


"NZSchoolTech" wrote:

> We have command scripts that are scheduled on our server to shut down all
> the PCs in specific places using the Shutdown command.
>
> These stopped working recently and all the PCs that are online return
> "Access is denied" instead of shutting down.
>
> The script still works if I execute it on a Windows XP desktop.
>
> The only thing I can think of is that we installed Service Pack 2 of WS2003
> on that server recently. Any ideas?
>
>

Might be something to do with the account that the script is executing
under, mabye one of the system accounts no longer supplies it's user
credentials when challenged for access to a network resource.

Try making sure that the script is executing as a normal user that you have
created and assigned the correct rights over the client computers.


"NZSchoolTech" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We have command scripts that are scheduled on our server to shut down all
> the PCs in specific places using the Shutdown command.
>
> These stopped working recently and all the PCs that are online return
> "Access is denied" instead of shutting down.
>
> The script still works if I execute it on a Windows XP desktop.
>
> The only thing I can think of is that we installed Service Pack 2 of
> WS2003 on that server recently. Any ideas?

"Mike Spike" <(E-Mail Removed)> wrote in message
news:e$(E-Mail Removed)...
> Might be something to do with the account that the script is executing
> under, mabye one of the system accounts no longer supplies it's user
> credentials when challenged for access to a network resource.
>
> Try making sure that the script is executing as a normal user that you
> have created and assigned the correct rights over the client computers.

The user that this task runs as is a member of the Domain Admins group. The
user account has not changed in all the time we have made use of this
scheduled task.

If I log onto an XP workstation as a member of the Domain Admins group and
then run that script, it works for most PCs, but there will still be an
occasional one that gives the same "Access denied" error message.