Skip to main content
Deploy by RMM

Deploy with N-able N-sight

Upload the client's script in N-sight Script Manager as an Automated Task, test it on one device, then add it to the client daily.

Written By The Lemhi Product Team

Last updated 10 days ago

For technicians on N-able N-sight RMM. When you're done, the client has its own script in Script Manager, running daily as an Automated Task on the client.

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 $ClientKey value. The full script and what it does: Deploy the extension with your RMM.

Upload the client's script

  1. Paste the script you copied from Engage into a new file, unchanged. Save it as lemhi-extension-<client>.ps1.

  2. Open Settings → Script Manager → Add.

  3. Choose the Automated Task type (not Script Check) and upload the .ps1.

  4. Name it Lemhi AI Usage extension - <Client> and set a timeout of 120 seconds.

The Add User Defined Scripts dialog with the name and the client's .ps1 filled in

Pilot on one computer

  1. Right-click one device → Add Automated Task (or Run Task Now).

  2. Pick the client's script.

The Add Automated Task script picker, with the client's script under a Lemhi category

  1. Check the result. N-sight reads exit code 0 as pass.

  2. Restart the browsers on that computer.

  3. 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

Right-click the client (or site) → Add Automated Task, with the client's script and a daily schedule. Re-runs are safe.

Confirming the client's devices before the task is added

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. Save it over the client's .ps1, re-upload it, and run the task now. See Rotate a client's deployment key.

To remove the extension: Delete the client's automated task. Upload the removal script and run it as a one-off task on the client. See Remove the extension from a client's computers.

Related

Was this helpful?

Still need help? Ask the team