Dell Wyse Management Suite Version 3.x Quick Start Guide December 2020 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. © 2020 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................................................................................................................. 5 Wyse Management Suite Feature Matrix...................................................................................................................... 5 Chapter 2: Getting started with Wyse Management Suite............................................................ 10 Log in to Wyse Management Suite on public cloud...........................................
Appendix G: Register Dell Hybrid Client manually........................................................................ 58 Appendix H: Registering Windows Embedded Standard device manually......................................60 Appendix I: Register ThinOS 8.x device manually......................................................................... 61 Appendix J: Register ThinOS 9.x device manually........................................................................
1 Introduction 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.
Table 2.
NOTE: *The asterisk indicates that for Dell Hybrid Client, an on-premise repository is required when you are using Wyse Management Suite public cloud environment. The following table provides information about the Wyse thin clients and zero clients management features supported for each subscription. Table 3.
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 Wyse ThinOS 8.
2 Getting started with Wyse Management Suite This section provides information about the general features to help you get started as an administrator and manage thin clients from the Wyse Management Suite software. Topics: • • Log in to Wyse Management Suite on public cloud Prerequisites to deploy Wyse Management Suite on the private cloud Log in to Wyse Management Suite on public cloud To log in to the Wyse Management Suite console, you must have a supported web browser that is installed on your system.
Prerequisites to deploy Wyse Management Suite on the private cloud Table 4. Prerequisites Description 10000 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. The Wyse Management Suite web server has an inbuilt Apache Tomcat web server. Ensure that you do not install Microsoft IIS, Apache Tomcat web servers separately.
3 Installing Wyse Management Suite on private cloud To set up the Wyse Management Suite on a private cloud, the following requirements must be met: ● Obtain and configure all the required hardware and software. You can download the Wyse Management Suite software from downloads.dell.com/wyse/wms. ● Install a supported server operating system on one or more server machines. ● Ensure that the systems are up to date with current Microsoft service packs, patches, and updates.
● Create a New user—Select this option and enter the credentials to create a new user. NOTE: If the Teradici EM SDK option is enabled on the Setup Type page, you can configure the port for the Teradici server on the Configuration page. 8. Select a path to install the software, and the path to install the local tenant file repository, and then click Next. The default path of the destination folder to install the software is C:\Program Files\DELL\WMS. 9. Click Next.
Figure 2. Welcome page 14. Select your preferred license. ● If you select the license type as Standard, and then click Next to proceed with the standard Wyse Management Suite installation. ● If you select the license type as Pro, you must import a valid Wyse Management Suite license. To import the Wyse Management Suite license, enter the requested information to import license if your server has Internet connectivity.
Figure 4. License information To export a license key from the Wyse Management Suite cloud portal, do the following: a. Log in to the Wyse Management Suite cloud portal by using one of the following links: ● US data center—us1.wysemanagementsuite.com/ccm-web ● EU data center—eu1.wysemanagementsuite.com/ccm-web b. Go to Portal Administration > Subscription.
Figure 5. Portal administration c. Enter the number of thin client seats. d. Click Export. NOTE: To export the license, select , WMS 1.1 or WMS 1.0 from the drop-down list. The summary page shows the details of the license after the license is successfully imported. 15. Enter your SMTP server information, and click Save. NOTE: You can skip this screen and make changes later in the console.
Figure 6. Email alert NOTE: You must enter valid SMTP server information to receive email notifications from the Wyse Management Suite. 16. Import your SSL certificate to secure communications with the Wyse Management Suite server. Enter the public, private, and Apache certificate and click the Import button. Importing the certificate takes three minutes to configure and restart Tomcat services.
Figure 8. PKCS-12 17. In the Device page, you can enable Enrollment Validation to enable administrators to control the manual and auto registration of thin clients to a group. Figure 9. Enrollment validation 18. Click Save and then click Next. 19. Click Sign in to WMS. The Dell Management Portal login page is displayed.
Figure 10. Sign in page Figure 11. Dell Management Portal NOTE: Licenses can be upgraded or extended at a later point from the Portal Administration page.
• • • • • Logging in to Wyse Management Suite Functional areas of management console Configuring and managing thin clients Creating policy group and updating configuration Registering new thin client Logging in to Wyse Management Suite To log in to the management console, do the following: 1. If you are using Internet Explorer, disable the Internet Explorer Enhanced Security and the Compatibility View setting 2.
● Settings or parameters that are configured at lower-level groups take precedence over the settings that were configured at the parent or higher-level groups. ● Parameters that are specific to a particular device which can be configured from the Device Details page. These parameters, like lower-level groups, take precedence over the settings configured in the higher-level groups.
e. Click Save. 3. To update or edit a policy group, do the following: a. Click Edit Policies, and select the operating system that the policy is intended to manage. b. Select the policies to be modified, and complete the configuration. c. Click Save and Publish. NOTE: ● For more details on various configuration policies supported by Wyse Management Suite, see Dell Wyse Management Suite Administrator’s Guide at support.dell.com.
Figure 12. Central Configuration 3. Select the Enable Wyse Management Suite check box to enable Wyse Management Suite. 4. Enter the Group Registration Key as configured by your administrator for the desired group. 5. Select the Enable WMS Advanced Settings option, and enter the WMS server or MQTT server details. 6. Enable or disable CA validation based on your license type—public cloud or private cloud.
WMSEnable=yes \ Server= \ CAValidation=no \ Override=yes ● Example for ThinOS 8.4: WDAService=yes \ Priority=CCM CCMEnable=yes \ CCMServer= \ GroupPrefix=< Prefix > \ GroupKey=< Key > \ MQTTServer= \ Override=yes \ CAValidation=no For more information, see the latest Dell Wyse ThinOS INI guide at support.dell.com. NOTE: ● For ThinOS 8.3 (ThinOS Lite 2.3) and later versions, a WDA Service Priority command allows you to specify the management protocol.
Table 5. Registering device by using DHCP option tags (continued) Option Tag Description You must enter the MQTT server details when you configure Wyse Device Agent details in the older version of ThinOS and Windows Embedded devices. MQTT is a component of WMS which is required to notify the thin clients. The URLs—with and without MQTT details—must be added to the allowlist in the Wyse Management Suite public cloud environment. NOTE: You cannot use the MQTT URLs to log in to Wyse Management Suite.
Table 6. Configuring device by using DNS SRV record (continued) URL/Tag Description https:// if you cannot register the ThinOS 9.x device to Wyse Management Suite. Record Name—_WMS_MQTT Record FQDN—_WMS_MQTT._tcp. Record Type—SRV This record directs the device to the Wyse Management Suite Push Notification server (PNS). For a private cloud installation, the device gets directed to the MQTT service on the Wyse Management Suite server. For example, wmsservername.domain.com:1883.
4 Deploying applications to thin clients The standard application policy allows you to install a single application package and requires reboot before and after installing each application. Using the advanced application policy, you can install multiple application packages with only two reboots. The advanced application policy also supports execution of pre and post installation scripts that may be needed to install a particular application. For more information, see Appendix B.
NOTE: ● The app policy is applied, when any device is moved to the defined group or registered directly to the group. ● If you select Apply the policy to devices on check in, the policy is automatically applied to the device at check-in to the Wyse Management Suite server. 6. To allow a delay in execution of the policy, select the Allow delay of policy execution check box.
5 Uninstalling Wyse Management Suite To uninstall Wyse Management Suite, do the following: 1. Double-click the WMS icon. The uninstaller wizard is initiated, and the Wyse Management Suite uninstaller screen is displayed. 2. Click Next. By default, the Remove radio button is selected that uninstalls all the Wyse Management Suite installer components.
6 Troubleshooting Wyse Management Suite This section provides troubleshooting information for Wyse Management Suite. Problems with accessing Wyse Management Suite web console ● Problem: When you attempt to connect to the Wyse Management Suite console, authentication GUI is not displayed and an HTTP Status 404 page is displayed. Workaround: Stop and start the services in the following order: 1. Dell WMS: MariaDB 2. Dell WMS: memcached 3. Dell WMS: MongoDB 4. Dell WMS: MQTT broker service 5.
○ Ensure that the ports 443 and 1883 are open. ○ Check the internet connectivity, and if you can access the Wyse Management web application from the browser. ○ If automatic discover is enabled, check if DHCP or DNS SRV records are configured correctly. Also, check the server URL and the group tokens. ○ Check if you can register the device manually. ○ Check if you are using self-signed or well known certificates. NOTE: By default Wyse Management Suite installs self-signed certificates.
7 Wyse Device Agent The Wyse Device Agent (WDA) is a unified agent for all thin client management solutions. If you install WDA, you can manage thin clients using Wyse Management Suite. The following three types of customer security environments are supported by the Wyse Device Agent: ● Highly secured environments—To mitigate the risk against rouge DHCP or DNS server for new device discovery, administrators must log in to each device individually and configure the Wyse Management Suite server URL.
8 Additional resources For video tutorials about: ● Installing Wyse management suite, see Installation of Wyse Management Suite. ● Automatic configuration of ThinOS clients using Wyse Management Suite On-Premise with DHCP option tags, see Configuring ThinOS devices using Wyse Management Suite.
A Remote database A remote or cloud database (DB) is a database that is built for a virtualized environment, such as hybrid cloud, public cloud, or private cloud. In Wyse Management Suite, you can configure either the Mongo database (MongoDB) or the Maria database (MariaDB) or both databases based on your requirement. Topics: • • Configure Mongo database Configure Maria database Configure Mongo database Mongo database (MongoDB) operates on the Transmission Control Protocol (TCP) port number 27017.
roles:[{role:"userAdminAnyDatabase",db:"admin"}, {role:"dbAdminAnyDatabase",db:"admin"}, {role:"readWriteAnyDatabase",db:"admin"}, {role:"dbOwner",db:"stratus"}] } ) 12. To switch to the stratus database, run the following command: use stratus; 13. To stop the MongoDB services, run the following command: net stop mongoDB 14. Add an authentication permission to the admin DB. Modify the mongod.cfg file to the following: systemLog: destination:file path:c:\data\log\mongod.log storage: dbPath:c:\data\db securit
B Custom installation In custom installation, you can select a database to set up Wyse Management Suite, and you must know the basic technical working knowledge of Wyse Management Suite. Dell recommends custom installation only for advanced users. 1. Select the Setup Type as Custom, and click Next. Figure 13. Setup type The Mongo Database Server page is displayed. 2. Select either Embedded MongoDB or External MongoDB as the Mongo database server.
Figure 14. Embedded Mongo Database Server ● If External MongoDB is selected, then provide user name, password, database server details, and the port details, and click Next. NOTE: The port field populates the default port which can be changed. Figure 15.
The MariaDB Database Server page is displayed. 3. Select either Embedded MariaDB or External MariaDB as the MariaDB database server. ● If Embedded MariaDB is selected, provide user name and password, and click Next. Figure 16. Embedded MariaDB ● If External MariaDB is selected, provide user name, password, database server details and the port details, and click Next. The port field populates the default port which can be changed.
Figure 17. External MariaDB 4. The Port page is displayed which allows you to customize the ports for the following databases: ● ● ● ● ● Apache Tomcat MySQL database Mongo database MQTT v3.
Figure 18. Port selection NOTE: Wyse Management Suite uses the Maria database and Mongo database for the following: Maria database—Relational database for data that requires well-defined structure and normalization Mongo database—No-SQL database for performance and scalability To complete the installation, follow the steps in the section Installing WMS on-premise and initial setup.
C Access Wyse Management Suite file repository File repositories are places where files are stored and organized. Wyse Management Suite has two types of repositories: ● Local Repository—During the Wyse Management Suite private cloud installation, provide the local repository path in the Wyse Management Suite installer. After the installation, go to Portal Admin > File Repository and select the local repository. Click the Edit option to view and edit the repository settings.
Figure 19. Wyse Management Suite Repository Installer NOTE: Do not select TLSv1.1 and later if the WDA version in the Windows Embedded Device is lower than 14.4.0.153_Unified, and if you are using Merlin Imaging agent. The TLSv1.1 and later should not be selected if you are using the import tool to migrate from Wyse Device Manager to Wyse Management Suite. To use Wyse Management Suite repository, do the following: 1. Download the Wyse Management Suite repository from the public cloud console. 2.
13. Add a note in the provided box. 14. Click Save Settings .
D Create and configure DHCP option tags NOTE: For information on customer security environment, see Wyse Device Agent. To create a DHCP option tag, do the following: 1. Open the Server Manager. 2. Go to Tools, and click DHCP option. 3. Go to FQDN > IPv4 and right-click IPv4. Figure 20. DHCP 4. Click Set Predefined Options. The Predefined Options and Values window is displayed. 5. From the Option class drop-down list, select the DHCP Standard Option value.
Figure 21. Predefined Options and Values 6. Click Add. The Option Type window is displayed. Figure 22. Option Type The options must be either added to the server options of the DHCP server or scope options of the DHCP scope. Configuring the DHCP option tags ● To create the 165 Wyse Management Suite server URL option tag, do the following: 1. Enter the following values, and click OK. ○ Name—WMS ○ Data type—String ○ Code—165 ○ Description—WMS_Server 2. Enter the following value, and then click OK.
For example, WMSServerName.YourDomain.Com:443 Figure 23. 165 Wyse Management Suite server URL option tag ● To create the 166 MQTT server URL option tag, do the following: 1. Enter the following values, and click OK. ○ Name—MQTT ○ Data type—String ○ Code—166 ○ Description—MQTT Server 2. Enter the following value, and click OK. String—MQTT FQDN For example, WMSServerName.YourDomain.
Figure 24. 166 Wyse Management Suite server URL option tag ● To create the 167 Wyse Management Suite CA Validation server URL option tag, do the following: 1. Enter the following values, and click OK. ○ Name—CA Validation ○ Data type—String ○ Code—167 ○ Description—CA Validation 2. Enter the following values, and click OK.
Figure 25. 167 Wyse Management Suite server URL option tag ● To create the 199 Wyse Management Suite Group Token server URL option tag, do the following: 1. Enter the following values, and click OK. ○ Name—Group Token ○ Data type—String ○ Code—199 ○ Description—Group Token 2. Enter the following values, and click OK.
Figure 26.
E Create and configure DNS SRV records NOTE: For information on customer security environment, see Wyse Device Agent. To create a DNS SRV record, do the following: 1. Open the Server Manager. 2. Go to Tools, and click DNS option. 3. Go to DNS > DNS Server Host Name > Forward Lookup Zones > Domain > _tcp and right-click the _tcp option. Figure 27. DNS manager 4. Click Other New Records. The Resource Record Type window is displayed. 5.
Figure 28. Resource Record Type a. To create Wyse Management Suite server record, enter the following details and click OK.
Figure 29. _WMS_MGMT service b. To create MQTT server record, enter the following values, and then click ÓK.
Figure 30. _WMS_MQTT service 6. Go to DNS > DNS Server Host Name > Forward Lookup Zones > Domain and right-click the domain. 7. Click Other New Records. 8.
Figure 31. Resource Record Type a. To create Wyse Management Suite Group Token record, enter the following values, and click OK.
Figure 32. _WMS_GROUPTOKEN record name b. To create Wyse Management Suite CA validation record, enter the following values, and then click OK.
Figure 33.
F Creating and deploying standard application policy to thin clients To deploy a standard application policy to thin clients, do the following: 1. In the local repository, go to thinClientApps, and copy the application to the folder. 2. Ensure that the application is registered by going to the Apps & Data tab and selecting Thin Client under App Inventory. NOTE: The App Inventory interface takes approximately two minutes to populate any recently added programs. 3. In App Policies, click Thin Client. 4.
G Register Dell Hybrid Client manually 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. 1. Log in to the hybrid client as a guest user. 2. On the top bar, click the Dell Client Agent icon. Figure 34. DCA icon 3. Click Dell Client Agent. The Dell Client Agent dialog box is displayed. 4. Click Registration.
Figure 35.
H Registering Windows Embedded Standard device manually Windows Embedded Standard devices can be registered manually by launching the WDA UI icon on the taskbar. 1. Select Wyse Management Suite-WMS as the management server. 2. Enter an appropriate tenant and group name. If this field is left blank, devices are registered to an unmanaged group. (Optional) 3. Click Register. Figure 36.
I Register ThinOS 8.x device manually 1. From the desktop menu of the thin client, go to System Setup > Central Configuration. The Central Configuration window is displayed. 2. Enter the Group Registration Key as configured by your administrator for the wanted group. 3. Select the Enable WMS Advanced Settings check box. 4. In the WMS server field, enter the Wyse Management Server URL. 5. Enable or disable CA validation based on your license type. For public cloud, select the Enable CA Validation check box.
J Register ThinOS 9.x device manually 1. From the desktop menu of the thin client, go to System Setup > Central Configuration. The Central Configuration window is displayed. 2. Enter the Group Registration Key as configured by your administrator for the wanted group. 3. Select the Enable WMS Advanced Settings check box. 4. In the WMS server field, enter the Wyse Management Server URL. 5. Enable or disable CA validation based on your license type.
K Registering Linux device manually Linux devices can be registered manually by launching the WDA UI icon from System Settings. 1. Enter the WMS Server details. 2. Enter an appropriate tenant and group name. If this field is left blank, devices are registered to an unmanaged group. (Optional) 3. Click Register. The device is registered to the Wyse Management Suite console. Figure 37.
L Terms and definitions The following table lists the terms that are used in this document and their definitions: Table 7. Terms and definitions Terminology Definition Private cloud Wyse Management Suite server installed on the cloud that is private to your parent data center. WDA Wyse Device Agent which resides in the device and acts as an agent for communication between server and client.
