Hi,
I am packaging Horizon Client 2.3.3 in Symantec Workspace Virtualisation and although the x86 version works fine, the x64 doesnt. Horizon is started using the following arguments:
vmware-view.exe
-serverURL qa-vdi.schools.net
-connectUSBOnStartup true
-connectUSBOnInsert true
-desktopLayout fullscreen
-desktopProtocol PCoIP
-logInAsCurrentUser true
-SingleAutoConnect
-nonInteractive
When executing the x86 package, it waits for a couple of seconds and then opens up the remote desktop ready to log in. The x64 package is executed and then waits for a bit, then changes the active window to a hidden window, then changes back again, then doesnt do anything else. Interestingly if I remove the nonInteractive argument then it displays the username\password\domain prompt. So it looks like its something to do with the authentication passthrough function?
I have checked the logs and no ERROR messages can be found. I have also checked the Windows event log, but nothing in there either. I have compared the logs between the working package and the non-working package and the only thing I can see which could be the problem is in the debug log in c:\programdata:
2014-06-09T13:03:14.732+01:00 DEBUG (1524-126C) <NodeManagerWatcher> [vmware-view] Connection to Node Manager established.
2014-06-09T13:03:14.732+01:00 DEBUG (1524-18F8) <Main CAPI Thread> [vmware-view] wsAuth not installed
2014-06-09T13:03:14.888+01:00 DEBUG (1524-18F8) <Main CAPI Thread> [vmware-view] wsAuth not installed
The same position of the x86 log shows:
2014-06-06T14:51:22.528+01:00 DEBUG (0CD0-07D4) <NodeManagerWatcher> [vmware-view] Connection to Node Manager established.
2014-06-06T14:51:23.480+01:00 DEBUG (09B0-0D40) <MessageFrameWorkDispatch> [ws_winauth] [GSSApiProcessClientContext]: ContextID : ba237e0b-a474-43f6-b6bd-e0f43d340996, TargetPrincipal : SDC-VDI-CS01$@enniqa.net IdentifyOnly false
2014-06-06T14:51:23.729+01:00 DEBUG (09B0-1814) <MessageChannel ReceiveThread> [MessageFrameWork] Closed incoming SharedMemory channel from machine 1209820-MST084.enniqa.net, user ENNIQA\bdooher600
This could be a red herring, but it looks suspicious. I have also attached the full logs to this post.
If anyone can help it would be appreciated. Both packages were created the same way and if I remove the nonInteractive argument and enter the username/password/domain then it logs in fine.
Regards,
Lee