Achieve multiple agent installation using Group Policy. Automatically install agents on multiple devices in a domain environment, and on any device logging into the domain that doesn’t already have the agent.
Install the Atera agent using Group Policy
For agent installation using GPO, we have to first download the installer.
Download agent installer
1. Access your Atera account, and click on Install agent.
2. Select Windows (.msi) for the OS version and click on Next.
3. Select the customer to whom you want the devices to be assigned and click on Next.
3. Select the site to whom you want the devices to be assigned and click on Next.
4. The installer setup is finished, now download the installer.
Upload agent installer to SYSVOL
The Atera agent installer has to be saved on a network path, that domain devices can access. We recommend using the SYSVOL folder. To upload the installer to the SYSVOL folder:
1. On your Primary Domain Controller, access the network path: \\domain-name.com\sysvol
2. Upload the agent installer create, in the SYSVOL folder.
Done! Now the only thing left to do is to create the GPO for the installation.
Create Group Policy Object
1. On the primary domain controller, open the Group Policy Management and edit the Default Domain Policy.
2. Under Computer Configuration, click on Policies.
4. Click on Software Settings >Software Installation.
5. Click on New, then Package...
6. Choose the Setup file from the SYSVOL folder and click Open.
7. Right-click on the new package, and click Properties.
Troubleshooting Group Policy Installation
An internet connection is required for agent installation.
To enable: Go to Computer Configuration > Administrative Templates > System > Logon > Always wait for the network at computer startup and logon – Enabled
Note: This can significantly slow down off-domain logins for laptops and wireless clients.
If the device is slow (e.g., old hardware, bad network) you might need to extend the timeout:
To extend: Go to Computer Configuration > Policies > Administrative Templates > System > Group Policy -> Specify startup policy processing wait time - Set timeout (in seconds)
Language discrepancies can cause installation failure. To work around this, it is necessary to remove the language check:
To remove the language check: Go to Computer Configuration > Policies > Software Installation > Right Click AteraGPO > Properties > Deployment > Advanced > Ignore language when deploying this package - Enabled
Previously installed agent: Sometimes, the installation will fail if an agent was previously installed through a different account. One of the following two registry keys might be the cause:
Note: After any of the above settings are applied, be sure to run gpupdate /force in order to force the GPO to update. Then reboot, and wait for the policy to enforce.