- What's new
- System requirements
- Technical overview
Install and configure
Prepare to install
- Microsoft Azure Resource Manager virtualization environments
- Microsoft System Center Virtual Machine Manager virtualization environments
- XenServer virtualization environments
- Microsoft System Center Configuration Manager environments
- VMware virtualization environments
- Nutanix virtualization environments
- Microsoft Azure virtualization environments
- Install core components
- Install VDAs
- Install using the command line
- Install VDAs using scripts
- Create a Site
- Create machine catalogs
- Manage machine catalogs
- Create Delivery Groups
- Manage Delivery Groups
- Create Application Groups
- Manage Application Groups
- Remote PC Access
- XenApp Secure Browser
- Publish content
- Server VDI
- Personal vDisk
- Remove components
- Prepare to install
- Upgrade and migrate
- Security considerations and best practices
- Integrate XenApp and XenDesktop with NetScaler Gateway
- Delegated Administration
- Smart cards
- Transport Layer Security (TLS)
- Federated Authentication Service
- General content redirection
- Work with policies
- Policy templates
- Create policies
- Compare, prioritize, model, and troubleshoot policies
- Default policy settings
Policy settings reference
- ICA policy settings
- Load management policy settings
- Profile management policy settings
- Receiver policy settings
- Virtual Delivery Agent policy settings
- Virtual IP policy settings
- Configure COM Port and LPT Port Redirection settings using the registry
- Connector for Configuration Manager 2012 policy settings
- Advanced configuration
- Monitor deployments
- Alerts and notifications
- Delegated Administration and Director
- Secure Director deployment
- Configure permissions for VDAs earlier than XenDesktop 7
- Configure network analysis
- Troubleshoot user issues
- Troubleshoot applications
- Troubleshoot machines
- Feature compatibility matrix
- Data granularity and retention
- Configure PIV smart card authentication
- Application probing
- SDKs and APIs
Application probing automates the process of checking the health of XenApp and XenDesktop applications that are published in a Site. The results of application probing are available in Director.
Ensure the following prerequisites:
- Delivery Controller runs version 7.18 or later.
- Endpoint machines running probe agents are Windows machines with Windows Receiver version 4.8 or later.
- Director supports the default form based authentication.
- StoreFront has HTTP Basic authentication enabled.
User accounts/permissions required to run Application Probing:
- A unique StoreFront user to probe on each endpoint machine. The StoreFront user need not be an administrator; the probes can run in a non-admin context.
- User accounts with Windows administrator permissions to install and configure the Citrix Probe Agent on the endpoint machines
- A full administrator user account or a custom role with the following permissions. Reusing existing user accounts for application probing might log off the users’ active sessions.
- Delivery Group permissions:
- Director permissions:
- Create\Edit\Remove Alert Email Server Configuration - if the email server is not already configured
- Create\Edit\Remove Probe Configurations
- View Configurations page
- View Trends page
- Delivery Group permissions:
You can schedule your application probes to run during off-peak hours across multiple geographies. The comprehensive probe results can help to troubleshoot issues related to the applications, hosting machine or connection before the users experience them.
Step 1: Install and configure the Citrix Probe Agent
The Citrix Probe Agent is a Windows executable that simulates the actual application launch by the user through StoreFront. It tests application launches as configured in Director and reports back the results to Director.
Identify endpoint machines from where you want to run application probing.
Users with administrative privileges can install and configure the Citrix Probe Agent on the endpoint machine. Download the Citrix Probe Agent executable available at https://www.citrix.com/downloads/xenapp-and-xendesktop/components/app-probe-agent.html
Start the agent and configure your StoreFront and Director credentials. Configure unique StoreFront users on each endpoint machine. The credentials are encrypted and stored securely.
Step 2: Configure Application Probing in Director
Go to Configuration > Application Probe Configuration.
Create a probe and choose:
- the applications to be probed,
- the endpoint machines on which the probe must run,
- the email addresses to which the failure probe results are sent (configure your email server in Alerts -> Email Server Configuration), and
- the time of the day at which the probe must run (as per the local time zone of the endpoint machine).
After configuration in Director, the agent takes 10 minutes before it is ready to start probing. Then, it runs configured probes starting the next hour.
Step 3: Probe execution
The agent executes application probing as per the probe configuration it fetches from Director periodically. It launches selected applications serially using StoreFront. The agent reports the results back to Director via the Monitor database. Failures are reported in five specific stages:
- StoreFront Reachability - configured StoreFront URL is not reachable.
- StoreFront Authentication - configured StoreFront credentials are invalid.
- StoreFront Enumeration - StoreFront Enumerate applications list does not contain the application to be probed.
- ICA download - the ICA file is not available.
- Application launch – the application cannot be launched.
Step 4: View probe results
You can view the latest probe results in the Applications page.
To troubleshoot further, click the probe result link to see more details on the Trends > Application Probe Results page.
The consolidated probe results data is available for the last 24 hours or last 7 days time periods on this page. You can see the stage in which the probe failed. You can filter the table for a specific application, probe failure stage, or endpoint machine.