Jump to content
Welcome to our new Citrix community!
  • 0

Citrix Probe Agent


Steve Beckwith

Question

Hello, I am trying to setup the Citrix Probe Agent to work with Citrix Cloud, i have managed to setup the API Access and got the end point configured, With "update citrix cloud with results"...which i though was the hard part...

 

but this is failing to launch the ICA file...[4] INFO ProbeEndPoint.Log - ICA Launch failed. Adding stage failure

 

The end point can login to Workspace client with the same user ID and launch the applications no problem, is the Probe using a different engine? can i capture this ICA file in a temp folder and see its contents?

 

Extract of the CitrixProbeAgent.txt log....

 

2019-02-06 13:00:00,827 [16] INFO ProbeEndPoint.Log - Running task for configuration Fetcher
2019-02-06 13:00:00,827 [16] DEBUG ProbeEndPoint.Log - param1
2019-02-06 13:00:00,827 [16] DEBUG ProbeEndPoint.Log - param2
2019-02-06 13:00:00,827 [16] DEBUG ProbeEndPoint.Log - param3
2019-02-06 13:00:00,827 [16] DEBUG ProbeEndPoint.Log - param4
2019-02-06 13:00:00,827 [16] DEBUG ProbeEndPoint.Log - param5
2019-02-06 13:00:00,827 [16] DEBUG ProbeEndPoint.Log - param6
2019-02-06 13:00:00,828 [16] DEBUG ProbeEndPoint.Log - param7
2019-02-06 13:00:00,828 [16] DEBUG ProbeEndPoint.Log - param8
2019-02-06 13:00:00,828 [16] DEBUG ProbeEndPoint.Log - param9
2019-02-06 13:00:00,828 [16] INFO ProbeEndPoint.Log - Retreiving
2019-02-06 13:00:00,829 [16] INFO ProbeEndPoint.Log - Retreiving
2019-02-06 13:00:00,830 [16] INFO ProbeEndPoint.Log - DirectorService logOnCloud
2019-02-06 13:00:01,236 [4] INFO ProbeEndPoint.Log - Config Fetcher is running
2019-02-06 13:00:01,236 [4] INFO ProbeEndPoint.Log - Waiting for the config fetcher to finish
2019-02-06 13:00:14,032 [16] INFO ProbeEndPoint.Log - Calling Director API: GetConfiguredAppDetails()
2019-02-06 13:00:14,811 [16] INFO ProbeEndPoint.Log - Cleared the existing job items
2019-02-06 13:00:14,811 [16] INFO ProbeEndPoint.Log - Added jobItem for appID:52620884-2446-4eaf-af98-1e445dd98848scheduled at: 13 hrs
2019-02-06 13:00:14,811 [16] INFO ProbeEndPoint.Log - Added jobItem for appID:1c1b4cbf-61ae-4010-bc91-97e1a61a620escheduled at: 13 hrs
2019-02-06 13:00:14,811 [16] INFO ProbeEndPoint.Log - Added jobItem for appID:d32ab427-4f0c-466f-b10c-c7dd02ac5a03scheduled at: 13 hrs
2019-02-06 13:00:14,811 [16] INFO ProbeEndPoint.Log - Added jobItem for appID:a5e96bec-8f99-45e3-9078-caf1116edd90scheduled at: 13 hrs
2019-02-06 13:00:14,811 [16] INFO ProbeEndPoint.Log - DirectorService logOff
2019-02-06 13:00:15,547 [16] INFO ProbeEndPoint.Log - Finished Logoff Director
2019-02-06 13:00:15,547 [16] INFO ProbeEndPoint.Log - Config fetch will be called in 00:59:45
2019-02-06 13:00:21,237 [4] INFO ProbeEndPoint.Log - Running task for probe scheduler
2019-02-06 13:00:21,237 [4] INFO ProbeEndPoint.Log - Retrieved items to run at hour: 13
2019-02-06 13:00:21,237 [4] DEBUG ProbeEndPoint.Log - param1
2019-02-06 13:00:21,237 [4] DEBUG ProbeEndPoint.Log - param2
2019-02-06 13:00:21,237 [4] DEBUG ProbeEndPoint.Log - param3
2019-02-06 13:00:21,237 [4] INFO ProbeEndPoint.Log - Retreiving
2019-02-06 13:00:21,239 [4] INFO ProbeEndPoint.Log - Jobitem Outlook OLD
2019-02-06 13:00:21,239 [4] INFO ProbeEndPoint.Log - Running reachability check
2019-02-06 13:00:22,574 [4] INFO ProbeEndPoint.Log - Reachability passed. Adding stage result
2019-02-06 13:00:22,574 [4] INFO ProbeEndPoint.Log - Running authentication check
2019-02-06 13:00:29,705 [4] INFO ProbeEndPoint.Log - Authentication passed. Adding stage result
2019-02-06 13:00:29,705 [4] INFO ProbeEndPoint.Log - Running enumeration check
2019-02-06 13:00:32,775 [4] INFO ProbeEndPoint.Log - a3c53bcb-5fae-4728-a216-9db911de45e2.Outlook OLD
2019-02-06 13:00:32,775 [4] INFO ProbeEndPoint.Log - Enumeration passed. Adding stage result
2019-02-06 13:00:32,775 [4] INFO ProbeEndPoint.Log - Running download and launch check
2019-02-06 13:00:35,060 [4] INFO ProbeEndPoint.Log - Launching app
2019-02-06 13:00:47,907 [4] DEBUG ProbeEndPoint.Log - param1
2019-02-06 13:00:47,907 [4] DEBUG ProbeEndPoint.Log - param2
2019-02-06 13:00:47,907 [4] DEBUG ProbeEndPoint.Log - param3
2019-02-06 13:00:47,907 [4] DEBUG ProbeEndPoint.Log - param4
2019-02-06 13:00:47,907 [4] DEBUG ProbeEndPoint.Log - param5
2019-02-06 13:00:47,908 [4] DEBUG ProbeEndPoint.Log - param6
2019-02-06 13:00:47,908 [4] DEBUG ProbeEndPoint.Log - param7
2019-02-06 13:00:47,908 [4] DEBUG ProbeEndPoint.Log - param8
2019-02-06 13:00:47,908 [4] DEBUG ProbeEndPoint.Log - param9
2019-02-06 13:00:47,908 [4] INFO ProbeEndPoint.Log - Retreiving
2019-02-06 13:00:47,909 [4] INFO ProbeEndPoint.Log - Retreiving
2019-02-06 13:00:47,910 [4] DEBUG ProbeEndPoint.Log - param1
2019-02-06 13:00:47,910 [4] DEBUG ProbeEndPoint.Log - param2
2019-02-06 13:00:47,910 [4] DEBUG ProbeEndPoint.Log - param3
2019-02-06 13:00:47,910 [4] INFO ProbeEndPoint.Log - Retreiving
2019-02-06 13:00:47,911 [4] INFO ProbeEndPoint.Log - DirectorService logOnCloud
2019-02-06 13:00:47,916 [13] INFO ProbeEndPoint.Log - OnConnect passed
2019-02-06 13:00:54,003 [4] INFO ProbeEndPoint.Log - Waiting for session launch
2019-02-06 13:02:54,005 [4] INFO ProbeEndPoint.Log - checking for session -> machine: ******CTX004 domain: <domain> user: s****.b******
2019-02-06 13:02:54,005 [4] INFO ProbeEndPoint.Log - Calling Director API: GetProbeSession()
2019-02-06 13:02:55,948 [4] INFO ProbeEndPoint.Log - Done executing the request
2019-02-06 13:02:55,948 [4] INFO ProbeEndPoint.Log - Waiting for session launch
2019-02-06 13:04:55,950 [4] INFO ProbeEndPoint.Log - checking for session -> machine: ******CTX004 domain: <domain> user: s****.b******
2019-02-06 13:04:55,950 [4] INFO ProbeEndPoint.Log - Calling Director API: GetProbeSession()
2019-02-06 13:04:57,883 [4] INFO ProbeEndPoint.Log - Done executing the request
2019-02-06 13:04:58,937 [9] INFO ProbeEndPoint.Log - Running task for heart beat
2019-02-06 13:04:58,937 [9] DEBUG ProbeEndPoint.Log - param1
2019-02-06 13:04:58,937 [9] DEBUG ProbeEndPoint.Log - param2
2019-02-06 13:04:58,937 [9] DEBUG ProbeEndPoint.Log - param3
2019-02-06 13:04:58,937 [9] DEBUG ProbeEndPoint.Log - param4
2019-02-06 13:04:58,937 [9] DEBUG ProbeEndPoint.Log - param5
2019-02-06 13:04:58,937 [9] DEBUG ProbeEndPoint.Log - param6
2019-02-06 13:04:58,937 [9] DEBUG ProbeEndPoint.Log - param7
2019-02-06 13:04:58,937 [9] DEBUG ProbeEndPoint.Log - param8
2019-02-06 13:04:58,938 [9] DEBUG ProbeEndPoint.Log - param9
2019-02-06 13:04:58,938 [9] INFO ProbeEndPoint.Log - Retreiving
2019-02-06 13:04:58,939 [9] INFO ProbeEndPoint.Log - Retreiving
2019-02-06 13:04:58,940 [9] INFO ProbeEndPoint.Log - DirectorService logOnCloud
2019-02-06 13:05:14,301 [9] INFO ProbeEndPoint.Log - Calling Director API: SendProbeEndpointHeartbeat()
2019-02-06 13:05:14,909 [9] INFO ProbeEndPoint.Log - DirectorService logOff
2019-02-06 13:05:15,813 [9] INFO ProbeEndPoint.Log - Finished Logoff Director
2019-02-06 13:05:17,884 [4] INFO ProbeEndPoint.Log - Calling Director API: ProbeSessionLogOff()
2019-02-06 13:05:18,909 [4] INFO ProbeEndPoint.Log - Done executing the request
2019-02-06 13:05:18,909 [4] INFO ProbeEndPoint.Log - DirectorService logOff
2019-02-06 13:05:19,781 [4] INFO ProbeEndPoint.Log - Finished Logoff Director
2019-02-06 13:05:19,795 [4] INFO ProbeEndPoint.Log - ICA download passed. Adding stage result
2019-02-06 13:05:19,795 [4] INFO ProbeEndPoint.Log - ICA Launch failed. Adding stage failure
2019-02-06 13:05:19,795 [4] INFO ProbeEndPoint.Log - Logging off storefront
2019-02-06 13:05:20,166 [10] INFO ProbeEndPoint.Log - publishing result for App id:52620884-2446-4eaf-af98-1e445dd98848, Rule id:3

