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. © 2017 – 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 Information............................................................................................................................................................
Post Clustering Procedure................................................................................................................................................66 Running the HA Configuration Utility................................................................................................................................ 67 Adding a License on WDM...............................................................................................................................................
Cloud Environment Setup Issue...................................................................................................................................... 102 Error in Installation of WDM in Upgrade Setup................................................................................................................
GUID-138DCFA2-F92E-4E1A-831F-BF7752000E32 1 Introduction Dell Wyse Device Manager (WDM) is a software that manages all Dell Wyse thin and zero clients.
Windows Server 2008 R2 SP1 RapportDB Authentication SQL Windows Windows 2012 + SQL Express 2014 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 + SQL Server 2012 Yes Yes Yes Yes Yes Yes GUID-601CA685-50C7-4427-8F88-2616CB02148F Support Information This section lists out the supported operating systems, the supported databases, and the supported thin client devices for WDM ver
• • • Wyse 5010 thin client with PCoIP Wyse 3030 LT thin client with PCoIP Wyse 5060 thin client with PCoIP Wyse Enhanced Microsoft Windows Embedded Standard 7 (WES7) build 818 or later: • Wyse 5010 thin client with WES7 • Wyse 5020 thin client with WES7 • Wyse 7010 thin client with WES7 • Wyse 7020 thin client with WES7 • • Wyse 7010 extended chassis thin client with WES7 Wyse 3030 thin client with WES7 Wyse Enhanced Microsoft Windows Embedded Standard 7p (WES7p) build 850 or later: • Wyse 701
• Wyse 7030 zero client • Wyse 5050 AIO zero client with PCoIP Thin Linux: Supported EOL Dell Wyse Thin Client Platforms • Wyse 3030 LT thin client with ThinLinux • Wyse 7020 thin client with ThinLinux • • Wyse 5020 thin client with ThinLinux Wyse 5060 thin client with ThinLinux Wyse Enhanced Microsoft Windows Embedded Standard 7 (WES7) build 818 or later: • C90LE7 • R90L7 • R90LE7 • • • X90c7 X90m7 Z90s7 Wyse Enhanced Microsoft Windows Embedded Standard 7P (WES7P): • X90m7P • Z90s7P Wys
• R90LEW • V90LEW • X90CW • X90MW • 7010 • Z90SW GUID-74DD12B0-B05D-498C-9AD7-F0C62A556CB5 Localization Support For the WDM Server, localization support is provided on Windows 2008 R2 SP1 Enterprise Edition and Windows 2012 Standard R2 for the following languages: • French • German • Spanish • Japanese • Simplified Chinese GUID-5FE389BD-ACDA-439F-A5FA-BEC06DE1A0AD Dell Wyse technical support To access technical resources self-service portal, knowledge base, software downloads, regist
GUID-4B94E14A-4924-456B-AAFE-9D1F2BA0DD32 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.
GUID-1E0BCB03-473D-40B5-A137-729BC9694152 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. Server Hardware Requirements for 32–bit OS Category Minimum Requirements Recommended Configuration CPU 2.
WDM Component Protocol and Corresponding Ports Port Function 280 FTP 21 Register new packages into the Master Software Repository. OLE DB 1433 (default) Communicate with the WDM database. Can be configured during installation. 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.
WDM Component Protocol and Corresponding Ports Port Function DHCP Proxy and TFTP Services and legacy support for older WDM agents UDP 44956 Discover devices using subnet directed broadcasts that have older WDM Agents (5.0.0.x and earlier) installed. ThreadX 4.x Manager Service 44957 TCP 44955 Discover devices using IP Range Walking. Upgrade devices that have an older WDM Agent (5.0.0.x and earlier) installed. TCP 9880 Communicate with ThreadX 4.x devices. 50000 ThreadX 5.
GUID-074DE4D6-9D3B-494E-AC6C-35CFD411B76C Checklist to Install WDM Enterprise Edition Only If you are installing WDM Enterprise Edition only, then ensure the following: • Obtain and have access to your WDM Enterprise Sales Key or Enterprise Evaluation Key that you use during installation. • Install the supported version of SQL Server. The WDM installer provides Microsoft SQL Express 2014 as the default option, but you can choose another supported version of SQL Server.
GUID-6DAC9ED4-4806-406E-B7A1-1B04E9444C31 3 Installing Dell Wyse Device Manager (WDM) This section guides you through the complete WDM installation procedures. 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.
GUID-0B71DF78-674B-4DF0-9868-B2250826321E Installing the WDM Workgroup Edition To install the Workgroup edition: 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. The Welcome screen is displayed. Figure 1. WDM Installer 5.7.2 Screen 3. Click Next. 4. Select Workgroup as the License Type and click Next.
Figure 2. WDM Installer 5.7.2 (Workgroup) Screen For Workgroup edition, the license key is provided within the Installer and you do not need to enter any details. 5. 18 The components are all selected by default and you cannot de-select any component. Click Next.
Figure 3. Components Screen 6. In the Configure Database screen, you can choose one of the following options: • Install New Database Server (Microsoft SQL Express 2014) — Select this option if you do not have any supported version of Microsoft SQL Server installed on the system. Proceed to step 7.
Figure 4. New Database Configuration • 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. Proceed to step 8. If you select this option, make sure that the existing database server is on the same system where you are installing WDM Workgroup edition. Provide the RapportDB database credentials. RapportDB is the WDM database instance that is created on SQL Server. a.
Figure 5. New Database Configuration 8. If you have selected the second option in step 6, then provide the following details: a. Enter Server Hostname, Port, Username, and Password. Port number is entered by default and the port number is 1433 NOTE: Password must match complexity rules of underlying Windows OS.
Figure 6. Existing Database Configuration 9. 22 Click Next. The Configure Software Repository Server screen is displayed.
Figure 7. Configure Software Repository Server Screen 10. Enter the authentication details for the Software Repository: a. Configure New Repository Server — select this option if you want the installer to configure the repository server. You can create a new user or use an existing user. b. Use Existing Repository Server — select this option if you have already configured the Repository Server. c. Enter Protocols — Select the protocol and settings to distribute software to the managed devices.
Figure 8. Other Services Screen 13. Provide the installation path and click Next.
Figure 9. Destination Screen 14. Select the certificate and import the same to start the installation. NOTE: If you click the NEXT without selecting a certificate, the installer installs a self signed certificate. The communications are encrypted, still the system is not completely secure. The certificate must be in the format of .pfx file.
Figure 10.
Figure 11. Installation Summary Screen The installation progress is displayed on the screen and after installation is complete, you are prompted to restart your system. Restart the system for the system changes to take effect. After installation, ensure that you will meet the following checklists: • Rapport folder should get created after installing WDM in C:\Inetpub\ftproot path. • WyseDeviceManager 5.7.2 WebUI icon will be created in the Desktop.
Figure 12. WDM Installer 5.7.2 Screen 3. Click Next. 4. Select Enterprise as the License Type.
Figure 13. License Screen a. 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. b. 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 need to 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. 5. Click Next.
Figure 14. Component 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. 7.
Figure 15. New Database Screen • 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. Proceed to step 9. Provide the RapportDB database credentials. RapportDB is the WDM database instance that is created on SQL Server. a. SQL Server Authentication is selected by default.
Figure 16. Existing Database Screen 9. If you have selected the second option in step 7, then provide the following details: a. Server — Provide the hostname of the system on which you have installed Microsoft SQL Server. b. Port — This is entered by default and the port number is 1433. NOTE: You can add five digit custom port for TCP/UDP in the range of 49152 to 65535. c. Username — Enter the user name to connect to the existing database. d. Password — Enter the password to access the database. 10.
Figure 17. New Software Repository Screen 11. Enter the authentication details for the Software Repository: a. Configure New Repository Server — select this option if you want the installer to configure the repository server. You can create a new user or use an existing user. b. Use Existing Repository Server — select this option if you have already configured the Repository Server. c. Enter Protocols — Select the protocol and settings to distribute software to the managed devices.
Figure 18. New Software Repository Protocol Screen b. Use Existing Repository Server — select this option if you have already configured the Repository Server.
Figure 19. Existing Software Repository Screen c. Enter Protocols — Select the protocol and settings to distribute software to the managed devices. HTTPS is selected by default. You can also select FTP and CIFS. d. Authentication Type — Windows is selected by default. You can also select Basic. e. Username — Rapport is displayed by default. You can change this. If you select the Use Existing Repository User option, enter the user name of the existing user. f.
Figure 20. Other Services Screen NOTE: • ThreadX 5.0 is supported on the operating system Windows Server 2012 and Windows Server 2012 R2 and above. NOTE: Dell recommends you to install all the four services during WDM installation itself. If the WDM installation is completed with only one service installed, then it is not possible to install the remaining services. You must uninstall and then re-install WDM by selecting the remaining services.
Figure 21. Destination Screen 16. Select the certificate and import the same to start the installation.
NOTE: If you click the NEXT without selecting a certificate, the installer installs a self signed certificate. The communications are encrypted, still the system is not completely secure. The certificate must be in the format of .pfx file. Figure 22. Certificate Screen 17. Click Next to begin the installation.
Figure 23. Installation Summary The installation progress is displayed on the screen and after installation is complete, you are prompted to restart your system. Restart the system for the system changes to take effect. GUID-E1664207-9B43-43B2-AAAC-629B85E8E347 Installing the WDM on Cloud Environment To install the Enterprise Edition: 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.
Figure 24. Welcome Screen 3. Click Next. 4. Select Enterprise as the License Type.
Figure 25. License Screen a. 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. b. 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 need to 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. 5. Click Next.
Figure 26. 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. 7.
Figure 27. New Database Server Screen • 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. Proceed to step 9. Provide the RapportDB database credentials. RapportDB is the WDM database instance that is created on SQL Server. a. SQL Server Authentication is selected by default.
Figure 28. Existing Database Screen 9. If you have selected the second option in step 7, then provide the following details: a. Server — Provide the hostname of the system on which you have installed Microsoft SQL Server. b. Port — This is entered by default and the port number is 1433. NOTE: You can use user dynamic port for TCP/UDP in the range of 49152 to 65535 while installing WDM on cloud environment. c. Username — Enter the user name to connect to the existing database. d.
Figure 29. Software Repository Screen 11. Enter the authentication details for the Software Repository: a. Configure New Repository Server — select this option if you want the installer to configure the repository server. You can create a new user or use an existing user. b. Use Existing Repository Server — select this option if you have already configured the Repository Server.
Figure 30. Existing Software Repository Screen c. Enter Protocols — Select the protocol and settings to distribute software to the managed devices. HTTPS is selected by default. You can also select FTP and CIFS. d. Authentication Type — Windows is selected by default. You can also select Basic. e. Username — Rapport is displayed by default. You can change this. If you select the Use Existing Repository User option, enter the user name of the existing user. f.
Figure 31. Other Services Screen NOTE: ThreadX 5.0 is available only for Windows Sever 2012 , Windows Server 2012 R2 and above. 13. Provide the destination path and click Next. The destination screen is displayed.
Figure 32. Destination Screen 14. Select the certificate and import the same to start the installation. NOTE: If you click the NEXT without selecting a certificate, the installer installs a self signed certificate. The communications are encrypted, still the system is not completely secure. The certificate must be of in the format of .pfx file.
Figure 33.
Figure 34. Installation Summary Screen The installation progress is displayed on the screen and after installation is complete, you are prompted to restart your system. GUID-B179116D-40E1-48E5-BC8C-4D723138FF93 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.
GUID-93A09892-AB21-4335-8463-3EEA054C6CF6 Installing the WDM Database Before you install the WDM database on a system or virtual machine (VM), make sure you have the supported version of Microsoft SQL Server installed on the system. If you do not have SQL Server on the system, you can choose to install Microsoft SQL Express 2014 that comes packaged with the WDM installer. NOTE: If you are installing the WDM database on an existing SQL Server database, make sure that port 1433 is available on the system.
The installation progress is displayed on the screen and after installation is complete, you are prompted to restart your system. Restart the system for the system changes to take effect. GUID-BBAD361F-18CC-49A6-8056-48C58E4E24CD Installing Management Server/Other Services/Management Console/ Web UI You can install the Management Server, Other Services, Management Console, and Web UI on the same system or on different systems. To install these components: 1.
The Welcome screen is displayed. 3. Click Next. 4. Select Enterprise as the License Type. a. 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. b. 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 need to obtain the license key and re-install WDM. 5. Click Next. The Components screen is displayed.
2. Navigate to the folder where you have extracted the installer and run Setup.exe. The Welcome screen is displayed. 3. Click Next. The Upgrade Information screen is displayed. Figure 35. Component Information 4. Click Next to continue. User Credentials screen is displayed. Enter the password. Important: The Password field is disabled for SQL Authentication. You are required to enter the password only for Windows Authentication. 5. Click Next. The Important Information screen is displayed. 6.
Configure SSL in IIS 7.0 on Windows Server 2008 R2 To configure SSL in IIS 7.0: 1. Download SelfSSL7 utility from the link SelfSSL.exe. 2. Call the utility SelfSSL7.exe with the below mentioned parameters: SelfSSL7.exe /Q /N cn=Certificate_Name /I /S Web_Site_Name. e.g. SelfSSL7.exe /Q /N cn="TestCert.TestLab.
19. In the tree pane select the Server and on the right pane double click Server Certificates. 20. In the right pane of Server Certificates, double click Create Domain Certificate... to begin creating a certificate. 21. Fill in the information requested in the Create Certificate window and click Next to open Online Certification Authority. 22. In Online Certification Authority, click select to Specify Online Certification Authority and provide a Friendly Name for the same and click Finish. 23.
15. Then in the Server Manager>> Dashboard console under notifications’ find the Post-deployment Configuration message. 16. In Post-deployment Configuration message click on link “Configure Active Directory Certificate Services on the local server”. 17. Then AD CS Configuration>> Credentials window will open get launched; provide the required appropriate credentials and click on ‘Next’ button. 18.
10. 58 In SSL Settings, select Require SSL check box and ‘Require’ radio button for Client certificate and Apply the settings.
GUID-95673E02-37F2-4DE5-AD34-9AF746A637BC 4 Uninstalling a Standalone Installation of WDM 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. To uninstall WDM: 1. Click the start menu and select Control Panel. 2. Click Programs → Uninstall a program on the Control Panel screen. 3. Select WDM 5.7.2 from the program list and click Uninstall. The Uninstallation Screen is displayed. 4.
5. Click Next on the Welcome screen. 6. Click Next to begin the uninstallation process. 7. Log in to the system where you have installed 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.
GUID-2E7ACC0A-9A35-4ABC-A35B-DBA0AB8388F7 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.
GUID-DC2CC4B7-E9EB-4289-B8CA-2F7B86D81BAB Components Required for Database Clustering The high availability environment for WDM consists of the following components: • Primary Server or Primary Node – This is one of the four Virtual Machines (VMs) on which you need to install Microsoft SQL Server 2012 database. This should have two network adapters, one configured for public and one configured for private.
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. 14. Make sure that the Private network contains only the IP address and Subnet mask. The Default Gateway or DNS Servers should not be defined. 15. Make sure that the servers can communicate acoss this network so that the nodes can communicate with each other across the network. 16.
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. Enter WINCLUSTER as the name of the cluster and enter the IP address. Click Next to continue. NOTE: This is also the computer name that you need to provide permission for the File Share Majority Quorum, that is described later in this document.
GUID-DFD0336F-6144-44F0-83E5-AE8FD1E7CDB5 Installing SQL Server on Primary and Secondary Nodes Installing SQL Server on both the nodes and configuring it to function in a cluster is an important step in the setup of a high availability database cluster. This section provides the steps to install and configure SQL Server 2012 standalone on both the nodes. If you want to install any of the supported versions of SQL Server, see the installation instructions provided by Microsoft.
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. 10. Make sure that the Feature Rules screen does not display any failures. Click Next. 11.
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
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. GUID-17004940-5904-45F0-AC6A-0065DF001DE9 Adding a License on WDM WDM needs a license to function. The licensing code is generated based on the database.
GUID-410FD7CB-0208-40F2-98FB-208BB21C8782 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 realtime command execution. Load balancing helps resolve these problems to a great extent.
NOTE: You can set up the ARR Proxy Server and the WDM Management Servers across different subnets in the same doamin. Setting up the ARR Proxy Server consists of the following steps: 1. Installing IIS. 2. Installing the ARR Module. 3. Configuring the Application Pool Process for ARR. 4. Creating a Server Farm of WDM Management Servers. 5. Configuring SSL 6. Configuring Server Farm Properties for ARR. 7. Configuring Request Filtering 8. Setting up the Proxy FQDN in WDM Preferences.
4. Select the following options: Option Common HTTP Features Health and Diagnostics Management Tools 5. Click Next to view the summary. 6. Click Install to install IIS. Sub-options • Static Content • Default Document • HTTP Errors • Directory Browsing • HTTP Logging • Request Monitor • Logging Tools • Tracing Select all the sub-options. GUID-BB2CB293-04D3-4353-B051-391E3A55917F Installing the ARR Module You must install the Application Request Routing version 3.
5. Under Process Model change the value of Identity from LocalSystem to ApplicationPoolIdentity. 6. Change the Idle Time-out (minutes) to 0 to disable the setting. Click OK to save the changes. GUID-5C922BF6-6F2D-4B4A-987D-8A3485666705 Creating a Server Farm of WDM Management Servers To create and define a server farm: 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.
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.
8. Double click Routing Rules. a. Click URL Rewrite on the Actions pane. 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. GUID-900447C9-A856-4699-8B66-B21F70F6FEDF Configuring Request Filtering To configure request filtering: 1. Log in to the ARR Proxy Server and launch the IIS Manager. 2.
The ARR Proxy Server is now recorded in the WDM database, and this completes the Load Balancing setup. GUID-E4AA88FE-9B3C-43F6-B592-18BD995B4118 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.
b. Select _PCOIP-tool on the right-hand pane, right-click and select Properties. c. In the Properties window, check the Time to live (TTL) value. The caching interval is called the Maximum TTL value and the default is 1 hour. You can change this if you want. 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.
Figure 38. DNS_SRV record for _pcoip-bootstrap 2. The second record required is an A record pointing to the name used in the Host offering this service field. Figure 39. 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.
Figure 40. Create TXT record 2. 80 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 41. 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. After opening the browser, press the bring Alt + T key to open Tools. 2. From the drop-down list, select Options. Figure 42. General Tab 3.
Figure 43. 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 44. 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 45. Downloading Certificate 9. 84 Copy the sha256 fingerprint value. Click Close and cancel all the firefox windows.
Figure 46. 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 47. tcmc2 Properties 10. The fourth and final record is a reverse PTR record for the management host. Figure 48. 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). GUID-398EA939-B93D-40D4-B8AC-5D2714138169 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.
bind 10.150.99.102:5172 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. 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. Click the Start menu → Administrative tools → Services. 10. Verify ThreadX 5x Manager Windows Service is installed and running. GUID-1F1F0F08-1799-4424-8681-339D80B2E193 Adding Teradici Device Proxy Servers to WDM Follow the steps provided to add Teradici Device Proxy Servers to WDM: 1.
5. Click on the Check Mark on the right hand side of the text boxes to save the values. GUID-F9A5DD5F-8612-41D2-85BA-B7BDA44E9DF4 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. GUID-82113E1B-2964-4809-B588-F8BF3EC699F5 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.
Figure 49. Status on Dashboard Figure 50.
Figure 51.
GUID-E660BA4F-137A-4D32-82B1-6159CC886736 7 Manual installation of WDM database using scripts This section contains database scripts supported by Wyse Device Manager (WDM) and related functionality details. CONCEPT-13-9B7B8096 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. The WDM installer stores the database to the respective folder (default is: C:\Program Files (
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. 2.
This script file contains script for Customize Data values. Provide the database server name while executing the following script. An error is displayed, if you do not enter the server name. NOTE: ---- Customize Script Use RapportDB Go SET IDENTITY_INSERT [dbo].[License] ON INSERT [dbo].
GUID-FAFC4809-DB30-4FB7-99AF-1AE3A80F51BC 8 Troubleshooting This section describes how to troubleshoot the issues that you may encounter while installing or upgrading WDM. GUID-A74DFC00-88C0-457A-9B67-2BD38395A266 .NET Framework Installation Error in Windows 2012 Issue: .NET Framework 3.5 installation fails on Windows Server 2012 with error code 0x800F0906 Resolution: Method 1: 1. Log in to the system where you have installed Windows Server 2012 and launch the Server Manager. 2. Install .
GUID-30C90F4C-5F33-4B37-BB2C-E723F08C8254 Error While Installing WDM Database in a Distributed Setup Issue: When you are installing the WDM Database on a separate system that has the supported version of SQL Server installed on it, then the following error may be displayed when you launch the Setup.exe : Setup was unable to initialize the required libraries. Resolution: Make sure that the Microsoft Visual C++ Redistributable 2008, version 9.0.21022 is installed.
Resolution :Add the Web.config of the HApi with a URL routing module as follows: GUID-82ED96F4-1A02-4318-B24E-98A25C4550B7 Troubleshooting Load Balancing Issues This section describes how to troubleshoot some issues that you may encounter in the Load Balancing setup.
GUID-DBA7BB21-ECFF-4200-B5CB-CCA2712F3616 ARR 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.
GUID-21AF881B-53EE-4686-A4C8-6B54396C2567 WDM Upgrade Installation Fails Problem: WDM Upgrade installation fails while connecting to software repository. 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.
• A warning message is displayed. Click OK. • Enter the user name and password of the user used when you installed WDM. Click Ok to continue. • Now close the WDM GUI and proceed with the installation. • After installation, run the Database Credential Manager available in the Install path (C:\Program Files(X86)\Wyse\WDM \Utilities\Database) again. • Provide your username and password used when you installed WDM, and then reboot the server.
