Event ID 1130 — Group Policy Scripts Processing
Updated: January 6, 2009
Applies To: Windows Server 2008 R2
During Group Policy processing, the Scripts client-side extension is responsible for launching not only computer startup and shutdown scripts but also user logon and logoff scripts.
|Product:||Windows Operating System|
%tGPO Name : %6
%tGPO File System Path : %7
%tScript Name: %8
Correct a scripts extension failure
Possible resolutions include:
- Logon and logoff scripts: Ensure the user has the proper file permissions to read and run the script. Users must have the Read and Execute NTFS permission. If the script is located on a network share, the user must also have Read share permissions.
- Startup and shutdown scripts: Ensure the computer account has the proper file permissions to read and run the script. Computers must have the Read and Execute NTFS permission. If the script is located on a network share, the computer must also have Read share permissions.
- Verify the user or computer can start the script from %SystemRoot%\system32 folder.
Group Policy applies during computer startup and user logon. Afterward, Group Policy applies every 90 to 120 minutes. Events appearing in the event log may not reflect the most current state of Group Policy. Therefore, you should always refresh Group Policy to determine if Group Policy is working correctly.
To refresh Group Policy on a specific computer:
- Open the Start menu. Click All Programs and then click Accessories.
- Click Command Prompt.
- In the command prompt window, type gpupdate and then press ENTER.
- When the gpupdate command completes, open the Event Viewer.
Group Policy is working correctly if the last Group Policy event to appear in the System event log has one of the following event IDs: