> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> What the Parallels RAS integration brings to your Neo Agent setup

Parallels RAS (Remote Application Server) publishes applications and desktops from RD Session Hosts, VDI and Azure Virtual Desktop. Each of your clients runs its own RAS farm, so you connect Parallels RAS once per client, with the address of that farm's REST API and a RAS administrator made for Neo.

## What Neo can do with Parallels RAS

> **Farm health**
>
> Read the state of each site, Connection Broker, Secure Gateway, HALB and Enrollment Server, and each session host's load, sessions and agent state.

> **Licence use**
>
> Read the licence type, licensed users, users connected now, the peak, the expiry date and any licence alert.

> **Drain mode**
>
> Drain an RD Session Host, drain it until reboot, disable logons, enable logons again, or take a host out of its site and back.

> **Sessions**
>
> Find a user's session on RD Session Hosts and VDI, message the user, disconnect the session or log it off, and end a process.

> **Publishing**
>
> Publish an application or desktop, choose who sees it, disable it, or unpublish it. Under the Helpdesk profile, each of these waits on a technician.

> **Farm settings**
>
> Read and change host pools, templates, client policies, gateways and farm settings, with the access you choose.

Some changes always ask a technician first, under every access profile, such as deleting a session host or rebooting one: [the full list](https://docs.neoagent.io/integrations/parallels-ras/connecting-to-neo.md#changes-that-always-ask-a-technician).

RAS commits a settings change only when it is applied. Neo applies the farm settings after each change it makes, so the change is live when the agent reports it.

## One connection per client

A RAS farm's records name no client: the farm is the client. You connect each client's farm under that client on your **Companies** tab, and an agent working a ticket reaches only the farm of the ticket's client. A farm that serves several of your clients is connected under one of them, and every call on it reaches all of it. There is no Organization Mapping tab for Parallels RAS.

## What Neo never does

* Log on or log off for anyone: Neo signs in with its own RAS administrator.
* Export or import the whole farm configuration, or download the system report.
* Upload a private key or a PFX file with its password.
* Run the MFA connection check, which takes the RADIUS secret in its query string.

Neo also removes the fields RAS keeps credentials in (passwords, secret keys, licence keys, tenant join hashes, session tokens and private keys) from every answer before an agent sees it.

## Next steps

> **[Connect Parallels RAS](https://docs.neoagent.io/integrations/parallels-ras/connecting-to-neo.md)**
>
> Make a RAS administrator for Neo, publish the REST API, and save it in Neo under the client.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.