ImmyBot Agent Deployment
Purpose
This solution outlines the full process for automatically deploying the ImmyBot agent using ConnectWise RMM, utilizing custom fields, a dynamic device group, a scheduled monitor, and an automated installation script.
Associated Content
Custom Fields
| Name | Example | Type | Level | Required | Purpose |
|---|---|---|---|---|---|
| ImmyBot Tenant | xyz | Text | COMPANY | Yes | Subdomain part of your ImmyBot URL used for agent installation configuration. |
| ImmyBot Installer ID | GUID | Text | COMPANY | Yes | Unique installer ID (GUID) for the ImmyBot agent MSI installation. |
| ImmyBot Installer Key | String | Text | COMPANY | Yes | Installer key string required to activate and authorize agent installation. |
| Deploy ImmyBot | Workstations and Servers | Dropdown | COMPANY | Yes | Select operating systems to enable auto deployment for the agent. |
| ImmyBot Exclusion (Site) | Flag | SITE | No | Prevents agent deployment at specific sites. | |
| ImmyBot Exclusion (Endpoint) | Flag | ENDPOINT | No | Prevents agent deployment to specific endpoints or devices. |
Group
| Name | Purpose |
|---|---|
| ImmyBot Agent Deployment Enabled | Dynamic group targeting devices that are eligible for auto deployment (based on OS and not excluded). |
Monitor
| Name | Type | Schedule | Purpose |
|---|---|---|---|
| ImmyBot Agent Deployment | Script | Every 24 hours | Monitors and runs the agent installation script on devices missing the ImmyBot agent. |
Task
| Name | Purpose |
|---|---|
| Install ImmyBot Agent | PowerShell script that installs or reinstalls the ImmyBot agent on selected devices. |
Implementation
Step 1: Create the Required Custom Fields
Create all the custom fields listed above under SETTINGS → Custom Fields in CW RMM. See individual documentation pages for configuration details.
- ImmyBot Tenant
- ImmyBot Installer ID
- ImmyBot Installer Key
- Deploy ImmyBot
- ImmyBot Exclusion (Site)
- ImmyBot Exclusion (Endpoint)
Step 2: Create the Dynamic Group
Create the group ImmyBot Agent Deployment Enabled under ENDPOINTS → Groups as a dynamic group. This group should match workstations or servers with deployment enabled and not excluded.
Step 3: Create the Installation Task
Create the install script task Install ImmyBot Agent under AUTOMATION → Tasks. Set up all required variables and use the detailed script from the referenced documentation.
Step 4: Set up the Deployment Monitor
Configure the monitor ImmyBot Agent Deployment under ENDPOINTS → Alerts → Monitors to target the deployment enabled group, running every 24 hours and triggering the installation task on missing/broken agents.
Step 5: Fetch and Apply Required Values
Follow the guide in the Install ImmyBot Agent documentation to fetch the Tenant, Installer ID, and Installer Key from your ImmyBot portal and set these in the appropriate custom fields for each client.
FAQ
Q: What happens if an endpoint is excluded at the site or endpoint level?
A: Devices or sites flagged for exclusion will not receive the agent, regardless of task or group membership. However, the Install ImmyBot Agent task can be executed manually.
Q: How often does the solution check devices for agent installation?
A: The monitor runs every 24 hours, but this can be changed in the monitor’s configuration.
Q: Can I trigger the agent install manually?
A: Yes, the Install ImmyBot Agent task can be run on demand independent of monitor or group status.
Q: Where do I find the installer ID and key for my ImmyBot tenant?
A: Generate these in your ImmyBot portal by going through the agent installer workflow; see details in the install script documentation.
Q: What OSes are supported for automated deployment?
A: Supported OS selection is controlled by the Deploy ImmyBot custom field (Workstations, Servers, Both, or None).
Q: Does the installer support forced reinstallation?
A: Yes, enable the "ReinstallAgent" runtime parameter when running the install task/script to force a reinstall even if the agent is present.