Release Type and Definition

WyseDeviceAgent

(WDA-11.0.0.324)

Release Notes

Contents

Release Type and Definition

Version

Release Date

Previous Version

Importance

Support Information

Supported Platforms

Supported OS Versions

Supported Upgrades

Prerequisites to Install WDA

Post WDA Installation Steps:

Supported Dell Wyse Thin Client Platforms

Key Features of WDA 11.0.0.324

Tested Platforms and Devices

Installer Matrix

Dell Cloud Client Manager (CCM)

Dell Wyse Device Manager (WDM)

Dell Wyse Configuration Manager (WCM)

Add-ons

Upgrading WDA

Downgrading WDA

Troubleshooting:

Known Issues/Limitations.

Software Information

Release Type and Definition

The Wyse Device Agent (WDA) is a unified agent for all thin client management solutions. Installing the WDA on a thin client makes it manageable by Dell Wyse Device Manager (WDM), Dell Cloud Client Manager (CCM) and Dell Wyse Configuration Manager (WCM). This document describes the supported platforms, tested environments, andkey features of WDA

Version

11.0.0.324

Release Date

15-May-2015

Previous Version

N/A

Importance

Dell Wyse recommends installing this version of WDA on Thin Clients to be managed by CCM. To manage the clients from CCM server, it is mandatory to have WDA installed in the clients.

Note: The agent replaces the WCM and WDM agents and is compatible with WCM, WDM (release version mentioned below), and CCM.

Support Information

You can install WDA on all devices with the Microsoft Embedded Standard 7 operating system installed on them.

Supported Platforms

The supported devices for WDAare:

D90D7
D90Q7
Z90D7
Z90Q7

Supported OS Versions

Windows Embedded Standard 7 (FR3 and above).

Supported Upgrades

You can upgrade to WDA:

1)If your WDM is one of the versions listed below:

WDM 4.9.1+HF4
WDM 5.0
WDM 5.0+MR1+MR1.5+MR2 (6.1.1.3, 6.3.2.54)

2)If WCM is one of the versions listed below:

WCM 1.2.0
WCM 1.3.0
WCM 1.3.3

Prerequisites to Install WDA

This section lists the pre-requisites that you must complete to install and configure WDA. When you run the installer on a thin client, it checks for the following:

The operating system on the thin client should be WES7. The installer is supported ona 32–bit OS.
Microsoft Visual C++ redistributable 2012 update 4 should be installed. The installer installs this if it does not find it on the thin client.
Microsoft .NET Framework 3.5 should be installed. The installer does not support automatic installation of .NET Framework and stops if the version is below 3.5.
The version of WCM installed on the thin client. The installer checks the product code for WCM, displays a message to uninstall the previous WCM version (1.2.0, 1.3.0, 1.3.3),and install WDA.
The version of WDM Agent installed on the thin client. The installer uninstalls any version of the WDM agent later than 5.X.X.X and installs WDA.
File based write filter (FBWF) should be disabled for the thin-client to be discovered by any management solution, but should be enabled to apply WCM configuration.
DHCP Option Tags for CCM server, MQTT server, Group Token should be configured for so that the thin-client is automatically discovered by CCM. Similarly, option Tags for WDM and WCM should also be for configured for auto-discovery.

For more information, see the WDA Installation and Configuration Guide.

Post WDA Installation Steps:

After you install WDA, you should install:

WDA_HF_1.0.0.0_X86.exe from the CCM server.This HF contains the latest flash.sys and MS (KB 3014793) hot fix which can be installed from CCM to the clients.
WDA_HF_1.0.0.0_WES7.exeshould be installed from WDM after WDA is installed. This HF contains latest flash.sys and MS (KB 3014793) hot fix which can be installed from WDM to the clients.

Supported Dell Wyse Thin Client Platforms

WDAsupports the following thin client systems for WDM/WCM Functionality:

Thin Client Operating System / Supported Platforms
Wyse Enhanced Microsoft Windows Embedded Standard 7 (WES7) build 818 or later / D90D7
D90Q7
Z90D7
Z90DE7
Z90S7
Z90Q7

