Hi
We were facing the same issue. We got the probe to work using an ica file, together with the probe settings (this was the ica_response 3.3, didn't try it with 3.4)
So:
General Tab - Server, Server IP filled in
Username and password filled in
Application Tab - Start Published Application and enter application name
Client Settings tab - Use ICA file, override authentication settings in ica file, override application settings in ica file
Misc tab - Select the QoS you want.
The issue with us was that the probe didn't seem to connect properly, so that's why we used the ica file for connection only.
Example of an ica file (in here the application name was filled in, not really needed because the probe has that data. But it might help to test the connection first)
[Encoding]
InputEncoding = ISO8859_1
[WFClient]
Version=2
ProxyType=Auto
HttpBrowserAddress=1.1.1.1:80
ConnectionBar=0
[ApplicationServers]
ApplicationName=
[1.1.1.1]
Address=ApplicationName
InitialProgram=#ApplicationName
CGPAddress=*:2598
ClientAudio=On
DesiredColor=8
DesiredHRes = 1024
DesiredVRes = 768
TWIMode = False
KeyboardTimer = 0
MouseTimer = 0
ConnectionBar=0
Username=
Domain=
ClearPassword=
TransportDriver=TCP/IP
WinStationDriver=ICA 3.0
BrowserProtocol=HTTPonTCP
Compress=On
EncryptionLevelSession=Encrypt
[Encrypt]
DriverNameWin32=PDCRYPTN.DLL
DriverNameWin16=PDCRYPTW.DLL
[Compress]
DriverName=PDCOMP.DLL
DriverNameWin16=PDCOMPW.DLL
DriverNameWin32=PDCOMPN.DLL
Using this setup, the probe could connect to the citrix server, log on, launch the application, close it and logoff and measure every QoS.
Hope this helps a bit.
Mark