Citrix Probe Agent - ICA Launch failure reported in multi-domain environment
Article ID: CTX694994
Updated On:
Description
Citrix Director displays multiple Failed Probe Runs.
Probe Failure Stage:
- Application Launch
- Desktop launch
The failure is reported incorrectly. The actual session was launched without any issues.
It can be also found in Director on the list of Sessions located in Filters > Sessions.
Citrix Probe Agent log (CitrixProbeAgent.txt) located in C:\Program Files (x86)\Citrix\Citrix Probe Agent shows the failure stage:
ERROR - [Probe Type: Desktop][Launch Name: S22][Step5] Launch desktop/app failed.
Cause
This is a product limitation. Probe Agent currently does not support multi-domains.
Probe Agent calls Director API: GetProbeSession and Director sends a query to Citrix Broker Service in order to check if the session has been launched.
This can be also observed in the logs:
[Probe Type: Desktop][Launch Name: Published_Desktop_Name]Checking for sessions on Broker with machineName: DOMAIN_1\VDA1 , userName: DOMAIN_1\RESPROBE1 , siteid:guid_here, endpointName: PROBEMACHINE, launchName: PublishedDesktop
INFO - Calling Director API: GetProbeSession()The example above shows that machineName and userName variables contain the same domain: DOMAIN_1
If the VDA is in a different domain, search fails as the probe agent can only pass the user domain. Probe Agent is not aware of VDA's domain and always adds User's domain to the search query for both: machineName and userName.
Resolution
Configure Probe Agent with the User account from the domain where VDAs are located.
Issue/Introduction
This document contains information about Probe Agent behaviour in a multi-domain environment where the Probe Agent user account configured for Workspace/Storefront is in a different domain than VDA used for application or Desktop launch.
