Kaseya Agents Continue Deployment Despite Inactive Domain

If Kaseya agents persistently deploy even after marking the domain as inactive, the following steps can help troubleshoot and resolve the issue.

1. Open Group Policy Management: Launch the Group Policy Management console on your Windows Server.

2. Navigate to Group Policy Objects: In the left pane of the Group Policy Management console, expand the forest and domain, then select "Group Policy Objects."

3. Locate ADAgentDeployGPO: Right-click on the ADAgentDeployGPO in the list of Group Policy Objects, then select "Edit." This will open the Group Policy Management Editor.

4. Navigate to Startup Scripts: In the Group Policy Management Editor, expand "Computer Configuration," then "Policies," "Windows Settings," and finally "Scripts (Startup/Shutdown)."

5. View Startup Properties: In the right pane, double-click on "Startup" to open the Startup Properties window.

6. Remove InstallKAgent.vbs: In the Startup Properties window, you'll see a list of scripts configured to run at startup. Look for "InstallKAgent.vbs" in the list. Select it, then click the "Remove" button to delete it from the list.

7. Apply Changes: Click "OK" to close the Startup Properties window, then close the Group Policy Management Editor.

8. Force Group Policy Update: To ensure the changes take effect immediately on client computers, run the following command in Command Prompt with administrative privileges:

  • gpupdate /force

After following these steps, the "InstallKAgent.vbs" script will no longer be executed at startup for computers affected by the ADAgentDeployGPO and agents should no longer be deploying from this domain.

Have more questions?

Contact us

Was this article helpful?
0 out of 0 found this helpful

Provide feedback for the Documentation team!

Browse this section