Dell Wyse Device Manager 5.7.
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. © 2018 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction....................................................................................................................................................6 Installer Matrix.................................................................................................................................................................... 6 Support matrix..............................................................................................................................................
6 Configuring load balancing........................................................................................................................... 71 Setting up the ARR Proxy Server................................................................................................................................... 71 Installing Internet Information Services—IIS.......................................................................................................... 72 Installing the ARR Module............
Indefinite Preceding during Installation....................................................................................................................111 Load Balancer Issue................................................................................................................................................... 111 Upgrading WDM on Windows 2008 SP2 32 bit.................................................................................................... 111 WDM Upgrade Installation Fails .....
1 Introduction Dell Wyse Device Manager (WDM) is a software that manages all Dell Wyse thin and zero clients.
Windows 2012 + SQL Express 2016 SP1 Yes Yes Yes Yes Yes Yes Windows 2012 + SQL Server 2008 R2 Yes Yes Yes Yes Yes Yes Windows 2012 + SQL Server 2008 Yes Yes Yes Yes Yes Yes Windows 2012 + Yes SQL Server 2012 Yes Yes Yes Yes Yes Windows 2012 + Yes SQL Server 2014 Yes Yes Yes Yes Yes Windows 2012 + Yes SQL Server 2016 Yes Yes Yes Yes Yes Windows Server 2016 Windows 2016 + SQL Express 2016 SP1 Yes Yes Yes Yes Yes Yes Windows 2016 + Yes SQL Server 2012 Yes Yes Ye
Supported thin clients • Microsoft SQL Server 2012 Enterprise Edition for High Availability • Microsoft SQL Server 2016 Express SP1 Wyse ThinOS • Wyse 3010 thin client with ThinOS • Wyse 3020 thin client with ThinOS • Wyse 3040 thin client with ThinOS • Wyse 5010 thin client with ThinOS • Wyse 5040 thin client with ThinOS • Wyse 3030 LT thin client with ThinOS • Wyse 5060 thin client with ThinOS • Wyse 7010 thin client with ThinOS Wyse ThinOS PCoIP • • • • Wyse 5040 AIO thin client wit
• Wyse 7040 thin client with Win10 IoT Wyse Enhanced SUSE Linux Enterprise • Wyse 5010 thin client with Linux • Wyse 5020 thin client with Linux • Wyse 7010 thin client with Linux • Wyse 7020 thin client with Linux ThinOS Lite • Wyse 3010 zero client for Citrix • Wyse 3020 zero client for Citrix • Wyse 5010 zero client for Citrix ThreadX/View zero client • Wyse 5030 zero client • Wyse 7030 zero client • Wyse 5050 AIO zero client with PCoIP ThinLinux Supported EOL Dell Wyse thin client
• Z50S ThinOS Lite • C00X • R00X ThreadX/View zero client • P20 Wyse ThinOS • C10LE • R10L Wyse Enhanced Microsoft Windows Embedded Standard 2009 —Build 641 and later • C90LEW • 5010 • R90LW • R90LEW • V90LEW • X90CW • X90MW • 7010 • Z90SW Localization Support For the WDM Server, localization support is provided on Windows 2008 R2 SP1 Enterprise Edition, Windows 2012 Standard R2, and Windows 2016 Standard R2 for the following languages: • French • German • Spanish • Japa
Related documentation and services Fact sheets containing features of hardware products are available on the Dell Wyse website. Go to http://www.dell.com/wyse and select your hardware product to locate and download the Fact Sheet. To get support for your Wyse product, check your product Service Tag or serial number. • For Dell service tagged products, find knowledge base articles and drivers on the Dell Wyse product pages.
2 Prerequisites This section lists the prerequisites, the hardware, and software requirements that you must complete to prepare your environment to install and configure WDM.
Hardware Requirements The system on which you install WDM should meet or exceed the minimum system requirements and depends on the operating system you install. The actual free space required depends on the number and size of the packages you register, and also on the number of devices you will be managing. Table 3. Server Hardware Requirements for 32–bit OS Category Minimum Requirements Recommended Configuration CPU 2.
WDM Component Protocol and Corresponding Ports Port Function VNC 5800 Remote shadows devices. 5900 Web Service HTTP 80 280 HTTPS 443 8443 Web Agent DHCP Proxy and TFTP Services and PXE Secure Communication with the Web Agent, GUI, and Standard Service. OLE DB 1433 (default) Can be configured Communicate with the WDM during installation Database. HTTP 80 280 DHCP Proxy and TFTP Services Communicates with the Web Agent, GUI, and Standard Service. Communication with the Web Service.
WDM Component Protocol and Corresponding Ports Port Function ThreadX 5.x Manager Service TCP 49159 Communicate with ThreadX 5.x devices. 5172 NOTE: Both the communication ports has to be added to firewall Inbound rules. If required, 49159 port number can be customized. The default port 49159 is customized, this needs to be manually added.
3 Installing Wyse Device Manager WDM consists of the following components: • Database • Management Server • Software Repository • Other Services • Web UI You can install all the components on the same system or you can have a distributed setup where each component is installed on different systems. WDM is available in the following editions: • Enterprise Edition—This edition needs a specific license key and comes packaged with all the features of WDM.
The Welcome screen is displayed. Figure 1. Welcome screen 3 Click NEXT. 4 In license type, select WORKGROUP, and click NEXT.
Figure 2. Workgroup license type NOTE: For the workgroup edition, the license key is provided within the installer and you need not enter any details. The Components screen is displayed.
Figure 3. Components screen 5 Click NEXT. NOTE: All the components are selected by default and you cannot de-select any component. The Configure Database screen is displayed.
Figure 4. Configure Database screen 6 On the Configure Database screen, select one of the following options: • Install New Database Server (Microsoft SQL Express 2016 SP1)—Select this option if you do not have any supported version of Microsoft SQL Server installed on the system and proceed to step 8. • 7 Use Existing Database Server (SQL Server Express or full)—Select this option if you have already installed a supported version of Microsoft SQL Server on the system.
Figure 5. Install New Database Server option • • SQL Server Authentication—This option is selected by default. To configure SQL server authentication, do the following: 1 Enter the WDM database credentials. 2 Enter the new database credentials. You can enter the instance name and the database name under the new database server details. The default instance name and database name is displayed as RapportDB. Windows Authentication—Enter the new database server details.
Figure 6. Use Existing Database Server option • SQL Server Authentication—This option is selected by default. To configure SQL server authentication, do the following: 1 Select either the create new user option or Use the existing user option, and then enter the WDM database credentials. 2 Enter the existing database server details such as server hostname, instance name, database name, port number, SQL administrator name and password. The default port number is 1433.
Figure 7. Configure Software Repository Server screen 10 On the Configure Software Repository Server screen, you can choose one of the following options: • CONFIGURE NEW REPOSITORY SERVER—Select this option if you want the installer to configure a new repository server. To configure a new repository server: – Select the protocol and settings to distribute software to the managed devices. HTTPS is selected by default. You can also select FTP for ThreadX 4.x and CIFS for ThreadX 5.x.
Figure 8. Other Services screen NOTE: DHCP Proxy is selected by default. 13 Enter the installation path, and click NEXT.
Figure 9. Destination screen 14 Select and import the certificate to start the installation.
Figure 10. Certificate screen NOTE: If you click NEXT without selecting a certificate, the installer installs a self signed certificate. The communications are encrypted, but the system is not completely secure. The certificate must be in the format of .pfx file. The installation progress is displayed on the screen. After the installation is complete, you are prompted to restart your system.
Figure 11. Installation summary screen 15 Restart the system for the changes to take effect. Next step After installation, ensure that the following checklists are met: • WDM is installed in \Inetpub\ftproot path and the Rapport folder is created. • WyseDeviceManager 5.7.3 WebUI icon is created on the desktop. • In IIS , HApi Application is created under Rapport HTTP server folder. • In IIS , MyWDM Application is created under Rapport HTTP server folder.
Figure 12. Welcome screen 3 Click NEXT. 4 In the license type, select ENTERPRISE.
Figure 13. Enterprise license type a b If you have the WDM license key, select the I have WDM Enterprise License Key option, and enter the license key in the space provided. If you do not have the license key, select the 30–days Enterprise Evaluation option. The license key is entered by default. However, after the 30 days evaluation period, you must obtain the license key and add it to WDM. For more information on adding the license key, see the Dell Wyse Device Manager Administrator’s Guide.
Figure 14. Components screen You can install all the components on the same system or each component on a different system. NOTE: If you are installing the components separately on different systems, make sure you install the Database first. If you do not install the database, you cannot install the remaining components.
Figure 15. Configure Database screen • Install New Database Server (Microsoft SQL Express 2016 SP1)—Select this option if you do not have any supported version of Microsoft SQL Server installed on the system and proceed to step 8. • 8 Use Existing Database Server (SQL Server Express or full)—Select this option if you have already installed a supported version of Microsoft SQL Server on the system.
Figure 16. Install New Database Server option • SQL Server Authentication—This option is selected by default. To configure SQL server authentication, do the following: 1 Enter the WDM database credentials. 2 Enter the new database credentials. You can enter the instance name and the database name under the new database server details. The default instance name and database name is displayed as RapportDB.
Figure 17. Use Existing Database Server option • • SQL Server Authentication—This option is selected by default. To configure SQL server authentication, do the following: 1 Select either the create new user option or Use the existing user option, and then enter the WDM database credentials. 2 Enter the existing database server details such as server hostname, instance name, database name, port number, SQL administrator name and password.
Figure 18. Configure Software Repository Server screen 11 On the Configure Software Repository Server screen, you can choose one of the following options: • CONFIGURE NEW REPOSITORY SERVER—Select this option if you want the installer to configure a new repository server. To configure a new repository server: – Select the protocol and settings to distribute software to the managed devices. HTTPS is selected by default. You can also select FTP for ThreadX 4.x and CIFS for ThreadX 5.x.
Figure 19. CONFIGURE NEW REPOSITORY SERVER option • USE EXISTING REPOSITORY SERVER—Select this option if you want the installer use an existing repository server. To configure the existing repository server: – Select the protocol and settings to distribute software to the managed devices. HTTPS is selected by default. You can also select FTP for ThreadX 4.x and CIFS for ThreadX 5.x. – Select the authentication type. Windows is selected by default. – Enter the server credentials.
Figure 20. USE EXISTING REPOSITORY SERVER option 12 Click NEXT. 13 Select the services you want to install, and click NEXT.
Figure 21. Other Services screen NOTE: DHCP Proxy is selected by default. 14 Enter the installation path, and click NEXT.
Figure 22. Destination screen 15 Select and import the certificate to start the installation.
Figure 23. Certificate screen NOTE: If you click the NEXT without selecting a certificate, the installer installs a self signed certificate. The communications are encrypted, but the system is not completely secure. The certificate must be in the format of .pfx file. The installation progress is displayed on the screen. After the installation is complete, you are prompted to restart your system.
Figure 24. Installation summary screen 16 Restart the system for the changes to take effect. Installing WDM on a cloud environment About this task To install the WDM on a cloud environment, you must install the enterprise edition. Steps 1 Extract the contents of the WDM installer on the system where you want to install WDM. 2 Navigate to the folder where you have extracted the installer, and run Setup.exe. If the server does not have .Net framework, then the .Net framework is installed automatically.
Figure 25. Welcome screen 3 Click NEXT. 4 In the license type, select ENTERPRISE.
Figure 26. Enterprise license type a b If you have the WDM license key, select the I have WDM Enterprise License Key option, and enter the license key in the space provided. If you do not have the license key, select the 30–days Enterprise Evaluation option. The license key is entered by default. However, after the 30 days evaluation period, you must obtain the license key and add it to WDM. For more information on adding the license key, see the Dell Wyse Device Manager Administrator’s Guide.
Figure 27. Components screen You can install all the components on the same system or each component on a different system. NOTE: If you are installing the components separately on different systems, make sure you install the Database first. If you do not install the database, you cannot install the remaining components.
Figure 28. Configure Database screen • Install New Database Server (Microsoft SQL Express 2016 SP1)—Select this option if you do not have any supported version of Microsoft SQL Server installed on the system and proceed to step 8. • 8 Use Existing Database Server (SQL Server Express or full)—Select this option if you have already installed a supported version of Microsoft SQL Server on the system.
Figure 29. Install New Database Server option • SQL Server Authentication—This option is selected by default. To configure SQL server authentication, do the following: 1 Enter the WDM database credentials. 2 Enter the new database credentials. You can enter the instance name and the database name under the new database server details. The default instance name and database name is displayed as RapportDB.
Figure 30. Use Existing Database Server option • • SQL Server Authentication—This option is selected by default. To configure SQL server authentication, do the following: 1 Select either the create new user option or Use the existing user option, and then enter the WDM database credentials. 2 Enter the existing database server details such as server hostname, instance name, database name, port number, SQL administrator name and password.
Figure 31. Configure Software Repository Server screen 11 On the Configure Software Repository Server screen, you can choose one of the following options: • CONFIGURE NEW REPOSITORY SERVER—Select this option if you want the installer to configure a new repository server. To configure a new repository server: – Select the protocol and settings to distribute software to the managed devices. HTTPS is selected by default. You can also select FTP for ThreadX 4.x and CIFS for ThreadX 5.x.
Figure 32. CONFIGURE NEW REPOSITORY SERVER option • USE EXISTING REPOSITORY SERVER—Select this option if you want the installer use an existing repository server. To configure the existing repository server: – Select the protocol and settings to distribute software to the managed devices. HTTPS is selected by default. You can also select FTP for ThreadX 4.x and CIFS for ThreadX 5.x. – Select the authentication type. Windows is selected by default. – Enter the server credentials.
Figure 33. USE EXISTING REPOSITORY SERVER option 12 Click NEXT. 13 Select the services you want to install, and click NEXT.
Figure 34. Other Services screen NOTE: DHCP Proxy is selected by default. 14 Enter the installation path, and click NEXT.
Figure 35. Destination screen 15 Select and import the certificate to start the installation.
Figure 36. Certificate screen NOTE: If you click the NEXT without selecting a certificate, the installer installs a self signed certificate. The communications are encrypted, but the system is not completely secure. The certificate must be in the format of .pfx file. The installation progress is displayed on the screen. After the installation is complete, you are prompted to restart your system.
Figure 37. Installation summary screen 16 Restart the system for the changes to take effect. Installing WDM in a Distributed Setup You can split the WDM components and install them on different systems. This setup is called a distributed setup of WDM.
Installing WDM Database Prerequisite Before you install the WDM database on a system or virtual machine (VM), ensure that you have installed the supported version of Microsoft SQL Server. If you do not have SQL Server on the system, you can choose to install Microsoft SQL Express 2016 SP1 which is packaged with the WDM installer. NOTE: If you are installing the WDM database on an existing SQL Server database, ensure that port 1433 is available on the system.
• Windows Authentication—Enter the existing database server details such as server hostname, instance name, database name, port number, SQL administrator name, and password. NOTE: The default port number is 1433. Dell recommends that you manually enter the port number since it is dynamic. You can add five-digit custom port for TCP/UDP in the range of 49152-65535. 10 Click NEXT. 11 Enter the installation path, and click NEXT. The Installation Summary screen is displayed. 12 Click NEXT.
NOTE: If you click the NEXT without selecting a certificate, the installer installs a self signed certificate. The communications are encrypted, but the system is not secure. The certificate must be in the format of .pfx file. The installation progress is displayed on the screen. After the installation is complete, you are prompted to restart your system. 12 Restart the system for the changes to take effect. NOTE: In distributed environment, Web UI can be installed on a multiple console.
Upgrading WDM Prerequistes The current version of WDM supports an upgrade from WDM version 5.7.2/5.7.2 hot fix release. You cannot upgrade from any other version. If you are running an older version of WDM, you must first upgrade to version 5.7.2/5.7.2 hot fix release and then upgrade to the latest version. NOTE: After you upgrade to WDM version 5.7.3, you must upgrade all devices with the latest Agents packages available to make sure your devices can be managed using WDM.
In order to install the certificate, two steps need to be followed: • Install the certificate on Domain Controller server. • Install the certificate on WDM server. Installing the Certificate on the Domain Controller Server Use the following guidelines: 1 Go to the Server Manager. 2 In the tree pane select Roles->Add Roles. 3 In Add Roles wizard, select Server Roles from the tree pane. 4 In select Server Role window, check Active Directory Certificate Service from Roles. 5 Click Next->Next.
5 Now the installation of certificate in WDM server is done. 6 After the installation of certificate, browse through Server ->Web Sites->Rapport HTTP Server and click Bindings... on right most pane to open Site Bindings window. 7 In Site Bindings window, click Add to Add Site Binding 8 In Add Site Binding, select the recently created certificate from SSL Certificate combo box and click OK button.
• and then either check or uncheck “Allow administrator interaction when the private key is accessed by the CA” check box • And click Next button to open Configure CA Name window. NOTE: Common name of the certificate should match with WDM server's computer name. 23 In CA Name window, provide the values for Common name for this CA and Distinguished name suffix fields and click Next to open Validity Period window.
4 Uninstalling standalone installation of WDM About this task If you have a standalone installation of WDM, where all the components are installed on the same system, then you can follow the steps given below to uninstall WDM. Steps 1 Go to Start > Control Panel. 2 Click Programs > Uninstall a program. 3 Select WDM 5.7.3 from the program list, and click Uninstall. The Uninstallation screen is displayed. 4 Click Next on the Welcome screen. 5 Enter the credentials to access the WDM database.
8 Repeat steps 2 to 5. 9 Enter the credentials to access the WDM database. You need to specify the SQL Login ID and password for SQL Server or SQL Express depending on where you have installed the WDM database. If you specify the wrong credentials, the program displays the following message: Unable to connect to database. Make sure you enter the correct credentials. 10 Click Next to begin the uninstallation process. 11 After the database is uninstalled, restart the system when prompted.
5 Configuring High Availability database clustering for WDM High-availability clusters (also known as HA clusters or failover clusters) are groups of computers that support server applications that can be reliably utilized with a minimum down-time. They operate by harnessing redundant computers in groups or clusters that provide continued service when system components fail.
• Implementing a Node and File Share Majority Quorum • Installing .
9 To launch the Advanced Settings window, press the Alt button to access the Advanced menu in the Network Connections screen and select the Advanced Settings option. 10 In the Network Connections screen, select Public, right click and select Properties. 11 In the Advanced Settings window, select IPv4 and click Properties. 12 Enter the IP address, Subnet mask, Default gateway and the Preferred DNS server. Click OK. 13 Repeat steps 10 and 11 for the Private network.
4 Enter the name of the secondary node and click Add. 5 After the servers are added, click Next to continue. You are prompted to validate your cluster. Select No since your cluster is validated. 6 Select the second option on the screen and click Next to continue. 7 Provide a name for the cluster and an IP for administering the cluster. The name you provide is to administer the cluster. This should not be the same as the name of the SQL Cluster resource that you will create later.
4 Click Add Required Role Services. The option .NET Extensibility is selected by default. Click Next to continue. 5 Confirm the installation selections and click Install. 6 After the installation of the selected components is complete, the installation results are displayed. 7 Click Close to complete the .NET Framework installation.
5 Accept the license terms and click Next. 6 Check the product updates and click Next. 7 Make sure that the Setup Support Rules screen does not display any failures or errors. You can ignore the warnings and click Next. 8 Select the SQL Server Feature Installation option in the Setup Role screen and click Next. 9 Select all the options under Instance Features → Database Engine Services , and Shared Features → Client Tools Connectivity on the Feature Selection screen. Click Next.
6 Run the following script on the database: Use RapportDB GO Update Install set ServerName='NEWCLUSTER01' where Module='Rapport4DB' 7 When you install the WDM components without the database, make sure you provide the name of the SQL Database Cluster name in the Server IP Address field. 8 Create the same directory structure pointing to the database location both in the primary as well as the secondary node. For example, if the database is present in C:\Program Files\WYSE\WDM\Database in the primary nod
4 • Database Server – Specify the hostname of the database cluster. For example, WDMCLUSTER. • Database User Name – Specify rapport as the database user. • Database Password – Specify the password of the rapport user. Click Configure. The connection details are displayed on the bottom pane of the utility. Adding a License on WDM About this task WDM needs a license to function. The licensing code is generated based on the database.
6 Configuring load balancing When you use WDM to manage thin client devices in a very large enterprise environment, a single WDM Management Server cannot scale up to manage the large number of devices. There could be problems or delays in client check-ins, schedule execution, or real-time command execution. Load balancing helps resolve these problems to a great extent.
• The entire setup should be on Windows 2008 Server R2 or higher. • Install all the components of WDM on one server. • Install only the WDM Management Server and ThreadX 4.x service on another server. NOTE: You can set up the ARR Proxy Server and the WDM Management Servers across different subnets in the same doamin. About this task Setting up the ARR Proxy Server consists of the following steps: Steps 1 Installing IIS. 2 Installing the ARR Module.
4 Select the following options: Option Sub-options Common HTTP Features • Static Content • Default Document • HTTP Errors • Directory Browsing • HTTP Logging • Request Monitor • Logging Tools • Tracing Health and Diagnostics Management Tools 5 Click Next to view the summary. 6 Click Install to install IIS. Select all the sub-options. Installing the ARR Module You must install the Application Request Routing version 3.0 on the system you have identified to be the ARR Proxy Server.
Configuring the Application Pool Process for ARR All HTTP requests and responses for the content sites go through Application Request Routing. For this to function correctly you must make sure that the worker process of the Default Web Site on ARR is always running. About this task To configure the application pool process: Steps 1 Log in to the ARR Proxy Server, and launch the IIS manager. 2 Select Application Pools under the root node.
Creating a Server Farm of WDM Management Servers About this task To create and define a server farm: Steps 1 Log in to the ARR Proxy Server system and launch the IIS Manager. 2 Select Server Farms under the root node. This option is available only after you install the ARR Proxy module. 3 Right-click and select Create Server Farm from the menu. The Create Server Farm screen is displayed. 4 Enter a name for the server farm. For example, WDMServerFarm. Click Next to add the WDM Management servers.
5 Type the host name of the WDM Server and click Add. You can add all the servers where you have installed the WDM Management Server. 6 Click Finish to add all the servers to the farm. After the servers are added and the server farm is created you are prompted with a message to rewrite the routing rules for all requests to automatically come to the server farm. 7 Click Yes so that IIS manager can create a URL rewrite rule to route all incoming requests to this server farm.
9 Double click on Routing Rules and select the Enable SSL offloading option if you want the communication between the ARR Proxy Servers and the WDM Management Servers to be in plain text. You also need to add both the HTTP and HTTPS ports to the Default Web Site Bindings on the individual WDM Management Server systems.
b In the Edit Inbound Rule page, set the Pattern to *hserver.dll*. This step ensures that the ARR Proxy Server forwards only the URL requests meant for the WDM Management Server to the Server Farm. The Server Farm properties are now configured. Configuring Request Filtering About this task To configure request filtering: Steps 1 Log in to the ARR Proxy Server and launch the IIS Manager. 2 Select Default Web Site under Sites and on the right-hand pane double click on Request Filtering.
4 Click Save to save the settings. The ARR Proxy Server is now recorded in the WDM database, and this completes the Load Balancing setup. Installing WDM Components The load balancing setup needs multiple installations of WDM Management Servers. However, you must make sure that one of the systems in this setup has a complete installation of WDM. You can then install only the Management Server and the ThreadX Service on the other systems.
The TTL field is displayed only if you have selected Advanced View in the View menu of the DNS Server. The load balancing is now configured for ThreadX devices and you can use the your WDM Management Servers to manage a large number of ThreadX devices. Configuring load balancing for ThreadX 5.x devices When WDM is used to manage ThreadX 5.
Figure 41. Host Record 3 The third record required is a Txt record. The txt record is the thumbprint of the SSL certificate in use by the management console. Complete the following steps to create A record for Host as well as Txt record: 1 Click the domain node (delldemo.int) and select the Other New Records and then select Host (A or AAAA), the name is the A record of the management console. Figure 42.
2 Click on the domain node (delldemo.int) and select the Other New Records and then select Text (TXT), to create the text field which has the thumbprint of the certificate. Figure 43. New Resource Record The Sha256 thumbprint can be obtained using Firefox browser. To obtain the thumbprint when Wyse Device Manager (WDM) is installed with Teradici 5x: 1 You must open the Firefox browser from the device where Teradici 5.x component is installed.
Figure 45. Advanced 4 Click View Certificates to open the Certificate Manager window. 5 Select the Authorities tab on the Certificate Manager window and click Import.
Figure 46. Certificate Manager 6 In the file browser dialog navigate to the location where WDM is installed, For example: \Wyse\WDM\TeraDici, where the root path can be C:\Program Files (x86) based on the operating system and installation path. NOTE: In some cases if the Teradici components are installed in a custom manner or manually configured, the above steps must be followed on the same device, and the standard installer path may not be applicable.
Figure 47. Downloading Certificate 9 Copy the sha256 fingerprint value. Click Close and cancel all the firefox windows.
Figure 48. Certificate Viewer NOTE: In the Text field the text must be prefixed with pcoip-bootstrap-cert= to the sha256 fingerprint which is obtained already.
Figure 49. tcmc2 Properties 10 The fourth and final record is a reverse PTR record for the management host. Figure 50. PTR Record 11 The zone must match the subnet that the host is in, and the record is the IP address assigned to the Teradici Device Proxy (HAProxy). Installing and configuring HAProxy HAProxy which is the load balancer for ThreadX 5x devices is configured on Ubuntu Linux version 16.04.1 with HAproxy version 1.6.
3 Execute the following commands to configure HAProxy: • Back up original configuration before editing, with the command sudo cp /etc/haproxy/haproxy.cfg /etc/haproxy/ haproxy.cfg.original • Now edit the configuration file with the command sudo nano /etc/haproxy/haproxy.
default_backend servers backend servers #Add your multiple back end windows machine IP with 5172 as port # maxconn represents number of connection- replace 10 with limit #(below 20000) # server1 server2 are just names and not keywords server server1 10.150.99.107:5172 maxconn 10 server server2 10.150.99.107:5172 maxconn 10 4 Now validate the HAProxy configuration file with the command sudo haproxy –f /etc/haproxy/haproxy.cfg –c.
c 90 Select emsdk.keystore file from the folder \Teradici\EMSDK\config on the machine where ThreadX 5X component is selected while installing WDM.
6 Provide the required inputs, and click Next. 7 Click Finish. 8 The install log will be created at \Teradici\Detail_TeradiciDeviceProxy.log. 9 Go to Start > Administrative tools > Services. 10 Verify that the ThreadX 5x Manager Windows Service is installed and running. Adding Teradici Device Proxy Servers to WDM Tasks 1 Open WDM Web UI and log in as administrator. 2 Go to System > Console and enable Teradici Device Proxy servers option. 3 Click Add Server.
5 Click the check mark on the right hand side of the text boxes to save the values. Adding HAProxy to WDM Follow the steps provided to add HAProxy to WDM: 1 Log in to WDM Web UI as administrator. 2 Go to console page and enable HAProxy Server option. 3 Click Add Server. 4 Add the HAProxy Server name in the server name field and give port number as 5172.
5 Click Add Server again. 6 Click on the check mark on the right hand side of the text boxes to save the values. Restarting Threadx API Follow the steps provided to restart Threadx API: 1 Log in to the server where WDM ThreadX 5x component is installed. 2 Click the Start menu > Administrative tools > Internet information service (IIS) manager.. 3 Expand the root node (host name of the server) and select Application pools > ASP .Net v4.0. 4 Right click ASP .Net v4.0 and select Stop.
Figure 51. Status on Dashboard Figure 52.
Figure 53.
7 Configuring high availability of web UI service When you have a single instance of web UI service and if that server goes down, then WDM cannot be managed from web UI. So a high availability (HA) of web UI service is recommended. You can use load balancer proxy like ARR reverse proxy where the configuration has to be done to support high availability of web UI service. Figure 54.
Steps 1 Install IIS. 2 Install ARR module. 3 Change application pool process model for Application Request Routing. 4 Create a Server farm of web UI servers. 5 Configure SSL on the proxy server. 6 Configure server farm properties for Application Request Routing. Installing Internet Information Services—IIS 1 Log in as an administrator. 2 Go to Control Panel > Programs and Features > Turn Windows features on or off. 3 Select the options as shown in the following screenshot. Figure 55.
Installing the ARR module You must install the Application Request Routing version 3.0 on the system you have identified to be the ARR Proxy Server. The installer is available on the Microsoft download site at support.microsoft.com. Download the ARRv3_0.exe file and install it. Changing application pool process model for Application Request Routing About this task All HTTP requests and responses for the content sites go through Application Request Routing.
Figure 57. Advanced settings 6 Click OK to save the changes. Create a Server Farm of web UI servers 1 Start the IIS Manager. 2 Right-click Server Farms, and select Create Server Farm.
Figure 58. Server Farms 3 Enter a name for the server farm. Figure 59. Create Server Farm 4 Click Next.
5 On the Add Server page, add the application servers (WebUI servers). Figure 60. Add Server 6 Click Finish to create the server farm with the entered application servers as the server farm members. The Rewrite Rules window is displayed.
Figure 61. Rewrite Rules 7 Click Yes so that IIS manager can create a URL rewrite rule to route all incoming requests to this server farm. Configuring SSL on the proxy server To configure SSL on ARR Proxy, create a domain certificate for the proxy server. Assign this certificate to the https binding for the web site and enable SSL. Figure 62.
The communication between the ARR Proxy Server and the WDM Management Servers must be on HTTPS protocol. Hence, you must disable the SSL off-loading feature and configure SSL on the individual WDM Management Servers. If you use a self-signed certificate setting up SSL on the WDM Management Server, then import this certificate to the Trusted Root Certificate Authorities store for a local computer on the ARR Proxy Server by following the steps available on support.microsoft.com.
d e f 5 Set the Acceptable Status codes to 200–399. If the Hhealth URL returns a status code that does not match with the value in the Acceptable Status Codes, then ARR marks that server as unhealthy. Set the text value Server Healthy in the Response Match field. The text in Response Match is verified against the response entity from each server and if response from server does not contain the string specified in response match then that server is marked as unhealthy. Click Verify URL.
8 Manual installation of WDM database using scripts This section contains database scripts supported by Wyse Device Manager (WDM) and related functionality details. Topics: • Requirements • Proposed way of installing WDM database • Script files Requirements Existing WDM database support WDM installation supports SQL Server 2008. The database contains all the SQL server objects such as tables, views, stored procedures, and so on.
NOTE: The database scripts are mentioned here for customization purpose. CREATE DATABASE [RapportDB] ON PRIMARY (NAME = N'Rapport_dat', FILENAME = N'C:\Program Files (x86)\Wyse\WDM\Database\Rapport4.MDF, SIZE = 42496KB, MAXSIZE = UNLIMITED, FILEGROWTH = 10%) LOG ON (NAME = N'Rapport_log', FILENAME = N'C:\Program Files (x86)\Wyse\WDM\Database\Rapport4.LDF', SIZE = 768KB, MAXSIZE = UNLIMITED, FILEGROWTH = 10%) GO 1 The script file contains RapportDB Database creating scripts.
NOTE: ---- Customize Script Use RapportDB Go SET IDENTITY_INSERT [dbo].[License] ON INSERT [dbo].[License] ([LicenseID], [Sales], [UnActivated], [Code], [License], [Utilize], [NumberOfClients], [VendorID]) VALUES (1, N'7V931PHY08K01LZHYXWKKP6GQ1', N'BR69T51SSP500PFW9W4R0Z0TL5', NULL, NULL, NULL, NULL, NULL) SET IDENTITY_INSERT [dbo].[License] OFF GO SET IDENTITY_INSERT [dbo].[sysHash] ON INSERT [dbo].
9 Troubleshooting This section describes how to troubleshoot the issues that you may encounter while installing or upgrading WDM. Topics: • .NET Framework Installation Error in Windows 2012 and Windows server 2016 • Failure While Attaching the Database • Error While Installing WDM Database in a Distributed Setup • Database Installation Failure After Manual Uninstallation of SQL Server Express 2014 • After Upgrading from WDM 5.5.1 to WDM 5.
Failure While Attaching the Database Issue: Failure while attaching the database on Windows 2012 Server, with SQL Server 2012. Resolution: Run SQL Service ‘MSSQLSERVER’ using the ‘LocalSystem’ account on the system where WDM installation is targeted. Retry WDM installation.
Troubleshooting Post Deployment Issue : HTTP Error 404.0 – Not Found. the Web.config of the HApi shall be added with a url routing module if it’s missing: Resolution :Add the Web.config of the HApi with a URL routing module as follows: PAGE 111ARR Proxy Returns HTTP Error Code 502.4 Issue: The ARR Proxy server could return the HTTP Error Code 502.4 when any of the Management Servers (HServers) are not available. The Health Status of all the HServers in the Server Farm may be set to Unhealthy because the configured Health Tests have failed. Resolution: To correct this: 1 Log in to the ARR Proxy Server and launch the IIS Server Manager. 2 Select the Server Farm you created and on the right-hand pane, select Monitoring and Management.
Resolution: One of the reason for this issue is, the Computername for the setup has more than 16 characters. This brings out a mismatch in Computername and NetBIOS name (truncated to 15 chars) for the setup. To confirm this issue, check if the above mentioned system variables are different. If yes, install WDM on a setup which has hostname to a max of 15 characters, and then re-run upgrade installer. Cloud Environment Setup Issue Issue: An error message is displayed intermittently when you run the setup.
