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 s...

Demystifying ThinOS Updates: Managing Firmware, BIOS, and App Packages via WMS You’ve set up bulletproof auto-discovery. You’ve architected your WMS group structure to perfectly route endpoints using auto-grouping rules. Now it’s time for the real work: keeping those endpoints secure, updated, and functional without disrupting your end-users. If you are coming from legacy environments (like ThinOS 8), you need to leave your old upgrade habits at the door. Modern ThinOS (9.x and 10.x) completely changed the game. It is no longer a monolithic, single-file upgrade. Here is how to master the modular update system in Wyse Management Suite (WMS) to deploy the "Holy Trinity" of endpoints: OS Firmware, Hardware BIOS, and VDI Applications. 1. The Modular OS: Welcome to Modern ThinOS Dell rebuilt ThinOS from the ground up starting with version 9.x. The biggest architectural shift was decoupling the VDI client applications (Citrix Workspace, VMware Hor...

Mastering WMS Policy Inheritance: Group Structure and Auto-Grouping Rules You’ve finally nailed down your auto-discovery using DNS SRV records and DHCP tags. You boot up a fresh thin client, and like magic, it checks into your Wyse Management Suite (WMS) tenant. But what happens next? If you haven’t properly architected your WMS group structure, that seamless check-in turns into an administrative nightmare, and troubleshooting becomes a game of hunting through nested folders to find where a conflicting policy was configured. To run a scalable, enterprise-grade EUC environment, you need a blueprint. Here is how to structure your WMS groups, master policy inheritance, and automate device placement so you never have to manually move a thin client again. 1. The Blueprint for WMS Groups: Architecture Matters A common misconception is that you must silo your groups by the operating system to prevent devices from pulling the wro...

Bulletproof WMS Auto-Discovery: Ditching CNAME for DNS SRV and DHCP Option Tags If you’ve been deploying Dell thin clients, you know that Wyse Management Suite (WMS) is the undisputed central nervous system of your EUC environment. But before we get to policy inheritances and firmware updates, we have to talk about step one: getting the clients to actually talk to the server right out of the box. Before diving into the auto-discovery configuration, let’s quickly recap your WMS architecture options to ensure you are routing clients to the right place: WMS Standard: This is your on-premises only solution. Keep in mind that Standard requires registration now, but it is completely free . WMS Pro: The enterprise tier, which is offered both as cloud and on-prem. Regardless of which tier you're running, you need a solid auto-discovery foundation. A lot of old documentation and community posts still talk about using CNAM...

How to Deploy Wyse Management Suite (WMS) Standard in a vSphere Lab If you are following along with my previous guides on building a VMware vSphere home lab, or if you are gearing up to deploy Dell Thin Clients in a corporate environment, you need a way to manage those endpoints. Dell's Wyse Management Suite (WMS) is the centralized command center for configuring, updating, and managing both ThinOS and Windows 11 IoT devices. Before we start building, it is important to understand how Dell offers this platform: WMS Pro (Paid): This is the enterprise-grade solution that offers subscription-based licensing. It can be deployed either fully on-premises or consumed as a Software-as-a-Service (SaaS) application in the public cloud. WMS Standard (Free): This edition is completely free and supports small to medium deployments, but it is only available for on-premises deployment . Note that while the software is free, Dell does now require you to register for a...

So you want to build a home lab for testing or to help study for a exam but you don't have a large budget to do this. You are in luck with the use of VMware Workstation you can create a nested vSphere lab on a single piece of hardware even a laptop so you can take your lab with you. Below I am going to cover what is needed to create this lab and how to build the basic items required to have your lab up and working. This will be broken into 8 steps to complete the lab setup process. Step 1) What is needed to build your vSphere lab on VMware Workstation This section will cover everything you need to have ready to get started with your home lab including hardware and software.  Step 2) Plan and design your vSphere lab networking in VMware Workstation This section will cover how to setup the networking inside of VMware Workstation to allow the lab to communicate. Step 3) Plan and create a windows template in VMware Workstation This is part of making this lab a l...