Dell Wyse Management Suite Version 1.
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. © 2019 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction....................................................................................................................................................4 2 Hardware requirements..................................................................................................................................5 3 Wyse Management Suite deployment architecture........................................................................................ 6 4 Deployment details..........................
1 Introduction Dell Wyse Management Suite is the next generation management solution that lets you centrally configure, monitor, manage, and optimize your Dell Wyse thin clients. The new Suite makes it easier to deploy and manage thin clients with high functionality and performance, and ease of use. It also offers advanced feature options such as cloud versus on-premises deployment, remote management by using a mobile application, BIOS configuration and port lockdown.
2 Hardware requirements The following table lists the hardware requirements: Table 1.
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.
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: • 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.
Change the MQTT port 1 Stop the Tomcat and MQTT services. 2 Perform the following steps to configure the MQTT broker service: a b Edit the file \wmsmqtt\mqtt.conf in a text editor. Note the following entries: # Port to use for the default listener c d e #port 1883 Uncomment the port 1883 entry and change the port number to your preferred port. For example, port 2883. Save the file, and start the MQTT broker service.
a b c 3 Edit the file \MongoDB\mongod.cfg in a text editor. Update the property in the file with your preferred port number. For example: port=27027. Save the file, and start the MongoDB service. Confirm that it is running on the new port. To configure Tomcat, do the following: a b c Edit the file \Tomcat-8\webapps\ccm-web\WEB-INF\classes\bootstrap.properties in a text editor. Update the properties in the file with your preferred port number. For example: mongodb.
Figure 7. Registration details 5 Click Register to start the registration. Select the Register to public WMS Management Portal if you are registering on the public cloud.
Figure 8. Register on a public cloud 6 Enter the following details, and click Register: a Wyse Management Suite server URL NOTE: Unless you register with Wyse Management Suite v1.0, you cannot use MQTT Server URL.
Figure 9. Registration successful 8 The following screen on the Wyse Management Suite portal confirms the successful registration of the remote repository: Figure 10. Registration successful on the portal 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 11. Certificate upload 10 The server restarts, and the uploaded certificate is displayed.
Figure 12. 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 13. 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.
Figure 14.
6 Upgrade Wyse Management Suite version 1.3 to 1.4 To upgrade Wyse Management Suite from version 1.3 to 1.4, do the following: 1 Double-click the Wyse Management Suite 1.4 installer package. 2 On the Welcome screen, read the license agreement and click Next. Figure 15. Welcome screen 3 On the Upgrade page, click Next. 22 Upgrade Wyse Management Suite version 1.3 to 1.
NOTE: • If EM SDK is installed on the server during the previous Wyse Management Suite installation, the Teradici EM SDK components are updated automatically. • If EM SDK is not installed on the device during the previous installation, select the Teradici EM SDK checkbox to install and configure the Teradici EM SDK components. • You can also install and update Teradici EM SDK using the Wyse Management Suite installer. NOTE: For more information, see Dell Wyse Management Suite 1.
Figure 17. Upgrade 4 Click Launch to open the Wyse Management Suite web console. 24 Upgrade Wyse Management Suite version 1.3 to 1.
Figure 18. Launch Upgrade Wyse Management Suite version 1.3 to 1.
7 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: mysq
