Skip to main content
Omnissa Horizon (formerly VMware Horizon) runs your clients’ virtual desktops and published applications from a Connection Server. Connect your Connection Server to Neo once, at the MSP level, with its address and an Active Directory user that is a Horizon administrator for Neo.

​
What Neo can do with Horizon

Desktops and pools

Create a desktop pool, change its size or settings, add or remove machines, push a new image, turn a pool on or off, and delete machines and pools.

Power and repair

Restart, reset, shut down, rebuild or recover a stuck virtual desktop, and put machines in or out of maintenance mode.

Onboard and offboard users

Entitle a user or group to a desktop or application pool, assign a dedicated desktop, and remove both when someone leaves.

Sessions

See who is on which desktop and for how long, message users before maintenance, and log off or disconnect a stuck session.

Unused desktops

List machines with no entitled user, machines idle now, and machines nobody signed in to for a number of days, for you to review or remove.

Health and events

Read the health of Connection Servers, gateways, vCenter servers and the event database, licence use, and the events around a user’s problem.
With the access you choose, Neo can also manage farms and RDS hosts, application pools, images, gateways, Cloud Pod federation and settings. Some changes always ask a technician first, under every access profile, such as deleting a desktop pool or changing administrators: the full list. Moving a virtual machine to another host or datastore is a vCenter change: connect VMware vSphere too for that.

​
Your clients in Horizon

Horizon’s API reference (release 2606) has no client object: you keep a client’s desktops in pools or farms that you name. Neo finds a client’s desktops by those names, so each client’s pools or farms need names that point to that client alone; when no name or two clients match, Neo stops and asks a technician. There is no Organization Mapping tab for Horizon.

​
What Neo never does

  • Sign in, sign out or refresh a token for anyone: Neo signs in with its own user.
  • Fetch a Remote Assistance ticket, which would let whoever holds it control a user’s desktop.
  • Export a Connection Server certificate, which carries its private key, or download a log bundle.
Neo also removes the fields Horizon keeps credentials in (passwords, shared secrets, tokens, licence keys, private keys, and the user name and password in a URL) from every answer before an agent sees it.

​
Next steps

Connect Horizon

Make a Horizon administrator for Neo and save it in Neo with your Connection Server address.