To assign computer startup scripts |
-
Open the Local Group Policy Editor.
-
In the console tree, click Scripts (Startup/Shutdown). The path is Computer Configuration\Windows Settings\Scripts (Startup/Shutdown).
-
In the results pane, double-click Startup.
-
In the Startup Properties dialog box, click Add.
-
In the Add a Script dialog box, do the following:
- In the Script Name box, type the path
to the script, or click Browse to search for the script file
in the Netlogon shared folder on the domain controller.
- In the Script Parameters box, type any
parameters that you want, the same way as you would type them on
the command line. For example, if your script includes parameters
called //logo (display banner) and //I (interactive mode), type
//logo //I.
- In the Script Name box, type the path
to the script, or click Browse to search for the script file
in the Netlogon shared folder on the domain controller.
-
In the Startup Properties dialog box, specify the options that you want:
- Startup Scripts for <Group Policy
object>: Lists all the scripts that currently are assigned
to the selected Group Policy object (GPO). If you assign multiple
scripts, the scripts are processed in the order that you specify.
To move a script up in the list, click it and then click Up.
To move a script down in the list, click it and then click
Down.
- Add: Opens the Add a Script
dialog box, where you can specify any additional scripts to
use.
- Edit: Opens the Edit Script
dialog box, where you can modify script information, such as name
and parameters.
- Remove: Removes the selected script
from the Startup Scripts list.
- Show Files: Displays the script files
that are stored in the selected GPO.
- Startup Scripts for <Group Policy
object>: Lists all the scripts that currently are assigned
to the selected Group Policy object (GPO). If you assign multiple
scripts, the scripts are processed in the order that you specify.
To move a script up in the list, click it and then click Up.
To move a script down in the list, click it and then click
Down.
Additional considerations
- To complete this procedure, you
must have Edit setting permission to edit a GPO. By default,
members of the Domain Administrators security group, the Enterprise
Administrators security group, or the Group Policy Creator Owners
security group have Edit setting permission to edit a
GPO.
- Startup scripts are run under the Local
System account, and they have the full rights that are associated
with being able to run under the Local System account.
- Beginning in Windows Vista, startup
scripts are run asynchronously, by default. This is a different
behavior from earlier operating systems.
- Setting startup scripts to run synchronously
may cause the boot process to run slowly.
- In Windows 7 and Windows Vista,
startup scripts that are run asynchronously will not be visible.
Enabling the Run Startup Scripts Visible policy setting will
have no effect when running startup scripts asynchronously.
- Local Group Policy Editor and the Resultant
Set of Policy snap-in are available in Windows Server 2008 R2 and
Windows 7 Professional, Windows 7 Ultimate, and Windows 7
Enterprise. For more information, see http://go.microsoft.com/fwlink/?LinkId=139815.