Skip to main content

Empowering the End-User: Mastering WMS Select Groups for ThinOS

Empowering the End-User: Mastering WMS Select Groups for ThinOS

In my previous posts, we talked about routing devices automatically into the right WMS groups based on subnets and naming conventions. That model is perfect when a thin client has a single, dedicated purpose. But what happens when a shared terminal has a split personality, or a user needs to connect to entirely different environments depending on the day?

Enter ThinOS Select Groups—a powerful, yet often underutilized feature in Wyse Management Suite (WMS) Pro.

Here is a breakdown of what Select Groups are, how to configure them, and the real-world use cases where they absolutely shine.

What is a ThinOS Select Group?

Normally, WMS dictates the configuration. A device checks in, it gets assigned a policy, and it does exactly what it's told.

A Select Group flips this model by putting the choice in the end-user's hands. When configured, the ThinOS lock screen dynamically generates a dropdown menu, allowing the user to select which environment, broker, or configuration profile they want to load before they even log in.

(Note: Select Groups are an exclusive feature of WMS Pro. They are not available in WMS Standard.)

How to Set Up Select Groups

The architecture of a Select Group is unique. You aren't just creating standard folders; you are building a Parent-Child relationship that ThinOS natively translates into a UI menu.

Step 1: Create the Parent Select Group

Select Groups must be created at the root of your tree.

  1. Navigate to Groups & Configs and click the + icon on your Default Device Policy Group (Global).
  2. Name the group (e.g., Terminal_Select_Profiles).
  3. Check the box that says "This is a ThinOS Select group parent".

Step 2: Create the Child Select Groups

Click the + icon on your newly created Parent group. You can create up to 10 Child Select groups underneath it.

  • Name these clearly (e.g., Citrix Production, Horizon DR, Timeclock Kiosk).
  • Pro Tip: Whatever you name these Child groups is exactly what the end-user will see in the dropdown menu on the ThinOS screen.

Step 3: Configure the Independent Policies

Edit the policies for each Child group independently. You can configure entirely different brokers, display settings, and USB redirection rules for each one.

Step 4: Register the Devices

When you configure your DHCP option tags or DNS SRV records for auto-discovery, point your Group Token to one of the Child Select groups, not the Parent. The group token you use dictates the default selection the thin client boots into. From there, the user can click the dropdown to change it.

3 Real-World Use Cases for Select Groups

When should you actually use this? Here are three scenarios where Select Groups solve massive administrative headaches.

1. The Kiosk vs. Full Desktop (Healthcare & Retail)

You have a shared terminal at a nurses' station or a retail back office.

  • Child Group A (Kiosk): Configured for a generic, auto-login web browser kiosk. Nurses or floor staff select this to quickly punch the timeclock, check the schedule, or submit a request without needing to consume a full VDI license.
  • Child Group B (Clinical): Configured for Imprivata badge tap or Smart Card authentication. Doctors select this, tap their badge, and launch directly into their full, secure Epic/Citrix session.

2. The Multi-Tenant Contractor (BPO Call Centers)

If you manage an outsourced call center, your contractors might service Client A in the morning and Client B in the afternoon. They can't use a static configuration.

  • Child Group A: Configured with the Microsoft AVD client pointing to Client A's Azure tenant.
  • Child Group B: Configured with the VMware Horizon client pointing to Client B's on-premises data center.

The user simply selects the client they are working for that shift, and ThinOS reconfigures itself instantly.

3. User-Driven Disaster Recovery (DR)

Relying on Global Server Load Balancing (GSLB) for disaster recovery is great, but sometimes it fails to route users properly during a catastrophic outage.

  • Child Group A: Points to your primary VDI broker URL.
  • Child Group B: Points to your backup cloud-based DR environment.

If the primary data center goes offline, you don't need to scramble to push a WMS policy update to 5,000 panic-stricken users. You simply send an email: "Please select the DR option from your ThinOS dropdown menu and log in."

Labels: