Zero Client machines via Teradici some users can't get a VDI but if they go to a different machine it is fine.

[mbze430]

I am having an issue that seems quite random.  I have capture an hour long log from the Horizon View Composer server that is about 1.6GB big.  I will try to describe the issue the best that I can.

I have group of people on a Microsoft AD.  We have several zero clients (HPs) running off Teradici PCoIP (firmware 5.4.1).  Several users trying to login to a VDI desktop will simply get disconnect trying to get to the VDI interface after passing the credential login screen (Imprivata).  HOWEVER, those same set of people that are having issue logging into VDI from a particular machine can move to another zero client in the same room and it will login to VDI just fine.  What make it even more random/strange is that a different person from a complete different set of people can login to the problematic machine and get a VDI without any problem whatsoever.

For an hour I have turned the logging level to Full on the View Composer (v7.4.0) and see if I can capture some errors.  However the log files isn't something I am familiar with nor does it indicate "Error" tags.

Any help or suggestion of the best way to isolate the issue would be greatly appreciated.

TIA

[NathanosBlightc]

Hi

If you used FQDN instead of IP Address to work in your VDI environment, please check again the DNS settings of each zero client, they must resolve each naming convention related to the Horizon connection servers in every step to login the desktop. (We had similar problem like this, So I don't think it's related to the device vendor or firmware version)

Also as your Zero Client device have a log repository, you must check it first to find any related problem then check the VDI Servers like connection and composer servers

[mbze430]

Thank you for your reply and suggestion.

All the zero client can resolve the FQDN.  As I have mentioned before.  One person can't get the VDI menu on a specific machine but a different person can on that same machine, to make matter worse, the same person having trouble with getting to the VDI menu, they can get on with another machine right beside the problem machine.