Wyse WSM 2.3 Release

External Release Notes

Date: 04/06/2009

©2009, Wyse Technology Inc.

All rights reserved. No part of this work may be reproduced or used in any form or by any means without the prior written permission of Wyse Technology.

WSM 2.3 External Release Notes

______________________________________________________________________

WSM V2.3 Page 2 of 5

Wyse Technology

WSM V 2.3 The Wyse WSM v 2.3 is a maintenance release for the product.

Software Features The following new features were added to this release:

• WSM Appliance Wyse R90LE with a hard drive, running a preconfigured WSM on XP Embedded.

• Moving Servers

Ability to move a server from one WSM installation to another WSM installation (includes the ability to convert a WSM Appliance into an Edge Server of another WSM installation).

• Enhanced Handling of Devices that are Forcibly Powered-off

o Client will be treated as "down", and resources will be released (files are closed, not deleted), if the client does not send a heartbeat for a “significant” length of time.

o Heart-beat timeout values are configurable from the System Settings page of the WSM Administrators Console.

o Devices will be shown as "Disconnected" (to distinguish them from "Down"). o If the device does reconnect (for example, a network cable is unplugged and reconnected later), it

will reconnect normally - assuming the administrator did not delete the OS image or WC file (or change the image assignments and so on).

• Easier Device Additions

Devices can be added to an OU that is different from the computers container (in the past a template was required to add devices to a non-default OU).

• WSM Prerequisites Package

SQL Express and dependencies are installed and configured automatically (using one installation wizard) to meet all your WSM SQL Server needs.

• Improved Integration with Virtual Center

o Multiple templates can be added to a single virtual center. o Ability to specify the Data Center and Folder under which the virtual machine is to be created. o Automatic prompt for the prefix, start serial no and number of the virtual machines while creating

the virtual machines (in the past the template name was used as a prefix and stored with the last used sequence number and did not allow administrators to modify it).

o Addition of flags that can enable and disable a Virtual Center Server Certificate validation process (this will allow the default certificate to be usable for an SSL connection).

• DHCP Proxy and TFTP Service

DHCP Proxy and TFTP Proxy now run as background services in the Admin Service of the WSM Core Server (no need to rely on external TFTP servers).

• WSM Self Diagnostic Feature for Hostname and IP Address Changes

If the Hostname or IP Address of a server is changed, WSM will attempt to automatically detect and reconfigure itself: o IP address of an edge or core server is changed — If the IP address of an edge or core server

changes, there is an automatic update of the corresponding WSM Data. If for any reason this automatic update fails, a message is displayed in the overview page to reflect this inconsistency.

WSM 2.3 External Release Notes

______________________________________________________________________

WSM V2.3 Page 3 of 5

Wyse Technology

In this situation, you must reconfigure the system manually according to your required configurations (for configuration guidelines, refer to the Administrators Guide: Wyse WSMTM).

o Name of an edge or core server is changed — If the name of an edge or core server changes, there is an automatic update of the corresponding WSM Data. If for any reason this automatic update fails, a message is displayed in the overview page to reflect this inconsistency. In this situation, you must reconfigure the system manually according to your required configurations (for configuration guidelines, refer to the Administrators Guide: Wyse WSMTM).

o Hostname of the SQL Server machine is changed — If the hostname of the SQL Server machine is changed, the SQL Server must be reconfigured to continue to function correctly. If your SQL Server is on the same machine as your WSM Server software and you have used the default WSM password (password@123), then WSM will automatically reconfigure the SQL Server. If for any reason this automatic update fails, or the SQL Server is installed on a different machine than your WSM Server software, a message is displayed in the Overview page to reflect this inconsistency. Use the link provided in this message to open a page where you can enter a username and password and make this update manually. WSM will then reconfigure the SQL Server.

• SQL 2008 Support

SQL 2008 is supported in this release. Notes for this Release:

• This release supports fresh installations and upgrades from versions 2.0.0, 2.1.0 and 2.2.0. • All application images are compatible between WSM versions. Existing application images packaged

in WSM 1.1, WSM1.2.X and WSM 2.X.0 can be deployed on WSM 2.3.0 without issue. • Upgrades from WSM 1.2.2, WSM 1.2.3 and WSM 1.2.4 are not supported in this release.

New Installations

