DELLTechnologies Windows 10 IoT Optimized Software User Guide

DELLTechnologies Windows 10 IoT Optimized Software

Specifications

• Supported Operating System: Windows 10 IoT Enterprise LTSC 2021
• Platforms Supported for New Policy: Wyse Device Agent, OptiPlex 3000 Thin Client, OptiPlex 7410 All-in-One Thin Client, Latitude 3440, Latitude 5440
• Minimum Wyse Device Agent Version Required: 14.6.9.X

Product Usage Instructions

Introduction:

The Wyse Management Suite 4.1 supports the WinIoT 2.x configurations through a new configuration user interface offering an enhanced user experience. The new interface includes a search function for easy configuration option location.

Transitioning to WinIoT 2.x Configuration:

To transition from WinIoT (Legacy WES) to WinIoT 2.x:

1. Ensure ConfigUISupport.exe is installed on the device.
2. Deploy the ConfigUI.exe package from WMS to manage WinIoT devices with WinIoT 2.x policy.
3. For public cloud environments, the new interface is automatically applied.

Benefits to Customers:

The transition to WinIoT 2.x brings benefits such as improved user experience, easier navigation of configurations, and access to the latest feature updates.

Platforms Supported:

The supported platforms for the new policy and binary requirements include Wyse Device Agent, OptiPlex 3000 Thin Client, OptiPlex 7410 All-in-One Thin Client, Latitude 3440, and Latitude 5440 with a minimum Wyse Device Agent version of 14.6.9.X.

Frequently Asked Questions

Q: What happens if I do not update to WinIoT 2.x policies?

If you continue using the Legacy WES policy, you will not have access to the new features and enhancements provided by the WinIoT 2.x policies. It is recommended to update for improved functionality.

Q: Do I need to redo configurations after transitioning to WinIoT 2.x?

Yes, after transitioning from WinIoT (Legacy WES) to WinIoT 2.x, it is necessary to redo all configurations to align with the new policy settings and features.

Q: Is there anything to prevent a device from running the WMS 1.0 & 2.0 policy at the same time? It seems like there could be a huge conflict potentially.
When we push both 1.x and 2.x policies together ,client will only take up the policies according to its Configuration (i.e when the end point has WinIoT 2.x compatible agent, then these devices receive only WinIoT 2.x policies from WMS and vice versa).

Q: Device with the latest WDA & ConfigUISupport package can use either 1.x or 2.x policy, how does it determine which config to use since they use the same WMS policy?
If the device is with latest WDA & ConfigUISupport.exe then the device will appear as WinIoT 2.x in WMS and only support for WinIoT 2.x policy from WMS. These devices can no longer be managed using WinIoT Legacy configuration set.

Transition from the WinIoT (WES) policy to WinIoT 2.x

Abstract
This document is about the transition of the Windows IoT configuration policies in Dell Wyse Management Suite to the latest 2.x policies. This document details the introduction, renaming, and benefits of the latest policies. It also provides step-by-step information about transitioning to the latest 2.x policies.
September 2023

Revisions

Acknowledgments

Author: Dell Windows IoT Engineering team

Support: Dell Windows IoT Engineering

• The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose.
• Use, copying, and distribution of any software described in this publication requires an applicable software license.
• This document may contain certain words that are not consistent with Dell’s current language guidelines. Dell plans to update the document over subsequent future releases to revise these words accordingly.
• This document may contain language from third party content that is not under Dell’s control and is not consistent with Dell’s current guidelines for Dell’s own content. When such third party content is updated by the relevant third parties, this document will be revised accordingly.
• Copyright © 09-2023 Dell Inc. or its subsidiaries. All Rights Reserved. Dell Technologies, Dell, EMC, Dell EMC and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. [9/15/2023] [Document Type] [Document ID]

New configuration user interface support for Windows 10 IoT Enterprise

devices

• From Wyse Management Suite 4.1, the WinIoT 2.x policies contain a new user interface and settings that are available under the WinIoT 2.x policies.
• The features are grouped to help with easier navigation of configurations. It is important to update new Configuration policy (WinIoT 2.x) to receive the latest feature updates. If you are using the WinIoT  (Legacy WES) policy, you will not have access to these new features.

Introduction of new WinIoT 2.x Configuration

• Wyse Management Suite 4.1 supports the WinIoT 2.x configurations through a new configuration user interface which provides 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 needed for any device to be recognized 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.
• For the public cloud environment, the new interface is applied automatically.
• 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 2.0.0.471 or later versions.
• NOTE: After you transition from WinIoT (Legacy WES) to WinIoT 2.x, you must redo all configurations.

Benefits to customers

• Enhanced user experience: The new policy provides a fresh and intuitive user interface, making it easier for users to navigate and use 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 in the WMS server and update the client agent by deploying the latest version of WDA. You do not have to upgrade the WMS server for new features to be supported.
• Reset Policy: The reset policy resets the configuration of the entire page and reset entire policy which will reset the configurations for all parameter groups. Both options are not part of legacy policy. Only the configured parameters are applied to the device.
• The parameter which is not configured from WMS, or the default values will not be applied on the device.
• The new Windows IoT User Interface has the similar look and feel of ThinOS and DHC features. The features are grouped to help with easier navigation of configurations.

WinIot (WES) and WinIot 2.x Policy

• WinIot 2.X is displayed in the Edit policies option, when you click the Edit Policy option in the Group & Configs page. WES is updated to WinIot(WES), and the new option WinIot 2.x is added. When you click WinIot 2.x, you are redirected to the WinIoT 2.x configuration page which is based on the new user interface for WinIoT 2.x.

