May 28, 2016

Administrators and help-desk personnel can monitor XenApp and XenDesktop Sites with Director, where administrators can access the Configuration Logging database, or by using the Site’s Monitor Service’s API using the OData protocol.

Administrators can monitor:

  • Session usage
  • Logon performance
  • Connection and machine failure
  • Load evaluation
  • Historical trends
  • Infrastructure
  • User sessions
  • Machines


Director is a real-time web tool that allows administrators to monitor, troubleshoot, and perform support tasks for end users.

Director can access:

  • Real-time data from the Broker Agent using a unified console integrated with EdgeSight features, Performance Manager, and Network Inspector.
    • EdgeSight features include performance management for health and capacity assurance, and historical trending and network analysis, powered by NetScaler HDX Insight, to identify bottlenecks due to the network in your XenApp or XenDesktop environment.
  • Historical data stored in the Monitor database to access the Configuration Logging database.
  • ICA data from the NetScaler Gateway using HDX Insight.
    • Gain visibility into end-user experience for virtual applications, desktops, and users for XenApp or XenDesktop.
    • Correlate network data with application data and real-time metrics for effective troubleshooting.
    • Integrate with XenDesktop 7 Director monitoring tool.
  • Personal vDisk Data that allows for runtime monitoring showing base allocation and gives help-desk IT the ability to reset the Personal vDisk (to be used only as a last resort).
    • The command line tool CtxPvdDiag.exe is used to gather the user log information into one file for troubleshooting.

Director uses a troubleshooting dashboard that provides real-time health monitoring of the XenApp or XenDesktop site. This feature allows administrators to see failures in real time, providing a better idea of what the end user is experiencing.

Session Recording

Session Recording allows you to record the on-screen activity of any user’s session, over any type of connection, from any server running XenApp subject to corporate policy and regulatory compliance. Session Recording records, catalogs, and archives sessions for retrieval and playback.

Session Recording uses flexible policies to trigger recordings of application sessions automatically. This enables IT to monitor and examine user activity of applications — such as financial operations and healthcare patient information systems — supporting internal controls for regulatory compliance and security monitoring. Similarly, Session Recording also aids in technical support by speeding problem identification and time-to-resolution.

Configuration Logging

Configuration Logging is a feature that allows administrators to keep track of administrative changes to a XenApp or XenDesktop Site. Configuration Logging can help administrators diagnose and troubleshoot problems after configuration changes are made, assist change management and track configurations, and report administration activity.

Configuration Logging can be viewed in Director with the Trend View interface to provide notifications of configuration changes to administrators who do not have access to XenDesktop Citrix Studio.

Trends View gives historical data of configuration changes over a period of time so administrators can assess what changes were made to the Sites, when they were made, and who made them to find the cause of an issue. This view breaks down configuration information in three categories.

  • Connection Failures
  • Failed Desktop Machines
  • Failed Server Machines


Administrators can use the Site’s Monitor Service’s API to search historical data using the OData protocol. This allows IT to analyze historical trends for planning purposes, to perform detailed troubleshooting of connection and machine failures, and extract information for feeding into other tools and processes.

The Monitor Service schema provides the following types of data:

  • Data relating to connection failures
  • Machines in a failure state
  • Session usage
  • Logon duration
  • Load balancing data