Use the following guidelines: • Extract all the files from the WSM download (WSM V 2.3.0_RTM_WYSE.exe). • Follow the steps as described in the WSM Installation Guide.

Upgrading Existing Installations – Servers

Use the following guidelines to upgrade your existing server installation: Ensure that the base installation of the WSM server is version 2.0.0 or 2.1.0 or 2.2.0 before you

proceed with the 2.3.0 upgrade. Refer to the 2.0.0 or 2.1.0 or 2.2.0 release notes for details on the installations.

Extract all the files from the WSM download (V 2.3.0_RTM_WYSE.exe). Upgrade the Core Server before other servers.

o Run WSMServer.exe on the core server. This will upgrade the existing Core Server software to the latest version of WSM 2.3.0).

o For details, refer to the WSM Installation Guide. Upgrade each Edge server in your installation.

o Run WSMServer.exe on all of the edge servers in your installation. o For details, refer to the WSM Installation Guide. o Note: If a message box pops up indicating that the edge server is not able to read data from

the Core Server’s registry, click OK and continue with the upgrade process. If you are using Active Directory (AD) integration, but not using certificates for secure communication

between WSM servers and AD, perform the following step on all WSM servers: o Change the OS Authentication service to run with the credentials of a user with Account

Operator privileges, and restart the service.

WSM 2.3 External Release Notes

______________________________________________________________________

WSM V2.3 Page 4 of 5

Wyse Technology

Upgrading Existing Installations – Clients

Ensure that the base installation of the WSM Client OS Image is version 2.0.0 or 2.1.0 or 2.2.0 before you proceed with the 2.3.0 upgrade. Note: This release only supports upgrades from the following WSM releases:

o WSM 2.0 o WSM 2.1 o WSM 2.2

Installing Microsoft SQL Server Using the WSM Prerequisites Package

In most cases, you can install an SQL Server on the same machine as the Wyse WSM servers for a single-server installation. To do so, it is highly recommended that you use the WSM Prerequisites Install Shield Wizard (using the WSM_Prerequisites.msi file) to easily and automatically install everything you need for an SQL Server 2005 Express installation (including Microsoft .Net Framework 2.0). Simply double-click the WSM_Prerequisites.msi file and follow the wizard. CAUTION: During the WSM Prerequisites Install Shield Wizard installation, do not close the Ready to Install the Program window (which continues to show in the background during installation) and do not click Install more than once. Doing either of these will prevent a successful installation

Supported Hardware Platforms

The following platforms are supported: • Wyse V00L • Wyse R00L • Wyse R00LE • PCs, other hardware platforms and virtual machines that satisfy the minimum requirements for a

WSM client

Supported Operating Systems - WSM Server

• Microsoft Windows 2000 Server family • Microsoft Windows 2003 Server family • Microsoft Windows 2008 Server family • Microsoft Windows XP Sp2 or Sp3

Supported Operating Systems - Client Devices

• Microsoft XP Professional with no Service packs • Microsoft XP Professional with SP1 or SP2 and Sp3 • Vista Enterprise Edition with no service pack ( Experimental) • Vista Enterprise Edition with Sp1 ( Experimental)

Supported Databases

• Microsoft SQL Server 2000 with SP4 • Microsoft SQL Server 2005 • Microsoft SQL Server 2005 Express • Microsoft SQL Server 2008

WSM 2.3 External Release Notes

______________________________________________________________________

WSM V2.3 Page 5 of 5

Wyse Technology

Limitations and Known Issues

• When using Kerberos Authentication, note that the username is case sensitive while adding a domain.

• Kerberos Authentication does not use the default administrator account for adding a domain. Any other user, with Account Operator privileges can be used.

• The Found New Hardware wizard may appear during installation of the WSM Client software on Windows XP. In such a case, select the No, not this time option to close the window, and then click Next to continue the WSM Client software installation.

• After a WSM Core Server upgrade from v2.0 to v2.3, if you reboot the clients a from streaming server that is not yet updated to v2.3 the boot status for the clients shows ‘Booting’ when viewed in the Administrator Console (the clients will continue to work, however). In addition, the Active Server and Active Image status will also show as not updated in the Administrator Console. After upgrading these servers, all server status will be updated in the Administrator Console.

• While upgrading or uninstalling WSM from Windows 2008 you may receive the following error message to which you can safely click OK and continue upgrading or uninstalling: