Dell Wyse Device Manager Version 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 Key Features....................................................................................................................................................................... 6 Key Features of WDM Enterprise Edition.......................................................................................................................
Adding Users and Groups from Active Directory......................................................................................................... 54 Editing User Permissions................................................................................................................................................ 54 Deleting Users..................................................................................................................................................................
EMSDK fails to start due to port number ................................................................................................................... 101 Domain user login and HApi Log Failure....................................................................................................................... 101 Problems with accessing Device Page.........................................................................................................................
1 Introduction Dell Wyse Device Manager (WDM) software is the premier enterprise solution for managing Dell Wyse thin and zero clients simply, remotely, and securely. It enables IT professionals to easily organize, upgrade, control, and support thousands of Windows Embedded, Wyse Enhanced Linux, Wyse ThinLinux, Wyse ThinOS, Wyse ThinOs Lite, and PCoIP zero client devices (ThreadX devices) across any LAN, WAN, or wireless network.
• Recurring scheduler - Allows packages to be scheduled repeatedly: daily (or specific weekdays), weekly, and monthly, upto a specific date or for a fixed number of times. • Device Configuration Deployment - You can create different configurations that can be deployed to a device independent of an image. • Repository Creation and Administration - WDMVXC-M allows you to easily build and administer a repository of software, images, and configuration updates for distribution.
• Support for Multiple Databases - Multiple database support when installing VXC-M for either an SQL 2005 or 2008 environment, allows you to use your existing back-end infrastructure. • Active Directory Integration - Allows you to easily import VXC-M user groups or individual users from your existing Active Directory setup. • Autogenic Imaging - Allows you to image the device with the image residing on flash or hard drive of the device.
• Chargeback Accounting - This feature is supported on Wyse Thin OS (ThinOS) devices. It collects and stores remote session information from thin clients. Support Information This section lists out the supported operating systems, the supported databases, and the supported thin client devices for WDM version 5.7.
• 7010 • 7020 • Z90DE7 • Z90S7 Wyse Enhanced Microsoft Windows Embedded Standard 7p (WES7p) build 850 or later: • X90m7p • 7010 • Z90DE7p • Z90S7p • 5020 • 7020 • 7040 Wyse Enhanced Microsoft Windows Embedded 8 Standard (64bit) (WE8S): • 5010 • 5020 • 7010 • 7020 Windows 10 IoT Enterprise (64–bit) (WIE10) • 5020 • 7020 Wyse Enhanced SUSE Linux Enterprise: • 5010 • 5020 • X5OM • 7010 • 7020 • Z50S Wyse Enhanced Ubuntu Linux: • T50 ThinOS Lite : • 3010 • 3020
• Supported EOL Dell Wyse Thin Client Platforms 5020 Wyse Enhanced Microsoft Windows Embedded Standard 7 (WES7) build 818 or later: • C90LE7 • R90L7 • R90LE7 • X90c7 Wyse Enhanced Microsoft Windows Embedded 8 Standard (32bit) (WE8S) : • 5010 • 7010 • Z90D8E Wyse Enhanced SUSE Linux Enterprise: • C50LE • R50L • R50LE • X50c ThinOS Lite: • C00X • R00X ThreadX/ View Zero Client: • P20 Wyse ThinOS: • C10LE • R10L Wyse Enhanced Microsoft Windows Embedded Standard 2009 (WES2009)
NOTE: Before proceeding, verify if your product has a Dell service tag. For Dell service tagged products, go to www.dell.com/support/ contents/us/en/19/article/Product-Support/Dell-Subsidiaries/wyse for more information. 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.
2 Accessing WDM To access WDM UI, do the following: 1 2 Open the Supported Browser for WDM UI. The following are the supported web browsers for accessing the WDM web UI: • IE11 • Chrome v40 and later versions • Firefox v40 and later versions In the Browser, enter the following URL: https:///WebUI/app/indexf.html# 3 Press the Enter button.
3 Dashboard The Dashboard page allows you to view the details of Server status, device health, jobs list, alerts, events and the information about the checked in server. You can quickly view the summary of the information for each functional area of the system. It displays the information of the following attributes: Figure 1. Dashboard • Server Status • Device Health • Jobs You can view the system updates by clicking the following tabs on the upper right of the Dashboard page.
Parameter Description • • • • Discovery and imaging Teradici server Scheduler MASTER Repository If any of the services are stopped due to some reason, then the status of the server is displayed as System is down. If the services are up and running, then the status of the server is displayed as System is healthy. Device Health If you click the Device Health tile, it displays the total number of device enrolled into WDM server.
Topics: • Licenses • Unlicensed Devices Licenses The License page provides the details of WDM licenses such as, Sale key, Non-activated key, Activation code, license Key and the description. To Add new license key, perform the following task: 1 Enter the license key in 7 charcters-6 characters-6 characters-7characters format in the provided field. 2 Click Save. The Default trial license period of WDM is for 30 days. You can extend the WDM trial license Period from 30 days to 60 days.
Figure 3. Unlicensed Devices NOTE: • To move unlicensed devices to licensed devices you must have enough number of licenses provided by the WDM administrator. • If you do not have enough licenses and attempt to move an unlicensed device to licensed devices, the following message is displayed:You have no license for the vendor. If you still want to add a device to licensed page, then add the license that can accommodate more number of devices or delete the already existing devices on the license page.
4 Devices In the Devices page you can view all the devices which are discovered automatically or manually. You can also view the details of the device information and perform the tasks such as adding the new device manually, real time commands and so on. Table 2. Devices Parameter Description Name Displays the name of the device. IP address Displays the IP address of the devices. Platform Displays the platform of the devices. Operating system Displays the operating system running on the devices.
Figure 5. Find Devices To discover a device, perform the following tasks: 1 Click the Find Devices option. You can discover a device using Local Network, IP Range and Subnet. 2 Click the IP Range option to discover a device using IP range and enter a range of the IP address in the provided field. 3 Click the Subnets option to discover a device using subnets. You can search for a subnet in the Global Search bar. 4 Click the Local Network option to discover devices from the local network.
e Click View Details to view complete overview, Status, Network, Hardware and Logs of the selected device. • Overview — Provides a complete overview of the System, Location, Capabilities, Network, and Drives of the selected device. • Status— Provide details of Apps that are installed and running on the system. Installed Update also provides details about the Processor running and system performance. The details of the Remote session are displayed for the selected devices.
e • Information • Warning • Critical 2 Enter the title of your message in the Message Title field. 3 Enter the content of the your message in the Message Body field. 4 Click Send button to send your message. Click More to perform more tasks. You can perform the following tasks: Table 3. More Parameter Description Rename Device Enter the updated name in the Rename Device field. Update Device Information Enter the device details to update the device information.
Figure 8. Manage Group Types 1 Click the All Devices option and select Manage Group Types option. A Manage Group Types page is displayed. 2 Enter the name of the custom groups in the Groups field. 3 Click the Add option to add the selected custom groups. 4 Select the added group from the list and add value for the particular group. 5 Click the Add option to add value for the selected groups. 6 Click the Save option to save your changes.
Figure 9. Create View 1 Click the All Devices option and select Create View option. A Create View page is displayed. 2 Enter the name of the view in the New view field. 3 Select the groups displayed on the left side of the screen in order of preferred hierarchy. NOTE: To add a custom group, click the + Add custom group option. Enter the name of the group and select the check mark to add the custom group in the list of group hierarchy. You can view the order of selected groups of hierarchy.
Figure 10. Assign Group 4 Select the group value to which you want to assign the device. Figure 11. Assign Group 5 24 Click Save.
5 Applications The Applications page allows you to perform the following tasks: • Register packages to the WDM Master Repository. • Deploying a package to the devices. • Manually registering the package images and/or configurations packages that you register or create or get from the devices in your network (to distribute it to other devices). • Upgrading the pre-registered WDM Agent and Boot Agent Packages.
• • WES7WDAAgentUpgrade— This package can be scheduled only to the devices running WES7 OS. This package can be used to update the existing HAgent and WDA to the WDA version incorporated in WDM. • WES7PWDAAgentUpgrade - This package can be scheduled only to the devices running WES7P OS. This package can be used to update the existing HAgent and WDA to the WDA version incorporated in WDM. • WESHAgentUpgrade— This package can be scheduled only to the devices running WES OS.
Figure 14. Images • • BootAgentUpgradeWES - This package can be scheduled only to the devices that are having Boot Agent embedded with the image. When scheduled to a device, it upgrades or downgrades the Boot Agent of the device. • BootAgentUpgradeXPe -This package can be scheduled only to the devices that are having Boot Agent embedded with the image. When scheduled to a device, it upgrades or downgrades the Boot Agent of the device. Parameter Description Name Displays the name of the packages.
Figure 15. Other Packages • • BootAgentUpgradeLinux- To upgrade the boot agent for a device running the SUSE Linux Enterprise OS. • BootAgentUpgradeThinLinux— To upgrade the boot agent for a device running the ThinLinux OS. • BootAgentUpgradeWE8S- To upgrade the boot agent for a device running Windows Embedded 8 Standard 64 bit OS. • BootAgentUpgradeWE8Sx- To upgrade the boot agent for a device running Windows Embedded 8 Standard 32 bit OS.
Figure 16. PCoIP Device Configuration • AdminPassword — Sample package to change the administrator password for ThreadX devices. • Certification — Sample package to change the device certificate for ThreadX devices. • Disable VDMUserNameCaching — Sample package to disable the caching of the VDM Login user name for ThreadX devices. • DisableWebInterface — Sample package to disable the web interface for ThreadX devices .
1 Select your preferred package from the application list. 2 Click the update option displayed on the top of the screen. 3 From the Select View drop-down list, select your preferred view. NOTE: The package distribution is the mass deployment process under Application tab. You can not select individual device to deploy a package. The selected package is deployed to the entire selected view. 4 Schedule the package distribution based on your preference.
Editing the Package Script of a Registered Package To view the property of a software package: 1 Click the Package Script option. The Package Script window is displayed. 2 Click the Edit option to edit the script. 3 Click Save. NOTE: You cannot modify the script for default packages. This is valid only for custom packages. Exporting the Package Script of a registered Package To export the package script of a registered software package: 1 Click the Package Script option.
Figure 17. Register Rsp 1 Download and open the Package Registration Utility dialog box. 2 Click the RSP tile displayed on the WDM Package Registration Utility dialog box. 3 Browse the .rsp file or package to upload. 4 The following details of the RSP package is displayed. 5 32 • Name • Description • Operating System • Category • Image Size • Image Type Click Upload.
Register a Package (exe, msi, msu, and bat files only) To register a package, do the following: Figure 18. WDM Package Registration Utility Figure 19. WDM Package Registration Utility 1 Download and open the Package Registration Utility dialog box. 2 Click the EXE tile displayed on the WDM Package Registration Utility dialog box. 3 Browse the exe, msi, msu, or bat files only or package to upload. The following details of the selected package is displayed.
4 • Command Parameters From the Operating System drop-down list, select the operating system. 5 Enter a valid thin client path to install the package in the provided field. 6 Enter the command parameters in the provided field. 7 Click Upload. PCoIP Device Configuration Use the PCoIP device configuration page to create and deploy new PCoIP device configuration packages. NOTE: For information about upgrading the ThreadX devices from version 4.X to version 5.X, see Upgrading the ThreadX 4.
Time Zone Configuration Provide the following details: • Select the mode through which you want to identify the Network Time Protocol (NTP) Host. • Enter the IP address or the host name of the NTP server. • Enter the Port number, the Query Interval in minutes and select Enable Daylight Saving Time, if it is applicable to the time zone you are selecting. • Select the time zone from the drop-down list. Language for the Local GUI Provide the local language and keyboard details for the localized GUI.
Figure 21. Connections VMware Horizon View PCoIP Connection Server Settings Provide the following details for the VMware Horizon view connection server: • Select the mode through which you want to identify the connection server. • Enter the IP address or the host name of the connection server. • Enter the connection port number and select the connection options as per your requirement. • Click Kiosk Mode if the device is to function as a Kiosk type terminal.
PCoIP Broker Servers • Select the option to add the broker server details up to 25. Security Figure 22. Security Certificate Select the option to enter the content of the certificate. USB Device Authorization Provide the USB permission details (Authorized and Unauthorized) for the device. Enable Advanced Configuration Select the options if you want to enable the web interface of device, Wake-on-LAN, Power on after Power Loss, User Name Caching and Enabling Unified communications.
6 Updates The Update page provides you the summary of Scheduled Jobs, Recurring Updates, Repository sync Jobs, Peer assisted delivery details. You can also create Profile and DDC.
Figure 23. Jobs • All jobs — If you select All Jobs, the Scheduled Jobs of all the Users are listed. • My jobs — If you select My Jobs, only the Scheduled Jobs of the logged in user are listed. 1 To reschedule the job, Select the distribute option as Now if you prefer to distribute the package or you can select the distribute option as A specific date and time and enter your preferred date and time of package distribution. Click the On/Off option to enable or disable the Retry failed updates option.
Figure 24. Recurring Updates 1 Click Refresh option to refresh the page. 2 Click Reschedule option to reschedule the package distribution. a Enter the following package distribution details: 1 Name of Recurring update. 2 From the Recur drop-down list, select the day for package distribution. 3 Enter the start and end date of the package distribution. 4 Enter the time duration of the package distribution. 5 Click Reschedule. 3 Click Delete option to remove the jobs.
Figure 25. Real Time Commands 1 Click Refresh option to refresh the page. 2 Click Delete option to remove the command. 3 Click Export option to export the device in .csv or .txt (tab delimited) format. Repository Sync In this category, you can view the Remote Sync jobs that are scheduled to the Remote Repository created. Figure 26. Repository Sync Peer Assisted Delivery In this category, you can view the details of the Peer Assisted deployment schedule for Subnet.
Figure 27. Peer Assisted Delivery Profiles Figure 28. Profiles This parameter helps to add new profile and provides the details such as, Groups, Assigned, and Inherited. To add a new profile complete the following task: 1 From the Select Operating System drop-down list, select your preferred operating system. 2 From the drop-down list, select the preferred view to be deployed for a particular profile. 3 Click Add to include the new profile to the groups.
Figure 29. DDC To add a new DDC, complete the following task: 1 From the Select Operating System drop-down list, select your preferred operating system. 2 From the Select Media Size drop-down list, select your preferred media size. 3 From the drop-down list, select the preferred view to be deployed for a particular profile. 4 Click the On/Off option to enable or disable the Enforce Sequence option.
3 In the capabilities section, look for WCM support. 4 The device is profile manager capable if it is in the following condition: 5 • Green color: The device is profile manager capable. • Red color: The device is not profile manager capable. To make the device profile manager capable, deploy the latest WDA agent available in WDM. NOTE: For HAgent supported devices, register the WCM client package and push to the devices having HAgent.
7 Reports In the Web UI you can generate the log reports on the daily basis, Weekly basis, or monthly basis. The report generated can be viewed, edited, and saved. Topics: • Creating a Log Report • Creating an Application Report • Creating a Remote Session Report Creating a Log Report Log Reports provide important information about the events or activities went into WDMVXC-M server related to WDMVXC-M components. It allows you to easily see what you want, when you want it.
4 To save the report, click the Save Report link in the Time Range area. 5 In the Save Report dialog box, enter the report name, and click Save. The saved report is listed in the Saved Reports drop-down list. NOTE: To save a log report as a .txt file or .csv file, click the Export icon on the upper-right corner of the page and select either .csv or .txt ( tab delimited) based on your preference. To use the report in the future, select the report from the Saved Reports.
Figure 33. Remote Session 2 From the Time Range drop-down list, select the desired time range or duration for which you want to generate the report. Reports can be generated for the present day, previous day, last 7 days, last 30 days or All time. To specify your own time range, click Custom and specify the start date and end date. 3 You can generate the report based on the following search criteria: 4 • From the Connection Type drop-down list, select your desired connection type.
8 System The System page in the web UI enables you to configure the following options: • Subnets: The Subnets page helps you to view the system broadcast IP, active IP, subnet mask and description. Subnets are autocreated when the device gets checked-in to WDM Server. You can also configure subnet manually. To manually configure the subnet, see Setting Subnets Manually. • Repositories: The Repository page contains the details of the Master repository and remote Repository.
• Adding Users and Groups from Active Directory • Editing User Permissions • Deleting Users • Console • Configure Device Discovery • About Services • Configure Logging Levels • Scheduling • Peer Assisted Deployment • Wyse ThinOS Setting Subnets Manually With WDM, you can add and configure subnets manually.
Figure 34.
To add and configure a subnet: 1 In the WDM Console, expand System and click the Subnet option. 2 Click Add subnet option. 3 Complete one of the following task: • If you want to provide a broadcast address for the subnet manually, select Manually create and enter the Broadcast Address.
Figure 35. Registering Remote Repositories You must configure the following points before you register remote repositories: • WDMVXC-M always names the first Repository Master. Any additional Remote Repositories that you install can be named anything other than Master. • If you do not install multiple Remote Repositories, then WDMVXC-M uses the Master Repository for all subnets.
• • 3 • Username - Username for FTP repository access. • Password - Password for FTP repository access. • Repeat Password- Re-enter the password for FTP repository access to confirm the password. • Bandwidth - How much bandwidth in Kbps to utilize for data transfer to and from the Software Repository. • Timeout (sec) - Time in seconds that the connection for each session should remain open.
Figure 36. Accounts NOTE: Before you can add a WDMVXC-M user, the user must already exist in the list of users for the Windows Domain where you installed WDMVXC-M. To add a user from a local computer account: 1 In the WDMVXC-M Console, expand System. 2 Select the name of the user you want to add as a WDMVXC-M user and click Add. 3 Click OK to add the new user to the list of WDMVXC-M users. NOTE: New users do not have permissions until you edit the user permissions.
Figure 37. Accounts NOTE: As an administrator, you can edit the permissions but the default Administrator will have all permissions and you cannot change it. To edit user permissions: 1 In the WDM Console tree pane, expand System, and click Accounts option. 2 Click Add option to add user or user group. 3 Click Local tab to view the list of WDM users. 4 Select the user you want from the list of users and click Add to open the User Permissions dialog box.
Console Click the Console in the System list to view the device status. Figure 38. Console 1 Enter the following details: • Device Health Status: • Perform a partial check-in every - Set the partial check-in frequency for all devices by selecting a number and a time unit (minutes, hours, days). The default is 1 Hour. Partial check-ins occur regularly at the specified interval to ascertain device health status (red, yellow, green). Partial check-ins require less network bandwidth than a full check-in.
2 The Default Device Configuration allows you to automatically distribute Firmware or SW packages or both to your thin clients devices, Assigning DDCs to groups of devices ensures conformity and allows you to target functional areas of your enterprise with tailored imaging and configuration. 3 Specify the following details: Figure 39. Console 4 • Default Device Configuration - (WDM Enterprise Edition only.) Select this option if you want to allow devices to use DDCs for automatic upgrades.
Figure 40.
• DNS Hostname: Select if you want to allow devices to use DNS Hostname lookup method to discover WDM Server. • DNS SRV record lookup : Select if you want to allow devices to use DNS SRV record lookup method to discover WDM Server. • DHCP optipon tags : Select if you want to allow devices to use DHCP option tags to discover WDM Server. • Manual discovery from Device Manager: Select if you want to discover the device uing IP Range or Subnet discovery methods in the Find Device window.
For CE devices, the default WOL port is 2344 and for rest of the devices it is 16962. You can change it to some custom port, but make sure to put an exception on firewall port, if Firewall is turned on. Configure Logging Levels This parameter helps you to view the following different configure logging levels. Higher logging level causes more data to be stored in the database. This could result in server slow down. The Debug and Informational levels should only be used during debugging. Figure 42.
Figure 43. Scheduling • Maximum Simultaneous Updates: The maximum number of device updates you can perform at the same time in the subnet. • Scheduled updates by timezone of: Select the WDM Time Zone that will be in effect when you schedule device updates. Options include: • DB Update Server : The time zone defined by the physical location of the WDM Database. • Console: The time zone defined by the physical location of the WDM Console.
Workflow from theWDMVXC-M Server to the Repository Device The image update process for the repository device configured for PAD consists of three basic steps: • Self-imaging of the device. • Making the device Repository-capable. • Switching off the repository when the PAD schedule is completed.
Pre-requisites for PAD The PAD feature is supported both on Windows and Linux thin client systems. For any device to become a master device there are certain pre-requisites. All Linux devices are PAD capable and can become master devices. For Linux devices to become PAD capable, make sure that you download and install the latest released version of the OS image on the Linux device. This image should be a PAD Capable image. You can download the image from the Dell Wyse Support Site.
4 After you configure the device to be PAD capable, the PAD Capable flag is set to Green as shown below: Figure 45. PAD Capable Making a Windows Device Repository Capable To make a Windows device Repository capable: 1 Deploy PADService_SysprepScript_WES7 on the WES7 device. 2 Deploy PADService_SysprepScript_WE8S on the WE8S device. 3 Deploy PADService_SysprepScript_WIE10 on the WIE10 device. To confirm whether the device is Repository capable or not: 1 In the Device page, select any device.
Figure 47. Repository capable Creating PAD Capable Images for Windows Devices To create a PAD capable image for WES7, WE8S and WIE10devices: 1 Set the device check-in interval to at least one hour in the WDMVXC-M GUI Preferences. 2 Log in to the device as an Administrator, disable the Write Filter, log out , and log in again as Administrator. 3 Delete the HagentSettings.ini file from C:\Program Files\Wyse\WDA\configC:\Program Files\VXC-M and run the following command in the command prompt for WES7 dev
Figure 48. Peer Assisted Deployment To configure PAD on WDM: 1 On the WDM Console, select System → Peer Assisted Deployment. 2 Specify the minimum number of required peer capable repositories as One or Two. 3 Change the maximum number of simultaneous connections to the master device if required. The default number of simultaneous connections is 7. 4 Change the maximum number of retry count to the master device if required. The default number of simultaneous connections is 3.
Figure 49. Deploy via peers 3 From the drop-down list, select your preferred platform. 4 Enter the start date, end date and timings in hh:mm:ss format to schedule a deployment. 5 Enter the subnet IP to select from the available subnets. NOTE: At least one subnet need to be selected for creating PAD schedule. 6 Click Deploy. Viewing PAD Details You can view the PAD details such as the PAD schedules, the clients that have been selected as Master repositories, and the image update process summary.
Figure 50. Repositories 3 To view the PAD schedules, select Jobs under Peer Assisted Delivery. The list of package deployment schedules are displayed. Figure 51. Jobs 4 To view the PAD Image update process, select Summary under Peer Assisted Delivery. The progress is displayed.
Figure 52. Summary Editing and Deleting PAD Schedules You can edit and delete PAD schedules on the WDMVXC-M console. 1 To edit a PAD schedule: a On the WDMVXC-M console, expand Peer Assisted Delivery under Updates and select Jobs. b The jobs are displayed. Select a job, click the three dots displayed and select Edit. The Edit window is displayed. Figure 53. PAD Edit c Change the date and time ranges as required and click Save. The scheduled job displays the new date and time.
b The schedule summaries are displayed. Select a summary, click Delete tab. The schedule is deleted. Wyse ThinOS This parameter helps you to view the WTOS INI root path. Figure 54. Wyse ThinOS • WTOS INI path upon checkin : Select to allow WDM to use FTP, HTTP, HTTPS, or CIFS when updating devices. • WTOS INI Root Path : Enter the WTOS INI root path.
9 Management of Teradici device using WDM Pre-requisite: Make sure you have already installed a WDM server with ThreadX support for the 5.x firmware. This section provides the information about the infrastructure changes needed for devices to discover, and register with management servers including Wyse Device Manager (WDM).
Figure 55. DNS SRV record 2 Select Service Location (SRV) from resource record type list. Figure 56. Resource Record Type 3 Click Create Record... option.
Figure 57. New Resource Record Table 4. 5 Parameter Description Domain delldemo.int Service _pcoip-tool Protocol _tcp Priority 0 (Zero) Weight 0 (Zero) Port Number 50000 Host offering this service Enter the the name or IP address of the WDM server Click OK. NOTE: A trailing . is automatically added to the host line by windows. Monitoring and Troubleshooting The easiest way to monitor the device is using the web UI of the device and the event logs.
Figure 58. Log In 3 Select Diagnostics option. Figure 59. Diagnostics 4 74 Enable the event log option to configure the diagnostic logging options.
5 Select the radio button of Management Console option. 6 Click View option to view the event log messages. Figure 60. Event Log 7 Search for DNS SRV information from the log and specifically for MGMT_DISC_DNS. In this example search for properly discovered intended WDM server which has the name dell-wdm55.delldemo.int and IP address of 192.168.251.65 Figure 61. Logs 8 Check your management console (WDM) to confirm that the device is appearing or listed. Figure 62.
Figure 63. 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 64. 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 76 Click the domain node (delldemo.
Figure 65. Create TXT record 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 66. 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 67.
Figure 68. 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 69. 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 70. Downloading Certificate 9 Copy the sha256 fingerprint value. Click Close and cancel all the firefox windows.
Figure 71. 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 72. tcmc2 Properties 10 The fourth and final record is a reverse PTR record for the management host. Figure 73. PTR Record 11 The zone must match the subnet that the host is in, and the record is the IP address assigned to the management console. 12 Once the DNS_SRV configuration is done, refer to Upgrading Teradici firmware from 4.x to 5.x using WDM for upgrading the firmware. Upgrading the ThreadX 4.x devices to ThreadX 5.
NOTE: Cert.pem is used to create certificate package and deploy to the ThreadX 4.x clients. Before upgrading the ThreadX devices, use the following guidelines: • To discover ThreadX devices using DNS SRV record: Adding the DNS SRV Record • To deploy the certificate to ThreadX 4.x devices :Deploy the certificate to ThreadX 4.x Devices • To upgrade the ThreadX devices: Upgrading the client firmware to ThreadX 5.x Deploy the certificate to ThreadX 4.x Devices To deploy the certificate to ThreadX 4.
Figure 74. RSP package folder 4 Rename the folder name as number value in the .rsp file. 5 Place the .rsp file outside the folder. NOTE: The file name of .rsp file, package folder name, and number value must be same. Figure 75. RSP package folder After deploying the created RSP package through WDM as described in the Deploying Teradici image version 5.x from 4.x firmware using DDC in WDM and Deploying Teradici image version 5.x using selected devices in WDM, the client checks in to WDM as a 5.
Figure 76. CIFS After testing the CIFS connection, add the following accounts to Rapport ftp folder, and share permissions on the machine where WDM repository is configured: • System account of the server where ThreadX 5.X component is installed. • User account that is used to install WDM. NOTE: If the repository is installed on a different server, then add the computer account of the ThreadX 5.x server instead of system account, along with the user account.
Figure 77. Rapport Properties 4 In the Advanced Sharing dialog box, click Permissions.
Figure 78. Advanced Sharing 5 88 Click the Add button, and give full permissions to the above mentioned users.
Figure 79. Permissions for Rapport Deploying Teradici image version 5.x from 4.x firmware using DDC in WDM To deploy the Teradici image version 5.x from 4.x firmware using DDC in WDM, do the following: 1 Open WDM Web UI and login as administrator. 2 Go to System > Console, and enable Default Device Configuration (DDC), and click the Save button. 3 Go to Updates > DDC, and click the+ button to add new DDC. 4 Select ThreadX as operating system from the Select Operating System drop-down list.
Deploying Teradici image version 5.x using selected devices in WDM To deploy Teradici image version 5.x using selected devices in WDM, do the following: 1 Open WDM Web UI and login as administrator. 2 Go to Applications > Images, and click the + button to download the package registration utility 3 Click the RSP button from the package registration utility. 4 Click the Browse button, and upload ThreadX 5.x firmware package to WDM. 5 Go to WDM Web UI again, and go to Devices page.
10 Troubleshooting This section provides troubleshooting information for WDM.
4 Subnet and IP ranges are defined correctly (when you are attempting to discover devices by subnet or IP range) You can also run the DNS_DHCP_Lookup Utility to verify if the WDMVXC-M server is reachable or not. Problems with Discovering PXE Devices Problem: You are having problems with discovering PXE devices.
To run the HTTP Application Manually: 1 Launch the command prompt on the system where you have installed WDMVXC-M. 2 Type the following command: Wyse-Http-server.exe –u < Username> –p –Po where — u is the user name for basic authentication, —p is the password for basic authentication, and —po is the port number on which the HTTP Application is running. Peer Device is unable to download an Image file If the peer device is not able to download the bios.img or the cmos.
If repository test connection fails in case of FTP, make sure the following settings are as per requirement for repository to work: • FTP service is up and running. • FTP site is created. • FTP site has “Read” and “Write” permission for all users with “Basic” and “Anonymous” authentication. • Try to connect to FTP using command prompt. • ftp • It will ask for the password and will connect to the FTP directory.
Tips when Transfer Type is CIFS: If repository test connection fails in case of CIF, make sure the following settings are as per the requirements for the repository to work. • The Rapport folder is shared • The Rapport folder has Read and Write permission for Everyone or specific users. • Enter the hostname/domain name, user name and password to access the shared folder, and try to connect. Troubleshooting T50 and WTOS Errors When T50 devices are checking in the WDMVXC-M 5.
Click Accept to continue. Troubleshooting WCM Issues When you use WCM from WDMVXC-M to create configuration files to be deployed to devices, you may come across the following issue: When you select all the configuration items and create the configuration.xml file, the relative path is missing from the XML file. The solution for this issue is that when you create WCM packages, you must not have any space in the file name. For example, if you want to name your configuration file as WCM Config.
PAD Imaging and Drag and Drop Features Not Working on Linux Devices Problem: The package drag-and-drop feature and PAD Imaging does not work on SUSE Linux devices with the MR3 build and the latest WDM Agent version 5.3.06, when Windows Authentication is enabled on WDM with the HTTPS protocol enabled in the software repository. Solution: Enable Basic Authentication in IIS Manager or change the protocol to CIFS in the software repository.
Devices not checking in Japanese OS Problem: If we have Hagent older than 6.3.2.54 in the devices then devices will not check in to Japanese OS. Solution: Update the Hagent to latest and then discover the devices in the WDM Server (Hagent should be greater than or equal to 6.3.2.54). After Upgrading WDM from version 5.5 or MR to 5.7 Application Failure Issue: When you start the WEB UI after Upgrading the WDM from version 5.5 or MR to 5.
4 Apply the settings and start the Application pool to run the WDM Web UI to see if the application starts. • 5 If the application shows login screen, follow Step-5. Now follow the steps 1 to 2 and change the Identity of the ASP.NET v4.0 App pool to the original setting, there is a prompt to enter the password and confirm it. After entering the password, apply the settings and start the app pool. Once this is done, start using the Web UI.
ThinOS device stops check-in to the WDM server Problem: ThinOS device stops check-in to the WDM server, due to untrusted certificate and then you can’t manage it. Solution: We need to send the following ini setting to the device in order to make it work: securitypolicy=low Steps to deploy it to the device: • Create a folder named wnos in ftp location. • Create an ini file with the name wnos.ini in the wnos folder and in the ini file add the content as securitypolicy=low.
Solution: Refresh the browser to see the login page. Issue While logging in to WEB UI Problem: Login to WDM Web UI is not possible, If the WDM server is joined to the Windows Server 2012 domain controller. Solution: The GetAuthorizationGroups() function fails on groups (SIDs) which are added to you by default, when a 2012 domain controller is involved. Installing KB2830145 on the WDM server will resolve the issue.
OSD Logo Configuration/Firmware Push Failure on ThreadX 5.X Devices Problem: Failed to push OSD logo configuration or firmware upgrade. Solution: Make sure Software repository test connection for CIFS is successful. Add the following accounts to rapport folder sharing permissions: • System account of the server where ThreadX 5.X is installed. • User account which is used to install WDM.
Figure 81. Advanced Settings 7 Right click the ASP.NET v4.0 application pool and click Start. Manually configuring the ThreadX 5.X devices using teradici client management console when automatic way does not work Pre-requisite: Make sure that EMSDK and ThreadXApi are installed and running successfully on the device. 1 On the management console of ThreadX device, select Upload Menu > Certificate, and browse for the certificate cert.pem installed at \WDM\TeraDici\cert.
Figure 82. Certificate Configuration Screen Figure 83. Certificate Upload Screen 2 The successfully uploaded certificate is listed in the Certificates Upload section. 3 In Configuration menu of the ThreadX devices management console, select Management sub menu > Security Level > High Security Environment – Bootstrap phase disabled option.
Figure 84. Management Screen In the Internal EM URI field, provide the uri of the EMSDK server as wss://
