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

Today I am going to talk about the design decision on how to manager your user profiles on VDIs. This topic has been evolving over the years as technology has made new solutions possible. The important thing to point out is out of all the solutions none of them are bad. It just depends on the use case you are working with as to what is the best fit. Below you will find 6 profile solutions and details about when to use each. Don't Use Any Solution - With this solution you chose to not do anything with the profiles. This means if you are running a non-persistent VDI when the VDI is refreshed all user data will be deleted. This has no real impact in a full persistent VDI environment. Recommended use case: Full Persistent VDI or Non-persistent VDI where you do not care if you do not retain user data. Horizon Persistent Disks - With this solution you redirect the user profile to a 2nd hard drive on the VDI. This allows you to be able to refresh the C drive of the VD...

With the recent release of VMware Horizon 7.5 a new feature was added to the product. This Feature is called JMP Integrated Workflow. JMP is a marketing term used by VMware to mean Just-in-Time Management Platform and really this is just a combination of 3 products inside of VMware Horizon Enterprise. The 3 products are Instant Clones, App Volumes, and User Environment Manager. With the introduction of the workflow in Horizon 7.5 it adds a new HTML5 console for user centric management. This is VMware's solution to bringing all the solutions under a single console to define what the users workspace will be and automate the creation of that workspace. Recently VMware created a Quick Start Guide for using this new console if you are using the 3 products i listed above or are looking into using them i would highly recommend giving this guide a look over.