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.
I am using ThinShell from HP WYSE7 clients to connect to a desktop in a coputer group in vWorkspace. Everything was working great in testing this new dpeloyment, until this morning. On day one of public availabilty at this college, I have a error message coming up when logging in to aVM via ThinShell:  "The computer operating system is loading..."  Nothig happens. It jsut sits there. This was all working great last week. No changes were made to this process. Any ideas would be wonderful! Please let me know if more information is needed to clarify.  -Aaron
ThinShell2.0 - The computer operating system is loading...