Re: Startup Bat File
- From: "Dave Stoecker" <david_stoecker@xxxxxxxxxxxxxxxxx>
- Date: Mon, 24 Apr 2006 16:12:27 -0500
Hi Again Kelli : )
Important distinction to make:
Startup/Shutdown scripts are for functions that pertain to computers, not
users. They run in system context. A startup script cannot for example map
a drive for a user because the user is not yet logged in. It could install
a program that has an unattended install mode, or change machine registry
settings - etc.
Logon/Logoff scripts operate on users, and have access to the current user's
registry settings and such for mapping drives, printers etc.
You appear to be trying to apply the script to certain users - so the
question is, what is your script doing?
If it is setting _user_ application preferences or something it should be a
Login script under user settings in the policy.
Otherwise, as Florian mentioned, you need to give Authenticated Users read
and apply permissions in the GPO, so the computer(s) can process the script.
Hope that helps.
Dave
"Kelli" <Kelli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A53C76B1-6F63-4A64-8E62-4B4B51DEB9CC@xxxxxxxxxxxxxxxx
I have a bat file that I would like to run at startup on specific computers
(will become a group once I get the kinks worked out).
I have tested the bat file and it works outside of group policy but I can
not get it to work within group policy. It is located in computer
configuration\windows settings\scripts\startup. It calles the file
\\server\share\location\NitroDefaults.bat
Are there parameters that I need to add? When I click on show files, it
looks but the folder it finds is empty.
The security settings are as follows
Authenticated Users - None
CREATOR OWNER - None
Domain Admins - Read, Write, Create All Child Objects, Delete All Child
Objects
Enterprise Admins - Read, Write, Create All Child Objects, Delete All
Child
Objects
USER1$ - Read, Apply
USER2$ - Read, Apply
USER3$ - Read, Apply
SYSTEM - Read, Write, Create All Child Objects, Delete All Child Objects
If I look at User 1,2 or 3's gpresult, this policy is called out and is
recognized. If I run gpupdate /force, it gives me the statement "Certain
Computer policies are enabled that can only run during startup. OK to
Reboot?" So I know that it sees the GP.
This policy has not changed since yesterday afternoon, giving it plenty of
time to replicate thru the domain.
I am at a lost for what to do next. I plan on expanding upon this idea
for
other things that need to be done at startup such as mapping printers and
network drives. So any help at all would be greatly appreciated!!
Kelli
.
- Follow-Ups:
- Re: Startup Bat File
- From: Kelli
- Re: Startup Bat File
- Prev by Date: Re: Windows 2000 computers dont update
- Next by Date: Re: Share perms problems with folder redirection
- Previous by thread: Re: Startup Bat File
- Next by thread: Re: Startup Bat File
- Index(es):
Relevant Pages
|