Computer doesn't appear on the Deployment tab

For technicians whose computer ran the deployment script but isn't listed on the client's Deployment tab in Engage. Work down the list in order and stop when the computer appears.

Checklist

1. Read the script's output in your RMM. If the run failed with clientKey is not a Lemhi deployment key, the script was edited or the key was mangled when it was pasted. Click Copy script on the client's Deployment tab again, paste it unchanged, and re-run.

2. Compare the key starts value in the output with the start of the key on the client's Deployment key card. If they differ, the key was regenerated since this script was saved. Copy the script again and replace the saved copy.

3. Check for does not match what this script wrote. It means something rewrote the policy keys while the script ran, such as Group Policy, Intune or another RMM job. Find and stop the other writer, then re-run.

4. Restart the browser on that computer. Browsers read policy when they start and on their periodic refresh, not when the registry changes. Policy present but extension not installed usually means the browser hasn't restarted since the script ran.

5. Open chrome://policy or edge://policy. The extension id is listed under ExtensionInstallForcelist with status OK. Chrome also lists clientKey, computerName and ingestBaseUrl under the extension, each with status OK. Edge does not show them on that page but still passes them to the extension, so on Edge the script's readout and the first check-in confirm them. If the run passed but chrome://policy doesn't list the id, confirm the RMM ran 64-bit PowerShell.

6. If the forcelist shows "Error" in chrome://policy, another tool wrote a malformed entry in the same list. Look at the other numbered values under ExtensionInstallForcelist. Lemhi's is only the bare id.

7. Open chrome://extensions or edge://extensions. Lemhi AI Usage extension is listed as installed by your organization.

8. If the script printed store update host NOT reachable or the extension never installs, a web filter is blocking the browser's store. Allow the store hosts below.

9. If it's installed but never checks in, or the script printed ingest NOT reachable, outbound HTTPS to Lemhi is blocked by a firewall or web filter. Allow https://ingest.lemhi.ai.

10. If the computer reports under the wrong client, it ran another client's copy of the script. Re-run the right client's script. The new key replaces the old one.

Hosts to allow through your web filter and proxy

The script runs as SYSTEM, which may use different proxy settings from your users' browsers. The deciding result is the computer appearing on the Deployment tab.

Related

• Deploy the extension with your RMM

• Check that a computer has the extension

• Rotate a client's deployment key

Still stuck? Send your Lemhi contact the client name, the computer name, and the script's output.