A connector is what lets Avvi reach a client’s on-premises world: their Active Directory, their servers, and their staff’s machines. Without one, Avvi works only against Microsoft 365.

Installing one takes two things: a code generated in Avvi, and the installer run on the target machine.

The modules you choose at install time decide what that machine can be asked to do afterwards, so it is worth getting right rather than guessing.

Before you begin

Know what the machine is. A domain controller and somebody’s laptop need different modules.

Have administrator access on the target machine, because the installer runs as a service.

Decide whether you are doing one machine by hand or many through your own deployment tooling. The two paths differ from the first click.

Install it

1. Open Settings, go to Integrations, choose the Connector, then Fleet. Select Install Connector.
2. Choose Single Machine for one interactive install, or Bulk RMM Deployment to generate a key you can reuse.
3. Pick the Client Tenant.
4. Choose the modules. Workstations take the Workstation module; domain controllers take Identity and Sync.
5. Generate the code, then run the installer on the machine with that code.

The connector appears on Connector Fleet once it has enrolled, and moves to ONLINE when it first checks in.

Good to know

A single-machine code is one-time and lasts fifteen minutes. It expires on screen while you watch, and generating another is quick.

A service key for bulk deployment is durable and reusable, which is what makes it suitable for pushing out at scale and also what makes it worth guarding.

Verify it worked

Return to the fleet page and find the new row. It should reach ONLINE within a few minutes of the install finishing.

Check the Modules column shows what you chose. A missing module means reinstalling rather than editing.

If something doesn’t look right

If a control is greyed out, your account is not allowed to change it. The setting is not broken and nothing is missing from the page.

If a setting is absent rather than greyed, the feature is switched off for your whole organisation rather than for you.

If the control works and saving fails, Avvi replies “Master admin access required”. That is the same permission problem, reported when you save rather than before.

If the row stays at ENROLLED, the connector enrolled but the service is not running on that machine. Check the service before anything else.

If the code expired before you used it, generate another. Nothing is wasted by doing so.

If the installer reports that a connector is already running on that machine, stop and uninstall the existing one first rather than installing over it.

If the row never appears at all, confirm the machine can reach out to the internet and that nothing is blocking it.

To report a failure, open a support conversation from the Help drawer with the client, the machine name, and what the installer printed.

FAQ

Q: The setting is greyed out and I cannot change it.

A: Your account is not allowed to change that setting. Ask an administrator with full access to change it for you, or to add your group to the permission.

Q: Who do I ask to get access?

A: Any administrator with full access in Avvi. Tell them which setting you were trying to reach and what you needed to change.

Q: How long does the code last?

A: Fifteen minutes for a single machine. A service key for bulk deployment does not expire the same way.

Q: Can I change the modules later?

A: Reinstall with the modules you want. They are chosen at install time.

Q: How many connectors can a client have?

A: More than one, on different machines. One per machine is the rule.