Introduction of new WinIoT 2.x Configuration

Wyse Management Suite 4.1 supports new WinIoT 2.x configurations through a new configuration user interface, which provides an enhanced user experience. The new interface includes a search function that enables you to locate configuration options easily, saving time and effort.

ConfigUISupport.exe is required to recognize any device as a WinIoT 2.x policy-enabled device. For the WinIoT devices to be managed with the WinIoT2.x policy, deploy the ConfigUI.exe package from WMS. This will require the installation of the Dell Application Store in the same policy.

For the public cloud environment, the new interface is applied automatically. On-Prem or local WMS, apply all ConfigUI updates to your WMS install. This functionality is supported when you upgrade Wyse Device Agent to version 14.6.9.x or later versions and Wyse Easy Setup to version or later.

NOTE: After transitioning from WinIoT (Legacy WES) to WinIoT 2.x, you must redo all configurations.

Benefits / Features

Enhanced user experience: The new policy provides a fresh and intuitive user interface, making it
easier for users to navigate and utilize the WMS effectively.

  • Search function: The new UI includes a search function that enables users to locate configuration options more easily, saving time and effort.
  • Autonomous feature updates: After the upgrade, IT administrators can upload the newer Config UI schema package to the WMS server and update the client agent by deploying the latest version of
    WDA. You do not need to upgrade the WMS server to support new features.
  • Reset Policy: The reset policy resets the entire page’s configuration and the entire policy, which will reset the configurations for all parameter groups. Both options are not part of the legacy policy.
    Only the configured parameters will be applied to the device. The parameters not configured from WMS, or the default values will not be applied on the device.
  • The new Windows IoT User Interface has a similar look and feel to ThinOS and DHC features. The features are grouped to help with easier navigation of configurations.

There is a key feature in WES 2.x that provides the ability to update Windows IoT Microsoft Updates using UWF Service Mode. This feature will reboot the device and apply relevant Windows IoT updates when applied or scheduled. Depending on how many updates are required, it may take 2 or more updates to patch Windows IoT fully.

For more information, refer to

“Transition from the WinIoT (WES) policy to WinIoT 2.x” discusses the transition of Windows IoT configuration policies in Dell Wyse Management Suite to the latest 2.x policies. Here’s a summary of the key points:

  1. Introduction: The document introduces the transition of Windows IoT configuration policies in Dell Wyse Management Suite to WinIoT 2.x policies. It outlines the renaming and benefits of these policies and provides step-by-step guidance on transitioning to the latest 2.x policies.
  2. Benefits to Customers: The new WinIoT 2.x policies offer an enhanced user experience and a more intuitive interface. They include a search function for easier configuration navigation. These policies also support autonomous feature updates and a reset policy feature.
  3. Supported Platforms: The document lists all supported platforms and binary requirements for the new WinIoT 2.x policy, including specific Windows versions and Dell hardware.
  4. Transition Process: It provides detailed steps for converting WinIoT (WES) devices to WinIoT 2.x devices, involving device registration, software deployment, and configuration.
  5. Customer Impact: The transition may require redoing all configurations. Only ConfigUI-enabled devices can be managed by the new WinIoT 2.x policy.
  6. Recommendation: Dell recommends transitioning to WinIoT 2.x policies, as new WinIoT-related features will only be available in these policies going forward. Legacy WinIoT (WES) policies will not receive new feature updates.
  7. FAQ: The FAQ section addresses common questions about policy conflicts, device compatibility, and how devices determine which configuration to use based on their software versions.