Skip to main content

How to Deploy Wyse Management Suite (WMS) Standard in a vSphere Lab

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 Standard license key via their digital portal before you can install it.

In this guide, we are going to walk through standing up a free WMS Standard server as a virtual machine in your on-premises vSphere lab environment.

Prerequisites and Resource Requirements

WMS is surprisingly lightweight for a lab environment, but it does require a dedicated Windows Server instance. Before we begin the installation, you need to provision a VM in vCenter with the following specifications:

  • Operating System: Windows Server 2019 or 2022
  • CPU: 4 vCPUs
  • Memory: 8 GB RAM (Minimum)
  • Storage: 40 GB for the OS, plus a secondary 40 GB drive for the WMS local repository (firmware and app packages)
  • Network: A static IP address on your management VLAN

Step 1: Register and Download WMS Standard

Before prepping the server OS, you need to grab the software and your license key.

  1. Register for your key: Go to the Wyse Management Suite trials page. Click Start Free WMS Standard. You will be prompted to enter your contact details, email address, and on-premises identifier. An email with the standard license key will be sent to you.
  2. Download the Installer: Grab the latest WMS installer executable from the Dell Support Site for WMS.

Step 2: Prepare the Virtual Machine

Before running the WMS installer, ensure your Windows Server VM is properly configured for the network.

  1. Install VMware Tools on the Windows Server guest OS.
  2. Assign a static IP address to the primary network adapter.
  3. Join the Windows Server to your lab's Active Directory domain.
  4. Format the secondary 40 GB hard drive (typically as the D:\ drive) and label it "WMS_Repository".

Step 3: Run the WMS Installation Wizard

With the base OS prepped, it is time to install the WMS software and its dependencies. WMS Standard includes a local MariaDB database, so you do not need to stand up a separate SQL server for this lab.

  1. Launch the WMS installer executable as an Administrator.
  2. Select Typical as the setup type. (Custom is only necessary if you are offloading the database or spreading roles across multiple servers).
  3. Create your WMS database credentials. Document this password securely, as you will need it if you ever upgrade or migrate the server.
  4. When prompted, enter the Standard License Key that you generated via the Dell registration portal.
  5. Specify the local repository path. Point this to the D:\ drive you provisioned earlier.
  6. Review the port configurations (HTTPS 443 for the web console and device traffic, and MQTT 1883/8443 for real-time device communication) and click Install.

Step 4: SSL Certificate Configuration

Once the installation finishes, you will be prompted to launch the web console. WMS requires HTTPS to communicate securely with your thin clients.

  1. Navigate to https://[Your-WMS-Server-IP-or-FQDN] in a web browser.
  2. For a simple lab environment, you can allow WMS to generate a Self-Signed Certificate. However, note that if you use a self-signed certificate, you must configure your thin clients to accept insecure connections (Low security mode).
  3. If you are running an internal Microsoft Certificate Authority (CA) in your lab, it is highly recommended to import a valid SSL certificate in the WMS Setup wizard. Select Import a PKCS12 format certificate, upload your .pfx file, and enter the certificate password.

Step 5: Initial Setup and Auto-Discovery

After the certificate is applied, you will log into the WMS web interface using the default global administrator credentials created during the initial setup wizard. To make sure your thin clients can actually find this new server when they boot up out of the box, we need to configure your network for Zero-Touch Deployment.

You have two primary methods to accomplish this in your lab: DNS SRV records or DHCP Option tags.

Method A: DNS SRV Records (Recommended)

ThinOS devices will query DNS for specific Service (SRV) records to locate the management and MQTT servers.

  1. Open the DNS Manager on your lab's domain controller.
  2. Navigate to your Forward Lookup Zone, right-click, and select Other New Records.
  3. Scroll down, select Service Location (SRV), and click Create Record.
  4. Create the Management Server record:
    • Service: _WMS_MGMT
    • Protocol: _tcp
    • Port Number: 443
    • Host offering this service: The FQDN of your WMS server (e.g., wms01.yourlab.local)
  5. Create the MQTT Server record (which handles real-time commands):
    • Service: _WMS_MQTT
    • Protocol: _tcp
    • Port Number: 1883 (or 8443 if you configured secure MQTT)
    • Host offering this service: The FQDN of your WMS server

Method B: DHCP Option Tags

If you prefer not to modify DNS or need to direct specific subnets to different WMS groups, you can pass the WMS server URLs directly to the thin clients when they pull an IP address.

  1. Open the DHCP Manager on your lab's DHCP server.
  2. Right-click IPv4 and select Set Predefined Options.
  3. Click Add to create a new option for the WMS Management Server:
    • Name: WMS Management URL
    • Data Type: String
    • Code: 165
    • String Value: https://[Your-WMS-Server-FQDN]:443 (e.g., https://wms01.yourlab.local:443)
  4. Click Add to create a second option for the MQTT Server:
    • Name: WMS MQTT URL
    • Data Type: String
    • Code: 166
    • String Value: [Your-WMS-Server-FQDN]:1883 (e.g., wms01.yourlab.local:1883)
  5. Navigate to your DHCP Scope Options, enable Option 165 and Option 166, and ensure the string values are applied to your VDI subnet.

Now, when you plug a factory-default Dell Thin Client into your lab network, it will pull these network configurations, check in to your new WMS server, and wait in the "Unmanaged Devices" tab for you to assign it a policy!

Labels: