Scripts Do Not Run

  • Article

You configure scripts (Log on, Log off, Startup, and Shutdown) in a Group Policy object, and the user who is managed by the Group Policy object logs on and later logs off, or starts and then shuts down his or her computer. One or more scripts that were configured to run are not run.

Possible Causes:

  • Group Policy is not applied.

  • Active Directory replication has not yet completed on the domain controller in use.

  • File Replication Service (FRS) replication has not yet completed on the domain controller in use.

Diagnostic Tests:

Confirm that the Group Policy Scripts extension is applied to the user's computer. Run Gpresult.exe in verbose mode, and examine the output under the heading User received " Scripts " settings from these GPOs .

Check to see if the user can successfully connect to a domain controller.

Run Gpotool.exe and confirm that the user can successfully connect to a domain controller on the network. If the result of this test does not show a domain controller, discontinue troubleshooting Group Policy, and investigate network connectivity to your domain controller. You can use Netdiag.exe to investigate your network connectivity further. If you can connect to a domain controller, check to see if other computers in the same organizational unit are successfully receiving the Group Policy Scripts extension Group Policy settings. If other computers are successfully receiving these Group Policy settings, it is probably a replication issue.

Run Gpotool.exe in verbose mode to verify that the Group Policy object that was not applied has been successfully replicated to all domain controllers.

It might be that the Group Policy Scripts extension Group Policy settings were applied, but the actual scripts did not run. The user might have received the Group Policy successfully, but failed to receive the actual script due to a synchronization problem with the Sysvol on the domain controller in use.

Run Gpotool.exe in verbose mode to find out which domain controllers have an unsynchronized Sysvol. After you have identified these domain controllers, copy a text file to the Sysvol of one of the domain controllers in question. Confirm that this text file is successfully replicated to the other domain controllers. If it has replicated, increase the version number of Group Policy. Then, at the next logon, the Group Policy is re-applied and the user receives the script. If the text file does not replicate, check the network connectivity between the servers.