We have an issue we have not had to consider until now.
Basically we have setup a desktop pool that only includes a single PC. This PC is used for programs that require a very high-end graphics card with no less than 10GB of graphics ram and high-end CPUs for 3D rendering. Up to now its been working great, we published it out through Horizon and anyone in the office can use it when they need to from within the office or at home.
Here's the complaint we are getting. User 1 is already in the system working, User 2 wants to use the system so logs in via Horizon and it locks User 1 session so User 2's session becomes active. Now when you do this with MS RDP protocol you get an alert about someone else being in the system and that user normally gets a message stating that another user is trying to login to the desktop, but it appears that this is not happening when using Horizon with the blast protocol.
Anyone seen this before?