WDA supports the following thin client systems for CCM Functionality:

Thin Client Operating System / Supported Platforms
Wyse Enhanced Microsoft Windows Embedded Standard 7 (WES7) build 818 or later / D90D7
D90Q7
Z90D7
Z90Q7

Key Featuresof WDA11.0.0.324

Wyse Device Agent is an integration of WDM, WCM, and CCM agents.

Installing WDA on a thin-client makes it manageable by WCM, WDM, and CCM.
You can configure the thin-client to be managed by any management solution by using the WDA Graphic UI.

For more information, see the WDA Installation and Configuration Guide.

The features of the WDA installer are listed below:

A new user-interface that makes the installer easy to use.
The installer takes the region and group token as the inputs to configure the clientto connect to CCM during a manual installation.
The detailed installation log is created under C:\Program Files\Wyse\WDA\Logs\WDA_Installer. You can view this log to check for any error during installation.

Agent Configuration:

You can now configure the thin-client to WDM, CCMand WCM using the WDA UI present on devices.
The Administrator can configure the DHCP option tag of a particular management solution in the DHCP server and the same is fetched by the WDA agent in the Auto-Discovery mode.
You can enabled and disable the log from the WDA GUI and view the log under C:\Users\Public\Documents\Wyse path

Discovery and Registration:

CCM agent discoversthe CCM tenant and group code from the DHCP server or other local environment settings. This is intended to allow multiple on-site thin-clients to be assigned to the CCM setup of a tenant without requiring them to touch or setup each device individually.The CCM agent looks for DHCP option tags 165 and 166 for the CCM server and the MQTT server,and tag 199 for the group token.
For CCM Group registration, the agent allows registration of the device, using a tenant and group code on the CCM server using any of the discovery methods mentioned above or any of the methods listed below:
Manual Registration - entered by Administrator during install or you can configure the WDA UI for manual registration.
Registration via auto-discovery

Basic thin-client management from the CCM server.
Group policy configuration from CCM or WDM.
Creating Device dependent Factory default Configuration:

Creating a device specific factory default configuration allows the user to define what should be configured as part of the device reset. This configuration is applied every time before applying the actual configuration received from CCM. Applying this factory default helps to ensure that the device is refreshed and it appearsthough it is configured with only policies created in the server.

Note: This implementation is only valid for CCM managed agents. For other Management solutions such as WDM and WCM the factory default configuration will be the default one provided along with those applications.

Discovery retry:

The discovery in WDA is a global discovery. It searches for the management software in the following order - WDM, CCM,WCM.
If a management solution is found then the agent continues with the registration of the thin-client. If the management solution is not found then the agent retries again after waiting for ‘n” minutes and increments by ‘n*2’ and then waits for 24 hours.

After all the methods are exhausted it enters into an idle thread loop which performs discovery once in 24 hours and even the WDM manual discovery is be valid during that time.

Note:The Priority is not configurable from WDA GUI or from CCM GUI.

WDA Upgrade/Downgrade from CCM:

You can upgrade WDA from the CCM server up to N+2 levels where “N” is the current version of WDA.
Similarly you can downgrade WDA from the CCM server up to “N-2” levels where “N” is the current version of WDA.

WDA Upgrade/Downgrade from WDM:

You can upgrade WDA from the WDM server up to N+2 levels where “N” is the current version of WDA.
Similarly you can downgrade WDA can be downgraded from the WDM server up to “N-2” levels where “N” is the current version of WDA.
You can install WDA can be installed on the client where the legacy WDM Agent and WCM services are installed.
It is recommended not toinstall the WDM Agent or WCM component separately on WDA.

WDA Icon in the Systray:

You can start the WDA GUI from the Systray Icon. There is no control panel applet in this release.

Note: Only the administrator can register or unregister the device and change the WyseDevice Agent UI settings. A normal orstandard user cannot change the settings.

Tested Platforms and Devices

Installer Matrix

The WDA installation is tested platforms mentioned below:

Note: CCM functionalities are tested on only Z90D7/Z90Q7/D90D7/D90Q7.

Platforms / WES7 WFR5 builds / WES7 WFR4 builds / WES7 WFR2 builds / WES7 WFR3 builds
Z90S7/D7 / 9.05 build 858 / 9.04 build 855 / 9.02 build 818 / 9.03 build 830
Z90DE7 / 9.05 build 858 / 9.04 build 855 / N/A / 9.03 build 832
D90D7 / 9.05 build 858 / 9.04 build 855 / N/A / 9.03 build 846
Z90Q7 / 9.05 build 858 / 9.04 build 856 / N/A / N/A
D90Q7 / 9.05 build 858 / 9.04 build 856 / N/A / N/A

Dell Cloud Client Manager (CCM)

CCM functionalities are tested with below platforms.

Platforms / WES7 WFR5 builds / WES7 WFR4 builds / WES7 WFR2 builds / WES7 WFR3 builds
Z90D7 / 9.05 build 858 / 9.04 build 855 / 9.02 build 818 / 9.03 build 830
D90D7 / 9.05 build 858 / 9.04 build 855 / N/A / 9.03 build 846
Z90Q7 / 9.05 build 858 / 9.04 build 856 / N/A / N/A
D90Q7 / 9.05 build 858 / 9.04 build 856 / N/A / N/A

Dell Wyse Device Manager (WDM)

WDMfunctionalities are tested with below platforms.

Dell Wyse Configuration Manager (WCM)

WCMfunctionalities are tested with below platforms.

Add-ons

CCM/WCMfunctionalities are tested with the add-ons mentioned below.

Platform OS / Build No. / Citrix Receiver version / VMware Horizon view version / RDP version / Internet Explorer
WES7 / D90Q7
(858) / 14.0.0.91 / 5.4.0.1219906 / 6.2.9200.16398 / 10.0.9200.16635
Z90Q7
(856) / 3.4.0.29577 / 5.3.0.1042023 / 6.2.9200.16398 / 10.0.9200.16537
D90D7
(858) / 14.0.0.91 / 5.4.0.1219906 / 6.2.9200.16398 / 10.0.9200.16635
Z90D7
(858) / 14.0.0.91 / 5.4.0.1219906 / 6.2.9200.16398 / 10.0.9200.16635

Upgrading WDA

This is the first release of WDA which has the capability to upgrade to future releases of WDA.

You can upgrade WDA can be to n+ 2 levels where "n” represents major version of the WDA installer.

The supported upgrade version will be up to 2 major versions.

Example:

WDA Released versions – 11.0.0.200, 12.0.0.100, 13.0.0.0, 11.1.0.200, 14.0.0.100

Upgrade / 11.0.0.300 / 12.0.0.100 / 13.0.0.0 / 11.1.0.200 / 14.0.0.100
11.0.0.300 / NS / √ / √ / √ / NS

√–Supported

NS –Not Supported

Downgrading WDA

You can downgrade WDA to n-2 version where "n” represents major version of WDA installer.

The supported downgrade version will be up to 2 major versions.

Troubleshooting:

Scenario / Resolution
Current DHCP configured values are not fetched by the client. / Restart the DHCP client service from the client.
Remote desktop/Citrix/VmWare connections are not launched. / Since you cannot configure Ethernet settings from the CCM server, make sure you configure the correct DNS servers in the remote connection details on the DHCP server.
Device always contains static Ethernet details. / Before registering the client to CCM server, you should configure the proper DNS from the DHCP.
If the static IP or DNS are configured in the client, the same details are captured in the factory default xml. Every time when the clients apply the configuration, the same Ethernet details will be present at the client.
After cancelling the uninstallation of WDA, the Services are in a stopped state and theSystray Icon is not available. / The Windows Rollback feature is available only after the WDA Services are deleted from the target machine.
The Cancel button is an inbuilt functionality of Windows installer,You cannot enable or disable the cancel buttons on the dialogs.
You must start the service manually or restart the machine for the WDA services to start.
WDA cannot be installed when Mcafee antivirus with maximum protection is installed. / Make sure Mcafee is installed with standard protection.
WDA Icon is not found on the systray / Navigate to the path C:/Program Files/Wyse/WDA/Bin, and double-click on DtcWDAClientUI.
If the Server is not reachable, WDA remains in ‘registering‘state for 5 minutes. / Wait for 5 minutes till auto-discovery is initiated.
WDA is making WCM active when it is installed for the first time,without configuring the discovery methods for CCM or WDM,and when DHCP option tags 184 and 185 are configured. / Restart the client after the WDA is installed.
Client starts the discovery and makes the required management active from the configured discovery methods.
Citrix connections are not launched with Enterprise receiver version. (3.4.0) / Install Citrix receiver standard version (4.2.0.10) on the clients.
User cannot Unregister/Register from CCM or from client GUI when MQTT server is not reachable. / If the client GUI is not responding for longer duration, restart the client.
After rebooting the system, client is registered back to the CCM or configured management solution.

