Skip to main content
Deploy by RMM

Deploy with N-able N-central

Add the client's script to the N-central repository, run it as LocalSystem on one device, then schedule it at the customer level.

Written By The Lemhi Product Team

Last updated 10 days ago

For technicians on N-able N-central. When you're done, the client has its own script in the Script/Software Repository, running daily as a scheduled task under LocalSystem against the client's devices.

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.

  • Target computers need Windows PowerShell 5.1.

  • Repository file names can't contain spaces. lemhi-extension-<client>.ps1 is fine.

Add the script to the repository

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

  2. Open Configuration → Scheduled Tasks → Script/Software Repository → Add → Scripting.

  3. Name it Lemhi AI Usage extension - <Client> and upload the file.

Pilot on one computer

  1. Open Configuration → Scheduled Tasks → Add → Run a Script (or, from a device, Actions → Run a Script).

  2. Set Script to the repository item.

  3. Set Credentials to LocalSystem.

  4. Set Target to one device and Schedule to Now.

  5. Check the task status.

  6. Restart the browsers on that computer.

  7. 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 the same scheduled task at the client's customer level, targeting its Windows devices (a customer-level filter works well), with a daily recurrence. 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. Upload it as the new copy of the client's repository item and run the task now. See Rotate a client's deployment key.

To remove the extension: Delete the recurring task, then add the removal script to the repository and run it on the client's devices. See Remove the extension from a client's computers.

Was this helpful?

Still need help? Ask the team