> 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/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/viewing-user-interactions-in-virtualized-and-embedded-environments.md).

# Viewing user interactions in virtualized and embedded environments

## Overview <a href="#viewinguserinteractionsinvirtualizedandembeddedenvironments-overview" id="viewinguserinteractionsinvirtualizedandembeddedenvironments-overview"></a>

Because of the non-standard user logon process in Citrix XenApp and embedded (kiosk mode) Windows, the Collector is neither able to report user logons nor user interactions by using its default detection mechanism when running on these systems.

When installing the Collector in Citrix XenApp or in a Windows device running on kiosk mode, make sure that you set the *custom shells* option. This option tells the Collector to detect user logon events and interactions by means of an alternative mechanism.

To enable this special mode in the Collector, use either the **CUSTOM\_SHELLS** [MSI parameter](/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/collector-msi-parameters-reference-table.md) during the installation of the Collector or the **custom\_shells** option of the [Collector configuration tool for Windows](/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/collector-configuration-tool-for-windows.md) after it has been installed.

If you happen to install the Collector in a Citrix XenApp server, carefully read the following section.

## Session termination in Citrix XenApp <a href="#viewinguserinteractionsinvirtualizedandembeddedenvironments-sessionterminationincitrixxenapp" id="viewinguserinteractionsinvirtualizedandembeddedenvironments-sessionterminationincitrixxenapp"></a>

Because of a [known limitation of Citrix XenApp](https://support.citrix.com/article/CTX891671), in some cases a session may fail to close even after the user has gracefully logged off.

When a user logs in, the Collector spawns the *rundll32.exe* process. To avoid leaving sessions active and wasting resources, ensure that Citrix is able to close this process when the user logs off and terminates the session:

1. Log in to the Citrix XenApp server as administrator.
2. Locate the following key in the registry editor:`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI`
3. Add the **rundll32.exe** process to the list of processes in the key value **LogoffCheckSysModules**:

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-42519161ef5689370d2faf351e64520514c3afa9%2F580px-citrix_regkey.png?alt=media" alt=""><figcaption></figcaption></figure>

***

RELATED TASKS

* [Collector MSI parameters reference table](/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/collector-msi-parameters-reference-table.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/deploying-nexthink-in-non-vdi-environment/installing-collector/windows-collector-references/viewing-user-interactions-in-virtualized-and-embedded-environments.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.