How to configure Group Policy Management for bulk agent deployment on Windows servers via Active Directory?
Overview
When adding multiple Windows servers through Active Directory, you can automate the deployment of the Applications Manager's FSO agent for Windows using Group Policy. This method ensures that the agent installation script runs automatically on all target machines during system startup.
Steps to configure Group Policy
Follow the steps given below to configure Group Policy:
Open Group Policy Management from Start → Administrative Tools → Group Policy Management. Right-click on your domain and select Create a GPO in this domain, and Link it here in the console tree. Provide a suitable name for the new GPO. Right-click the newly created GPO and select Edit to open the Group Policy Management Editor. Navigate to Computer Configuration → Policies → Windows Settings → Scripts → Startup. Double-click on Startup to open the Startup Properties window. Click Add, then click Browse, and select the agent installation script ( \\<MyServer>\MyShare\InstallAgent.vbs). Ensure the script is accessible by all the target Windows servers.Click OK to save the configuration and close the Group Policy Management console.
Note:
- Ensure that all target systems have access permissions to the shared location where the installation script is hosted.
- The script will execute during system startup, enabling automatic agent installation across all systems linked to the GPO.
- Verify that the agent installation package and required dependencies are correctly referenced within the script.
Verification
After applying the policy:
- Restart the target machines (or wait for the next reboot cycle).
- Log in to Applications Manager and navigate to Settings → Manage Agent → View Agents
- Confirm that the agents are successfully installed and reporting data.
New to ADSelfService Plus?
Related Articles
Setting WMI access through Active Directory and Group Policy Object for non-admin user
In our case, we run Active Directory on Windows 2008 R2 and we want to scan the target machine which is Windows 2012 R2 machine. Our domain is called “APMCLU” and we name our dedicated WMI user-account “wmiuser”. First – Setting done from Active ...How to add an APM Insight Python agent in Kubernetes via InitContainers?
Adding the APM Insight Python agent via init containers in Kubernetes enables the seamless integration of performance monitoring for Python applications, ensuring efficient tracking and analysis of application behavior within the Kubernetes ...APM Insight Java Agent – Onboarding & Troubleshooting Guide
This guide helps support engineers troubleshoot cases where the APM Insight Java Agent is not onboarding (not appearing in Applications Manager) after installation. Follow the step-by-step verification checklist in Section 2 to quickly diagnose and ...How can I configure application filtering for the .NET Agent on non-desktop Windows servers?
Steps to follow Non-Windows desktop servers have the capability to set up application filtering for monitoring exclusively through the agent configuration file. To configure application filtering for your non-Windows server, follow the steps given ...APM Insight Python Agent – Offline Installation via Environment Variables
This article explains how to install the APM Insight Python Agent in offline (air-gapped) environments using environment variables. No code changes or pip install required. Refer: APM Insight Python Agent – Official Installation Help 1. Prerequisites ...