On-Premise Agent Installation Best Practices
- Install On-Premise Agents on Domain Controllers
- We support On-Premise Agents being installed on servers; however, installing an On-Premise Agent on a Domain Controller will result in more Inspector Auto-Discovery, and therefore, less manual work.
- Generally, Install One On-Premise Agent per Network
- Our Agents speak across VPN tunnels
- Our Agents DO NOT speak across Active Directory Domains, so if you have two Active Directory Domains in one network, then you'll need an Agent within each Active Directory Domain.
- Install an Additional On-Premise Agent on any Server NOT Tied to an Active Directory Domain
- The additional Agent will auto-activate an Inspector for the local Windows server, and that Inspector will auto-discover a Hyper-V or SQL Server Inspector if either system is present
- Agent Names must be unique. Include a unique identifier in the Agent script to ensure all Agents will have a unique name.
On-Premise Agent Installation = Inspector Auto-Discovery
When you roll out an On-Premise Agent, there is a potential for the Auto-Discovery of four Inspectors:
- Upon install, an On-Premise Agent will auto-activate an Inspector for the local Windows Server
- After the Windows Inspector runs, it will auto-discover an Active Directory Inspector
- Once activated and successfully run, the Active Directory Inspector will auto-discover Inspectors for any additional Windows servers within its Domain
- Once activated and successfully run, the Windows Inspectors will Auto-Discover Inspectors for any Hyper-V or SQL Server Inspectors installed
The script below provides for a basic install of the Roar Agent via ConnectWise Automate using our MSI installer.
- The script takes in variables associated with your Roar instance such as the URL, Access Key ID and Secret, and completes an install.
- This script will be supported on a best-effort basis.
The current version of this script does not set the Agent service's "Run As" user or associate the Agent with an Environment upon install. The script can be modified to meet your particular needs by modifying the parameters passed into our MSI install. Full details of how the MSI is parameterized are available on our MSI Installer documentation page.
Download the Automate Installation Script
Then, import it into your ConnectWise Automate instance. System > General > Import > XML Expansion
The imported script is named "Roar-Agent Installer."
- Open the script and populate the variables (lines 1-4) from your Roar setup
- Create Ticket: Whether or not you would like a service ticket created for a failed install
- Roar URL: Insert your Roar URL (e.g., roar.app.liongard.com)
- Roar Access Key: Insert your Roar Access Key generated from your Roar instance (See Step 1: Obtain Your Access Token and Key)
- Roar Access Secret: Insert your Roar Access Key Secret from the steps above
- Assign the Agent to an Environment
- This script does not assign the Roar Environment to the newly installed Agents, so newly installed Agents will need to be assigned an Environment from the Admin > Agents screen in Roar.
- If your Automate instance has access to company names that precisely match the Roar Environment names, this script can be expanded to add that information as a part of the scripted process by adding the ENVIRONMENT= parameter to the msiexec.exe call.
- Additional details of how our MSI installer is parameterized are available in the MSI Installer documentation.
Thanks to Roar partner Matthew Weir for sharing the above ConnectWise Automate script. If you'd like to share how your team is using automation with Roar, email us at [email protected]
Last Updated: 2020-07-21
Updated 20 days ago