Skip to main content
Deploy by RMM

Deploy with NinjaOne

Add the client's script to the NinjaOne Automation Library, run it as System on one device, then schedule it in the client's policy.

Written By The Lemhi Product Team

Last updated 10 days ago

For technicians on NinjaOne. When you're done, the client has its own PowerShell script in the Automation Library, running daily as System through the client's Windows policy.

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.

  • A Windows policy for this client's computers. If the client shares a policy with other clients, use a per-organization policy (or a policy override), because each client needs its own key.

NinjaOne's built-in Browser Management can force-install an extension by store id, but it can't set the extension's values, and the extension needs its key. The script does both.

Add the script

  1. Open Administration → Library → Automation → Add → New Script.

  2. Set Name to Lemhi AI Usage extension - <Client>.

  3. Set Language to PowerShell and Operating system to Windows.

  4. Set Architecture to 64-bit (or All).

  5. Paste the script you copied from Engage. Don't edit it.

An older NinjaOne script editor with the client's script pasted and PowerShell and Windows selected; the current menu path is in step 1

  1. Click Save.

Pilot on one computer

  1. Open the device, choose Run → Automation, and pick the script.

  2. Leave Run As on System. It's chosen here, at run or schedule time.

An older NinjaOne layout with Run As set to System for the script

  1. Read the result in the device's activity.

  2. Restart Chrome and Edge 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.

Schedule it on the client

In the Windows policy assigned to the client's computers, open Scheduled Automations → Add and pick the script, with Run As on System. Run it daily. Re-runs are safe and heal the policy.

An older NinjaOne scheduled task set to repeat daily; today you schedule it under Scheduled Automations in the client's policy
The client's organization picked as the target in the older scheduled task layout
The saved daily task in the older NinjaOne task list

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. Paste it over the client's library script and run it on the client's devices now. See Rotate a client's deployment key.

To remove the extension: Remove the scheduled automation, then add the removal script as a library script and run it on the client's devices. See Remove the extension from a client's computers.

Related

Was this helpful?

Still need help? Ask the team