Startup Script in Group Policy

  • Thread starter Thread starter john.marthe
  • Start date Start date
J

john.marthe

Hi,

I have a batch file script that I can use to load a program to our
workstations that runs fine when I log on the computer with an
administrator account. And I want to push it out with Group Policy.
When I push it out with as a Startup Script, it starts, but fails to
load. I believe that it is a rights issue. I cannot create an msi file
since it is a novell based executable (GroupWise).
Since it is not an msi, the Always install with elevated priviledges
for the Windows Installer does not help.
Is there some way to force the batch file to run with credentials?
What can I do to install this program?

thanks,
John
 
Howdy John!

I have a batch file script that I can use to load a program to our
workstations that runs fine when I log on the computer with an
administrator account. And I want to push it out with Group Policy.
When I push it out with as a Startup Script, it starts, but fails to
load. I believe that it is a rights issue. I cannot create an msi file
since it is a novell based executable (GroupWise).
Since it is not an msi, the Always install with elevated priviledges
for the Windows Installer does not help.
Is there some way to force the batch file to run with credentials?
What can I do to install this program?
Click to expand...

So you're sure that you deployed it as a Startup Script (SYSTEM context)
and no Logon Script (user context)? What does the batch file do? Can you
let it output what it does to see, where it stops working?

cheers,

Florian
 
Hi,

Startup scripts run under the "System" account which means they have full
access to the machine like an Administrator (unless you have removed the
Default SYSTEM group from the C:\ or the Registry).

There is a GPO that runs startup scripts visable. It is a very handy tool
for troubleshooting. You can see where it is stalling.

I use BATCH files and have no problems installing "most" software on
startup. However, I have had some fail for unknown reasons. One is the ISA
Firewall Client that I have never got to install on startup which is annoying.

Cheers,
Lara
 
When i applied the startup scripts through GP, they are not running on
Wondows XP machines, but they are running successfully on all windows 2000
machines. Can one give me the solution, why they are not running on XP
machines.
 
Howdy!
When i applied the startup scripts through GP, they are not running on
Wondows XP machines, but they are running successfully on all windows 2000
machines. Can one give me the solution, why they are not running on XP
machines.
Click to expand...

If you apply the following two policies to the XP clients, will they
then process the scripts?

"Always wait for the network at computer startup and logon" at
"CompConf\Adm Temp\System\Logon"

"Run logon scripts synchronously" at "Administrative
Templates\System\Scripts"

cheers,

Florian
 
Hi,

What Florian said was correct. You need to enable these at the DOMAIN level.
If XP still isn't running the scripts then there may be something up with
the way you have DNS setup which will affect all group policies with XP. XP
relies heavily on DNS while 2000 is a little less picky. Check my website to
make sure you have DNS setup correctly
http://www.sd61.bc.ca/windows2000/dns.htm

If it is not that then check the event viewer on the XP machines to get any
error messages.

Cheers,
Lara
 
I don't see "Always wait for the network at computer startup and logon"
at
CompConf\Adm Temp\System\Logon.

Plz post the exact solution...
 
Dasharath said:
I don't see "Always wait for the network at computer startup and logon"
at
CompConf\Adm Temp\System\Logon.
Click to expand...

Then you are not working with the GPMC from a XP or 2003.
Your 2000 Client is not showing the options, because of the
"if version" entry in the ADM Template.

Mark
 
Back
Top