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.......................................................................................................................
8 Reports........................................................................................................................................................53 Creating a Log Report..................................................................................................................................................... 53 Creating an Application Report......................................................................................................................................
VNC Log Not Generated................................................................................................................................................ 114 ‘Update Now’ window is not displayed to the user for WCM-Linux.........................................................................114 Not able to push pulled image back to T50 device.....................................................................................................114 PCoIP Language package deployment failed..........
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 - WDM allows you to easily build and administer a repository of software, images, and configuration updates for distribution.
• Expanded Hierarchical Views - Expand the visual device management capabilities of your WDM server by using this feature to create up to a total of 30 different organizational views of your devices. • Automated Grouping - This feature is used to automatically place any new device that has been added to the system into the predefined groups that you want.
• 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 with PCoIP 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 3020 zero client for Citrix • Wyse 5010 zero client for Citrix • Wyse 3010 thin client with Linux ThreadX/View Zero Client: • Wyse 5030 zero client • 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
• C10LE • R10L Wyse Enhanced Microsoft Windows Embedded Standard 2009 (WES2009) build 641 or later: • C90LEW • 5010 • R90LW • R90LEW • V90LEW • X90CW • X90MW • 7010 • Z90SW Dell Wyse technical support To access technical resources self-service portal, knowledge base, software downloads, registration, warranty extensions/ RMAs, reference manuals, and so on, visit www.dell.com/wyse/support . For Customer Support, visit www.dell.
2 Accessing WDM To access WDM UI, do the following: 1 Open the supported browser for WDM UI. The following are the supported web browsers for accessing the WDM web UI. 2 • Internet Explorer 11 • Chrome v40 and later versions • Firefox v43 and later versions In the browser, enter the following URL: https:///WebUI/app/indexf.html# 3 Press Enter.
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.
Dashboard
• Device Health • Jobs The date and time for the last checked-in server is displayed. You can also view the system updates by clicking the following tabs on the upper right corner of the Dashboard page: • Alerts • Events You must have the administrator privileges to select, deselect and delete the updates. Steps to delete alerts or events is as follows: • Select an alert or event. • You can select or deselect the entire list of alerts or events by clicking Select all or Deselect all.
Parameter Description NOTE: For Threadx 5.x devices, it displays the following warning alerts when it reaches full capacity per Teradici Proxy server available in the WDM deployment. • • Events At 15000 devices, it displays full capacity alert. At 18000 devices, it displays an error alert. In the upper right of the dashboard screen, you can view the list of events or actions performed such as Device manually added, Real time commands, Distributed package and so on.
2 Enter the license in 7 characters-6 characters-6 characters-7characters format or copy-paste the license. 3 Click Save. Activating workgroup license 1 Select the non-activated workgroup license. 2 Click Activate License on the right corner of the license page. NOTE: Make a note of your non-activated license to use in the online WDM licensing form. You can also copy and paste the non-activated license in the online WDM licensing form.
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.
Importing data using import utility In the WDM Common Utilities section, you can import data from comma-delimited and tab-delimited files. This utility allows you to import devices, subnets, IP ranges, repositories, or default groups for subnets from a file into the WDM database. The data must be imported from flat files. A delimited flat file contains one or more records separated by a specified delimiter or separator such as a comma or a tab.
• Windows Embedded 8 Standard 64 - WE8SEmbedded 8 Standard 64 — WE8S • Windows 10 IoT Enterprise — WIE10 An example for device settings data is as follows: D90Q8;A02040401050;5020;XYZ;MN;OP;WE8S;W1009341019;0080646A1144;VX0;ABCD;EFGH;IJKL;Administrator ;San Jose Office;WES Format for importing subnet data from flat files The format to provide data in a flat file for subnet is as follows: Broadcast Address, Description, SW Repository, Override Default Parameters, IP Address, Subnet Mask, Max.
The IP range definition is added to the database to discover all devices between the ranges of 10.10.10.10 to 10.10.10.19 and 10.10.10.31 to 10.10.10.200. This IP range definition shows up in the WDM GUI as My IP Range.
The software repository definition is added to the database to define a repository on a server at 10.10.11.9. The default path for the root directory of the FTP service is /rapport. This repository is accessed with the username of the user. The FTP is used as the transfer protocol and is displayed in WDM as remote.
2 3 • Database Name — The name of the WDM database. • User Name— The user name to access the WDM database. This is the user name you have specified while installing WDM. To change the credentials to access the database: a Enter the new User Name under New credentials for WDM database. b Enter the Password to access the database. c Re-enter the password in the Confirm Password field. d If you want to use your domain user name and password, select Connect as domain user.
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 3. 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 4. 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 30 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.
• 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. This package can be used to update the existing HAgent to the HAgent version incorporated in WDM. • WIE10WDAAgentUpgrade— This package can be scheduled only to the devices running WIE10 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. Table 6.
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 38 • 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.
Figure 21. System Version 5.X Table 9. 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.
To Enable the setting, the Timeout range is 10 to 14400 seconds and to disable enter 0. • RDP This option is applicable only to ThreadX v4.X Provide the RDP connection details. Reboot This option is applicable only to ThreadX v5.X. Select this check box along with the Company Logo check box. This results in rebooting of the ThreadX device after deploying the package that contains the Company Logo. Connections Figure 22. Connections Table 10.
• • • • • Port number Domain User Name Password Certificate Check Mode Based on your requirement, select the following check boxes: • • PCoIP or VMware • Certificate Check Lockout Mode Enable Session Disconnect Hotkey You can select the server type as PCoIP or VMware. A maximum of 25 servers can be added for both PCoIP as well as VMWare. Security Figure 23. Security Table 11. Certificate Select the option to enter the content of the certificate.
Reset Administrator Password • If you want to reset the password of the device administrator, then select the option and provide the new password. Session (Version 5.X) Figure 24. Session Table 12. Imprivata OneSign Select this option to enable Imprivata OneSign. Disable Imprivata OneSign Select this option to disable Imprivata OneSign. Bootstrap URL Enter the Bootstrap URL in the provided field. OneSign Pool Name Mode Select the preferred option.
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.
• 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 27. 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 28. Repository Sync Peer Assisted Delivery In this category, you can view the details of the Peer Assisted deployment schedule for Subnet.
Figure 29. Peer Assisted Delivery Profiles The Profiles page enables you to deploy a predefined configuration on a specified group of devices. You can create the configurations by using the Dell Wyse Configuration Manager (WCM) and save them in a specified repository. A repository is a system where the configurations are saved. Thin client devices connect to these repositories through HTTP , FTP, or CIFS and download the configurations.
2 Click the view details option and check the capabilities section. 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: You can only create one profile for a particular operating system at any given point. If you want to create another profile for the same operating system, you must delete the existing package and create a fresh one.
7 Default Device Configuration (DDC) WDM allows you to easily create and manage DDCs. You can apply Images or multiple Software packages or both to the devices using DDC. DDC ensures that all the device in the Group where DDC is assigned will have same Images or Configurations assigned. This parameter helps to add new Default Device Configuration (DDC) and provide the details such as, Groups, Image, Packages, and Execute DDC Figure 31.
Figure 32. 7 Select a software package from the packages drop-down list. 8 Specify Execute DDC either Device Checks in or Every Day at Specific Time. 9 Click Save.
8 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 WDM server related to WDM components. It allows you to easily see what you want, when you want it.
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. The saved reports can be edited or deleted as per your requirement.
Figure 35. 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.
9 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 36.
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 37. Registering Remote Repositories You must configure the following points before you register remote repositories: • WDM 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 WDM 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 38. Accounts NOTE: Before you can add a WDM user, the user must already exist in the list of users for the Windows Domain where you installed WDM. To add a user from a local computer account: 1 In the WDM Console, expand System. 2 Select the name of the user you want to add as a WDM user and click Add. 3 Click OK to add the new user to the list of WDM users. NOTE: New users do not have permissions until you edit the user permissions.
NOTE: If It is an upgrade setup from the previous version of WDM, you must reassign the permissions for all existing users before using WDM 5.7.2. Figure 39. 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.
Figure 40. Devices Table 14.
Devices Remote shadow Reboot Shutdown Refresh Device Send Message Execute Commands Wake On Lan Relay Wake On Lan Exclude from PAD Repository Include in PAD Repository Create and View Log Get Device Log Get Image Figure 41.
Table 15. Applications Applications Create Packages Modify Packages Distribute Packages Configure Packages Register Packages View Packages Script Export Packages Disable distribution Deploy via peers in subnet Create new configuration Save script Edit Config Figure 42. System Table 16.
Figure 43. License Table 17. License License Add License Remove License Figure 44. Utilities Table 18.
Figure 45. Reports Table 19. Reports Reports Create Reports Figure 46. Updates Table 20.
Updates Move to error Delete Job Reschedule Job Roll to boot Delete recurring update Delete real time command Delete repository sync Delete PAD Move to error(PAD) Deploy via peers Reschedule PAD Deleting Users As an administrator you can delete WDM users. NOTE: You cannot delete yourself as a user. To delete a user: 1 In the WDM Console, expand System and click Accounts to view the list of WDM users. 2 Select the check-box of the user you want to remove from the list of users, and select Delete.
Figure 47. Console 1 Enter the following details: • 70 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.
• Custom Group Folders - Select this option if you want to view empty folders in the Device Manager when you create userdefined groups for your Device Views. • HA Proxy Server- Select this option if you want to add or update a new HA Proxy Server. Enter the name and port details in the provided field to add or update a new HA Proxy Server. • Remote Sessions- This option is applicable to Windows, Linux, and Thin OS (WTOS) devices, where you have configured remote sessions .
Figure 48. Console • Teradici Device Proxy Server - Select this option to add a new server or update the existing server. Default Device Configuration - (WDM Enterprise Edition only.) This option allows you to automatically distribute software packages to your thin client devices. Assigning DDCs to group of devices ensures conformity and allows you to target functional area of enterprise with tailored imaging and configuration.
• 4 Schedule DDC Reconciliation at: Enter the time. Click Profile Manager in the Device Manager tree to start Profile Manager Preferences window. Profile Manager enables you to deploy a predefined configuration on a specified group of devices. You can create the configurations using Dell Wyse Configuration Manager (WCM). 5 Specify the following details: a Select Enable Profile Manager in the Profile Manager Preferences pane. b Click OK to save your settings.
Figure 49.
• 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 option 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.
Figure 50. Services • TFTP Server: Enable this option to allow WDM to use Trivial File Transfer Protocol (TFTP) when updating the device. • 76 TFTP Mount Point: Displays the TFTP mount point that WDM set during installation. Typically, this is the TFTP root directory (WDM) below the FTP home directory used by the Master Repository.
• • TFTP time Out: Specify the time interval (in seconds) that device waits for a connection to the TFTP service before attempting to reconnect. • TFTP retries: Specify the number of times that device will attempt to connect to the TFTP service before failing. Wake On Lan: Allows you to wake up devices that are in sleep mode or are shut down. • Set the Wake On Lan tries. The number of times that the service attempts to perform a WOL command before stopping and the Delay between WOL Retries (Secs) .
• • • • Debug: Consisting of all information in Errors, Warning, Informational, and additional debugging data that might be useful to WDM developers, sales engineers, and administrators. Web Services: Details the activity of the WDM Web Services for device management. DHCP Proxy: Details the activity of the WDM Dynamic Host Configuration Protocol as it discovers the device. TFTP: Details the Trivial File Transfer Protocol activity for distributing software packages to devices.
• SUSE Linux • ThinLinux • Windows Embedded Standard 2009 • Windows Embedded Standard 7 (WES7) • Windows Embedded Standard 8 (WE8S) • Windows 10 IoT Enterprise The following diagram and workflows best describe the working of the PAD functionality. Workflow from the WDM 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.
• Deploying a Package Using PAD • Viewing PAD Details • Editing and Deleting PAD Schedules 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.
Figure 53. PAD Capable 4 After you configure the device to be PAD capable, the PAD Capable flag is set to Green as shown below: Figure 54. 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.
Figure 55. Repository capable 4 After you configure the device to be Repository Capable, the Repository Capable flag is set to Green as displayed below: Figure 56. Repository capable Creating PAD Capable Images for Windows Devices To create a PAD capable image for WES7, WE8S and WIE10 devices: 1 Set the device check-in interval to at least one hour in the WDM GUI Preferences. 2 Log in to the device as an Administrator, disable the Write Filter, log out , and log in again as Administrator.
6 Log in to the system where the WDM console is running, and right click on a schedule from Update Manager > Schedule Packages. 7 Select the Roll to Boot option. 8 For WES7 devices, press the P key, and boot the device through the PXE LAN mode. For WE8S and WIE10 devices, press the P key, and boot the device through Merlin Non-PXE mode. 9 After the image is pulled, deploy the pulled image using the Deploy via Peers in Subnet option.
• Windows 10 IoT Enterprise Deploying a Package Using PAD To deploy a image with PAD: 1 On the WDM Console, select Images under Application. The registered images are displayed. NOTE: PAD can only deploy images, not application packages. 2 Select an image, click and select Deploy via Peers tab. The Deploy via peers window is displayed. Figure 58. Deploy via peers 3 From the drop-down list, select your preferred platform.
Figure 59. Repositories 3 To view the PAD schedules, select Jobs under Peer Assisted Delivery. The list of package deployment schedules are displayed. Figure 60. Jobs 4 To view the PAD Image update process, select Summary under Peer Assisted Delivery. The progress is displayed.
Figure 61. Summary Editing and Deleting PAD Schedules You can edit and delete PAD schedules on the WDM console. 1 To edit a PAD schedule: a On the WDM 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 62. 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 63. 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.
10 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 64. DNS SRV record 2 Select Service Location (SRV) from resource record type list. Figure 65. Resource Record Type 3 Click Create Record... option.
Figure 66. New Resource Record Table 21. 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 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 67. Log In 3 Select Diagnostics option. Figure 68. Diagnostics 4 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 69. 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 70. Logs 8 Check your management console (WDM) to confirm that the device is appearing or listed. Figure 71.
Figure 72. 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 73. 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 74. Create TXT record 2 94 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 75. 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 76. General Tab 3 In the left pane of the Options page, click Advanced tab and then click Certificates option.
Figure 77. 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 78. 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 79. Downloading Certificate 9 98 Copy the sha256 fingerprint value. Click Close and cancel all the firefox windows.
Figure 80. 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 81. tcmc2 Properties 10 The fourth and final record is a reverse PTR record for the management host. Figure 82. 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 83. 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 84. 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 85. 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 86. Rapport Properties 4 104 In the Advanced Sharing dialog box, click Permissions.
Figure 87. Advanced Sharing 5 Click the Add button, and give full permissions to the above mentioned users.
Figure 88. 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.
11 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 WDM 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 WDM. 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.
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 WDM 5.0 security alert messages may be displayed.
Click Accept to continue. Troubleshooting WCM Issues When you use WCM from WDM 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 116 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.
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. EMSDK fails to start due to port number Problem: EMSDK component uses port number 49155 by default for its communication.
• User account which is used to install WDM. To give permission to the user, do the following: 1 Right-click the rapport folder from repository and select properties. 2 Click the sharing tab. 3 Go to advanced sharing option and click permissions. 4 Click the add button and give full permissions to the above mentioned users. ThreadX 5.X devices moves to Offline state Problem: ThreadX 5.X devices are moving to Offline after few days of discovery. Solution: 1 Go to IIS management console.
Figure 90. 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 91. Certificate Configuration Screen Figure 92. 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 93. Management Screen In the Internal EM URI field, provide the uri of the EMSDK server as wss://
