Skip to content
English
getvim.com
  • There are no suggestions because the search field is empty.

Troubleshooting GPO Deployment

If you're experiencing issues with remote deployment via GPO, follow the steps below to troubleshoot common problems and ensure Vim Connect installs smoothly.

The network shared folder is inaccessible from a workstation/the script is not running due to permission issues. 

  1. Ensure the sharing permissions include “Everyone” and it has only read permissionsa
  2. Ensure the security permissions for the shared folder include "Everyone" and that "Read & execute," "List folder contents," and "Read" permissions are allowed. b

The GPO does not appear in the list when running gpresults-r. 

  1. On the workstation, open CMD as admin and run gpresult -r (this will show which GPOs applied after running gpupdate /force). Notice the output under COMPUTER SETTINGS, if you do not see the GPO you created listed there, then it might mean that the GPO was not applied domain-wide on not under the right OU. c
  2. Make sure you applied the policy to the right OU, or if you want to apply the policy domain-wide, make sure you applied the policy right under the default. d

The scheduled task is not running or not being created. 

  1. Make sure you set the task to run as NT AUTHORITY\SYSTEM user
  2. Double check that the GPO is linked correctly (domain-wide or applied to the right OU)
  3. To verify that the scheduled task was created and launched, open Event Viewer on the workstation and navigate to Applications and Services Logs → Microsoft → Windows → TaskScheduler → Operational
  4. Click Find then type the name of the scheduled task you configured while configuring the GPO
  5. You should now see find some logs about the task, go through them and see if you find a log that states: “The NT AUTHORITY\System” registered Task Scheduler task “\task name” (as in the picture below) e

Note: After the MSI gets installed, It will generate an installation log called vim-connect-msi-install.log on your C:\ drive (“C:\vim-connect-msi-install.log“) You can check it for any errors. If the log is not present, it could indicate an issue with the deployment.