Dell Wyse Management Suite Version 3.3 Administrator's Guide July 2021 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Introduction to Wyse Management Suite...................................................................... 9 Editions of Wyse Management Suite..............................................................................................................................9 Wyse Management Suite Feature Matrix...................................................................................................................... 9 What is new in Wyse Management Suite version 3.3................
Create a default device policy group............................................................................................................................33 Create a ThinOS Select group................................................................................................................................. 34 Edit a default device policy group........................................................................................................................... 34 Edit a ThinOS select group.
Registering devices by using DHCP option tags.................................................................................................. 61 Registering devices by using DNS SRV record.................................................................................................... 62 Search a device by using filters..................................................................................................................................... 63 Save the filter in Devices page..................
Image policy........................................................................................................................................................................ 86 Add Windows Embedded Standard operating system and ThinLinux images to repository..................... 87 Add ThinOS firmware to repository........................................................................................................................ 87 Add ThinOS BIOS file to repository...............................
Edit an end user............................................................................................................................................................... 109 Configure end user policy.............................................................................................................................................. 109 Bulk import end users...........................................................................................................................................
Configure license expiry email notifications.............................................................................................................. 135 Chapter 19: Firmware upgrade................................................................................................... 136 Upgrading ThinLinux 1.x to 2.1 and later versions....................................................................................................136 Prepare the ThinLinux 2.x image.....................................
1 Introduction to Wyse Management Suite Wyse Management Suite is the next generation management solution that enables you to centrally configure, monitor, manage, and optimize your Dell Hybrid Client powered endpoints and Dell thin clients. It also offers advanced feature options such as cloud and on-premises deployment, manage-from-anywhere option by using a mobile application, enhanced security such as BIOS configuration and port lockdown.
Table 1.
The following table provides information about the Dell Hybrid Client management features supported for each subscription type. Table 2.
Table 2.
Table 3. Wyse thin clients and zero clients management feature matrix (continued) Wyse thin clients and zero clients management features Wyse Management Suite Standard Wyse Management Suite Pro-private cloud Wyse Management Suite Pro-cloud edition Secure communication (HTTPS) √ √ √ 802.
Table 3.
2 Getting started with Wyse Management Suite This section provides information about the general features to get you started as an administrator and manage thin clients using Wyse Management Suite.
Logging out To log out from the management console, do the following: 1. Click the account link at the upper-right corner of the management console. 2. Click Sign out. Prerequisites to deploy Wyse Management Suite on the private cloud Table 4. Prerequisites Description 10,000 devices or less 50,000 devices or less 120,000 devices or less Wyse Management Suite – Software repository Operating system Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019 Standard.
NOTE: WMS.exe and WMS_Repo.exe must be installed on two different servers. You must install the Wyse Management Suite remote repository for the public cloud. For private cloud, you must install the Wyse Management Suite remote repository and local repository. The software can be installed on a physical or a virtual machine. Also, it is not necessary that the software repository and the Wyse Management Suite server have the same operating system.
￭ Configure different settings for the custom group. The settings that are configured at lower-level groups take precedence over the settings that were configured at the parent or higher-level groups. ○ Settings that are specific to a particular device which can be configured from the Device Details page. These settings, like lower-level groups, take precedence over the settings that are configured in the higher-level groups.
The Agent Configuration folder is available at the following location: ○ Windows Embedded Standard devices—%SYSTEMDRIVE%\\Wyse\\WCM\\ConfigMgmt\\Certificates ○ ThinLinux devices—/etc/addons.d/WDA/certs ○ ThinOS devices—wnos/cacerts/ NOTE: You must import the certificate to a thin client running ThinOS operating system using a USB drive or FTP paths.
3 Installing or upgrading Wyse Device Agent This section provides information about how to install or upgrade Wyse Device Agent on your thin clients, such as Windows Embedded Standard, Linux, and ThinLinux devices by using Wyse Management Suite. ● Windows Embedded Standard devices—Wyse Device Agent version 1.4.x can be downloaded from support.dell.com.
Steps 1. After the WDA.exe file is copied to the repository, go to Apps and Data, and create a standard application policy with this package—see Create and deploy standard application policy to thin clients. NOTE: Advanced application policy is supported only from Wyse Device Agent 14.x onwards. It is recommended that you use the standard application policy when you upgrade Wyse Device Agent from 14.x. You can also use the advanced application policy for upgrading Wyse Device Agent from 14.
4 Installing or upgrading DCA-Enabler on Ubuntu devices This section provides information about how to install or upgrade DCA-Enabler on Ubuntu devices. Topics: • • Install DCA-Enabler on Ubuntu devices Upgrade DCA-Enabler on Ubuntu devices Install DCA-Enabler on Ubuntu devices DCA-Enabler is preloaded in most of the Dell Ubuntu platforms. If DCA-Enabler is not preloaded, you can install DCA-Enabler. Steps 1. Download the DCA-Enabler packages from www.dell.com/support. 2. Extract the downloaded file.
5 Registering and configuring a new device using Wyse Management Suite Topics: • • • • • • • Register Register Register Register Register Register Register and and and and and and and configure configure configure configure configure configure configure a new Windows Embedded Standard device using Wyse Management Suite a new ThinOS 8.x device using Wyse Management Suite a new ThinOS 9.
5. Enable or disable CA validation based on your license type. For public cloud, select the Enable CA Validation check box. For private cloud, select the Enable CA Validation check box if you have imported certificates from a well-known certificate authority into your Wyse Management Suite server. To enable the CA validation option in the private cloud, you must install the same self-signed certificate on the ThinOS device as well.
page and validate the enrollment. The devices are moved to the intended group after they are validated. For more information about how to validate the devices, see Enrollment validation. The device is registered to Wyse Management Suite. 9. Log in to Wyse Management Suite. 10. Add the device to your desired group (optional)—see Managing groups and configs. 11. Configure the thin client using any of the following options: ● Using the Groups and Configs page—see Edit the ThinOS 9.x policy settings.
● Using the Devices page—see Managing Devices. Register and configure Dell Hybrid Client using Wyse Management Suite Prerequisites Before registering the device, ensure that your device has network connectivity to contact the Wyse Management Suite server. NOTE: You can register or unregister the device only from the guest user account. Steps 1. Log in to the Dell Hybrid Client as a guest user. 2. On the top bar, click . Figure 1. DCA icon 3. Click Dell Client Agent.
Figure 2. Dell Client Agent 10. Log in to Wyse Management Suite. 11. Add the device to your wanted group (optional)—see Managing Groups and Configs. 12. Configure the thin client using any of the following options: ● Using the Groups and Configs page—see Edit the Dell Hybrid Client policy settings. ● Using the Devices page—see Managing Devices.
You can also register the devices using any of the following methods: ● Using DHCP option tags—see Register devices by using DHCP option tags. ● Using DNS SRV record—see Registering devices by using DNS SRV record. NOTE: When the Enrollment Validation option is enabled, the manual or auto-discovered devices are in Enrollment Validation Pending state in the Devices page. The tenant can select a single device or multiple devices in the Devices page and validate the enrollment.
6 Wyse Management Suite dashboard The Dashboard page enables you to view the status of a system, and the recent tasks that are performed within the system. To view a particular alert, click the link in the Alerts section. The Dashboard page also enables you to view the device summary. Figure 3.
2. Click View All Alerts. The following attributes are displayed in the Events page: ● Devices Not Checked In ● App Compliance ● Other Device Alerts View the list of events The Events section displays the summary of events that have occurred in the last few days. Steps 1. Click Dashboard. The events summary is displayed. 2. Click View All Events. The Events page is displayed with list of all the events. View the device status The Display section provides the summary of device status. Steps 1.
3. Click Alerts, and select the appropriate check boxes to assign an alert type—Critical, Warning or Info—for notifications from your emails and mobile applications. 4. Click Policies, and select the Ask me if I want to use the ThinOS Wizard mode check box to display the Select ThinOS Configuration Mode window every time you configure the ThinOS policy settings. 5. Click Page size, and enter a number from 10 to 100 in the Number Of Items Per Page text box.
7 Managing groups and configurations The Groups & Configs page enables you to define policies that are required to configure your devices. You can create sub groups of the global group policies and categorize devices based on your requirements. For example, devices may be grouped based on job functions, device type, and so on. For each group, you can define policies for the following operating systems: ● ThinOS ○ ThinOS ○ ThinOS 9.
• • • • • • • • • • • • • • • • • Create a user policy group Configure a global level policy Import a user policy group Remove a group Configure a device level policy Export group policies Importing group policies Edit the ThinOS policy settings Edit the ThinOS 9.
Admins box. To move one group from the Assigned Group Admins to Available Group Admins, do the reverse. This step is optional. 8. Click Save. The group is added to the list of available groups on the Groups & Configs page. NOTE: The devices can be registered to a group by entering the group token which is available in the Groups and Configs page for the respective group. NOTE: The parent device policy group can have only 10 child device groups. Create a ThinOS Select group Steps 1.
Remove a ThinOS select group As an administrator, you can remove a group from the group hierarchy. Steps 1. In the Groups & Configs page, select the ThinOS select group that you want to delete. 2. Click . A warning message indicating that this action removes one or more groups from the group tree hierarchy is displayed. 3. From the groups drop-down list, select a new target group for users and devices in the current group. 4. Click Remove Group.
Figure 4. Add a new group NOTE: If the AD group is inside an OU group in the domain, then you must select the OU group as the AD Attribute. 4. Select the name of the group administrators who are tasked with managing this group. 5. From the Available Group Admins box, select the particular group and click the right arrow to move it to the Assigned Group Admins box. To move one group from the Assigned Group Admins to Available Group Admins, do the reverse. 6. Click Save.
7. Select the Device Group Mapping option to import user groups with device mapping to control the configurations that are applied to all device groups by default. AD User groups which are imported into Wyse Management Suite can be mapped to the respective device group. By mapping the devices, they do not receive unwanted user group policies. NOTE: By default, user groups are not mapped to a device group. If you select the Default device group policy, all sub-device groups are selected.
Remove a group As an administrator, you can remove a group from the group hierarchy. Steps 1. In the Groups & Configs page, select the group that you want to delete. 2. Click . A warning message indicating that this action removes one or more groups from the group tree hierarchy is displayed. 3. From the drop-down list, select a new group to move the users and devices in the current group. 4. Click Remove Group.
Importing group policies The Import Policies option enables you to import the policies. This option is available for Wyse Management Suite PRO license users. You can import the group policies from the Groups & Configs page or from the Edit Policies page. Import group policies from Groups and Configs page Steps 1. On the Groups & Configs page, select your preferred group. If the destination group contains policies of the same device type as the imported ones, they are removed and new ones are added. 2.
● From an existing group—Select a group from the drop-down list. Policies from that group are copied to the current group. ● From an exported file—Click Browse and select the .JSON file. Policies from that file are copied to the current group. 5. Click Next. A preview of the policies in the selected group is displayed. 6. Click Next.The summary of the import process is displayed.
● LPT port bind ThinOS—Wizard mode Use this page to configure the most frequently used parameters for the ThinOS devices. Steps 1. Select Wizard as the mode of configuration. 2. Configure the options are required. 3. Click Next to go to the next policy setting. 4. Click Save & Publish after you configure the options. NOTE: To go to ThinOS advanced configuration mode, click Continue. ThinOS—Advanced mode Use this page to configure the advanced policy settings for the ThinOS devices. Steps 1.
Figure 5. Configuration Control | ThinOS 3. Click the Advanced or Standard option. 4. Select the options that you want to configure. 5. In the respective fields, click the option that you want to configure. You can use the Global search option to find the relevant settings or parameters that are available in the Policy Settings. The search result displays the settings in the following order: ● Setting ● Parameter Group ● Parameter sub group ● Parameter 6. Configure the options as required.
BIOS configurations for ThinOS 9.x About this task BIOS configuration settings can be configured to ThinOS 9.x devices using Wyse Management Suite 2.1. You can deploy the BIOS packages using the Groups & Configs page, or using the subnet mapping option. NOTE: This feature is available only with Wyse Management Suite Pro license. Steps 1. Go to the Groups & Configs page, and select a group. The Configuration Control | ThinOS window is displayed. 2. From the Edit Policies drop-down menu, click ThinOS 9.x. 3.
Steps 1. Go to the Groups & Configs page, and select a group. 2. From the Edit Policies drop-down menu, click ThinOS 9.x. The Configuration Control | ThinOS window is displayed. 3. Click Advanced. 4. In the Firmware field, click BIOS Firmware Updates. 5. From the Select the ThinOS BIOS to deploy drop-down menu, select the package. NOTE: You can upload and deploy multiple firmware packages from the remote repository, tenant cloud repository or operator cloud repository.
The WES page is displayed. 4. After configuring the policy settings, click Save and Publish. Configure deployment settings for Windows Embedded devices From Wyse Management Suite 3.1, you can configure the deployment settings for Windows Embedded devices. You can configure the settings to silently deploy configurations to devices. Steps 1. Go to the Groups & Configs page, and select a group. 2. From the Edit Policies drop-down menu, click WES or ThinLinux.. 3. Click Deployment Setting. 4.
Table 5. Remote Connections Chromium Browser (continued) Field name Option Favorites Add favorites, trusted sites and shortcuts Require Server Verification (https:) for all sites in this zone Privacy Do Not Track requests Track prevention Appearance Home Button Favorites Bar Collections Button User Feedback Button Share Button System Hardware Acceleration Edit the Linux policy settings Steps 1. Click Groups & Configs. The Groups & Configs page is displayed. 2.
● Application Update Notification—If you disable this option, the user notification is not displayed when you deploy an application policy. ● Image Update Notification—If you disable this option, the user notification is not displayed when you deploy an image policy. ● Logoff Notification—If you disable this option, the user notification is not displayed for a user to log off from the device.
The following table lists the feature set that you can configure in the Configuration Control | Hybrid Client window. Table 6.
Table 6.
NOTE: If you disable the option, the application deployment may enter an error state since Wyse Management Suite does not send the push notification to Dell Hybrid Clients. 9. To apply the configuration outside of the specified business hours, select the option from the drop-down menu. The available options are: ● Immediately—If you select this option, the configurations are applied immediately after you click Save & Publish.
Edit the Dell Generic Client policy settings Prerequisites ● Create a group with a group token for the devices. ● Register the Dell Generic Client to Wyse Management Suite. Steps 1. Go to the Groups & Configs page, and select a group. 2. From the Edit Policies drop-down menu, click Generic Client. The Configuration Control | Generic Client window is displayed. 3. Click the Advanced option. 4. Select the options that you want to configure. 5.
} ] } } } "updatedAt": "1581466506234" }, "TimeServer": { "value": "10.10.10.10", "updatedAt": "1581466506234" }, "timeZone": { "value": "America/Phoenix", "updatedAt": "1581466506234" }, "TerminalNameCapital": { "value": "yes", "updatedAt": "1581466506234" }, "DeviceNICDefault": { "value": "Wlan", "updatedAt": "1581466506234" }, "AdminMode": { "value": "yes", "updatedAt": "1581466506234" } ● Create a .
} } } For example, { } "devices": { "9EPDL900051": { "parameters": { "TerminalName": { "value" : "Cubical 5 - Floor 3" }, "TerminalNameCapital": { "value": "no" } }, configurations: ["westWingExceptions"] }, "5LGDO600108": { "parameters": { "TerminalName": { "value" : "Cubical 15 - Floor 2" }, "TerminalNameCapital": { "value": "no" } }, configurations: ["westWingExceptions"] } }, "configurations": { "westWingExceptions": { "DeviceNICDefault": { "value": "Wlan" }, "timeZone": { "value": "America/Phoenix" }
6. Click Next. Select the device type configurations to import page is displayed. 7. Click Next. NOTE: Since you can bulk import a device exception file for ThinOS 9.x devices, you cannot configure the options in the page. 8. Enter the .zip file password that was used to zip the .json file. 9. Click Next. A summary of the bulk device exceptions import is displayed. 10. Click Import.
8 Managing devices This section describes how to perform a routine device management task by using the management console. To locate the inventory of the devices, click the Devices tab. You can view a subset of the devices by using various filter criteria, such as groups or subgroups, device type, operating system type, status, subnet, platform, or time zone.
• • • • • • • • • • • • • • • • • • • • • • • • • • • Enrollment Validation Reset the device to factory default settings Change a group assignment on the Devices page Send messages to a device Wake On LAN command View the device details View the display parameters View the virtual NIC details View the BIOS details Manage the device summary View the system information View device events View the installed applications Rename the thin client Enable remote shadow connection Configure remote shadow connection
2. On the top bar, click . 3. Click Dell Client Agent. The Dell Client Agent window is displayed. 4. Click Registration. The default status is displayed as Discovery In Progress. 5. To register manually, click the Cancel button. 6. In the WMS Server field, enter the URL of the Wyse Management Suite server. 7. In the Group Token field, enter your group registration key. The group token is a unique key for registering your devices to groups directly.
3. Restart the device. Register ThinOS devices by using Wyse Device Agent To register the ThinOS devices manually, do the following: Steps 1. From the desktop menu of the thin client, go to System Setup > Central Configuration. The Central Configuration window is displayed. 2. Click the WDA tab. The WDA service automatically runs after the client boot up process is complete. WMS is selected by default. 3. Select the Enable Wyse Management Suite check box to enable Wyse Management Suite. 4.
NOTE: The group token that is entered in the Group Token field is not displayed in clear text. 5. Enable or disable CA validation that is based on your license type. NOTE: If you disable CA validation, a warning message is displayed. Click Ok to confirm. 6. Click Register. Register Wyse Software Thin Client to Wyse Management Suite by using Wyse Device Agent Prerequisites Create a group to register a device to Wyse Management Suite. Steps 1. Open the Wyse Device Agent application.
Steps 1. Create a wnos.ini file. Enter the following parameter: CCMEnable=yes/no CCMServer=FQDN of WMS Server GroupPrefix=The prefix of the Group Token GroupKey=The Group Key CAVAlidation=yes/no Discover=yes/no For example, to register the ThinOS device to Wyse Management Suite (FQDN of the server is ServerFQDN.domain.com) having with the group token defa-defadefa, and with the CA Validation option enabled, enter the following INI parameter: CCMEnable=yes CCMServer= is ServerFQDN.domain.
Steps 1. Create a wlx.ini file and enter the following parameter: WMSEnable=yes\no WMSServer=https://FQDN of the WMS Server:Port GroupRegistrationKey=GroupToken present in WMS Server CAValidation=True/False For example, to register the ThinLinux version 1.0 device to Wyse Management Suite (FQDN of the server is ServerFQDN.domain.
Table 8. Registering device by using DHCP option tags (continued) Option Tag Description Name—CA Validation You can enable or disable CA validation option if you are registering your devices with Wyse Management Suite on private cloud. By default, the CA validation is enabled in the public cloud. You can disable the CA validation in the public cloud as well.
Table 9. Configuring device by using DNS SRV record (continued) URL/Tag Description To register your devices in Wyse Management Suite public cloud, the device should point to the PNS (MQTT) servers in public cloud. For example, US1—us1-pns.wysemanagementsuite.com EU1—eu1-pns.wysemanagementsuite.com You must enter the MQTT server details when you configure Wyse Device Agent details in the older version of ThinOS and Windows Embedded devices.
○ Pending ○ Non-Compliant ● Online Status ○ Online ○ Offline ○ Unknown ● Others ○ Recently Added 3. From the OS Type drop-down list, select any of the following operating systems: ● Thin Client ○ Linux ○ ThinLinux ○ ThinOS ○ WES ○ Teradici (Private cloud) ○ Wyse Software Thin Client ● Hybrid Client ○ Hybrid Client 4. From the OS Subtype drop-down list, select a subtype for your operating system. 5. From the Platform drop-down list, select a platform. 6.
Lock the devices You can send a command to lock the registered device for a group of devices that are connected to a VDI session. This option is applicable for thin clients running ThinOS operating system. Prerequisites The device should be connected to a VDI connection, and a user must be logged in to the device. Steps 1. Click Devices. The Device page is displayed. 2. Apply the filters to find the preferred device. 3. Select the check box of the device. 4. Click Lock. An Alert window is displayed. 5.
Enrollment Validation When you register a device manually or using DHCP/DNS auto discovery method, the device gets registered to a particular group if the group token is defined. If the group token is not defined, the device gets registered to the unmanaged group. In Wyse Management Suite, the Enrollment Validation option is introduced where the tenant must manually approve before the device is registered to a group.
Change a group assignment on the Devices page You can change the group assignment of a device using the Devices page. Steps 1. Click Devices. The Device page is displayed. 2. Apply the filters to find the preferred device. 3. Select the check box of the device. 4. From the More Actions drop-down menu, click Change Group. The Change Group Assignment window is displayed. 5. From the drop-down menu, select a new group for the device. 6. Click Save.
3. Click any of the displayed devices. The Device Details page is displayed. View the display parameters From Wyse Management Suite 3.1, you can view the display setup of the devices running a Windows Embedded and ThinLinux operating system. You can view the vendor name, model number, serial number, resolution, aspect ratio, mode, alignment, and rotation details of the display setup. Steps 1. Go to the Devices page. 2. Apply the filters to find the preferred device. The preferred device list is displayed.
Figure 8. Network Details - Network Adapters View the BIOS details From Wyse Management Suite 3.1, you can view the BIOS parameter value on the Device Details page. Steps 1. Go to the Devices page. 2. Apply the filters to find the preferred device. The preferred device list is displayed. 3. Click any of the displayed devices. The Device Details page is displayed. You can view the BIOS details in the BIOS settings section of the SystemInfo tab.
View device events You can view and manage information about the system events pertaining to a device. Steps 1. Click Devices. The Device page is displayed. 2. Apply the filters to find the preferred device. The preferred device list is displayed. 3. Click any of the displayed devices. The Device Details page is displayed. 4. On the Device Details page, click Events tab. The events on the device are displayed. View the installed applications Steps 1. Click Devices. The Device page is displayed. 2.
5. Click Send Command. A confirmation message is displayed. Enable remote shadow connection Use this page to enable global and group administrators to access the Windows Embedded Standard, ThinLinux, and ThinOS thin client sessions remotely. This feature is applicable only to private cloud and it is available for both Standard and Pro licenses. Steps 1. On the Devices page, click the device. 2. From the More options drop-down list, select the Remote Shadow (VNC) option.
NOTE: The Shutdown Now option is not enabled for thin clients running on Linux operating system. Tag a device Wyse Management Suite enables you to identify a device or group of devices by using the Tag Device option. Steps 1. Click Devices. The Device page is displayed. 2. Apply the filters to locate the preferred device. The preferred device list is displayed. 3. Select one or more devices. From the More Options drop-down list, click Tag Device. The Set Device Tag window is displayed. 4.
○ Remote Wyse Management Suite repository ● Pull Type—Select either Default or Advanced based on your pull type requirement. ○ When the Default pull type is selected, the following options are displayed: ￭ Compress ￭ OS ￭ BIOS ￭ Recovery–—For ThinLinux 2.x ○ When the Advanced pull type is selected, a drop-down list for selecting the templates is displayed. Select any template which is available by default.
4. Click Request Services List, to view the list of the services running on the thin client. 5. Click Start Monitoring, to access the performance metric console. On the Performance metric console, the following details are displayed: ● Average CPU last minute ● Average memory usage last minute Reimage your Dell Hybrid Client You can send a command to reimage your Dell Hybrid Client. Steps 1. Click Devices. The Device page is displayed. 2. Apply the filters to find the preferred device. 3.
4. From the More Actions drop-down menu, click Pull Configuration UI Package. An Alert window is displayed. 5. Click Send Command. Reset your Dell Hybrid Client to factory settings You can send a command to reset your Dell Hybrid Client to factory settings. Steps 1. Click Devices. The Device page is displayed. 2. Apply the filters to find the preferred device. 3. Select the check box of the device. 4. From the More Actions drop-down menu, click Factory Reset. An Alert window is displayed. 5.
9 Apps and data This section describes how to perform routine device application tasks, operating system imaging, inventory management, and set policies by using the Wyse management console. The repository names are color coded to indicate the status. You can configure the following type of policies using the Apps and Data page: ● Standard application policy—This policy enables you to install a single application package.
Configure thin client application inventory Steps 1. Click the Apps and Data tab. 2. In the left pane, go to App Inventory > Thin Client. Application details are displayed in the Thin Client Inventory window. 3. To add an application to the inventory, place the thin client application files in the \repository\thinClientApps folder. Wyse Management Suite Repository sends metadata for all the files to the Wyse Management Suite server periodically. 4. To edit the application, do the following: a.
12. From the Apply Policy Automatically drop-down list, select any of the following options: ● Do not apply automatically—This option does not apply a policy automatically to the devices. ● Apply the policy to new devices—This option automatically applies the policy to a registered device which belongs to a selected group or to the device that is moved to a selected group. When this option is selected, the policy is applied to all the new devices that are registered to the group.
11. From the Apply Policy Automatically drop-down list, select any of the following options: ● Do not apply automatically—This option does not apply a policy automatically to the devices. ● Apply the policy to new devices—This option automatically applies the policy to a registered device which belongs to a selected group or to the device that is moved to a selected group. When this option is selected, the policy is applied to all the new devices that are registered to the group.
4. Go to Apps & Data > App Policies > Thin Client. 5. Click Add Advanced Policy. Add Advanced App Policy page is displayed. 6. Enter the Policy Name. 7. From the Group drop-down list, select the group. 8. Select the Sub Groups check box to apply the policy to sub groups. 9. From the Task drop-down list, select the task. 10. From the OS Type drop-down list, select the operating system. 11. Select the Filter files based on extensions checkbox to filter the applications. 12.
● On device time zone—Server creates one job for each device time zone and schedules the job to the selected date or time of the device time zone. ● On selected time zone—Server creates one job to run at the date or time of the designated time zone. 24. To create the job, click Preview and schedules are displayed on the next page. 25. You can check the status of the job by going to the Jobs page. Create and deploy advanced application policy to Wyse Software Thin Clients Steps 1.
NOTE: For Windows-based devices, specify the silent installation parameters for .exe files to run the application in the silent mode. For example, VMware-Horizon-Client-4.6.1-6748947.exe /silent /install /norestart. 19. Select the Skip write filter check check box to skip the write filter cycles. This option is applicable for Windows Embedded Standard operating system devices and Wyse Software thin client devices. 20.
in the group immediately or at a scheduled time before the device check-in, you must schedule the policy. After you schedule the policy, the job status displays the count of devices that are already present in the group. NOTE: The job status of the newly added device count that is checked in to Wyse Management Suite is not displayed. 13. Specify the number of minutes the message dialog box should be displayed on the client in the Timeout (1-999 min) box.
16. Specify the number of minutes the message dialog box should be displayed on the client. A message on the client which gives you time to save your work before the installation begins. 17. To enable delay in implementation of the policy, select the Allow delay of policy execution checkbox. If this option is selected, the following drop-down menus are enabled: ● From the Max Hours per Delay drop-down list, select the maximum hours (1–24 hours) you can delay running the policy.
7. From the Task drop-down list, select the task. 8. From the OS Type drop-down list, select the operating system. 9. From the Application drop-down list, select the application. If the application files are available on multiple repositories, then the number of repositories is displayed next to the file name. 10. To deploy this policy to a specific operating system or a platform, select either OS Subtype Filter or Platform Filter. 11.
13. Click Add app and repeat the step to add multiple applications. NOTE: To stop the application policy at first failure, select Enable app dependency. If this option is not selected, failure of an application affects the policy implementation. If the application files are available on multiple repositories, then the number of repositories is displayed next to the file name. 14. To deploy this policy to a specific operating system or a platform, select either OS Subtype Filter or Platform Filter. 15.
Add Windows Embedded Standard operating system and ThinLinux images to repository Prerequisites ● If you are using Wyse Management Suite with cloud deployment, go to Portal Administration > Console Settings > File Repository. Click Download version 3.2.0 to download the WMS_Repo.exe file and install the Wyse Management Suite repository installer. ● If you are using Wyse Management Suite with on-premise deployment, the local repository is installed during Wyse Management Suite installation process. Steps 1.
Add ThinOS package file to repository Steps 1. In the Apps & Data tab, under OS Image Repository, click ThinOS. 2. Click Add Package file. The Add File screen is displayed. 3. To select a file, click Browse and go to the location where your file is located. 4. Enter the description for your file. 5. Click Upload. NOTE: If the application exists in the public repository, the application reference is added to the inventory.
NOTE: The file is added to the repository when you select the check box but it is not assigned to any of the groups or devices. To deploy firmware to a device or a group of devices, go to the respective device or the group configuration page. NOTE: The operator can upload the firmware from operator account and is visible to all the tenants. Tenants cannot delete or modify the files. Add ThinOS 9.x BIOS file to repository Steps 1. In the Apps & Data tab, under OS Image Repository, click ThinOS 9.x. 2.
3. In the Add Hybrid Client Policy page, do the following: a. b. c. d. Enter a Policy Name. From the Group drop-down menu, select a group. From the OS Type drop-down menu, select an OS type. From the OS Subtype Filter drop-down menu, select an OS subtype filter. e. If you want to deploy an image to a specific operating system or platform, select either OS Subtype Filter or Platform Filter. f. From the OS Image drop-down menu, select an image file. g.
NOTE: The file is added to the repository when you select the check box but it is not assigned to any of the groups or devices. To assign the file, go to the respective device configuration page. 6. Click Upload. How to change wallpaper for all devices belonging to marketing group Steps 1. Go to the Apps & Data tab. 2. In the navigation bar on the left pane, select Inventory. 3. Click the Add File button. 4. Browse and select the image that you want to use as a wallpaper. 5. For type, select Wallpaper. 6.
10 Managing rules This section describes how to add and manage the rules in the Wyse Management Suite console. The following filtering options are provided: ● Registration ● Unmanaged Device Auto Assignment ● Alert Notification Figure 9.
NOTE: The notification frequency can be configured for every 4 hours, every 12 hours, daily, or weekly basis to the target device. 5. Enter the number of days until you want to apply the rule in the Apply rule after (1–30 days) box. NOTE: By default, registration of an unmanaged device are unregistered after 30 days. 6. Click Save. Create auto assignment rules for unmanaged devices Steps 1. Click the Rules tab. 2. Select the Unmanaged Device Auto Assignment option. 3. Click the Add Rules tab. 4.
Steps 1. Click the Rules tab. 2. Select the Unmanaged Device Auto Assignment option. 3. Select the rule which you want to move and then move it to the top order. 4. Click Save Rule Order. NOTE: You cannot change the IPV6 Prefix rule order. Add a rule for alert notification Steps 1. Click the Rules tab. 2. Select the Alert Notification option. 3. Click Add Rule. An Add Rule window is displayed. 4. From the Rule drop-down list, select a rule. 5. Enter the Description. 6.
Figure 10. Failed Check-In tab 3. Click Add Rule. The Add Rule window is displayed. Figure 11. Add rule 4. Enter the description for the rule. 5. Select the group from which the devices must be unregistered. 6. In the Apply rule after (1-120 days) field, enter the duration in days after which the device is unregistered from Wyse Management Suite. NOTE: The device is unregistered from Wyse Management Suite only if the device does not check-in for the specified number of days. 7. Click Save.
11 Managing Jobs This section describes how to schedule and manage jobs in the management console. In this page you can see jobs based on the following filtering options: ● Configuration Groups—From the drop-down menu, select the configuration group type. ● Scheduled by—From the drop-down menu, select a scheduler who performs the scheduling activity.
Topics: • • • • • • Sync BIOS admin password Search a scheduled job by using filters Schedule a device command job Schedule the image policy Schedule an application policy Restart a failed job Sync BIOS admin password Steps 1. Click Jobs. The Jobs page is displayed. 2. From the More Actions drop-down menu, select the Sync BIOS Admin Password option. The Sync BIOS Admin Password Job window is displayed. 3. Enter the password. The password must be a minimum of 4 and a maximum of 32 characters. 4.
● Dell Hybrid Client 5. From the Status drop-down menu, select the status of the job. The available options are: ● Scheduled ● Running/In Progress ● Completed ● Canceled ● Failed 6. From the Detail Status drop-down menu, select the status in detail. The available options are: ● 1 or more failed ● 1 or more pending ● 1 or more In progress ● 1 or more canceled ● 1 or more completed 7. From the More Actions drop-down menu, select the Sync BIOS Admin Password option.
Schedule the image policy Image policy is not a recurring job. Each command is specific to a device. Steps 1. On the Jobs page, click the Schedule Image Policy option. The Image Update Job screen is displayed. 2. From the drop-down list, select a policy. 3. Enter the job description. 4. From the drop-down list, select the date or time. 5. Enter/select the following details: ● Effective—Enter the starting and ending date. ● Start between—Enter the starting and ending time.
NOTE: The global administrator, user with a custom role (if job permissions are assigned), or a group administrator for specific group can restart a failed job. NOTE: You can only restart a failed job once, since a new child job is created for the failed one.
12 Managing Events In the Events page, you can view all events and alerts in the management system using the management console. It also provides instructions on viewing an audit of events and alerts for system auditing purposes. A summary of events and alerts is used to obtain an easy-to-read daily summary of what has happened in the system. The Audit window arranges the information into a typical audit log-view.
● ● ● ● ● Registration Configuration Remote Commands Management Compliance View the summary of events The Events and Alerts window displays all the events and alerts that have taken place in the system. Go to Events > Summary. View the audit log The Audit window arranges the information into a typical audit log-view. You can view the timestamp, event type, source, and description of each event in the order of time. Steps 1. Go to Events > Audit. 2.
13 Managing users This section describes how to perform a routine user management task in the management console. The following are the three types of users: ● Administrators—Wyse Management Suite administrator can be assigned the role of a global administrator, group administrator, or viewer. ○ A Global Administrator has access to all the Wyse Management Suite functions. ○ A Group Administrator has access to all assets and functions for specific groups that are assigned to them.
• • • • • • • • • • • • • • • Assign WMS custom roles to imported AD groups Bulk import unassigned administrators or cloud connect users Edit an administrator profile Activate an administrator profile Deactivate an administrator profile Delete an administrator profile Unlock an administrator profile Deactivate an administrator profile Create auto assignment rules for unmanaged devices Add end user Edit an end user Configure end user policy Bulk import end users Deleting end user Edit a user profile Add a
Create a WMS custom role in Wyse Management Suite Using Wyse Management Suite 3.1 or later versions, a global administrator can create a new administrator role and provide granular permissions for different functionalities of Wyse Management Suite. You can create multiple users using the Custom Global Administrator role. Steps 1. Go to the Users tab. 2. Click Administrator(s). 3. Click Add Admin. The New Admin User window is displayed. 4. Enter the email ID and username in the respective fields. 5.
NOTE: If the Assign Roles option is not selected, then the group is added to the Default User Policy group and can be viewed from the Groups page. 5. Click Import Groups. The groups are imported and assigned default roles. 6. Go to the Users tab and click Group Assignment. Figure 15. Group Assignment The imported groups are listed in the Group Assignment tab. 7. Select the group that you want to assign roles and click Edit Permissions. The Roles window is displayed. 8.
Edit an administrator profile Steps 1. Click Users. 2. Click Administrator(s). 3. Click Edit Admin. The Edit Admin User window is displayed. 4. Enter your email ID and user name in the respective fields. NOTE: When you update the login name, you are forced to log out from the console. Log in to the console using the updated account login name. 5.
Steps 1. Click Users. 2. Click Administrator(s). 3. Select the check box of a particular admin or admins which you want to delete. 4. Click Delete Admin(s). An Alert window is displayed. 5. Enter a reason for the deletion to enable the Delete link. 6. Click Delete. Unlock an administrator profile Steps 1. Click Users. 2. Click Administrator(s). 3. Select the administrators that you want to unlock. 4. Click Unlock Admin(s). Deactivate an administrator profile Steps 1. Click Users. 2.
Edit an end user Steps 1. Click the Users tab. 2. Click End Users. 3. Click Edit End Users. 4. Enter your email ID and user name in the respective fields. 5. Click Save. Configure end user policy You can configure and deploy settings to an individual user. The settings are applied to the user account and are applied to the thin client when the user logs in. This option is applicable only to thin clients running the ThinOS 9.x operating system and Dell Hybrid Clients. Steps 1. Click the Users tab. 2.
3. Click Delete. Edit a user profile Steps 1. Click Users. 2. Click Unassigned Admins. 3. Click Edit User. The Edit Admin User window is displayed. 4. Enter your email ID and user name in the respective fields. NOTE: When you update the login name, you are forced to log out from the console. Log in to the console using the updated account login name. 5.
14 Portal administration This section contains a brief overview of your system administration tasks that are required to set up and maintain your system. Figure 16.
Import unassigned users or user groups to public cloud through active directory Steps 1. Download and install the file repository, see Accessing file repository. The repository must be installed by using the company network and must have the access to the AD server to pull the users. 2. Register the repository to public cloud. Once registered, follow the steps mentioned on the UI to import the users to Wyse Management Suite public cloud.
After you assign the roles to the active directory user, they are moved to the Administrators tab on the Users page. NOTE: To close the AD Authentication and One-time Import page during the configuration, click AD LogOut option. NOTE: To log in as a domain user after you import groups, the administrator must import group users using the Unassigned Users tab under Users tab.
NOTE: Tenants can activate/deactivate SSO login by using ADFS. 5. Click Save. 6. After you save the metadata file, click Update Configuration. NOTE: Tenants can log in and log out by using their AD credentials that are configured from their ADFS. You must ensure that the AD users are imported to the Wyse Management Suite server. On the login page, click Sign in and enter your domain credentials. You must provide the email address of your AD user and sign in.
● Wyse Management Suite Repository—Log in to Wyse Management Suite public cloud, go to ,Portal Admin > File Repository and download the Wyse Management Suite repository installer. After the installation, register the Wyse Management Suite repository to Wyse Management Suite Management server by providing the required information. You can enable the Automatic Replication option to replicate files that are added to any of the file repositories to other repositories.
Figure 17. File repository 2. Select a file repository. 3. Click the Subnet Mapping option. 4. Enter subnets or ranges, one value per line. You must use hyphen for range separation. 5. Optionally, clear the Allow devices from subnets not mapped to this file repository to download files from this repository as a fallback method using subnet proximity check box if you want the file repository to be accessed only through the configured subnets or ranges.
● WMS API—Select this check-box to enable Wyse Management Suite API. Enable Wyse Management Suite API Wyse Management Suite server uses a proprietary API to serve request generated from the user interface components. User Interface created with java scripts which uses a rest like API call to get required data in JSON format. The JSON format is request-specific.
Enabling multi-tenant accounts This section allows you to create tenant accounts which can be managed independently of one another. You can manage the organizations independently. Each account must have its own license key and can set up its own set of admin accounts, policies, operating system images, application, rules, alerts, and so on. The high level operator creates these organizations. To enable multi tenant accounts, do the following: 1. 2. 3. 4.
Manage system setup You can change the SMTP details, certificates, MQTT details, and external Wyse Management Suite URL details configured during the installation. From Wyse Management Suite 2.1, the Dynamic Schema Configuration is supported for ThinOS 9.x devices that enables you to update the latest configuration settings without any changes on the server side. In public cloud, the Wyse Management Suite operator can upgrade the 9.x configuration user interface.
Important information Devices with older agents continue to communicate with non-secure port and the devices with new agents such as Windows Embedded device and Dell Hybrid Client powered device can communicate with the secure port. Default selection for preferred MQTT is External MQTT—tcp://:1883. For public cloud, the default selection for preferred MQTT is External MQTT—tcp://:443. Any device registered to Wyse Management Suite public server connects to External MQTT.
10. Click Save. 11. Enter the AD credentials and connect to the active directory. NOTE: After the on-premise installation, you can import the server certificate and configure secure LDAP by updating the certificate in the OOBE screen. Next steps ● After the on-premise installation with a single tenant, go to Portal Administration > Setup to import the public key of the certificate to the trust store. For multi-tenant setup, go to WMS Operator Administration > System Settings > LDAPS.
15 Convert Dell Wyse 5070 devices and Dell Ubuntu Generic Clients to Dell Hybrid Client You can convert the Dell Wyse 5070 devices running Windows 10 IoT Enterprise LTSB, Windows 10 IoT Enterprise LTSC, ThinLinux 2.x, and ThinOS 8.6 to Dell Hybrid Client using Wyse Management Suite Pro 3.1 or later versions. You can also convert the Dell OptiPlex 7070 Ultra systems running Ubuntu 18.04 and Windows 10 to Dell Hybrid Client using Wyse Management Suite Pro 3.1 or later versions.
● Wyse Management Suite manages the device as a Dell Hybrid Client device. Adding Dell Hybrid Client images to repository Steps 1. Copy the Dell Hybrid Client conversion image to the repository location or the operating system images folder using Wyse Management Suite. NOTE: Dell Technologies recommends to copy the image file to the local system and then copy the file to Wyse Management Suite repository location.
● Do not apply automatically—The image policy is not applied automatically to a device registered with Wyse Management Suite. ● Apply the policy to new devices—The image policy is applied to a new device registered with Wyse Management Suite. 9. Click Save. Figure 20. Creating Hybrid Client image policies Scheduling the image policy Steps 1. Go to Jobs and click the Schedule Image Policy tab. The Image Update Job tab is displayed. 2. Select a policy from the drop down menu of the Policy tab. 3.
Convert Dell Generic Client to Dell Hybrid Client Prerequisites ● DCA-Enabler version 1.2 is required to convert Ubuntu 18.04 or 20.04 on Dell Ubuntu Generic device to Dell Hybrid Client. You can download the package from the Drivers and Downloads page atwww.dell.com/support. ● If DCA-Enabler version 1.0 or 1.1 is installed on your device, you must upgrade it to 1.2. To upgrade DCA-Enabler, you must register the device to Wyse Management Suite 3.2 and push the DCA_Enabler_ Package 1.2.
16 Security configurations This section describes the key security features of Wyse Management Suite and provides the procedures that are required to ensure data protection and appropriate access control.
13. Click Close. The created relay trust is listed in the Relay Party Trust console. 14. Log in to the Wyse Management Suite public cloud server. 15. Go to Portal Administration > Active Directory and click Show WMS rules. 16. Copy the content displayed in the WMS Rules window. 17. Go to the ADFS console, right-click the relay trust, and select Edit Clam Issuance Policy. 18. Click Add Rule in the Issuance Transform Rules tab. 19. Click Ok. The Select Rule Template window is displayed. 20.
13. Import the AD domain server certificate into Wyse Management Suite java key store manually to the Wyse Management Suite server setup. To import the certificate, do the following: a. Go to the server where Wyse Management Suite is installed. b. Open Command Prompt and run the command keytool.exe> -importcert -alias -keystore "" -storepass changeit -file "C:\. 14.
17 Teradici device management The Teradici device management section provides the information about managing and discovering the teradici divices. The teradici management console uses SDK’s to support management, configuration for tera devices. This is applicable only for Wyse Management Suite private cloud with pro license type.
2. Accept the certificate warning message. 3. Enter the administrator password (default password is Administrator) and login. 4. Go to, upload > certificate. Select the Cert.pemfile from the default path and click Upload. 5. Go to Configuration > Management. Click the clear management state button to register the device to the new Management Server. 6. Set the manager discovery mode to manual 7.
16. Click OK to save the settings. 17. Go to the client web browser. 18. Go to Configuration > Management, and set the manager discovery mode to Automatic 19. The client is connected to the server which is mentioned in the DHCP server. Creating the DNS SRV record 1. Log in to the DNS server. 2. Right-click the DNS server in the SERVERS pane, and the select DNS Manager from the context menu. 3. In Forward Lookup Zones, right-click the domain, and then select Other New Records from the context menu. 4.
○ CIFS configuration page is displayed. This page is required as we need to configure the shared folder. NOTE: The Configure CIFS User Credentials option is disabled by default. ● When you select Teradici EMSDK as Setup Type while installing Wyse Management Suite private cloud. ○ For CIFS credentials, you can use an existing account or create a new one. ● When you select both Wyse Management Suite and Teradici EMSDK as Setup Type while installing Wyse Management Suite private cloud.
18 Managing license subscription This section enables you to view and manage the management console license subscription and its usage. On ● ● ● ● ● ● the Portal Admin page, you can view the Subscription option.
Export licenses to Wyse Management Suite Private Cloud You can export licenses to Wyse Management Suite Private Cloud from Wyse Management Suite public cloud. Steps 1. Log in to Wyse Management Suite public cloud console. 2. Go to Portal Administration > Accounts > Subscription. 3. Enter the number of thin client seats that must be exported to Wyse Management Suite Private Cloud. 4. Click Export. 5. Copy the generated license key. 6. Log in to Wyse Management Suite Private Cloud console. 7.
Configure license expiry email notifications You can enable license expiration email notifications. An email notification is sent to tenants before the license expires. Steps 1. Log in to Wyse Management Suite private cloud. 2. Go to Portal Administration > Other Settings. 3. Select the Enable License Expiration Notifications on Email check box.
19 Firmware upgrade You can use Wyse Management Suite to upgrade your firmware. Topics: • • Upgrading ThinLinux 1.x to 2.1 and later versions Upgrading ThinOS 8.x to 9.0 Upgrading ThinLinux 1.x to 2.1 and later versions If you want to pull a customized image from TL 2.x before you upgrade, you must prepare the ThinLinux 2,x and then upgrade the ThinLinux 1.x image. Prepare the ThinLinux 2.x image Prerequisites Use Wyse Management Suite version 1.
Results NOTE: ● If you are using Wyse Management Suite 1.3 remote repository, then the xml file is not available in the repository. You must upgrade Wyse Management Suite to 1.4 or later versions to access the file. ● Recovery Pull operation does not preserve the user settings. Upgrade ThinLinux 1.x to 2.x Steps 1. Go to www.dell.com/support. 2. Click Product Support, enter the Service Tag of your thin client, and then press Enter.
Table 12. Firmware images Platform ThinOS firmware image Wyse 3040 Thin Client A10Q_wnos Wyse 5070 Thin Client—Celeron processor X10_wnos Wyse 5070 Thin Client—Pentium processor X10_wnos Wyse 5070 Extended Thin Client—Pentium processor X10_wnos Wyse 5470 Thin Client X10_wnos Wyse 5470 All-in-One Thin Client X10_wnos Add ThinOS 9.x firmware to the repository Steps 1. Log in to Wyse Management Suite. 2. In the Apps & Data tab, under OS Image Repository, click ThinOS 9.x. 3.
The firmware is deployed to the thin client. The conversion process takes 15 s to 20 s, and the thin client restarts automatically. Upgrade ThinOS 9.x to later versions using Wyse Management Suite Prerequisites ● Ensure that you are running ThinOS 9.0.4024 or later versions on your thin client. ● Ensure that you have created a group in Wyse Management Suite with a group token. Use this group token to register the ThinOS 9.x devices. ● Ensure that the thin client is registered to Wyse Management Suite.
20 Remote repository Wyse Management Suite allows you to have local and remote repositories for applications, operating system images and so on. If the user accounts are distributed across geographies, it would be efficient to have a separate local repository for each of the distributed user account so the devices can download images from its local repository. This flexibility is provided with WMS_Repo.exe software. The WMS_Repo.
Figure 22. Register on a public cloud 5. Enter the following details: a. Wyse Management Suite server URL NOTE: Unless you register with Wyse Management Suite version 1.0, you cannot use MQTT Server URL. b. c. d. e. WMS Repository URL (update the URL with the domain name) Wyse Management Suite administrator login username information Wyse Management Suite administrator login password information Repository path information 6. Click Register. 7.
Figure 23. Registration successful 8. The following screen on the Wyse Management Suite portal confirms the successful registration of the remote repository: Figure 24.
9. HTTPS is by default enabled with WMS_Repo.exe, and is installed with the self-signed certificate. To install your own domain-specific certificate, scroll down the registration page to upload the SSL certificates. Figure 25. Certificate upload 10. The server restarts, and the uploaded certificate is displayed.
Figure 26. SSL certificate enabled 11. If the Wyse Management Suite is enabled with self-signed or a private domain certificate, you can upload the certificate on the Wyse Management Suite repository server to validate the Wyse Management Suite CA credentials. Figure 27. Trust store certificates 12. Navigate to the C:\wmsrepo location that you entered during registration, and you can view the folders where all the repository files are saved and managed.
Manage Wyse Management Suite repository service Wyse Management Suite repository is displayed as Dell WMS Repository: Tomcat Service in the Windows Local Services window and is configured to start automatically when the server restarts. Proxy support for Wyse Management Suite remote repositories From Wyse Management Suite 3.2, remote repositories support HTTPS and SOCKS5 proxy for all HTTPS and MQTT communications to Wyse Management Suite.
} return "DIRECT"; You can also configure the proxy settings using group policies. NOTE: Proxy settings are read when the repository service starts. If you make any changes to the proxy settings later, you must restart the repository service. NOTE: Host name resolution is not set if SOCKS4 proxy is used. You must update the hosts file present in C: \Windows\System32\drivers\etc to resolve the public cloud URL/hostname on the server where Wyse Management Suite repository is installed.
21 Proxy support for Windows Embedded Standard WDA and Dell Hybrid Client DCA Windows Embedded Standard WDA supports HTTPS proxy, and Dell Hybrid Client DCA supports HTTPs and SOCKS5 proxy for all HTTP and secure MQTT communications with Wyse Management Suite public server. Only system-wide proxies are supported as WDA and DCA run as a service. Proxies with AD authentication or no authentication are supported. PAC script that is configured using DHCP option tag 252 is supported.
The following is a sample PAC file (WPAD.dat) content: function FindProxyForURL(url, host) { if (shExpMatch(host, "*wysemanagementsuite.com*")) { return "SOCKS 100.xxx.xxx.xxx:1080"; } return "DIRECT"; } The following are the limitations: ● Only Secure MQTT communication supports proxy. ● MQTT port 1833 does not support proxy.
22 Troubleshooting your device You can view and manage the troubleshooting information using the Devices page. Steps 1. On the Device Details page, click Troubleshooting tab. 2. Click Request Screen Shot. You can capture the screenshot of the thin client with or without the client permission. If you select the Require User Acceptance check box, then a message is displayed on the client. This option is applicable only for Windows Embedded Standard, Linux, and ThinLinux devices. 3.
Device fails to register to Wyse Management Suite when WinHTTP proxy is configured WDA is a WinHTTP Client and fetches WinHTTP proxy information from the local system. If you have configured WinHTTP Proxy and the device fails to contact the Wyse Management Suite server, do the following to enable the Proxy Information available at the system level: ● Case 1—When the device is added to a domain, enable IE-Proxy Configurations for each user using the Group Policy from the domain.
6. Clear the Password field, and enter the password again. 7. Click Change Password. NOTE: Do not click the Export WiFi Profiles button again. 8. Close the Wireless Profile Password Editor window. 9. Log in to Wyse Management Suite. 10. Go to Apps & Data > File Repository > Inventory. 11. Click Add File. 12. Browse to the xml file. 13. From the Type drop-down list, select Windows Wireless Profile. 14. Enter the description. 15.
23 Frequently asked questions Topics: • • • • • • • • What takes precedence between Wyse Management Suite and ThinOS UI when conflicting settings are enforced? How do I use Wyse Management Suite file repository? How do I import users from a .
Certificate Authority under Events page. All the operations, such as, Apps and Data, Image Pull/Push is not successful. ● When CA Validation from Wyse Management Suite server is disabled, then the communication from server and client happens in a secure channel without Certificate Signature validation. e. Add a note in the provided box. f. Click Save Settings . How do I import users from a .csv file? Steps 1. Click Users. The Users page is displayed. 2. Select the Unassigned Admins option. 3.
● To create the 166 MQTT server URL option tag, do the following: a. Enter the following values, and click OK. ○ Name—MQTT ○ Data type—String ○ Code—166 ○ Description—MQTT Server b. Enter the following value, and click OK. String—MQTT FQDN For example, WMSServerName.YourDomain.Com:1883 ● To create the 167 Wyse Management Suite CA Validation server URL option tag, do the following: a. Enter the following values, and click OK. ○ Name—CA Validation ○ Data type—String ○ Code—167 ○ Description—CA Validation b.
● Host offering this service—FQDN of MQTT server 6. Go to DNS > DNS Server Host Name > Forward Lookup Zones > Domain , and right-click the domain. 7. Click Other New Records. 8. Select Text (TXT), click Create Record, and do the following: a. To create Wyse Management Suite Group Token record, enter the following values, and click OK. ● Record name—_WMS_GROUPTOKEN ● Text—WMS Group token b. To create Wyse Management Suite CA validation record, enter the following values, and then click OK.
3. Push the certificate to the target clients or groups of clients using the security policy. Wait for the Configuration Policy Job to complete. 4. Enable CA Validation from local repository of private cloud or from the remote repository of public cloud. 5. Create an image policy and schedule it to the group.
