> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/connector-for-omnissa-horizon.md).

# Omnissa Horizon connector

{% hint style="warning" %}
This documentation references external sources. Nexthink does not have control over the accuracy of third-party documentation, nor any external updates or changes that might create inconsistencies with the information presented on this page. Please report any errors or inconsistencies to [Nexthink Support](https://support.nexthink.com/).
{% endhint %}

The Nexthink Connector for Omnissa Horizon retrieves the desktop pool of each Horizon virtual machine and Remote Desktop Services (RDS) server, with its pool type, virtualization host name and disk image, and adds them to the matching devices in Nexthink.

This installation guide helps you install the connector securely. Your security team should review the installation steps described in this document and adjust them to meet your organization’s security policy.

## Data imported into Nexthink

The connector populates the following fields of the `virtualization` grouping in the [`devices`](https://docs.nexthink.com/understanding-key-data-platform-concepts/nql-data-model.md#device_device) table.

| Nexthink field                    | Type        | Description                                                                                                                                                                                                                                                                                                                                                                                      |
| --------------------------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `virtualization.desktop_pool`     | string      | The name of the Horizon desktop pool the virtual machine belongs to.                                                                                                                                                                                                                                                                                                                             |
| `virtualization.type`             | enumeration | <p>The type of the desktop pool. Possible values are:</p><ul><li>shared: several users work on the same virtual machine at the same time</li><li>personal: the virtual machine is used by one user at a time and all changes to the system persist</li><li>pooled: the device is used by one user at a time and during the logoff all changes including documents and data are erased.</li></ul> |
| `virtualization.hostname`         | string      | The name of the virtualization host where the virtual machine was last observed running.                                                                                                                                                                                                                                                                                                         |
| `virtualization.environment_name` | string      | The name of the connector used to retrieve the virtualization details: the `Name` of the Horizon environment in the configuration file.                                                                                                                                                                                                                                                          |
| `virtualization.desktop_broker`   | enumeration | The VDI broker platform of the virtual machine, `horizon_on_prem` for this connector.                                                                                                                                                                                                                                                                                                            |
| `virtualization.disk_image`       | string      | The disk image last observed in use by the virtual machine.                                                                                                                                                                                                                                                                                                                                      |

## Nexthink connector server <a href="#connectorforcitrixvirtualappsanddesktops-nexthinkconnectorserver" id="connectorforcitrixvirtualappsanddesktops-nexthinkconnectorserver"></a>

Nexthink recommends installing the Nexthink Connector for Omnissa Horizon on a separate Windows server, not on a Horizon Connection Server, so that it never disrupts the Horizon infrastructure it reads from.

### Prerequisites <a href="#connectorforcitrixvirtualappsanddesktops-prerequisites" id="connectorforcitrixvirtualappsanddesktops-prerequisites"></a>

* Nexthink Collector installed on the virtual machines of every Omnissa Horizon environment, as described in [Configuring and deploying Collector for VMs](https://docs.nexthink.com/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows/configuring-and-deploying-collector-for-vms.md).
* Installed Windows PowerShell 5.1.
* Execution policy set to **Bypass**.
* The following PowerShell modules, installed for the local user account that runs the connector:
  * [Logging 4.8.5](https://www.powershellgallery.com/packages/Logging/4.8.5)
  * [CredentialManager 2.0](https://www.powershellgallery.com/packages/CredentialManager/2.0)
* The lowest compatible version of Omnissa Horizon is 8 2309.
* [Downloaded the Nexthink Connector for Omnissa Horizon](https://download.nexthink.com/integrations/Omnissa+onPrem+Connector/0.2.16/OmnissaConnector-0.2.16.zip).

### Hardware requirements

| Component        | Minimum                  | Recommended              |
| ---------------- | ------------------------ | ------------------------ |
| CPU              | 2-core x64               | 4-core x64               |
| RAM              | 2 GB                     | 4—8 GB                   |
| Free disk space  | 2 GB                     | 5 GB                     |
| Operating system | Windows 10 / Server 2016 | Windows 11 / Server 2022 |

### Networking <a href="#connectorforcitrixvirtualappsanddesktops-networking" id="connectorforcitrixvirtualappsanddesktops-networking"></a>

The Nexthink Connector for Omnissa Horizon connects to the Omnissa Horizon Connection Server and to your Nexthink instance.

* The connector communicates with your Nexthink instance over TCP port 443.
* The connector connects to the Horizon Connection Server REST API at the `Host` address of each environment in `config.json`, over HTTPS on TCP port 443 unless the address names another port.

#### URLs to allow through the firewall or proxy for PowerShell `Install-Module`

| Purpose                                                         | URL                                         |
| --------------------------------------------------------------- | ------------------------------------------- |
| PowerShell Gallery                                              | `https://www.powershellgallery.com`         |
| CDN for packages                                                | `https://www.powershellgallery.com/api/v2/` |
| NuGet provider                                                  | `https://www.nuget.org`                     |
| NuGet API                                                       | `https://api.nuget.org`                     |
| Alternate NuGet V2 API                                          | `https://www.nuget.org/api/v2/`             |
| Certificate revocation (normally optional; sometimes necessary) | `http://crl.microsoft.com`                  |

#### Additional considerations

* If SSL inspection is enabled on your proxy, ensure it does not break the TLS handshake.
* If you're behind a proxy, ensure `PowerShell` is configured to use it by running the following command:

{% code overflow="wrap" %}

```powershell
[System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials
```

{% endcode %}

#### Test connectivity

You can test access using a PowerShell terminal by running the following command:

```powershell
Invoke-WebRequest https://www.powershellgallery.com
```

### Local user account for scheduled tasks

The Nexthink Connector for Omnissa Horizon runs as scheduled tasks, one Runner task per Omnissa Horizon environment and one Auto-Updater task, and needs to access the Omnissa Horizon APIs. To limit security concerns, Nexthink recommends using a local user account on the server where you install the connector or a regular domain user account without any special privileges at the domain level.

The following guide uses a local account on the Nexthink connector server.

{% stepper %}
{% step %}
Log on as an administrator to the server that will run the Nexthink Connector for Omnissa Horizon.
{% endstep %}

{% step %}
Launch the local users and groups console by running the following command from the Start Menu:

```powershell
lusrmgr.msc
```

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-e33a79105f0d5b3d5de897a63c6ac9bb729684d0%2Fcitr-1678980898.png?alt=media" alt="Run the lusrmgr.msc command"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Right-click on the **Users** folder in the **Local Users and Groups (Local)** directory and select **New user…**
{% endstep %}

{% step %}
Create a user account according to your organization's naming conventions, for example `nxt-omnissa`. This guide uses `nxt-omnissa` in later commands. Replace it with your account name. Make a note of the **User name** and **Password**: you need them to store credentials, to test the connector and to create the scheduled tasks.

To keep the connector running, select the following options:

* **User cannot change password**
* **Password never expires**

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-389a86ffc7c8222b5a76c8796bc8df8459068325%2F01.png?alt=media" alt="New user options" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Select **Create**.
{% endstep %}

{% step %}
Open the local group policy editor by running the following command from the Start Menu:

```powershell
gpedit.msc
```

{% endstep %}

{% step %}
Navigate to *Computer Configuration > Windows Settings > Security Settings > Local Policies > User Rights Assignment* and open the **Log on as a batch job** policy.
{% endstep %}

{% step %}
Open the policy and select **Add User or Group** to add the previously created user to the list.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-29fb7db66b46706dd153e3c7233b32f901c389df%2F04.png?alt=media" alt="Add user or group"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### Installing the connector <a href="#connectorforcitrixvirtualappsanddesktops-installingtheconnector" id="connectorforcitrixvirtualappsanddesktops-installingtheconnector"></a>

{% stepper %}
{% step %}
Download the [Nexthink Connector for Omnissa Horizon](https://download.nexthink.com/integrations/Omnissa+onPrem+Connector/0.2.16/OmnissaConnector-0.2.16.zip).
{% endstep %}

{% step %}
Extract the zip file and copy the contents of its `OmnissaConnector-<version>` folder to a folder on your system. Nexthink recommends the following folder:

`C:\Program Files\Nexthink\Connectors\Omnissa`
{% endstep %}

{% step %}
Apply **Modify** permissions on the connector folder, for example `C:\Program Files\Nexthink\Connectors\Omnissa`, for the local user account you created earlier, applied to **This folder, subfolders and files**. The connector can then create and write its `Logs` and `Storage` folders inside it.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-de3396966bd944f265cee6995b687c66bcafedee%2F02.png?alt=media" alt="Folder properties, Security tab, with Modify permission granted to the local user account" width="365"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### Nexthink API credentials

The Nexthink Connector for Omnissa Horizon needs appropriate credentials to connect to the Nexthink Enrichment API. Nexthink stores the credentials safely in the credential store of the local user account you created earlier.

{% stepper %}
{% step %}
Create API credentials with the **Enrichment API** permission. Refer to the [API credentials](https://developer.nexthink.com/docs/api/api-credentials) documentation for step-by-step guidance.

When you save the API credentials, a new window containing the Client ID and the Secret key appears. Make a note of both: they are not shown again once you close the window.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-25527dad3aca35423e85a92c8f2bcd90999443c5%2Fcitr-1679044299.png?alt=media" alt="OAuth client credentials"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
On the server that will be running the Nexthink Connector for Omnissa Horizon, open PowerShell under the credentials of the local user you created earlier by running `runas` in the command line:

```powershell
runas /user:nxt-omnissa powershell.exe
```

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-49ee15c0d61b4d6cdbca2fb785de4c23cb0c3a23%2F05.png?alt=media" alt="runas CLI"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In the new PowerShell window, store the API credentials by running the following command:

{% code overflow="wrap" %}

```powershell
New-StoredCredential -Target "nxt-omnissa-credentials" -UserName "<Client ID>" -Password "<Secret key>" -Persist LocalMachine
```

{% endcode %}

Replace `<Client ID>` and `<Secret key>` with the values you noted down. Make a note of the `TargetName` you used with `-Target`: you need it for the configuration file.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-1c9ca32d90fec7234a30577ee03419c9c7bf4301%2F06.png?alt=media" alt="PowerShell window"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
In the `config.json` [configuration file](#connectorforcitrixvirtualappsanddesktops-updatingtheconfigurationfile), these credentials are stored in `"NexthinkAPI"`.

The `TargetName` used with `-Target` is stored in `"WindowsCredentialEntry"`.
{% endhint %}

### Updating the configuration file <a href="#connectorforcitrixvirtualappsanddesktops-updatingtheconfigurationfile" id="connectorforcitrixvirtualappsanddesktops-updatingtheconfigurationfile"></a>

For the configuration file update, you need the API address of your Nexthink instance, `<instance>.api.<region>.nexthink.cloud`.

{% hint style="info" %}
If you do not know your region, reach out to your Nexthink representative to obtain this information.
{% endhint %}

{% stepper %}
{% step %}
Locate the folder where you unzipped the Nexthink Connector for Omnissa Horizon.
{% endstep %}

{% step %}
Navigate to the `Config` folder and open the `config.json` file using a text editor.
{% endstep %}

{% step %}
The file has the following structure. In this procedure, you edit the `"NexthinkAPI"` section. You edit the `"OmnissaEnvironments"` section later, in [Setting up a connection to an Omnissa Horizon environment](#setting-up-a-connection-to-an-omnissa-horizon-environment), after you store the Omnissa Horizon credentials.

```json
{
    "_Info": "This is the JSON based configuration for Omnissa connector",
    "Info": {
        "Project": "connector-omnissa-horizon-server",
        "ConfigVersion": "0.1.0"
    },
    "Logging": {
        "LogRetentionDays": 7,
        "LogLevel": "INFO"
    },
    "OmnissaEnvironments": [
        {
            "Name": "<environment-name-1>",
            "Host": "<host>",
            "WindowsCredentialEntry": "<omnissa-user-credentials-1>"
        },
        {
            "Name": "<environment-name-2>",
            "Host": "<host>",
            "WindowsCredentialEntry": "<omnissa-user-credentials-2>"
        }
    ],
    "NexthinkAPI": {
        "HostFQDN": "<nexthink_api_host>",
        "WindowsCredentialEntry": "<nxt-omnissa-credentials>",
        "RequestBatchSize": 1000
    }
}
```

{% endstep %}

{% step %}
Change the following values under the `"NexthinkAPI"` section:

* Replace the `"HostFQDN"` value with the URL of your Nexthink cloud API instance using the format `<instance>.api.<region>.nexthink.cloud` where `<instance>` and `<region>` are placeholders.
  * Replace `<instance>` with the name of the instance
  * Replace `<region>` with the name of one of the following regions:
    * `us` for the United States
    * `eu` for the European Union
    * `pac` for Asia-Pacific
    * `meta` for the Middle East, Turkey, and Africa
  * If needed, refer to the following URL example:\
    `gwy-eu-west-3-fuji-rest.api.eu.nexthink.cloud`
* Replace the placeholder in `"WindowsCredentialEntry"` with the `TargetName` of the API credentials you stored earlier, for example:\
  `"WindowsCredentialEntry": "nxt-omnissa-credentials",`
  {% endstep %}
  {% endstepper %}

## Setting up a connection to an Omnissa Horizon environment

The previous section described the basic configuration of the Nexthink Connector for Omnissa Horizon. This section helps you set up a connection to an Omnissa Horizon environment. Repeat the procedures in this section for every Omnissa Horizon environment you connect to.

The connector reads the desktop pools, machines, RDS servers and farms from the REST API of the Horizon Connection Server. It also reads the base VMs, snapshots and VM templates that Horizon reads from vCenter Server. It signs in with a domain user account.

### Creating an administrator account <a href="#connectorforcitrixvirtualappsanddesktops-creatingaread-onlycitrixadministrator" id="connectorforcitrixvirtualappsanddesktops-creatingaread-onlycitrixadministrator"></a>

The Nexthink Connector for Omnissa Horizon needs read-only access to the Horizon REST API. Create a domain user account without any special privileges and make a note of the username and password: you need them to store the Horizon credentials.

{% stepper %}
{% step %}
Log in to the **Horizon Console**.
{% endstep %}

{% step %}
Go to *Settings > Administrators* and select **Add**.
{% endstep %}

{% step %}
Search for the domain user account you created and select it.
{% endstep %}

{% step %}
Assign the user a read-only role on the root access group. The connector only signs in and reads desktop pools, machines, RDS servers and farms, and the base VMs, snapshots and VM templates from vCenter Server. If no predefined role grants this read access, create a custom role with these read privileges.
{% endstep %}
{% endstepper %}

### Setting up stored credentials <a href="#connectorforcitrixvirtualappsanddesktops-settingupstoredcredentials" id="connectorforcitrixvirtualappsanddesktops-settingupstoredcredentials"></a>

{% stepper %}
{% step %}
On the server that will be running the Nexthink Connector for Omnissa Horizon, open PowerShell under the credentials of the local user you created earlier by running `runas` in the command line:

```powershell
runas /user:nxt-omnissa powershell.exe
```

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-49ee15c0d61b4d6cdbca2fb785de4c23cb0c3a23%2F05.png?alt=media" alt="runas CLI"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In the new PowerShell window, store the credentials of the domain user account with the read-only Omnissa Horizon administrator role by running the following command:

{% code overflow="wrap" %}

```powershell
New-StoredCredential -Target "nxt-omnissa-prod" -UserName "<domain\username>" -Password "<password>" -Persist LocalMachine
```

{% endcode %}

Replace `<domain\username>` with the domain and user name of the domain user account, in the `DOMAIN\username` form, for example `DOMAIN\svc_horizon_api`. Replace `<password>` with its password.

Make a note of the `TargetName` you used: you need it for the configuration file.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-f735fbdaf4bcdbb3f889fe2ed4948ec748dd2dd5%2F07.png?alt=media" alt="PowerShell window"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

### Updating the configuration file <a href="#connectorforcitrixvirtualappsanddesktops-updatingtheconfigurationfile.1" id="connectorforcitrixvirtualappsanddesktops-updatingtheconfigurationfile.1"></a>

Each Omnissa Horizon environment has its own section in the configuration file. The configuration file that comes with the connector contains an example of how to configure multiple environments. If needed, create a copy of the original `config.json` file for future reference.

{% stepper %}
{% step %}
Locate the folder where you unzipped the connector.
{% endstep %}

{% step %}
Navigate to the **`Config`** folder and open the `config.json` file using a text editor.
{% endstep %}

{% step %}
Scroll to the `"OmnissaEnvironments"` section. Keep one entry for each Omnissa Horizon environment you connect to. If you connect to a single environment, remove the second entry. Each entry looks similar to the following:

```json
{
    "Name": "<environment-name-1>",
    "Host": "<host>",
    "WindowsCredentialEntry": "<omnissa-user-credentials-1>"
}
```

{% endstep %}

{% step %}
Change the following values in the entry:

* Replace `<environment-name-1>` with a name for this Omnissa Horizon environment, for example `Horizon Prod`. You pass this name, in quotes, to the connector with `-OmnissaEnvironment`. Nexthink shows it in the `virtualization.environment_name` field.
* Replace `<host>` with the address of the Horizon Connection Server, including `https://`, for example `https://horizon.example.com`.
* Replace `<omnissa-user-credentials-1>` with the `TargetName` of the stored credentials you created earlier in PowerShell, for example `nxt-omnissa-prod`.
  {% endstep %}
  {% endstepper %}

### Testing the connector <a href="#connectorforcitrixvirtualappsanddesktops-testingtheconnector" id="connectorforcitrixvirtualappsanddesktops-testingtheconnector"></a>

The test is a real run: it reads the Omnissa Horizon environment and sends its data to Nexthink.

{% stepper %}
{% step %}
On the server that will be running the Nexthink Connector for Omnissa Horizon, open PowerShell under the credentials of the local user you created earlier using the `runas` command on the command line:

```powershell
runas /user:nxt-omnissa powershell.exe
```

{% endstep %}

{% step %}
Change to the directory where you installed the connector, for example:

```powershell
cd 'C:\Program Files\Nexthink\Connectors\Omnissa\'
```

{% endstep %}

{% step %}
Run the Auto-Updater, which installs the connector module for the local user account:

```powershell
.\Omnissa-Connector-Auto-Updater.ps1
```

{% endstep %}

{% step %}
Run the Runner for the environment:

```powershell
.\Omnissa-Connector-Runner.ps1 -OmnissaEnvironment "<environment name>"
```

Replace `<environment name>` with the `Name` of the environment in `config.json`, for example `Horizon Prod`.
{% endstep %}

{% step %}
Open the log file of the run, `Logs\<environment name>\OmnissaConnector-<yyyyMMdd>.log` in the connector folder, and review it for errors. A successful run ends with `Stopping Omnissa connector <version> with exit code 0`.
{% endstep %}
{% endstepper %}

### Setting up the scheduled tasks

Create one scheduled task for the Runner of each Omnissa Horizon environment, and one for the Auto-Updater.

{% stepper %}
{% step %}
Open the task scheduler and select **Create task…**

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-e4cdd40df98d68e566780ee02b2ecd8127017101%2Fcitr-1669383499.png?alt=media" alt="Create a task"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In the **General** tab, name the task, for example `Nexthink Horizon connector - Horizon Prod`, and change the user to the local user account you created earlier, for example `nxt-omnissa`. Select **Run whether user is logged on or not**.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-781c005287fa11ef72510be74aad6c9c76b376c4%2Fcitr-1679385360.png?alt=media" alt="Task properties, General tab" width="315"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In the **Triggers** tab, click **New…**. Under *Advanced settings > Repeat task every*, select **15 minutes** and set **for a duration of** to **Indefinitely**. Click **OK**. Each run sends only the devices that changed since the previous run, so a short interval costs little.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-cea2410aa896e66d8e251dca7b92d894c00f3086%2F03.png?alt=media" alt="New trigger, repeating the task every 15 minutes" width="375"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
In the **Actions** tab, click **New…** and enter the following values. Click **OK**.

* **Program/script**: `powershell.exe`
* **Add arguments (optional)**: `-ExecutionPolicy Bypass -File "C:\Program Files\Nexthink\Connectors\Omnissa\Omnissa-Connector-Runner.ps1" -OmnissaEnvironment "Horizon Prod"`, with the environment name from `config.json`
* **Start in (optional)**: the connector folder, for example `C:\Program Files\Nexthink\Connectors\Omnissa`

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-b39ad1dcc25eb3e105661c61b283fe920d140462%2Fcitr-1670319737.png?alt=media" alt="Edit action" width="227"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Click **OK** to save the task. When prompted, enter the password of the local user account and click **OK**.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-b34805f1e6808fd75ff8560bfcb6f7f97958b03b%2Fcitr-1679387044.png?alt=media" alt="Confirm credentials"><figcaption></figcaption></figure>
{% endstep %}

{% step %}
Repeat these steps for each other Omnissa Horizon environment, changing only the task name and the `-OmnissaEnvironment` value.
{% endstep %}

{% step %}
Repeat these steps once for the Auto-Updater, which installs the connector module for the local user account, with these differences:

* Task name: for example `Nexthink Horizon connector - Auto-Updater`
* Trigger: the same as the Runner, repeated every 15 minutes, so a new connector version is in use within 15 minutes.
* **Add arguments (optional)**: `-ExecutionPolicy Bypass -File "C:\Program Files\Nexthink\Connectors\Omnissa\Omnissa-Connector-Auto-Updater.ps1"`
  {% endstep %}
  {% endstepper %}

## Verifying the data in Nexthink

After the first run of the Runner scheduled task, open **Investigations** in Nexthink and run the following query:

```
devices
| where device.virtualization.desktop_broker == horizon_on_prem
| list device.name, device.virtualization.environment_name, device.virtualization.desktop_pool, device.virtualization.type, device.virtualization.hostname, device.virtualization.desktop_broker, device.virtualization.disk_image
```

Each row is a virtual machine the connector enriched, and the environment name shows which connection delivered it.

## Where to go next

* [VDI Experience](https://docs.nexthink.com/user-guide/vdi-experience.md): the module Nexthink monitors virtual desktops with. The library pack below requires it.
* [Omnissa Horizon on-premises essentials](https://docs.nexthink.com/library-packs/vdi/omnissa/omnissa-horizon-on-premises-essentials.md): a library pack to install from the Nexthink Library. Its dashboards show the online and offline distribution of the virtual machines, their reboot health and registration, and their CPU, GPU, memory, storage and network load.

***

RELATED TOPIC

* [API Credentials](https://developer.nexthink.com/docs/api/api-credentials)
* [Configuring and deploying Collector for VMs](https://docs.nexthink.com/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/installing-collector-on-windows/configuring-and-deploying-collector-for-vms.md)
* [VDI Experience](https://docs.nexthink.com/user-guide/vdi-experience.md)
* [Omnissa Horizon on-premises essentials](https://docs.nexthink.com/library-packs/vdi/omnissa/omnissa-horizon-on-premises-essentials.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nexthink.com/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/connector-for-omnissa-horizon.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
