← Dell WMS
Dell WMSArchitectureThinOSInfrastructure

Dell WMS Architecture — Complete Reference

4 min read Patricio Parra Galia

Dell Wyse Management Suite connects three layers: the management server, the enterprise network, and ThinOS endpoints. Understanding how these interact is fundamental to designing a robust, secure deployment.

Core Components

1. WMS Server

The heart of the system. Available in two deployment modes:

ModeDescriptionWhen to use
On-PremiseWindows Server in your datacenterFull control, no cloud dependency
WMS CloudDell-managed SaaSSmall teams without own infrastructure
HybridOn-prem + cloud repositoryDistributed multi-site fleets

The server runs three primary services:

  • WMS Web Console: HTTPS interface (port 443)
  • MQTT Broker: bidirectional communication channel with endpoints (port 1883 / 8883 TLS)
  • File Server: firmware image and package repository (FTP/HTTPS)

2. Database

WMS uses MariaDB 10.x as its database engine. The default installation creates a local instance, but for production environments with more than 200 devices, externalizing is recommended:

# Recommended MariaDB configuration for production
[mysqld]
innodb_buffer_pool_size = 2G
innodb_log_file_size = 256M
max_connections = 300
query_cache_size = 0
query_cache_type = 0

At Radial Netherlands we managed 340 endpoints with an external MariaDB on a dedicated server. Performance with this configuration was excellent even during mass firmware updates.

3. ThinOS Agent

Dell Thin Clients run ThinOS — a read-only embedded OS designed exclusively for VDI. The WMS agent is built into all ThinOS 9.x versions and requires no manual installation.

The agent communication cycle:

Boot → DHCP → Resolve WMS FQDN → Connect MQTT → Register Device ID
     → Download Policy → Apply configuration → Connect VDI broker

4. Firmware Repository

WMS can connect to Dell’s repository or use a local mirror (recommended if internet connectivity is limited):

# Configure proxy for Dell repository access
Set-WmsServerProxy -Server "proxy.yourcompany.com" -Port 8080

Small environment (up to 100 endpoints)

[WMS Server]─────────[Core Switch]─────[Thin Clients]

                      [VDI Server]

                      [NAS/Storage]

All components on the same VLAN. Direct communication without additional complexity.

Medium environment (100–500 endpoints, multi-site)

[WMS Server (HQ)] ──── WAN/VPN ──── [Branch Switch] ──── [ThinOS]
        │                                    │
   [Database]                           [Local Cache]

   [VDI Farm]

For remote sites, consider WMS Local Edition as a local cache if WAN latency exceeds 80ms.

Enterprise (500+ endpoints, multi-country)

At Radial Netherlands we operated this topology with 340 endpoints across 6 countries:

  • Centralized WMS Server in the primary datacenter (Netherlands)
  • Site-to-site VPN for all branches (FortiGate)
  • Differentiated group policy by country and function
  • Firmware updates in maintenance windows by time zone region

Required Ports

PortProtocolDirectionUse
443TCP/HTTPSEndpoint → ServerConsole + REST API
1883TCP/MQTTEndpoint ↔ ServerReal-time telemetry
8883TCP/MQTTSEndpoint ↔ ServerMQTT with TLS (recommended)
21TCP/FTPEndpoint → ServerFirmware download (legacy)
443TCPServer → InternetDell repo (optional)

Golden rule: If you can only open one port, open 443. WMS can operate in degraded mode over HTTPS only, though you’ll lose real-time MQTT telemetry.

Security and Certificates

Trust Chain

Root CA (internal)
    └── Intermediate CA
            └── wms.yourcompany.local (SAN: IP also)

To distribute the root certificate to Thin Clients without physical access:

  1. Upload the .cer file to the server’s File Repository
  2. Create a policy with the Security → Certificates → Import section
  3. Devices will import the certificate on the next sync cycle
  • Disable FTP, use HTTPS for everything
  • Enable MQTT over TLS (port 8883)
  • Segment Thin Clients in a dedicated VLAN with ACLs
  • Configure nightly MariaDB backups
  • Enable LDAP/AD authentication for the WMS console

Scalability

SizeEndpointsServer RAMvCPUStorage
Small< 1008 GB4100 GB SSD
Medium100–50016 GB8200 GB SSD
Large500–200032 GB16500 GB SSD
Enterprise2000–1000064 GB321 TB SSD

For enterprise environments, Dell recommends distributing load across multiple WMS instances with a front-end load balancer.


Need help designing the WMS architecture for your organization? Get in touch — I can assess your current environment and propose the optimal topology.

Patricio Fabián Parra Galia

Dell WMS specialist · IT Infrastructure Engineer · 15+ years across Europe and Latin America.