Deploy with ConnectWise RMM
Add a per-client PowerShell script in ConnectWise RMM, run it as System on one device, then schedule it as a task on the client.
Written By The Lemhi Product Team
Last updated 10 days ago
For technicians on ConnectWise RMM (the SaaS RMM, formerly Continuum). When you're done, the client has its own PowerShell script running as a daily Task on its company or site.
Before you start
The client's script. In Engage, open the client, then Shadow AI Usage under Compass, then the Deployment tab. Expand Deploy with your RMM and click Copy script. It already carries this client's key, so paste it unchanged. This guide keeps one copy per client. If you'd rather keep one script, store each client's key in a client-level RMM variable and put that variable in place of the
$ClientKeyvalue. The full script and what it does: Deploy the extension with your RMM.
Add the script
Open Automation → Tasks → Add, open the Script Editor tab, then Add Function → PowerShell script.

Set Name to
Lemhi AI Usage extension - <Client>.Set Type to PowerShell and OS to Windows.
Set Execute as to System.
Paste the script you copied from Engage. Don't edit it.
Click Save.
Pilot on one computer
Run the task on one device.
Check the task's execution history for success.
Restart the browsers on that computer.
Within a few minutes it appears on the client's Deployment tab.
"Extension not installed yet" is expected until the browser restarts. A failed run (exit code 1) means the key isn't a valid Lemhi key, usually because it was mangled in the copy, or a value didn't read back. Copy the script from Engage again and re-run. If the run fails with does not match what this script wrote, something rewrote the policy keys while the script ran, such as Group Policy, Intune or another RMM job: see Computer doesn't appear on the Deployment tab.
Schedule it on the client
Create a task from the script targeting the client's company or site (Windows devices), with a daily schedule. Re-runs are safe.
Rotate the key or remove
To rotate the key, regenerate it on the Deployment tab, then click Copy script again: the copied script carries the new key. Edit the client's script and run the task now. See Rotate a client's deployment key.
To remove the extension: Disable the task, add the removal script as a script, and run it on the client. See Remove the extension from a client's computers.
Related
Was this helpful?
More in Deploy by RMM
Deploy with Kaseya VSA 9Deploy with Kaseya VSA 10Deploy with N-able N-centralDeploy with N-able N-sightStill need help? Ask the team