Citrix Virtual Apps and Desktops

Known Issues and Limitations

May 10, 2026

Contributed by:

Only One Log Server Is Supported Per Environment

The current architecture supports only a single AOT Log Server per environment, and both Web Studio and Director/Monitor are designed to work with only one Log Server configuration. All components must point to this same Log Server; configuring or distributing workloads across multiple Log Servers is not supported today. This single Log Server can handle up to 128,000 active component connections and process up to 10,000 log events per second, which is sufficient for most deployments. Since these limits are based on connection capacity and log-throughput, not on the number of components, even very large environments can operate with one Log Server as long as they remain within throughput thresholds.
However, customers with extremely high log volumes during peak activity may reach ingestion or indexing limits due to the absence of horizontal scaling. Support for multiple Log Servers and broader scaling options will be introduced in future releases as part of the evolving architecture.

Running the AOT Log Server on a Windows VM hosted on XenServer is not supported. XenServer does not support nested virtualization, which prevents Docker from running inside the guest VM. As a result, the Log Server container cannot be deployed in this configuration.
Docker Desktop on Windows requires an active user session for AOT Log Server

When the AOT Log Server is deployed on a Windows VM using Docker Desktop, the container runs within the context of the user session that started Docker Desktop. Docker Desktop is designed as a user-session-based application and does not run as a system-level service on Windows. As a result, if the user logs out, Docker Desktop stops, which causes the AOT Log Server container to stop. Because of this behaviour: The AOT Log Server stops when the user logs out as the deployment depends on a specific user session. Other administrators cannot access or manage the running containers.

Workaround: Keep the user session active or in a disconnected state (do not log out) to ensure that Docker Desktop and the AOT Log Server container continue running.

Recommendation For production deployments, use one of the following:

Deploy the AOT Log Server on a Linux VM using Docker Engine
Use the Citrix Connector Appliance (CCA)-based deployment where supported

These options allow the Log Server to run independently of user sessions and provide a more reliable, always-on deployment model.

Note:

This approach may not be reliable in environments with session timeouts or strict security policies.

This behaviour is a known limitation of Docker Desktop on Windows and is not specific to the AOT Log Server.

License Server logs appear with incorrect Host Type in Director/Monitor

When viewing AOT logs from the License Server in Director, the Host Type column may incorrectly display the value as DDC instead of License Server, even though the hostname is correct.

This issue is limited to how the Host Type is represented in Director and does not impact log collection or functionality. This issue has been resolved in the latest License Server release and is fixed starting from License Server version: 55000 or later.

Citrix Cloud Connector is required to view AOT logs in Monitor

Customers using Citrix Monitor to view AOT logs must have at least one Citrix Cloud Connector deployed in their environment. This requirement applies regardless of where the AOT Log Server is hosted, including Linux VM or Windows VM or Citrix Connector Appliance

Citrix Monitor relies on the Monitor service running on the Cloud Connector to retrieve logs from the configured Log Server and display them in the UI.

Without a Windows Cloud Connector, AOT logs cannot be fetched or displayed in Monitor.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Known Issues and Limitations

May 10, 2026

Contributed by:

May 10, 2026

Contributed by:

Known Issues and Limitations

In this article