Skip to main content

How to configure a Windows 7 Startup Script

Add or Configure Windows 7 Startup Script

Startup script runs when the computer turns on and runs under local system account.

To run Windows 7 startup script, needs to configure two Group Policy Settings. ( I had use this settings to deploy Office 2010 in an AD Environment)

Steps provided here are from Windows 7 but still same settings would apply to server GPOs.
  • Run startup scripts asynchronously set to Disabled 
  • Run startup scripts visible set to Enabled
Press Windows + R  and type: "gpedit.msc" (don't include quotes) and click "OK".

Local group policy window will open. Configure the two settings described above. 

Follow steps below on how to configure the Local Group Policy for the startup scripts.

On Local Computer Policy window.
Expand and click on  Computer Configuration.
Select Administrative Templates
Click  on System
Then scroll down to find and select Scripts.

On the right hand side window, you will be able to select and configure the settings for the "Scripts".

Set these settings below:

"Run startup scripts asynchronously" - Set state to "Disabled"
"Run startup scripts visible" - Set state to "Enabled"

After configuring this settings assuming that the script has been placed on the startup policy settings, reboot the PC and the scripts will run automatically.

Please follow steps below on how to configure or place the startup script.

Under Local Computer Policy.
Click and expand Computer Configuration
Select Windows Settings
Then select on Scripts (Startup/Shutdown)

On the right hand side of the window, double click on "Startup"

Then the startup properties window will open, click on "Add" button, a window will pop up browse and find  the script you want to run and click OK.

After clicking the "OK" button, you will notice that the script will be listed on the "Startup Properties" and it's ready to roll.

There you go a quick tutorial on how to use startup script on Windows 7.

Hope you find it helpful :)


Popular posts from this blog

Copy a single file using robocopy

Copy a single file using robocopy from a local folder to a shared folder on the network.
A simple rule of thumb before any disaster strike, don't interchange the source and the destination.

If source and destination is mistakenly reverse, files might get overwritten. To avoid any loss of data do a test with a dummy file to ensure things work perfectly.
Robocopy [source][destination]   [file to be copied]
robocopy c:\local_c_folder  \\PC_network\shared_folder   file_to_be_copied_xx.txt
The command will be completed successfully provided the network access right has no issues.

Robocopy works quite good on large files. A simple copy or xcopy command will also work but the speed might vary.

However, if the file (ex. an ISO file) and is more than 4GB and the filesystem  of the thumbdrive or the storage is FAT system, then robocopy or any methods of copying will not work. Since FAT has a file size limitation of less than 3GB.

Robocopy is free it can be accessed from command line. No ne…

WMIC List printers

WMIC comes handy if you are a command line junkie.

To list printers via command line type:

wmic printer get name  = = = this will list all the printers installed on a workstation

To list the printer name and the port name of the printers, type this command:

wmic printer get name, portname

Type this command below to list the printer drivers:

wmic printer get name, drivername

To get the device id:

wmic printer get name, deviceid

You can deploy a batch file startup script to check which printer is installed on the computers and redirect the output to a shared folder.

PowerShell can also be used in conjunction with WMIC command:

To see more WMIC tips, click on WMIC label below.


Linux Android App cheat sheet:

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username.
WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided.
Why would you need a command line tool if there’s a GUI to check?
If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username.
If you have remote computers, you need to delegate someone in the remote office or location to check.
Or you can just write a batch file or script to automate the task.
Here’s the code below on how get computer model, manufacturer and the username.
Open an elevated command prompt and type:
wmic computersystem get "Model","Manufacturer", "Name", "UserName"
Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name.
A sample output below will be generated if the co…