Link to comment

3 answers to this question

Recommended Posts

  • 0

For anybody who has the same issue, basically you need to use the NETBIOS name of the domain where your workers are joined, so for my example the client has on-prem  "company.local" and a seperate azure domain which was "compan.co.nz" you will need an account in "company.co.nz" domain (cant use a domain trusted account created in company.local), and when using it to login to the Workspace URL (first configuration window of agent setup) you leave off the "co.nz" eg: "company\probeuser"

 

TLDR: Use the first part of the FQDN before the first "." of the domain your Workers are in, and the user must have been created in that same domain

 

 

  • Like 1
Link to comment
  • 0

How did you solve this:

Hello, I am trying to setup the Citrix Probe Agent to work with Citrix Cloud, i have managed to setup the API Access and got the end point configured, With "update citrix cloud with results"...which i though was the hard part...

I cant get past Client ID,SecretKey part in the2view the probe result on Citrix cloud"

 

best regards

Uffe

Link to comment
  • 0
On 5/23/2019 at 4:32 PM, Ulf Johansson1709160988 said:

How did you solve this:

Hello, I am trying to setup the Citrix Probe Agent to work with Citrix Cloud, i have managed to setup the API Access and got the end point configured, With "update citrix cloud with results"...which i though was the hard part...

I cant get past Client ID,SecretKey part in the2view the probe result on Citrix cloud"

 

best regards

Uffe

I am having the same issue configuring Display Probe Result to Citrix Cloud. On that option there is no way of configuring the NetBIOS domain, since it asks for API Client ID.

 

Best Regards

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...