Sign in with
Sign up | Sign in
Your question

Problems with startup script

Last response: in Windows 2000/NT
Share
Anonymous
July 16, 2005 9:31:16 AM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Hello all,
I have a Wsf-Scriptfile that I would like to run on all our machines on
startup. Because it requires to be run with cscript.exe I have
configured a CMD file to be run as startup script.

It is configured as:

Script.exe //H:CScript //NoLogo //S
\\[domainname]\sysvol\[domainname]\scripts\serverstart.wsf

It looks like the wsf file is not run at all, however.
I also tried the following, but without success:

Script.exe //H:CScript //NoLogo //S
serverstart.wsf

In the GPO, the script is configured to be run as:

\\[domainname]\sysvol\[domainname]\scripts\serverstart.cmd

The Script and CMD works without problem if I run it manually after the
server is started and I log on to the machine.

Again I have tried without the path, but without success.
Is there anyone that has experienced and solved similar problems?

Thanks in advance for any help...

Markus
Anonymous
July 16, 2005 11:22:37 PM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Hi,

A startup script runs without a user, with the credentials of the computer
account. Make sure the Computer account (computer object) has rights to read
the wsf in the unc you gave. I generally give the domain group "Domain
Computers" permissions on the share. All computers joined to the domain
should be members of this group.

--
Richard
Microsoft MVP Scripting and ADSI
Hilltop Lab web site - http://www.rlmueller.net
--
"Markus" <support@epp-online.com> wrote in message
news:1121517076.435190.294380@o13g2000cwo.googlegroups.com...
> Hello all,
> I have a Wsf-Scriptfile that I would like to run on all our machines on
> startup. Because it requires to be run with cscript.exe I have
> configured a CMD file to be run as startup script.
>
> It is configured as:
>
> Script.exe //H:CScript //NoLogo //S
> \\[domainname]\sysvol\[domainname]\scripts\serverstart.wsf
>
> It looks like the wsf file is not run at all, however.
> I also tried the following, but without success:
>
> Script.exe //H:CScript //NoLogo //S
> serverstart.wsf
>
> In the GPO, the script is configured to be run as:
>
> \\[domainname]\sysvol\[domainname]\scripts\serverstart.cmd
>
> The Script and CMD works without problem if I run it manually after the
> server is started and I log on to the machine.
>
> Again I have tried without the path, but without success.
> Is there anyone that has experienced and solved similar problems?
>
> Thanks in advance for any help...
>
> Markus
>
Anonymous
July 19, 2005 6:34:17 AM

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Thanks, that did it.
Looks like a colleague changed the default permissions...
!