The client will show any pool that a user is entitled to that the connection server is allowed to present, usually protected using CS tags.
In this "Testing Center," is this the only pool that will be used in that space? In that case I would reconfigure your thin clients in that room to auto-select the "Testing Center" pool. This can be done in most thin client configurations. This pool will still be seen on Thin Clients outside this space to users that are entitled.
Another option would be to break SSO in this "Testing Center" pool and create Kiosk Accounts for your thin clients and add them to an AD group. That AD group is entitled to the Testing Center pool so that the TC's can log in and then when your users enter the testing center, they will be at a windows login screen instead of a TC login.
A third way you could do is create an additional View connection server and assign connection server tags (say Standard and Testing) and then assign pools to those connection server tags so that only the Testing Center pool is available on one of the connection servers. Then reconfigure all your pools to have the Standard tag, except for your testing pool which should have the "Testing" tag. Then reconfigure your thin clients in the Testing Center to connect to the one connection server with the Testing tag. The pool will only be exposed on that Connection server and all other pools will not be available on that CS.
If you have any questions on the options, let me know.
VDI Engineer
VCP-DCV, VCP7-DTM, VCAP7-DTM Design
. I'm afraid it looks like I would have to build a CS, I was hoping for a way around not building one. I hope vmware in the future will build it like the HTML, where we can check it to make it display or hide it.
