We have several zero client based computer labs on our campus, and these are set for open use for all users. The zero clients are pre-programmed to connect to the correct pools, but I'm having some trouble with non-lab users consuming VMs set aside for the lab.
The reason that this is happening is the fact that once you set the domain\users group on a pool entitlement, it becomes visible and available to everyone on the network. This creates a situation where either we don't have enough VMs to service the zero clients, or we have to overcommit the pool. Since the lab is supposed to be available to any user that walks in the door (including staff), AD groups aren't going to help me here.
Is there a way to create an active pool that does not advertise itself? The zero clients already have the exact pool name they need as a hard-coded entry; all I'm trying to do is stop the software client from displaying the pool to users sitting in an office (or at home).
Is this possible?
