This turned out to be a bug in ThinShell. We are using a generic account to log into a group of VDI desktops. ThinShell was not passing a device name with the login to the connection broker. This caused the connection broker to redirect the session to the next ThinShell initiated connection from a client. This was solved by using ThinShell to call a server hosted .pit file and using unique logins.
Unlike AppPortal, Thinshell won't recheck to see when the VMs OS has finished loading.
This means you'll need to try the connection again through ThinShell to see if it is working yet.
Assuming you get the same message, swap to the vWorkspace Management Console and take a look at the Status of the Virtual machine you're trying to connect to. What does it say here ?
aaron_kay
4 Posts
1
October 20th, 2011 16:00
This turned out to be a bug in ThinShell. We are using a generic account to log into a group of VDI desktops. ThinShell was not passing a device name with the login to the connection broker. This caused the connection broker to redirect the session to the next ThinShell initiated connection from a client. This was solved by using ThinShell to call a server hosted .pit file and using unique logins.
DELL-Andrew W1
378 Posts
0
August 22nd, 2011 14:00
Hello,
Unlike AppPortal, Thinshell won't recheck to see when the VMs OS has finished loading.
This means you'll need to try the connection again through ThinShell to see if it is working yet.
Assuming you get the same message, swap to the vWorkspace Management Console and take a look at the Status of the Virtual machine you're trying to connect to. What does it say here ?
Thanks, Andrew