• The new interface includes a search function that enables you to locate configuration options easily.

• The new interface includes for Reset Policy and Reset Entire Policy.

• WinIoT 2.x is a new Config UI interface for Windows 10 IoT Enterprise LTSC 2021 thin clients that are supported in WMS 4.1 with WDA 14.6.9.x and later versions.
• WinIoT (WES) is a legacy configuration interface for Windows 10 IoT Enterprise LTSC 2021 thin clients that are supported in WMS 4.0 with WDA 14.6.8.1 or earlier versions.

Platforms that are supported for the new policy and binary requirement

OptiPlex 7410 All in One Thin Client
Latitude 3440
Latitude 5440
Wyse Device Agent| 14.6.9.X or higher
Wyse Easy Setup| 2.0.0.471 or higher
ConfigUISupport| 1.0.0.3 or higher

Converting WinIot (WES) device to WinIot 2.x device

1. Register the device to the Wyse Management Suite server and add to the New Device Policy group (New Policy is a group name).

2. Log in to the Wyse Management Suite server and go to Apps&Data.

3. Under App Inventory, select Thin Client and click Add WinIot Package File.

4. Browse and select ConfigUISupport.exe.

5. Click Upload.
   Note: You can download the latest ConfigUI package from dell.com/support.

6. Go to Apps&Data>App Policies >Thin Client>Add Policy.

7. Provide a policy name and then select the Device Group.

8. Select Install Application and then select WinIoT as the operating system type.
   Note: If you have a PRO license, you can use Advanced App Policy to simultaneously deploy the package to multiple groups.

9. In the Application option, select ConfigUISupport.exe file from the Apps drop-down list.

10. Enter the required time as Install Timeout.

11. Enter –silent as the install parameter.

12. Select OS Subtype Filter as WIE10 (Windows IoT Enterprise).

13. Select Platform Filter as OptiPlex 3000 Thin Client, OptiPlex All-in-One, OptiPlex Micro Plus, Latitude 3440 or Latitude 5440.

14. Click Save and then click Yes to schedule a job immediately.
    You can verify the status in the Jobs page of Wyse Management Suite.

15. Verify that the Registry HKLM\Software\WNT IsConfiUIsuported is enabled (set to 1).
    Note: You must use Wyse Device Agent 14.6.9.x or later versions.

16. Log in to the Wyse Management Suite server and go to Portal Administration.

17. Under System, select Setup.

18. From the Portal Administration setup under Configuration UI Package, upload the new configuration UI package.
    Note: This is required only for the on-premises WMS servers. For the cloud WMS server, this is already completed.

Alert message is displayed in Wyse Management suite.

Customer impact

• Deployment transition
  • Only the ConfigUI-enabled devices can be managed by the new WinIoT 2.x policy.
  • During the transition from WinIoT (WES) to WinIoT 2.x, you must redo all configurations.
• Policy compatibility:
  • Non-Config UI-enabled devices will not have the option to use the new WinIoT 2.x policy.
  • You can continue using the WinIoT (Legacy WES) policy even with the newer version of WMS.

Recommendation

Dell Technologies recommends you to transition to WinIoT 2.x policy since new WinIoT-related features on the Wyse Management Suite will only be available under the WinIoT 2.x policy, going forward. If you are using the WinIoT (Legacy WES) policy, devices cannot be managed using WinIoT 2.x policy and there will be no new feature updates.

New WinIoT 2.x policy transition requirements

WinIoT 2.x

| + WMS 4.1 or above

+ DellWMS-ConfigurationUI- Package.zip (1.9.950)

| + WDA 14.6.9.21 or above

+ ConfigUISupport.exe (1.0.0.3)

| ****

Dell thin clients with Windows 10 IoT Enterprise LTSC 2021

Support Matrix

WDA

v 14.6.9.21+

| ConfigUISupport.exe v 1.0.0.3| DellWMS- ConfigurationUI[1]Package.zip v 1.9.950| WMS 4.1+| WMS policy supported on the device
---|---|---|---|---
N| N| N| N| 1.x policy
N| N| N| Y| 1.x policy
N| N| Y| N| 1.x policy
N| N| Y| Y| 1.x policy
N| Y| N| N| 1.x policy
N| Y| N| Y| 1.x policy
N| Y| Y| N| 1.x policy
N| Y| Y| Y| 1.x policy
Y| N| N| N| 1.x policy
Y| N| N| Y| 1.x policy
Y| N| Y| N| 1.x policy
Y| N| Y| Y| 1.x policy
Y| Y| N| N| The device would continue to be seen as 1.x device but no configuration policy deployment to the device would be applied.
WDA

v 14.6.9.21+

| ConfigUISupport.exe v 1.0.0.3| DellWMS- ConfigurationUI[1]Package.zip v 1.9.950| WMS 4.1+| WMS policy supported on the device
---|---|---|---|---
Y| Y| N| Y| The device would be recognized as 2.x capable, but Config UI options would not appear in the WMS console for WinIoT 2.x edit policies.
Y| Y| Y| N| The device would continue to be seen as 1.x device but no configuration policy deployment to the device would be applied. Also, no Config UI options would appear as in the above case.
Y| Y| Y| Y| The device would recognize as

2.x capable device and could support the deployment of ONLY

2.x policies. 1.x policies pushed to such a device will not apply.

Read User Manual Online (PDF format)

Download This Manual (PDF format)

Download this manual  >>