Known Issues/Limitations.

STRATUS-9174 / Imported WIFI profiles passwords or network key failed to decrypt
STRATUS-9165 / WDA GUI crashes on a C90L7 device displaying "low on memory error".
STRATUS-9103 / When you clicking on WCMRegister, the status changes to Registeredeven if WCM server not available
STRATUS-9041 / Previous sessions are not getting closed after applying the new configuration from the CCM Server .
STRATUS-8990 / When you upgrade or downgrade the WDA from WDM, only the Update window option is displayed to the user but the 5 mins delay option is not displayed.
STRATUS-8980 / WDA send Managed App Policy Failed Reason: 12
STRATUS-8893 / WES-WDA: Renaming the installer with region code misinterprets the region code.exe
STRATUS-8880 / The Unregister option is displayed on the client GUI when the client is deleted from WDM eventhough the status of the registration is changed to Unregistered.
STRATUS-8849 / After deleting DHCP option tags for CCM, Auto-discovery still registers the client to CCM
STRATUS-8804 / CCM configurations are not getting applied intermittently, it applies only the Facdef xml
STRATUS-8787 / WDM Switch With Wrong IP entered is showing WDA Status as 'Registered to WDM'
STRATUS-8513 / Configurations are not getting applied when device is freshly discovered on WCM.
STRATUS-8223 / You cannot choose Desktop color from Desktop color applet after upgrading to IE11 .
STRATUS-7959 / After cancelling the Uninstallation of WDA , Services are in stopped state and Systray Icon is not available.
STRATUS-7899 / Client "Status" is seen as "Unregistered" when it is joined to Domain and you are logged in as the Domain Administrator.

Software Information

For MD5, use express Checksum Calculator from Irnis.net (

The WDA11.0.0 build 324is available at:

ftp://sjc-vw-prdimg01/BinRapport/WDA

File Name / Description / Version / Build / MD5
WDA_11.0.0.324_x86.exe / WDA package for CCM / 11.0.0 / 324 / 3ABFEE5BBA74E3F6CCB713A2B742F206
WDA_11.0.0.324_WES7.exe / WDA RSP package for WDM / 11.0.0 / 324 / E33A1718D30F30CFC2E286D95F2E8517
WDA_HF_1.0.0.0_X86.exe / HF for CCM / 1.0 / N/A / 11B0B112D66D0CB26C70A839E2E73C45
WDA_HF_1.0.0.0_WES7.exe / HF for WDM / 1.0 / N/A / 346FD58E1D5E56A9A17159EF91EB6BC6

Trademarks used in this text: Dell™, the Dell logo, vWorkspace® , and Wyse® are trademarks of Dell Inc. Microsoft®,Windows® Embedded Standard 2009, Windows® Embedded Standard 7, Windows® Embedded Standard 8, Windows Server®, and Internet Explorer®, are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Citrix®, Xen®, XenServer® and XenMotion® are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/or other countries. VMware®, Virtual SMP®, vMotion®, vCenter® and vSphere® are registered trademarks or trademarks of VMware, Inc. in the United States or other countries. IBM® is a registered trademark of International Business Machines Corporation.

WDA 11.0.0 “Build 324” / Page 1 of 12