Unsolved
This post is more than 5 years old
2 Posts
0
29919
May 26th, 2015 09:00
R50L - Appliance mode
R50L - Appliance mode
We are currently implementing a XenDesktop 5-solution for one of our customers, and they are planning to use R50L as clients. We have just begun testing the client, and tried to get Desktop Appliance mode against the Citrix Web Interface up and running.
The problem is as follows;
We setup the appliance mode against the Web Interface; https://portal.domain.com
After the client finished booting into appliance mode we get a black screen with the message:
Desktop Appliance could not locate your desktop
Desktop Appliance cannot detect a Citrix XenDesktop Server on your network. Please verify that network cable is attached to your unit and press F5 to re-attempt.
If you continue to see this screen please contact your system administrator for assistance.
When we press F5, the login appears just fine! (The fastest we have gotten this to work is five seconds after the browser/black screen appears).
The first time we did this we got a firefox-message telling us we had to accept that the certificate was not trusted, so we set that the exeption was OK, and should be used in the future.
This setting must somehow be remembered, because we are not seeing this message anymore.
Sadly, this makes us have to press F5 everytime a user needs to log on, and it doesn't look very appealing to the users.
This is okay for one client, but this is a solution with 500+ clients! This has to be solved if we are gonna be able using Wyse clients.
PS: Kind of a bug, when pressing the Citrix.com/HDX-icon from the Web interface login portal we get the same black screen, and no way getting back to the login screen but restart the client. This is because the clients are behind a very restrictive firewall and cannot reach the resources - but we should be able to get back to the login screen without restarting said client.
We will really appreciate any help!



tomasrk
2 Posts
0
May 26th, 2015 09:00
Perfect! Thank you for the quick response, jpropsner!
I suspected that slow networking might be the culprit. To bad there's no public fix for this yet, would want to demo this right away.
Anyways, this will make our customers very happy.
jpropsner
67 Posts
0
May 26th, 2015 09:00
The issues is that the network is not starting fast enough to allow the webinterface connection, like if you are connecting wireless. Once you hit F5, the network has had time in the background and the user gets connected. There is a new appliance mode add-on that has a built in delay to give the network enough time to start before bringing up the webinterface connection. You need to contact your local Wyse rep or the help desk to get this new addon, until the next release of Linux. It will have the new add-on built in.