Prevent concurrent connections to desktops in two different pools?

[gmtx]

To test new software or configuration changes we typically create a second desktop pool and allow users to pick this desktop when they log in. Everything's fine until they disconnect and then accidentally log back in to the other desktop instead of reconnecting to their existing session. Persona Management chokes and user changes in that second session don't persist - never a good thing. Just looking for a way to disable multiple logins across pools. Is it possible?

Geoff

[Linjo]

What about having your test users connect to a different connection broker (replica) and use tags to filter off the pools you want to expose?

// Linjo

[gmtx]

Linjo,

Unless I'm missing something I'm not sure that solves my problem. I'd like to allow any user to participate in the test whenever they choose, so all users have access to both pools on the same broker right now. Adding another connection server would allow me to serve both pools individually using tags, but I'm not sure how it would prevent someone from connecting to one broker, starting a desktop, and then connecting to the other broker and starting another.

That extra step of picking the second broker might be enough to prevent accidentally starting a new session vs reconnecting to an existing session, but it also means I'll also have to teach users how to switch brokers if they want to participate in the test or switch back to their normal desktop if the new desktop has issues. In my environment that likely means I'm just going to trade one problem for another - but I do appreciate the suggestion!

Geoff