Skip to main content

Before you start

  • You need Nerdio Manager for MSP and an MSP-level administrator in it. Nerdio Manager for Enterprise is a different product, which this integration does not connect.
  • Neo reaches Nerdio Manager over the internet at the address you sign in at, such as https://nmm-app-abc123.azurewebsites.net or your own domain. If you limit who can reach the app, allow Neo’s addresses.

1. Turn on the REST API in Nerdio Manager

1

Open the REST API settings

In Nerdio Manager, at the MSP level, open Settings > Integrations. In the REST API area, select Disabled to start turning it on.
2

Create the API app and grant consent

Select Run to create the API application, then Grant, and in the Azure portal select Grant admin consent. Back in Nerdio Manager, select the refresh icon to check the permissions.
3

Generate the secret

Select Generate. Copy the Tenant ID, Client ID, Scope and the client secret. The secret is shown once.

2. Add the credentials in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations → Nerdio Manager, under Servers & Virtualization.
2

Save the values

Enter the address you sign in to Nerdio Manager at, and the Tenant ID, Client ID, Scope and Client Secret from step 1, then click Save settings. Neo gets a token and reads your accounts before saving, so a wrong value is rejected straight away.
After the save, Neo matches your Nerdio accounts to your PSA companies. Check them on the Organization Mapping tab: an agent working a ticket acts only in the account its company maps to.
When the client secret expires, Neo loses access until you generate a new one in Nerdio Manager and save it here.
Neo logs off a user’s stuck session with an Azure runbook scripted action, which you add once:
  1. In Nerdio Manager, at the MSP level, open Scripted Actions > Azure runbooks and select Add scripted action.
  2. Name it Neo - Log off an AVD user session, paste the script below, and save it.
  3. The script needs the Az.DesktopVirtualization module in Nerdio’s scripted actions automation account, as Nerdio’s own AVD runbooks do. It acts only in the subscription Nerdio Manager runs the account’s scripted actions in ($AzureSubscriptionID), and Neo runs it only for a host pool that Nerdio Manager lists under that client’s account.
Without it, Neo asks a technician to approve a restart of the session host, which signs out every user on it, or gives the technician the steps to log the user off in Nerdio Manager.

4. Turn Nerdio Manager on per agent

Open the agent, go to the Integrations section, and configure the Nerdio Manager block. Agents can do only what Nerdio Manager’s REST API app may do.

Pick an access profile

Read Only

Read sessions, hosts, host pools and every other area. Nothing is changed, and device passwords stay off.

Helpdesk

Starting a host and running a scripted action wait on a technician. Everything else is read only, and device passwords stay off.

IT Admin

Starting hosts, scripted actions, host pools and images change without approval. Accounts, backup, networks and variables, and billing wait on a technician.

Full Automation

Every change runs without approval, except the changes that always ask a technician.

Or set each area by hand

Each area can be Disabled, Read Only or Read/Write, and has its own technician approval setting.

Changes that always ask a technician

These wait on a technician under every profile, whatever the area’s own approval setting:
  • Linking a new client tenant to Nerdio Manager, which gives it admin rights in that tenant, and granting a Nerdio role.
  • Restarting or stopping a session host, which signs out every user on it.
  • Deleting a host pool, which deletes its session hosts.
  • Turning a resource’s backup off, unlinking a recovery vault, and deleting a backup policy.
  • Creating, changing or deleting a secure variable.
  • Replacing an app’s assignments.
  • Any change that sends a password, a secret, a token or a storage key, or hands a scripted action a secure variable.

Troubleshooting