Dell Wyse Management Suite Version 3.x Deployment 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. © 2020 - 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................................................................................................................. 4 Chapter 2: Hardware requirements................................................................................................5 Chapter 3: Wyse Management Suite deployment architecture....................................................... 6 Chapter 4: Deployment details...........................................................................................
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.
2 Hardware requirements The following table lists the hardware requirements: Table 1. Hardware requirements 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. 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 Wyse Management Suite deployment architecture The following are the Wyse Management Suite installer components to deploy at the work place: ● WMS Web Application—Application Server that hosts Wyse Management Suite. ● Memcached—Used to Cache data for performance and scalability. ● MQTT—Used to push notifications to thin clients. ● MongoDB—No SQL database for performance and scalability. ● MariaDB—Relational database for structured data and normalization. ● EMSDK—SDK to manage Teradici devices. Figure 1.
4 Deployment details This chapter contains the deployment architecture details for Wyse Management Suite. The Wyse Management Suite supports up to 120,000 connected devices. Single server deployment is easier to maintain, however, you have an option to deploy Wyse Management Suite on multiple servers as per your preference. Deployment on a single server to support 50,000 thin client devices The minimum hardware requirement on a single server for 50,000 devices is: Table 2.
Figure 2. Wyse Management Suite on a single server Deployment details to support Teradici devices EMSDK software component must be installed with Wyse Management Suite, to support Teradici devices. EMSDK components are included in WMS.exe installer, however the installation is optional. EMSDK can be installed locally on Wyse Management Suite server or on a separate VM or server.
Figure 3.
Figure 4.
Figure 5. Wyse Management Suite on a single VM with multiple remote EMSDKs Wyse Management Suite on a separate database server This section explains the deployment architecture of Wyse Management Suite on a separate database server. MongoDB and MariaDB may be on the same server or on separate servers. The following diagram depicts the deployment architecture of Wyse Management Suite on a separate database server.
Figure 6.
5 Custom port configurations Wyse Management Suite uses the following port as the default port for the applications that are installed: About this task ● Apache Tomcat: 443 ● MariaDB database: 3306 ● Mongo database: 27017 ● MQTT Broker: 1883 ● Memcached: 11211 ● EMSDK: 5172, 49159—optional and required only to manage Teradici devices It is recommended that you use the default port for one or more of the preceding services.
NOTE: The Memcached port can be changed during Wyse Management Suite installation. Dell recommends not to change the Memcached port detail after installation. Change the MQTT port Steps 1. Stop the Tomcat and MQTT services. 2. Perform the following steps to configure the MQTT broker service: a. Edit the file \wmsmqtt\mqtt.conf in a text editor. b. Note the following entries: # Port to use for the default listener #port 1883 c.
Change the MongoDB database port Steps 1. Stop the Tomcat and MongoDB services. 2. To configure the MongoDB port entry, do the following: a. Edit the file \MongoDB\mongod.cfg in a text editor. b. Update the property in the file with your preferred port number. For example: port=27027. c. Save the file, and start the MongoDB service. Confirm that it is running on the new port. 3. To configure Tomcat, do the following: a. Edit the file \Tomcat-8\webapps\ccm-web\WEB-INF\classes\bootstra
Figure 7. 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 8. Registration successful 8. The following screen on the Wyse Management Suite portal confirms the successful registration of the remote repository: Figure 9.
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 10. Certificate upload 10. The server restarts, and the uploaded certificate is displayed.
Figure 11. 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 12. 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.
6 Upgrade Wyse Management Suite version 2.x to 3.x Prerequisites ● Ensure that there is enough space on the drive where Wyse Management Suite is installed and the local repository is configured. ● If you have installed or configured an antivirus or other monitoring tools on the Wyse Management Suite setup, Dell Technologies recommends that you disable the tools temporarily till the upgrade is complete.
7 Upgrade Wyse Management Suite version 3.x to 3.3 Prerequisites ● Ensure that there is enough space on the drive where Wyse Management Suite is installed and the local repository is configured. ● If you have installed or configured an antivirus or other monitoring tools on the Wyse Management Suite setup, Dell Technologies recommends that you disable the tools temporarily until the upgrade is complete.
Figure 13. Port selection 8. Click Next. 9. Click Launch to open the Wyse Management Suite web console. Upgrade Wyse Management Suite version 3.x to 3.
8 Maintenance This chapter describes how to take a backup of the database. Database backup Stop Tomcat Service before taking a backup of the database. Tomcat Service is identified as “Dell WMS: Tomcat Service” and must be stopped from Local Services. To dump the contents of the MongoDB, run the following command: mongodump --host -u stratus –p --authenticationDatabase admin --db stratus --out ".\wmsmongodump" To dump the contents of the MarioDB, run the following command: mysql
