WSM 2.3 Installation Guide

Installation Guide
Wyse WSM™ Release 2.3
Issue: 040609
PN: 883875-01 Rev. F
Copyright Notices
© 2009, Wyse Technology Inc. All rights reserved.
This manual and the software and firmware described in it are copyrighted. You may not reproduce, transmit,
transcribe, store in a retrieval system, or translate into any language or computer language, in any form or by any
means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, any part of this publication
without express written permission.
End User License Agreement (“License”)

A copy of the Wyse Technology End User License Agreement is included in the software and provided for your
reference only. The License at http://www.wyse.com/license as of the purchase date is the controlling licensing
agreement. By copying, using, or installing the software or the product, you agree to be bound by those terms.
Trademarks
The Wyse logo and Wyse are trademarks of Wyse Technology Inc. Other product names mentioned herein are for
identification purposes only and may be trademarks and/or registered trademarks of their respective companies.
Specifications subject to change without notice.
Restricted Rights Legend

You acknowledge that the Software is of U.S. origin. You agree to comply with all applicable international and
national laws that apply to the Software, including the U.S. Export Administration Regulations, as well as end-user,
end-use and country destination restrictions issued by U.S. and other governments. For additional information on
exporting the Software, see http://www.microsoft.com/exporting.
Ordering Information
For availability, pricing, and ordering information in the United States and Canada, call 1-800-GET-WYSE
(1-800-438-9973) or visit us at http://www.wyse.com. In all other countries, contact your sales representative.
Contents
1 Introduction 1
About this Guide 1
Organization of this Guide 1
Wyse Technical Support 2
Links to Related Documentation and Services 2
2 Overview 3
Introducing Wyse WSM 3
Wyse WSM Key Components 4
Wyse WSM Services 4
General Overview of the Wyse WSM Setup Process 5
3 Preparing for Installation 7

Recommended Technical Knowledge 7
Planning for Your Installation 7
Pre-Installation Checklist 7
Hardware Requirements 8
Software Requirements 8
System Security and Credentials 9
Server to Server Communication Ports 9
Domain Names 10
Server License Files 10
Installing Microsoft SQL Server Using the WSM Prerequisites File 10
Configuring a DHCP Server 11
4 Installing and Configuring the WSM Core Server 13

Installing the WSM Core Server 13
5 Starting Wyse WSM for the First Time 19

Using the Configuration Wizard 19
6 Installing and Configuring the WSM Client 25

Preparing to Install the WSM Client 25
Installing the WSM Client on Wyse Thin Clients 25
Installing the WSM Client in a VMware Environment 26
Installing the WSM Client 26
Capturing an OS Image to the Core Server 31
Comparing Network and Mobile Mode 33
Configuring the OS Image for Network Mode 34
Configuring an OS Image for Mobile Mode 35
7 Installing and Configuring a WSM Edge Server 37

Installing a WSM Edge Server 37
iv Contents
8 System Maintenance 43
Passwords 43
Logs 43
Backup Recovery 44
System Monitoring 44
9 Upgrading Wyse WSM 45

Preparing for Upgrade Installation 45
Performing the Upgrade 45
Upgrading the Core Server and Edge Servers 45
Upgrading the Client OS Images 46
10 Troubleshooting 49
Verifying if the Database Is Operational and Configured Correctly 49
Verifying that WSM Services are Running 49
Verifying if the ODBC is Operational and Configured Properly 50
Audio Problems in the Streaming Environment 50
Unable to Capture an OS Image after Cancelling the Capture Process 51
Error when Enabling Active Directory for the First Time 51
Error when Installing WSM Client on Windows XP 51
Network Devices are Unable to be Created in the Active Directory 51
HTTP Error:404 /admin/ not found RequestURL=/admin/ powered by jetty 52
Verifying the Status of the Wyse WSM Service Files 52
Reconfiguring an OS Image 53
Hostname and IP Address Changes 55
Uninstalling Wyse WSM Software 55
A Error Codes 57
B Booting Wyse WSM on PXE and Non-PXE Networks 59

Comparing PXE and Non-PXE Boot-Ups 59
PXE and Non-PXE Boot-Up Processes 59
PXE and Non-PXE Boot-Up Requirements 60
PXE and Non-PXE Boot-Up Features 60
Non-PXE Bootstrap Deployment 61
Launching Non-PXE from a Floppy Disk 61
Launching Non-PXE from a Hard Disk or Flash Drive 62
Preparing the Hard Disk or Flash Drive 62
Booting from a Non-PXE Hard Disk or Flash Drive 63
Launching Non-PXE from a USB Key 63
Preparing the USB Key 63
Booting from a Non-PXE USB Key 64
Configuring BIOS to Boot to the USB Key 64
Entering Network Configuration Information for Non-PXE Boot-Ups 64
C Installing Your Own SQL Server 65

Installing SQL Server 2000 65
Installing SQL Server 2005 or SQL Server 2005 Express 66
Installing the Latest Microsoft SQL Server Service Pack 67
Figures 69
Tables 71
1 Introduction
Wyse WSMTM is an operating system and application distribution and streaming
technology that provides a cost-effective method to rapidly deploy and manage operating
systems and applications to a large pool of users. It provides core functions for streaming
operating systems and applications to subscribers.
Wyse WSM main features include:
• Patented streaming operating system and application technology.
• Anti-piracy protection of operating system and application code.
• Usage metrics collection.
• Licensing policies to enforce all operating system and application usage.
• Scalability and built-in fail-over support.
About this Guide

This guide is intended for administrators of the Wyse WSM system. It describes the Wyse
WSM installation process for Windows servers and clients. This guide provides the
step-by-step instructions you need to install and configure a Wyse WSM environment. It
also includes the requirements you must address before you begin the installation
procedures.
This installation guide is intended for experienced network administrators and Information
Technology professionals who have installed and configured Windows operating systems
and applications.
It is recommended that you have the following technical knowledge:
• Working knowledge of Windows Server 2000 and Windows Server 2003.
• Working knowledge of client/server systems and technologies.
• A conceptual understanding of database systems and SQL server.
• Working knowledge and understanding of the Windows registry, including machine
profiles, user profiles, and software registry entries.
• Experience in an environment with some automated/centralized networking tool is a
major plus (Tivoli, Openview, Unicenter, etc.)
Organization of this Guide

This guide is organized as follows:
• Chapter 2, "Overview," provides an overview of the Wyse WSM system and a general
overview of the installation process.
• Chapter 3, "Preparing for Installation," contains hardware and software requirements
and the procedures you must complete to prepare the environment for the Wyse WSM
system installation.
2 Chapter 1
• Chapter 4, "Installing and Configuring the WSM Core Server," provides the detailed
procedures you must complete to install the Wyse WSM Core Server.
• Chapter 5, "Starting Wyse WSM for the First Time," provides the detailed procedures
you must complete to start Wyse WSM for the first time.
• Chapter 6, "Installing and Configuring the WSM Client," provides the detailed
procedures you must complete to install the Wyse WSM Client.
• Chapter 7, "Installing and Configuring a WSM Edge Server," provides detailed
procedures you must complete to install a Wyse WSM Edge Server.
• Chapter 8, "System Maintenance,", contains information to help you successfully
maintain the Wyse WSM system.
• Chapter 9, "Upgrading Wyse WSM," provides the steps you need to upgrade your
Wyse WSM system from a previous version.
• Chapter 10, "Troubleshooting," contains information and help on installation, setup,
conflicts, and general troubleshooting.
• Appendix A, "Error Codes," includes the most common errors that you may encounter
in a displayed message box or in a log file.
• Appendix B, "Booting Wyse WSM on PXE and Non-PXE Networks," describes how to
boot Wyse WSM clients on networks that don’t support PXE or that have not been
modified to support PXE or standard DHCP.
• Appendix C, "Installing Your Own SQL Server," provides instructions for installing the
supported SQL Servers.
Wyse Technical Support

To access Wyse technical resources, visit http://www.wyse.com/support. If you still have
questions, you can submit your questions to the Wyse Self-Service Center or call
Customer Support at 1-800-800-WYSE (toll free in U.S. and Canada). Hours of operation
are from 6:00 A.M. to 5:00 P.M. Pacific Time, Monday through Friday.
To access international support, visit http://www.wyse.com/global.
Links to Related Documentation and Services

Getting Started Guide: Wyse WSM ApplianceTM is intended for administrators of the Wyse
WSM system. It provides a setup and configuration overview of the entire WSM system to
help you get your Wyse WSM environment up and running quickly and easily.
Publisher Guide: Wyse WSMTM is intended for administrators of the Wyse WSM system. It
describes how to use Wyse WSM Publisher to publish applications and to make them
available for distribution.
Administrators Guide: Wyse WSMTM is intended for administrators of the Wyse WSM
system. It provides information, and detailed system command and parameter
configurations, to help administrators design and manage a Wyse WSM environment. It
also explains how to use Wyse WSM, manage the availability of software applications for
distribution to subscribers, manage application subscription licenses, install and configure
published applications, provide subscriber profile and billing information for efficient
application usage tracking, and control subscriber access to the Wyse WSM system.
Users Guide: Wyse WSMTM is intended for users of the Wyse WSM Client system. It
provides detailed instructions on using the Wyse WSM Client to manage the applications
available to users from a network server.
Wyse Thin Computing Software is available on the Wyse Web site at:
http://www.wyse.com/products/software.
2 Overview
This chapter provides an overview of the Wyse WSM system. It explains the key
components and services of the system so you can get a feel for how the system works
before you install its various components.
Introducing Wyse WSM

Wyse WSM makes it possible for IT staff to deploy operating systems and applications on
demand to clients in near real-time. Wyse WSM offers these advantages over
conventional computing solutions:
• On-demand OS and applications provisioning: IT can provision operating systems
and applications to devices without having to visit individual desktops and without the
failures common to traditional software distribution solutions.
• Centralized management of software updates and patches: IT can be sure that
software is up to date all across the system, as well as eliminate downtime for
upgrades.
• Fast deployment of new applications: IT can deliver applications at any time to
respond to the organization’s up-to-the-minute needs.
• License management and metering: IT can control and monitor application license
usage throughout the organization, and in so doing efficiently purchase licenses based
on usage patterns.
• Management of application use: IT can determine which applications users
subscribe to, auto-subscribe applications to some users, and specify mandatory
applications for users.
• Scalability. IT can employ the Wyse WSM distributed architecture to support multiple
servers and, therefore, multiple clients by using a tiered-server deployment.
• Reporting. IT can quickly get reports about applications and system usage.
• Instantaneous recovery from hardware failure. IT can replace a device with a new
one and automatically download user data, applications, and an operating system to
the new device.
• Monitoring. IT can monitor and generate reports about clients, license usage, and
application usage.
4 Chapter 2
Wyse WSM Key Components

Wyse WSM provides streaming services through these key components:
• Simplified OS image creation tool: An OS image-creation tool that administrators
use to create OS images so that the images can be deployed to clients.
• Wyse WSM Publisher, an application packager: An application-packaging tool that
administrators use to create application images that can be deployed to end users.
• Wyse WSM Servers:
· Core Server. The primary WSM server that delivers OS images and application
images to clients and (optionally) to Edge Servers. Administrators manage OS
images and applications images throughout the network from the Core Server.
They accomplish this through the Wyse WSM Administrator Console. After
administrators create OS images and application images, they can stream them to
clients from the Core Server.
· Edge Servers. Additional WSM servers that provide streaming services to clients
for scalability purposes. Edge Servers are optional.
· Wyse WSM Administrator Console: A Web-based Administrator Console from
which an IT administrator can control the entire installation process.
Wyse WSM Services

Each Wyse WSM server — the Core Server as well as the Edge Servers — provides
these services:
• WSM Administration Web Service: Provides an administration interface for the Wyse
WSM.
• OS Authentication Service: Prevents unauthorized devices from connecting to the
WSM system. It informs each device which OS image it has been configured to
receive.
• OS Streaming Service: Responds to OS image requests from client devices.
• Application Authentication Service: Manages and tracks application licenses;
meters application usage.
• Application Streaming Service: Services end-user application client requests.
• Monitor Service: Monitors and controls the Wyse WSM services on the Wyse WSM
server. This service is in charge of detecting errors and outages, as well as stopping
and starting the servers and monitoring their server load.
• Content Distribution Service: Synchronizes the repositories of OS and application
images between the Core Server and remote servers.
• Multicast Boot Service: Multi-casts an OS image to devices when the system is set
up to provide the OS Image in multi-cast mode.
• DHCP Proxy Service: Responds to requests from PXE devices; prevents Wyse WSM
servers from responding to PXE requests from outside devices that are not part of the
WSM system.
• TFTP Proxy Service: Allows for thin client booting, data transfer, and so on.
Overview 5
General Overview of the Wyse WSM Setup Process

This section offers a general overview of installing the Wyse WSM system. Detailed
instructions for completing these basic steps are found throughout this installation guide.
To install the Wyse WSM system:
1. Meet all pre-installation requirements (see "Planning for Your Installation").
2. Install the Wyse WSM Core Server (see "Installing and Configuring the WSM Core
Server").
3. Install and configure the Wyse WSM Client on a reference device (see "Installing and
Configuring the WSM Client").
4. Capture an OS Image to the Core Server and configure the OS Image using the WSM
Administrator Console to enable streaming to clients (see "Capturing an OS Image to
the Core Server").
5. Configure one or more client devices to boot from this OS image (see "Configuring the
OS Image for Network Mode").
6. Configure Users in Groups (see Administrators Guide: Wyse WSMTM).
7. Publish applications and make them available for streaming (see Publisher Guide:
Wyse WSMTM).
8. (Optional) Install one ore more Edge Servers (see "Installing and Configuring a WSM
Edge Server").
6 Chapter 2
This page intentionally blank.

3 Preparing for Installation
This chapter contains hardware and software requirements and the procedures you must
complete to prepare the environment for the Wyse WSM system installation. If you
configure multiple machines, you will repeat some of the steps. You must complete the
Wyse WSM Core Server and Wyse WSM Client installation steps for each related
machine being configured.
Recommended Technical Knowledge

Wyse recommends that the person who installs Wyse WSM have this technical
knowledge:
• Working knowledge of Windows Server 2000 and 2003.
• Working knowledge of client/server systems and technologies.
• A conceptual understanding of database systems and SQL server.
• Working knowledge and understanding of the Windows registry, including machine
profiles, user profiles, and software registry entries.
• Experience in an environment with some automated/centralized networking tools.
• Knowledge of Active Directory configuration.
Planning for Your Installation

This section describes the hardware requirements, software requirements, and system
and security credentials you need for a successful installation. It also offers a
pre-installation checklist so you can be ready to start installing.
Pre-Installation Checklist
Before you start begin installing, make sure you have met the requirements on this
checklist:
• Obtain and configure all hardware, as necessary.
• Obtain administrator rights on all systems to begin the server installations.
• Install Windows 2000 Server or Windows 2003 Server systems on all server machines.
Make sure all systems are up to date with current Microsoft service packs, patches,
and updates.
• Download and install Microsoft Internet Explorer (IE) 6.0 or later on all machines.
• Obtain a Server License File from Wyse (provided to you by e-mail) for the system (see
"Server License Files").
• Install the Microsoft SQL Server (see "Installing Microsoft SQL Server Using the WSM
Prerequisites File"). Make sure the server is running before you begin installing WSM.
8 Chapter 3
• If needed, download and install the latest Microsoft SQL Server Service Pack (see
"Installing the Latest Microsoft SQL Server Service Pack").
• If you are planning to integrate Active Directory with Wyse WSM (see Administrators
Guide: Wyse WSMTM), make sure that the Core Server and the Active Directory Server
are part of the Domain before the administrator of the local system begins installing
WSM Core Server.
Hardware Requirements
Each machine must meet or exceed the minimum system requirements shown in Table 1.
Table 1 Server Hardware Requirements
Category Minimum Requirements Recommended
CPU 1 GHz CPU 3 GHz dual CPU or higher
RAM 512 MB 1 GB or higher
Disk Space 20 GB + AppSets size 20 GB (RAID) + AppSets

size (if applicable)
Network Interface Card (NIC) 100 Mbps 100 Mbps/1 Gbps
Note
These requirements may vary due to application and operating system sizes.
Software Requirements
Besides the Wyse WSM software, you must install the software shown in Table 2 on each
server. Installing the most up-to-date version of each software package is highly
recommended.
Table 2 Server Software Requirements
Component Software Requirements
Operating System Microsoft Windows 2000 Server SP4 or Windows 2003

Server or later (includes SP1 or R2)
Database Server Microsoft SQL Server 2000, 2005, or 2005 Express
Directory Service (optional) Microsoft Active Directory

Preparing for Installation 9
System Security and Credentials

To keep the system secure, Wyse WSM uses various credentials. Most of these
credentials are common for system administrators. The only new credential is for the
Wyse WSM system itself. The following credentials require passwords when they are
installed:
• Wyse WSM Database: The database requires a username and password for
executing SQL queries. Each server in Wyse WSM requires this password to access
the database. This information is stored encrypted in the Windows registry after
installation. The default account is wsmdb; the default password is wsmdb.
• Windows Service: All Wyse WSM servers are required to run as Windows Service
with local system privileges.
Note
If you plan to integrate Active Directory with Wyse WSM without SSL, you
must ensure that the WSM OS Authentication service is running with the
credentials of an Active Directory user with privileges to create and manage
computer accounts (for example, a member of the Account Operator group).
For more information about integrating Active Directory with Wyse WSM
without SSL, see Administrators Guide: Wyse WSMTM.
• Wyse WSM: To administer the Wyse WSM provider environment, a default account
named admin must be created in the system. This account enables you to log on for
the first time and to configure the system. You can change the default password
(admin) after you log in for the first time.
Server to Server Communication Ports

The servers communicate through the port attribute in the Server table. These values are
not exposed through the Administrator Console. However, a mechanism is in place to
resolve port conflicts at startup. When the server detects a port conflict, it will try to
allocate another port above it (for example: 5000 + 1, 5000 + 2, 5000 + 3, and so on). It
will try for a maximum of 100 times before failing.
The following is a list of servers and default Server/Server communication ports:
• OS Authentication Service (Default Port: 6910)
• OS Streaming Service (Default Port: 6911; note that this port can be configured to a
different port by an administrator through the Administrator UI)
• Application Authentication Service (Default Port: 8001)
• Application Streaming Service (Default Port: 8002)
• Monitor Service (Default Port Range: 5000-5100)
• Content Distribution Service (Default Port: 20248)
• Multicast Boot Service (Default Port: 10703)
• DHCP Proxy Service (Default Port: 67)
Note
Ensure that these ports are open for proper communication between servers.
If you have a firewall enabled on any server where Wyse WSM is installed,
you must also ensure that the following ports are configured as follows:
Content Distribution Service Client Port (Default Port: 10802)
NetBIOS Name Service (Default Port: 137)
TFTP Service (Default Port: 69)
10 Chapter 3
Domain Names
It is important to use DNS entries for mapping IPs to servers. Although you can use IP
addresses, it will make scaling and system changes more difficult. This entry point DNS
will be used to allow the client to talk to the server farm. The DNS name that is used
should be entered into the machine name when configuring the core server (as described
in "Installing and Configuring the WSM Core Server"). Also, the client port configured in
that section will be the port used by the clients and will need to be configured in both the
firewall and load-balancing switch. Wyse WSM requires a minimum of two public IP
addresses with DNS entries.
Server License Files

You need to obtain license files to start the system and register network devices (license
files are provided to you in e-mail by Wyse). Wyse Technology uses license files to control
client seats and prevent software piracy. A license file is encrypted using a PKI to sign
each key based on x509 SSL Certificate.
You need a key for any of the following reasons:
• adding additional network devices
• license expiration
License files are stored in the database in an encrypted format. You can add the license
file to the system by using the Administrator Console (after the server installation is
complete). For instructions on adding the licenses file, refer to "Installing and Configuring
a WSM Edge Server." For more details on the Administrator Console, refer to the
Administrators Guide: Wyse WSMTM.
Installing Microsoft SQL Server Using the WSM Prerequisites File

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 InstallShield 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 InstallShield 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.
Note
For instructions on installing your own SQL Server, refer to "Installing Your
Own SQL Server."
Preparing for Installation 11
Configuring a DHCP Server

A DHCP Server must be installed and configured on your network to provide IP addresses
to your thin clients. For reference, the parameters shown in Table 3 must be specified.
Table 3 DHCP server options
DHCP
Option
Number Purpose DHCP Option Value for the Thin Client
03 Gateway Specific to the network.

If a DNS server is not on the local area network,
then specify the IP address of the gateway for the
local area network in which the client resides.
Otherwise, this option is optional.
06 IP Address of the Specify the IP address of DNS server that

DNS Server contains the record for the boot server.
60 Client Identifier (Use Only if the DHCP Server is on the Same

Machine as the WSM Server) - Set to PXE
Client (“Configure DHCP option 60 to
‘PXEClient’” in the server properties).
12 Chapter 3

4 Installing and Configuring the WSM
Core Server
This chapter provides the detailed procedures you must complete to install the Wyse
WSM Core Server. Although you can select custom installation configurations during the
installation, it is recommended that you use the default configurations.
Note
Be sure you have completed all pre-installation requirements as described in
"Preparing for Installation" before you begin installing the WSM Core Server.
Installing the WSM Core Server

To install the WSM Core Server:
1. After downloading the Wyse WSM Server software, double-click the WSMServer.exe
to open the Installation Wizard.
Figure 1 Installation Wizard - Core Server
2. Click Next to open the License Agreement window.

14 Chapter 4
Figure 2 License Agreement - Core Server
3. After reading the agreement, select the I accept the terms in the license agreement
option and click Next to open the Destination Folder window.
Figure 3 Destination Folder - Core Server
4. Click Next to open the Streaming Directory Information window.
Note
The Streaming Directory is where the Write Cache files, OS Images, and
Application Images will be stored.
Installing and Configuring the WSM Core Server 15
Figure 4 Streaming Directory Information - Core Server
5. Click Next to open the WSM Server Information window.
Figure 5 WSM Server Information Window
6. Select the This is a new WSM installation option to install the Core Server.
7. Click Next to open the Database Server window.
Figure 6 Database Server - Core Server

16 Chapter 4
8. Use the following guidelines:

• Enter the Database Name to use for the SQL server (default is StreamingDB).
Note
Do not use special characters for the Database Name.
• Enter the Username for the database (default is wsmdb).

• Enter the Password for the database (default is wsmdb@123).
• Confirm the password by re-typing it in the Re-Type Password text box.
Warning
If you will be installing a WSM Edge Server in the future, be sure to
remember the information you enter in this Database Server window, as you
will need this information when you install the WSM Edge Server.
• Click Next to open the Database Server and Authentication Method window.
Figure 7 Database Server and Authentication Method - Core Server

• Enter the Database Server IP Address or Name in the Database text box (you can
use Browse to locate the server you want).
• For a successful WSM installation, you must select the Server authentication
using the Login ID and password below option for your connection.
• Enter the Login ID and Password for the server in the appropriate text boxes.
• Click Next to open the Ready to Install the Program window.
Installing and Configuring the WSM Core Server 17
Figure 8 Ready to Install the Program - Core Server
10.Click Install to begin the installation.
Figure 9 Installing WSM Core Server
Caution
Do not interrupt the installation.
During the installation, the WSM Server Configuration dialog box opens.
Figure 10 WSM Server Configuration - Core Server

18 Chapter 4
11. Select the Network Adapter to use, select the IP Address list to use, and then click OK
to save the configurations, close the WSM Server Configuration dialog box, and open
the Installation Wizard Completed window.
Figure 11 Installation Wizard Completed - Core Server
12.Click Finish to close the InstallShield Wizard.

13.Continue with "Installing and Configuring a WSM Edge Server."
5 Starting Wyse WSM for the First
Time
This chapter provides the detailed procedures you must complete to start Wyse WSM for
the first time.
Note
Be sure you have successfully installed the WSM Core Server before you
complete the procedures in this section.
Using the Configuration Wizard

After you successfully install the WSM Core Server, you can use the Configuration Wizard
to add your Core Server License (required) and enable Active Directory integration with
Wyse WSM (optional).
Note
You can skip any of the configurations in this section and complete the Wyse
WSM system configurations according to your environment needs by
following the appropriate procedures in the Administrators Guide: Wyse
WSMTM.
To complete the Configuration Wizard:

1. Open the Administrator Console login page by choosing Start | WSM Server | WSM
on the machine to which you have installed the WSM Core Server (you can also open
a Web browser from any machine with access to the WSM Core Server and go to http:/
/<ipaddress>:8080/admin/).
20 Chapter 5
Figure 12 Login page
2. Enter the Admin Username (default is admin) and Password (default is admin) and
click Login to open the Import Server License page.
Figure 13 Import Server License page
3. Click Browse to find and select the license.txt file that was provided to you by
Wyse, and then click Import Server License to import the license and view the licence
details.
4. Click Next to open the Configure Active Directory page.
5. Depending on whether or not you want to enable Active Directory integration with
Wyse WSM, select or clear the Enable Active Directory check box.
Note
For information to help you decide whether or not you want to integrate
Active Directory with your Wyse WSM system, refer to the Administrators
Guide: Wyse WSMTM.
If you need to configure or re-configure the Active Directory in the future,
refer to the Administrators Guide: Wyse WSMTM.
If you do not select the Enable Active Directory check box, click Finish to view the
System Overview Congratulations page, and continue with step 15.
If you select the Enable Active Directory check box, the Configure Active Directory
page expands.
Starting Wyse WSM for the First Time 21
Figure 14 Configure Active Directory page - expanded
6. Enter the Group Synchronizing Polling Frequency time (number of seconds between
synchronizing the members of user groups between the Active Directory and the Wyse
WSM database; the default is 600 seconds, but you can turn off the feature by setting
the time to 0).
7. Click Next to open the Add Domain page.
Figure 15 Add Domain page
8. Enter the Domain Name of the Active Directory.

9. (Optional) Enter the DC Hostname or IP Address of the Active Directory.
10.Enter the Active Directory User.
Note
A user with privileges to create and manage computer accounts is needed
for Active Directory integration. By default, members of the group named
Account Operators or Domain Administrators have the privilege to create and
maintain computers accounts.
11. Enter the Password.

12.Click Add Domain to add the domain and open the Import Groups page.
Note
The Domain is added to the list of available domains on the Active Directory
Domains page.
22 Chapter 5
Figure 16 Import Groups page
13.Select the User Groups you want by using the following guidelines:
• Enter the group name you want in the Group Name Contains text box (use only
letters, numbers, dashes, spaces, the @ character, and periods).
• Enter the LDAP Context Root.
• Enter the Max Results limit (zero to the limit of all Users in Active Directory).
• After entering your filter criteria, click Filter to view the results.
• Scroll through the list of Groups and select the check boxes for the Group Names
you want.
14.After selecting the Groups you want, click Finish to view the System Overview
Configurations page.
Note
Users of these imported groups will automatically be added to the Wyse
WSM User Name list on the Users page.
Figure 17 System Overview Configurations page

Starting Wyse WSM for the First Time 23
Note
The Domains link only appears in the Category area if Active Directory is
enabled.
15.After completing the Configuration Wizard, you can view the Core Server Details page
to see that the Core Server Services are successfully running by clicking the Servers
link in the Category list on the System Overview page, and then clicking the Name link
of the Core Server.
Figure 18 Core Server Details page
Now that the Core Server services are running, you can continue to configure the rest of
the Wyse WSM system according to your environment needs by following the appropriate
procedures in the Administrators Guide: Wyse WSMTM.
24 Chapter 5

6 Installing and Configuring the WSM
Client
This chapter provides the detailed procedures you must complete to install the Wyse
WSM Client. Although you can select custom installation configurations during the
Note
"Preparing for Installation" before you begin installing the WSM Client.
Preparing to Install the WSM Client

This section contains the procedures you must complete to prepare the environment for
the WSM Client installation. Before you begin installing the WSM Client, you must first
decide where and how you want to install the WSM Client and complete all pre-installation
requirements for the installation environment you want. After preparing the environment,
you can install the WSM Client as described in "Installing the WSM Client."
Note
The Reference Device is the device from which you initially capture the OS
image; subsequently, the Reference Device is used for applying patches to
this OS image. The Reference Deice has a hard disk and a locally installed
Windows operating system. After an OS image is captured from the
Reference Device, other devices can be configured to boot from this OS
image file in shared mode. Because other devices will boot from the
Reference Device’s OS image, this image should be configured to meet the
needs of all devices that will boot from it. The best practice is to reserve the
Reference Device for use by the Administrator and not assign it to end users.
This way, the Administrator can easily deploy and test OS images by using
the Reference Device.
Installing the WSM Client on Wyse Thin Clients

If you are planning to install the WSM Client on Wyse thin clients, you must complete the
following:
• Access to reference device VRO with 4GB of flash.
• Use USB CD-ROM drive. Although you can use other USB CD-ROM drives, the
following are certified for use.
• IBM USB CDROM, Model Part Number 00N8239
• Addonics USB CDROM, Model Part Number AECD2K32UM.
• Install the Microsoft operating system on the flash.
26 Chapter 6
Installing the WSM Client in a VMware Environment

If you are planning to use Wyse WSM in a VMware environment, you must complete the
following:
• Create a target VM machine on an ESX Server as described on the VMware Web site
and install the Microsoft operating system in VM.
• Use USB CD-ROM drive. Although you can use other USB CD-ROM drives, the
following are certified for use.
• IBM USB CDROM, Model Part Number 00N8239
• Addonics USB CDROM, Model Part Number AECD2K32UM.
Installing the WSM Client

To install the WSM Client:
1. After downloading the Wyse WSM Client software, double-click WSMClient.exe to
open the InstallShield Wizard.
Figure 19 InstallShield Wizard - WSM Client

Installing and Configuring the WSM Client 27
Figure 20 License Agreement - WSM Client
option and click Next to open the Customer Information window.
Figure 21 Customer Information - WSM Client
4. Enter the User Name and Organization and click Next to open the Destination Folder
window.
28 Chapter 6
Figure 22 Destination Folder - WSM Client
5. Click Next to open the Ready to Install the Program window.
Figure 23 Ready to Install the Program - WSM Client
6. Click Install to begin the installation.
Figure 24 Installing WSM Client
Note
During installation, Windows Logo testing messages may appear in front of
or behind the wizard windows. If these messages appear, click Continue
Anyway to continue the installation.
Figure 25 Windows Logo testing message - WSM Client
During the installation, the Found New Hardware Wizard opens.
Figure 26 Found New Hardware Wizard - WSM Client
7. Select the Install the software automatically (Recommended) option and click Next
to begin installation.
Figure 27 Installing hardware - WSM Client
After the software is installed, the Completing the Found New Hardware Wizard
window appears.
30 Chapter 6
Figure 28 Completing the Found New Hardware Wizard - WSM Client
8. Click Finish to close the wizard and open the WSM Client Config Wizard.
Figure 29 WSM Client Config Wizard
9. Use the following guidelines to complete the WSM Client Config Wizard:
• Enter the Authentication Server Info IP address to be used by the WSM OS
Authentication Service (this address is the same as the Core Server). The default
Port information is automatically entered.
• Enter the Imaging Server Info IP address to be used by the WSM OS Streaming
Service (this address is the same as the Authentication Server Info IP Address).
The default Port information is automatically entered.
• Enter the Web Server Info Port address, if necessary. This is the port on which the
Web server runs. The default is entered automatically.
• Enter the IOS Streaming Max Packet Size. This is the maximum data size of OS
streaming packets sent from the server to the client; the default value is 1420. If
your network, to meet encryption or other types of requirements, requires a custom
MTU (Maximum Transmission Unit) for IP packets, you can adjust this number to
restrict the size of the packets. Set the value to 1370 to yield an MTU of 1398 (the
maximum OS streaming data size [1370], plus the UDP header size [8], plus the IP
header size [20]). Matching this value to the OS Streaming Max Packet Size setting
on WSM servers is recommended.
Note
The default Client Info IP Address and Port, Subnet Mask, and Gateway IP
Address are automatically entered.
• Click OK to close the WSM Client Config Wizard and open the InstallShield Wizard
Completed window.
Figure 30 InstallShield Wizard Completed - WSM Client
10.Click Finish to close the InstallShield Wizard.

After completing the procedures in this section, restart the system (Escape out of the
network boot by pressing ESC) and continue with "Capturing an OS Image to the Core
Server."
Capturing an OS Image to the Core Server

After installing the Wyse WSM Client software, you must capture an OS Image to the Core
Server.
Note
Be sure you have all peripherals you want to use (for example, keyboard,
mouse, printers and so on) connected before you begin capturing the OS
Image to the Core Server.
To capture an OS Image to the Core Server:

1. After installing the Wyse WSM Client software, locate OSMVDiskImage.exe (the
default location is C:\Program Files\Wyse\WSM\os).
32 Chapter 6
Figure 31 OSMVDiskImage.exe
2. Double-click the OSMVDiskImage.exe to open the WSM VDisk Image Creation Utility
window.
Figure 32 WSM VDisk Image Creation Utility
3. Enter the Virtual disk size in MB (if you are running in shared mode, the maximum
virtual disk size is 32 GB).
4. Enter a Disk name.
5. (Optional) Enter a Description for the disk.
6. Depending on whether or not you want to integrate WSM with Active Directory, select
or clear the Enable Active Directory Integration check box.
7. Click OK to begin building the virtual disk.
Figure 33 Building Virtual Disk
After building is complete, the Done message appears in the WSM VDisk Image
Creation Utility window.
Figure 34 Done message
8. Click Finish to complete the OS Image capturing process.

9. After completing the procedures in this section, continue with "Configuring the OS
Image for Network Mode."
Comparing Network and Mobile Mode

An OS image can be provisioned to devices in two modes:
• Network mode - The device must always have a LAN connection to the WSM server
(see "Configuring the OS Image for Network Mode").
• Mobile mode - The OS image is provisioned to the hard disk on a laptop or other
mobile device so that the device can operate without being connected to the server.
The device can be disconnected from the server and still be operational (see
"Configuring an OS Image for Mobile Mode").
Note
Whichever mode is in use, the OS image itself remains the same; it is not
modified in any way. The Network/Mobile modes apply to devices, not OS
images. The same OS image can be used by Network mode devices and
Mobile mode devices simultaneously. By choosing a mode, you are deciding
how the device receives the OS image — over the network or cached to the
local disk.
34 Chapter 6
Configuring the OS Image for Network Mode

After capturing an OS Image to a Core Server, you must, using the Administrator Console,
configure the OS Image for use in Network mode.
Note
When users start the WSM Client device for the first time, they may
encounter a WSM Client Login in progress message. This will occur for all
users who log in and are not yet registered in the WSM Database.
Completing the procedures in this section prevents these users from
encountering these messages.
To configure the OS Image:

1. Log in to the Administrator Console, add the OS Image you created in "Capturing an
OS Image to the Core Server," and assign the OS Image to the Core Server. For
procedures on adding an OS Image and assigning it to the Core Server, refer to the
Note
When adding the OS Image, be sure to select the No Cache (Private Mode)
option for Mode.
2. Reboot the machine to which you installed the WSM Client and use the following
guidelines for the DOS prompts:
• You must enter the client name.
• Entering a description is optional.
• Be sure you select the vdisk you just added in "Capturing an OS Image to the Core
Server."
• Press any key to restart the system.
Note
Upon system restart, close the WSM Client Login in progress message that
appears (right-click the minimized application in the taskbar and select Close
to close the window).
Figure 35 WSM Client Login in progress message
3. Upon system restart, the System Settings Change message appears; when this
message appears, click No to close the window. Note that this is a good time to clean
up or customize your environment (for example, selecting the desktop background,
and so on, prior to sharing the OS Image on multiple client machines).
Figure 36 System Settings Change message
4. After you have completed customizing your environment, shut down the client
machine.
5. After the client machine has shut down, log in to the Administrator Console.
6. Edit the OS Image you created in "Capturing an OS Image to the Core Server," so that
either the Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode) option
is selected for the Mode.
After completing the procedures in this section, the OS Image is ready to be used by
multiple client machines. For more information, see Administrators Guide: Wyse WSMTM.
Note
In the future, if you want to copy or move an OS Image from one streaming
server (for example, a lab environment) to another streaming server (for
example, a production server), or if you want to change the current Active
Directory integration mode (Enabled or Disabled), then that OS Image must
be re-configured as described in "Reconfiguring an OS Image."
Configuring an OS Image for Mobile Mode

To configure an OS image for Mobile mode, follow these basic steps:
1. Capture an OS image for the device (see the previous section in this chapter). You only
need to complete this step once.
2. In the WSM console, choose Mobile Disconnected as the Connection Type (see
Administrators Guide: Wyse WSMTM for more information about adding network and
mobile devices). Choosing this option tells WSM that the OS image must be
provisioned (or cached) to the device’s local hard disk. Note that the actual
provisioning (or copying) doesn’t begin immediately.
3. Have the user reboot the device. The device will boot from the network initially. After
the user logs in, the provisioning process will either start automatically (an enabled
force provision) or when the user initiates it (a disabled force provision).
To configure and provision additional devices for Moble mode, start with step 2. You don’t
have to capture a new Network OS image for each additional mobile device.
Warning
Provisioning a mobile device erases all data currently on the device’s hard
disk. Make sure mobile users understand that they will lose data currently on
the hard disk when they provision an up-to-date OS image from the server.
36 Chapter 6
Note
In order to download an OS image for Mobile mode, the mobile device
requires at least twice the amount of disk space as the OS image plus
100MB. For example, if the OS image being provisioned is 6GB, the mobile
device requires at least 12GB+100MB of free disk space to accommodate
the image.
See Administrators Guide: Wyse WSMTM for more for information about converting a
device from Network mode (the default) to Mobile mode.
7 Installing and Configuring a WSM
Edge Server
This chapter provides the detailed procedures you must complete to install a Wyse WSM
Edge Server. Although you can select custom installation configurations during the
Note
"Preparing for Installation" and installed WSM Core Server before you begin
installing a WSM Edge Server.
Installing a WSM Edge Server

To install a WSM Edge Server:
1. After downloading the Wyse WSM Server software, double-click WSMServer.exe to
open the Welcome window.
Figure 37 InstallShield Welcome - Edge Server

38 Chapter 7
Figure 38 License Agreement - Edge Server
option and click Next to open the Destination Folder window.
Figure 39 Destination Folder - Edge Server
4. Click Next to open the Streaming Directory Information window.
Figure 40 Streaming Directory Information - Edge Server
Note
The Streaming Directory is where the Write Cache files, OS Images, and
Application Images will be stored.
Installing and Configuring a WSM Edge Server 39
5. Click Next to open the WSM Server Information window.
Figure 41 WSM Server Information - Edge Server
6. Select the This server belongs to the following WSM installation option and enter
the Core server IP address to install the Edge Server and connect to the Core Server.
7. Click Next to open the Database Server and Authentication Method window.
Note
If the WSM Edge Server cannot connect to the Core Server Registry (for
example, the remote registry is disabled on the Core Server for security
reasons), then a warning message appears.
Figure 42 Warning message - Edge Server
Click OK to close the Warning message and open the Database Server window.
Figure 43 Database Server - Edge Server
Use the following guidelines:

• Enter the Database Name to use for the SQL server (default is StreamingDB).
40 Chapter 7
Note
Do not use special characters for the Database Name.
• Enter the Username for the database (default is wsmdb).

• Enter the Password for the database (default is wsmdb@123).
• Confirm the password by re-typing it in the Re-Type Password text box.
• Click Next to open the Database Server and Authentication Method window.
Figure 44 Database Server and Authentication Method - Edge Server

• Enter the Database Server IP Address or Name in the Database text box (you can
use Browse to find the server you want).
• For a successful WSM installation, you must select the Server authentication
using the Login ID and password below option for your connection.
• Enter the Login ID and Password for the server in the appropriate text boxes.
• Click Next to open the Ready to Install the Program window.
Figure 45 Ready to Install the Program - Edge Server
9. Click Install to begin the installation.

Installing and Configuring a WSM Edge Server 41
Figure 46 Installing WSM Edge Server
Caution
Do not interrupt the installation.
During the installation, the WSM Server Configuration dialog box opens.
Figure 47 WSM Server Configuration dialog box - Edge Server
10.Select the Network Adapter to use, select the IP Address list to use, and then click OK
to save the configurations, close the WSM Server Configuration dialog box, and open
the Installation Wizard Completed window.
Figure 48 InstallShield Wizard Completed - Edge Server
11. Click Finish to close the InstallShield Wizard.

42 Chapter 7

8 System Maintenance
This chapter contains information to help you successfully maintain the Wyse WSM
system.
Passwords
Wyse WSM uses three sets of username and password credentials. The following list
describes how to change the passwords:
Note
It is strongly recommend that administrators implement a password policy.
• Wyse WSM Database – If you need to change the database user account password
(default is wsmdb@123), you must change the account password on the database
itself and then restart the Administrator service (Administrator Console). The next time
you log into the Administrator Console, the Database Configuration page displays
allowing you to edit the database configurations (including the user account password).
After changing the database configurations you must restart all services on all servers
for the changes to take effect.
• Windows Service – If you change the windows system password on the administrator
user, which is used to start the Wyse WSM services servers, then you will need to
update the services. This is can be accomplished under the Management Console for
Windows Services by selecting the Log On tab and changing the account password.
• Wyse WSM – To change the administrator account password for the Wyse WSM
provider environment, log in to the Wyse WSM as an administrator, select Change
Password, and use the Change Password page.
Logs
Errors pertaining to the Wyse WSM and related components are logged to the System
Event Viewer. Descriptions of errors regarding licensing, server connections, database
problems, configuration errors, and so on, are available through the System Event Viewer.
Wyse WSM stores log files in the database and on your file system. These have a set size
and will rollover when they become too large (making the system self-maintaining). The
default size of these logs is 10,000,000 bytes.
The Profile Log is a log of communication statistics on the server side giving information
on how long request queue is at a given time, the effective bandwidth amount of requests
received so far, and the type of requests received so far. It is located at the
/server-install/log folder with the name in the format of:
prof-<erver-id>-<random>.txt. Format: Date [universal-time]
[start-time] [delta-time] [request-count] [S/M] [CLIENT/CACHE]
[IP address] [app-id] [fileID,pageID] (S=single, M=multiple)
44 Chapter 8
Backup Recovery
It is highly recommended that all system data is backed up for recovery purposes. Wyse
WSM stores all system, topology, user, application, and usage data within the database.
Since all information is contained in the Wyse WSM Database, backing up this database
enables you to recover all system data. Use standard backup procedures common to
database servers. For fault-tolerant systems, it is also recommended to replicate the
database for fail-over.
System Monitoring
Wyse WSM comes with built-in monitoring tools that can be used to watch and check the
health of the system. When an administrator logs into the Administrator Console, the
System Overview page is shown. The System Overview page allows you to quickly view
important summary information for each functional area of the Wyse WSM system. It also
provides links to all of the functional areas so you can easily perform many of the
Administrator duties that are required to run and maintain your Wyse WSM environment.
For example, the Overview page allows you to quickly see that a server requires your
attention (since Wyse WSM has noted this server problem in the Requires Attention area
and provides you a link to the Server functional area page that you need to address the
message).
For fault-tolerant provider systems, it is recommended to have system hardware
monitoring in place. Third-party system monitoring software can be configured to watch
and report on system status, including:
• Ping availability and response times
• % CPU Utilization
• Memory Available
• Bandwidth consumption
The following list provides a few examples of system monitoring software:
• Tivoli by IBM
• Big Brother by Quest software
• Nagios by Nagios
• Performance Monitor by Microsoft
9 Upgrading Wyse WSM
This chapter provides the steps you need to complete to upgrade your Wyse WSM system
from a previous version.
Preparing for Upgrade Installation

To prepare for the upgrade installation:
1. Back up your WSM database before you begin the upgrade process.
2. Schedule the upgrade for a time when you can upgrade all of the servers at the same
time.
3. Ensure that all devices are shut down during the upgrade process.
Performing the Upgrade

To upgrade your Wyse WSM system from a previous version, you must perform the
upgrade process in the following order:
1. Core Server (see "Upgrading the Core Server and Edge Servers").
2. All Edge Servers (see "Upgrading the Core Server and Edge Servers").
3. All Client OS Images (see "Upgrading the Client OS Images").
Note
Application Images do not need to be upgraded. All Application Images of
previous Wyse WSM versions are compatible with the latest Wyse WSM
version.
Upgrading the Core Server and Edge Servers

In the Wyse WSM upgrade installation, there is a single installation package for both the
Core Server and the Edge Server(s). You must run the same installation package
(WSMServer.exe) on both the Core Server and all of the Edge Servers that you have in
your current Wyse WSM installation.
During upgrade installation, the installation package will:
1. Check your current server for an existing installation of WSM.
2. Prompt you for an upgrade confirmation after finding that previous WSM components
are installed.
46 Chapter 9
3. Prompt you for confirmation of the existing database settings.
Caution
It is recommended that you select the existing database settings and not
change them at this time. If you need to change the location of the database,
you must completely uninstall your current Wyse WSM installation (see
"Uninstalling Wyse WSM Software"), and then install the new Wyse WSM
version on the same machine according to the instructions in this guide.
4. Remove the existing WSM components.
Caution
During the upgrade installation for the servers, a message may appear
informing you that a reboot is needed after the existing WSM components
have been removed. Do not reboot the servers at this time. Click OK to close
the message.
5. Install the new WSM components.

6. Retain the existing WSM settings.
7. Add default values for the new WSM features that are available.
Note
After the upgrade installation is successfully completed, a message will
appear prompting you to reboot before the new WSM components can be
used from the servers. You must reboot the servers at that time.
Upgrading the Client OS Images

To upgrade the Client OS Images:
1. After downloading the Wyse WSM Client software, double-click WSMClient.exe to
open the InstallShield Wizard (the software will automatically check to see if this
installation is an upgrade installation).
Figure 49 InstallShield Wizard - WSM Client Upgrade
2. Click Upgrade to begin installing the WSM Client upgrade.

Upgrading Wyse WSM 47
Figure 50 Installing - WSM Client Upgrade
After installation is complete, the InstallShield Wizard Completed window appears.
Figure 51 InstallShield Wizard Completed - WSM Client Upgrade
3. Click Finish to close the InstallShield Wizard and open the WSM Client Installer
Information message prompting you to restart your system so that configuration
changes made to WSM Client can take effect.
Figure 52 WSM Client Installer Information - WSM Client Upgrade
4. Click Yes to restart you system.

48 Chapter 9

10 Troubleshooting
This chapter contains information and help on installation, setup, conflicts, and general
troubleshooting. For a complete list of error codes and descriptions, refer to "Error Codes."
Verifying if the Database Is Operational and Configured Correctly

Follow these steps to verify if the database is operational and configured correctly:
1. Using the SQL Server Enterprise Manager, verify that the StreamingDB database
exists.
· To verify whether SQL Server user account wsmdb is set up correctly, choose
Access Enterprise Manager. Then expand your SQL Server tree and expand the
Security Folder. Then click Users, verify that the wsmdb exists, and verify that it has
the proper permissions by right-clicking the wsmdb name and choosing Properties,
clicking the Database Access tab, and selecting the StreamingDB. Then verify that
the db_owner and public boxes are checked.
2. Verify that the ODBC Connection is set up correctly:
a. Access the System DSN tab within the ODBC Data Source Administrator window
under Administrative Tools.
b. Select the StreamingDB connection and click Configure.
c. Click Next, and then click Client Configuration.
d. Click the TCP/IP option button and fill in the appropriate IP information for your SQL
Server.
e. Finish configuring the ODBC connection and verify that it was set up by running the
Data Source connection test.
f. Verify that a connection can be made from the WSM Server to the SQL Server.
Verifying that WSM Services are Running

Follow these steps to verify that WSM services are running:
1. Log in with the WSM Administration UI with the admin account.
2. Go to the Servers page.
3. Click the name of the WSM Server. You go to the Server Details page.
4. Examine the Status column for down servers.
5. Click the Start link to start the service.
50 Chapter 10
Verifying if the ODBC is Operational and Configured Properly

To allow communication between the WSM Server and the database, the installer creates
and configures an ODBC connection. Follow these steps to verify that the ODBC Data
Source is configured properly:
1. Open the Control Panel, choose Administrative Tools, and click Data Sources
(ODBC).
2. Click on the System DSN tab and click Configure.
3. In the Name field, enter StreamingDB; in the Which SQL Server do you want to
connect to? field, enter the IP address of your SQL Server; then click Next.
4. Select SQL Server Authentication.
5. In the Login ID field, enter wsmdb; in the Password field, enter the password for
wsmdb; then click Next.
6. Click the Change the Default Database To check box and select StreamingDB in the
list; then click Next.
7. Click Next to finish establishing the ODBC database connection.
8. Click Test Data Source, and click Next to determine whether the ODBC connection
has been set up correctly.
To indicate that the ODBC connection was set up correctly, you should see the Tests
Completed Successfully message box. The server installation setup is now complete.
Audio Problems in the Streaming Environment

Problem: All non-administrator users on the locally streamed OS Image are having audio
problems.
Solution: Use the following procedures to solve this problem:
1. Shut down all client devices booted from this OS Image.
2. Change the OS Image Mode to No Cache (Private Mode) using the Administrator
Console (for procedures on editing an OS Image, refer to the Administrators Guide:
Wyse WSMTM.
3. Boot one client device from the OS Image in No Cache (Private Mode).
4. Login to the client device as a user with administrator privileges and set the registry
values as follows:
A DWORD value named SType must be created and set to 19601 (decimal) in both of
the following keys:
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Efsd\
• HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OTFileSpoofer\
5. Shut down the client device.
6. Change the OS Image Mode back to either Persistent Cache (Shared Mode) or
Volatile Cache (Shared Mode) using the Administrator Console (for procedures on
editing an OS Image, refer to the Administrators Guide: Wyse WSMTM.
7. Login as a non-administrator user, and verify that the audio is working properly.
Troubleshooting 51
Unable to Capture an OS Image after Cancelling the Capture Process

Problem: A user cancels the OS Image capture process and then cannot restart the
capture process again.
1. Reboot the client device.
2. Login to the hard disk.
3. Start the OS Image capture process as described in "Capturing an OS Image to the
Core Server."
Error when Enabling Active Directory for the First Time

Problem: After enabling and configuring the Active Directory for the first time (as described
in "Installing and Configuring a WSM Edge Server"), clicking Finish produces an error
stating that the Active Directory cannot be connected.
• Be sure that the Core Server and the Active Directory Server are part of the Domain
before the administrator of the local system begins installing the WSM Core Server.
• Ensure that the display name for the Active Directory user is the same as the user
name used for connecting to Active Directory.
• Ensure that you can ping the Domain (for example, wsm.com).
Error when Installing WSM Client on Windows XP

Problem: You are installing the WSM Client on Windows XP (without a SP) and you
encounter an error message that a .dll file is missing.
Figure 53 Missing file message
Solution: Obtain winhttp.dll and copy it into the Windows system32 folder. After you
have done this, begin installing the WSM Client as described in "System Maintenance."
Network Devices are Unable to be Created in the Active Directory

Problem: You are trying to add a Network Device from the WSM Administrator Console
and you encounter an error message.
Solution: Use the following procedures, in the order presented, to solve this problem:
1. Ensure that the Network Device is created in Active Directory.
2. If you are using Active Directory integration without SSL, change the OS
Authentication service to run with a user with Account Operator credentials.
3. Ensure that the Active Directory connection Status is Up.
52 Chapter 10
HTTP Error:404 /admin/ not found RequestURL=/admin/ powered by jetty

Problem: You are logging in to the Administrator Console and you encounter the following
error message:
“HTTP Error:404 /admin/ not found RequestURL=/admin/ powered by jetty.”
Solution: Use the following procedures, in the order presented, to solve this problem:
1. Ensure your WSM Administration Web Service is running (see "Verifying the Status of
the Wyse WSM Service Files"). If you still encounter the error, go to Step 2.
2. Ensure that your database is correctly configured and running. If you still encounter the
error, go to Step 3.
3. Open the registry at
HKLM\System\CurrentControlSet\Services\WSMAdminService, add a
multi-string key called DependOnService, set the value to MSSQLSERVER, and then
reboot the Core Server.
Verifying the Status of the Wyse WSM Service Files

A successful installation places the following WSM files into the Services folder (you can
view these files by clicking Start | Control Panel | Administrative Tools | Services):
• WSM Administration Web Service - Provides an administration interface for the
Wyse WSM.
• OS Authentication Service - Allows you to manually start and stop the
authentication service for the Wyse WSM.
• OS Streaming Service - Allows you to manually start and stop the streaming service
for the Wyse WSM.
• Application Authentication Service - Manages subscriber licenses and metering
application usage.
• Application Streaming Service - Services end-user application client requests.
• Monitor Service - Monitors and controls the Wyse WSM Services on the machine to
which it is loaded.
• Content Distribution Service - Allows you to synchronize the repositories of OS and
Application images between the Core and remote servers.
• Multicast Boot Service - Allows you to multi-cast the operating system information
to devices when the system is setup to provide the OS Image in multi-cast mode.
• DHCP Proxy Service - Allows you to prevent any unauthorized devices from
connecting to the WSM system. It also prevents WSM from responding to other
PXE requests from devices that are not part of the WSM system.
• TFTP Proxy Service - Allows for thin client booting, data transfer, and so on.
Troubleshooting 53
Figure 54 Services folder and WSM files
Note
To start or stop a service, right-click on the service file (for example, WSM
Administration Web Service) and select Start or Restart (to start the service)
or select Stop (to stop the service).
Reconfiguring an OS Image
If you want to copy or move an OS Image from one Core Server (for example, a lab
environment) to another Core Server (for example, a production server), then that OS
Image must first be re-configured.
Similarly, if you want to change the current Active Directory integration mode (Enabled or
Disabled), then that OS Image must be re-configured.
Note
These re-configuration procedures must be done on a client machine that
has been booted from this OS Image in No Cache (Private Mode). For
procedures on adding an OS Image and assigning it to a server, refer to the
To re-configure an OS Image:
1. (Only required if you want to change the current Active Directory integration from
Disabled to Enabled) Join the OS Image to the domain you specified (when you added
the OS Image using the Administrator Console as described in "Capturing an OS
Image to the Core Server") by using the Microsoft procedures for joining a domain,
reboot the system, and continue with Step 2.
2. Login as a user with administrator privileges on the client machine and locate the
WSMClientPostConfig.exe (default location is C:\Program Files\Wyse\WSM\os).
54 Chapter 10
Figure 55 WSMClientPostConfig.exe
3. Double-click the WSMClientPostConfig.exe to open the WSM Client Post

Configuration window.
4. Use the following guidelines to complete WSM Client Post Configuration dialog box:
• Depending on whether or not you want to integrate WSM with Active Directory,
select or clear the Enable Active Directory Integration check box.
• If you want to change the WSM Core Server settings, select the WSM Core Server
settings check box and enter the new IP Address of the Core Server, and Port
settings of the WSM OS Streaming Server.
5. Click OK.
6. Shut down the client machine.
7. Log in to the Administrator Console and edit the OS Image so that either the
Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode) option is
selected for the Mode. For procedures on editing an OS Image, refer to the
8. If the intention of this re-configuration was to move the OS Image to a different Core
Server, the OS Image can be now copied to that new Core Server, and added to the
new Core Server through the Administration Console. For procedures on adding an
OS Image to a server, refer to the Administrators Guide: Wyse WSMTM.
After completing the procedures in this section the OS Image is ready to be used by
multiple client machines.
Troubleshooting 55
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:
• 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. In this situation, you must reconfigure the system
manually according to your required configurations (for configuration guidelines, refer
to the Administrators Guide: Wyse WSMTM).
• 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).
• 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.
Uninstalling Wyse WSM Software

To uninstall Wyse WSM software, use the Windows Add or Remove Programs tool (follow
the Windows procedures for removing a program).
Note
Some uninstallations may require a reboot.
56 Chapter 10

A Error Codes
This appendix covers common errors that you may encounter in a displayed message box
or in a log file. For information and help on installation, setup, conflicts, and general
troubleshooting, refer to "Troubleshooting."
Table 4 Error codes, symbolic representation, and error description
Code Symbolic Representation Error Description
2 OTERROR_AI_BAD_XML_FORMAT Missing configuration data in

the basicConfig.jsp file
for the AutoInstall routine.
4 OTERROR_AI_SYSCHECK_REJECTED Failed AutoInstall system

check because of existing
MacID.
10 OTERROR_AI_ENVTEST_BAD_OS Unsupported Operating

System version.
15 OTERROR_AI_ENVTEST_NO_APPSERV Could not ping the

Application server, probably
because of an Application
server outage or a firewall
issue.
16 OTERROR_AI_ENVTEST_NO_SLIMSERV Could not ping the

Application Authentication
Server, probably because of
a Application Authentication
Server outage or a firewall
issue.
26 OTERROR_AI_TERMINAL_SESSION_DET Client cannot be installed

using Terminal Services.
3002 to OTERROR_EMS* Network communication

3008 time-out.
3024 to OTERROR_EMS_PROXY* Proxy issues with

3030 authentication or proxy
gateway detection.
58 Appendix A
Table 4 Error codes, symbolic representation, and error description, Continued
Code Symbolic Representation Error Description
5006 OTERROR_SLIM_AT_ALREADY_HELD User attempted to run more

sessions of an application
than allowed (for information
on license management,
refer to the Administrators
Guide: Wyse WSMTM).
5010 OTERROR_SLIM_USER_DISABLED Disabled or deleted user

attempted to run an
application session.
7003 OTERROR_APS_BAD_PAGE_NUMBER The page requested is not

valid. Either the appset has
been unloaded or badly
published.
8001 OTERROR_DB_CONNECT_FAILURE Servers could not connect to

the database. Be sure that
the ODBC and JDBC
configurations are correct
and DB is up.
10021 OTERROR_MONITOR_TERMINATED Monitor terminated.
100020 OTERROR_OUT_OF_MEMORY AutoInstall component

cannot download the
configuration XML, usually
because of an old AutoInstall
version.
B Booting Wyse WSM on PXE and
Non-PXE Networks
To download a Wyse bootstrap file and begin streaming a Wyse WSM client, many
networks use Intel’s PXE (Preboot eXecution Environment, also called “pixie”). PXE is
supported in many BIOS, but not all networks are configured to use PXE.
This appendix describes how to boot Wyse WSM clients on networks that don’t support
PXE or that haven’t been modified to support PXE or standard DHCP. It also describes the
PXE and non-PXE boot-up process, the prerequisites for performing a non-PXE boot-up,
and how to boot Wyse WSM in a non-PXE network.
Comparing PXE and Non-PXE Boot-Ups

The boot-up process for Wyse WSM clients is different in the PXE and non-PXE
environment. This section examines the boot-up process, boot-up requirements, and
boot-up features in PXE and non-PXE networks.
PXE and Non-PXE Boot-Up Processes

The PXE and non-PXE boot-up processes are different. This section compares the
different boot-up processes.
In each environment, the bootstrap file resides in a different location:
• PXE environment: The WSM PXE bootstrap file (vldrmi13.bin) resides on a network
TFTP server that is accessible by the WSM client.
• Non-PXE environment: The WSM non-PXE bootstrap file (secrmi13.bin) resides on a
hard disk, floppy disk, or USB key attached to the WSM client.
The boot-up process in the PXE and non-PXE environment is as follows:
PXE Boot-Up Non-PXE Boot-Up

1 The WSM client boots up with the LAN/ The WSM client boots up to the hard
PXE boot option enabled. disk, floppy disk, or USB-key device.
2 In BIOS, the PXE client is executed. BIOS loads and initiates the WSM
non-PXE bootstrap file from the hard
disk, floppy disk, or USB-key device.
3 The BIOS PXE client obtains network The WSM non-PXE bootstrap file tries to
configurations and boot-server obtain network configurations from the
information from the DHCP server (for standard DHCP server. If DHCP fails, the
this to occur, the DHCP or proxy DHCP user can enter network configurations
server must support PXE extended manually. (These statically configured
protocol). network settings are saved in permanent
storage so that they can be used on
subsequent boot-ups.)
60 Appendix B

3A The BIOS PXE client downloads and
executes the WSM PXE bootstrap file
from the WSM server using TFTP.
4 The WSM PXE bootstrap file The WSM non-PXE bootstrap file
communicates with the WSM Login communicates with the WSM login
server and starts the streaming process. server and starts the streaming process.
PXE and Non-PXE Boot-Up Requirements

The requirements for PXE and non-PXE boot-ups are as follows:

WSM Client Must support PXE v0.99 or Must support PXE v2.0 or above. (PXE is
BIOS above. not used, but the UNDI APIs within PXE
support must be present for the non-PXE
bootstrap file to communicate with the
network. Some BIOS do not load UNDI
support when the PXE Boot option is not
used. A WSM non-PXE bootstrap will fail
with a “No APIs” error when running on
such BIOS.)
If the non-PXE bootstrap file resides on a
USB key, BIOS must support booting up
to a USB key.
DHCP server Must support PXE. Support is optional. If not supported, the
user can enter a static IP for the WSM
client.
WSM bootstrap The WSM bootstrap file The WSM bootstrap file must be
installation must reside on a TFTP programmed into the WSM client’s hard
server that the WSM client disk, floppy disk, or USB key. This is a
can access over the manual process. See “Non-PXE
network. This file’s location Bootstrap Deployment” for details.
is established during the
WSM server installation.
PXE and Non-PXE Boot-Up Features

The features for PXE and non-PXE boot-ups are as follows:

Use DHCP Yes Yes (optional)
Use statically entered network No Yes (if DHCP fails)
configuration (IP, gateway, subnet mask,
DNS servers, domain name)
WSM login server IP Hard-coded in the DNS lookup on
bootstrap file upon hostname
WSM installation “WSMServer” or
manually entered if
DNS fails
Booting Wyse WSM on PXE and Non-PXE Networks 61

Dynamically obtain new WSM login No Yes
servers list from existing login server
Save login servers list to permanent No Yes
storage; use saved settings on
subsequent boot-ups
G key reset (pressing the G key on N/A Yes
boot-up restores the WSM bootstrap file to
default settings)
Non-PXE Bootstrap Deployment

To boot a Wyse WSM client on a network that doesn’t support PXE, the bootstrap file must
reside on a local storage device attached to the WSM client, and the WSM client BIOS
must be able to boot to the storage device where the non-PXE bootstrap file is installed.
Following are deployment options and setup instructions for booting a Wyse WSM client
from a non-PXE bootstrap file located on a floppy disk, hard disk or flash drive, or USB
key.
Wyse supports these non-PXE boot media and WSM client combinations:
• Wyse Vx0 or VLx0 thin clients: USB key, USB floppy disk.
• X86-based PCs: Hard disk, built-in and USB floppy disk.
• VMware virtual session: Floppy disk (in floppy disk image file format).
Launching Non-PXE from a Floppy Disk

A WSM non-PXE boot floppy image can be downloaded from the Wyse Knowledgebase
at this address: www.wyse.com/serviceandsupport/support/kbase.asp.
Configure a VMware virtual session floppy device as follows:
1. Select the WSM non-PXE boot floppy image file provided by Wyse.
2. Connect at power up.
Power up the virtual session when you have finished configuring the virtual session floppy
device.
Configure Wyse thin clients and X86-based PCs as follows:
1. Use any third-party tool (such as dskimage) to program a 1.44MB floppy disk from the
WSM non-PXE boot floppy image you downloaded from the Wyse Web site.
2. Configure the WSM Client BIOS to boot from the built-in or USB floppy disk.
3. Plug in the WSM non-PXE boot floppy and power up the WSM client.
62 Appendix B
Launching Non-PXE from a Hard Disk or Flash Drive

This section explains how to prepare a non-PXE hard disk or flash drive for WSM
non-PXE bootstrap and how to boot from a non-PXE hard disk or flash drive.
Preparing the Hard Disk or Flash Drive

Use the WSM Bootstrap Utility to prepare a hard disk or flash drive so you can use it for a
WSM non-PXE bootstrap. This application is available in the client utilities package.
Note
You cannot create a bootstrap partition on a bootstrap partition previously
created by the WSM Bootstrap Utility. Even if you specify the size of the
partition to be the required 8MB, Windows in most cases rounds the size of
the partition to less than 8MB, rendering the bootstrap invalid. To create a
new bootstrap partition, either erase the old partition and allocate 8MB or
more to it, or create a new partition larger than 8MB.
After you start the utility, you see the WSM Bootstrap Utility dialog box.
Figure 56 WSM Bootstrap Utility dialog box
Follow these steps to prepare a hard disk or flash drive for a WSM non-PXE bootstrap:
1. On the Available Disks drop-down list, choose a drive connected to the system.
Network drives and mapped drives are not listed.
2. On the Drive to Format drop-down list, choose which drive you want to format as the
drive for the WSM non-PXE bootstrap (if a hard disk has existing partitions, all
available partitions will be listed in the Drive to Format drop-down list).
After you choose a drive, the Drive Details section of the dialog box provides
information about the drive you selected. Review this information to make sure the
drive you selected is sufficient for the WSM non-PXE bootstrap:
· Type: Lists the type of drive you selected. Hard disks and flash drives are fixed.
· Format: Lists the format that the drive supports—FAT, FAT32, or NTFS.
· Capacity: Lists the storage capacity of the drive. The minimum capacity
requirement for a non-PXE boot partition is 8MB.
· Partition: Indicates whether the partition you selected is an active partition.
3. Click the Create button to begin creating a non-PXE bootstrap partition on the drive
you selected.
Booting Wyse WSM on PXE and Non-PXE Networks 63
The WSM Bootstrap Utility does the following:

1. Changes the drive’s partition information to show 8MB only.
Note
Even if the drive being partitioned is more than 8MB in size, if you select it as
the WSM non-PXE bootstrap drive, its size is reduced to 8MB and the
remaining capacity is wasted. However, you can reuse the wasted space by
creating another drive using Windows’ Disk Management Console.
2. Formats the drive with the FAT12 format, makes it Active (i.e., bootable), and installs
the WSM non-PXE bootstrap.
Warning
The partition will be repartitioned and reformatted. Any existing files on the
partition will be erased.
In the case of a raw disk with no existing partitions, clicking the Create button begins
creating a non-PXE bootstrap partition on the raw disk. The utility creates an 8MB partition
in FAT12 format, makes it bootable, and installs the non-PXE bootstrap file.
Booting from a Non-PXE Hard Disk or Flash Drive

Follow these steps to boot from a non-PXE hard disk or flash drive:
1. Make sure your WSM client BIOS is configured to boot from the local hard disk.
2. Power up the WSM client.
Launching Non-PXE from a USB Key

To program a USB key as the WSM non-PXE bootstrap partition, the USB flash key must
be preformatted to a bootable hard drive in the FAT16 or FAT32 format. Formatting drives
for FAT16 or FAT32 can be accomplished with any third-party tool that makes bootable
USB keys.
Preparing the USB Key

Follow these steps to prepare the non-PXE USB key:
1. Use a third-party tool to format a USB key to a bootable hard drive in FAT16 or FAT32
format. Note that floppy drive partitions are not acceptable.
2. With the USB key plugged in, launch the WSM Bootstrap Utility.
3. Select the drive letter to which the USB key is mounted.
4. Click Create.
The WSM Bootstrap Utility installs a WSM non-PXE bootstrap file on the USB key. The
drive is not re-formatted; any existing files on the drive are preserved.
64 Appendix B
Booting from a Non-PXE USB Key

Follow these steps to boot to the WSM client:
1. Configure the WSM client BIOS to boot to the USB key.
2. Power on the WSM client.
Configuring BIOS to Boot to the USB Key

Different BIOS have different configuration fields for setting boot priorities and options.
Following are instructions when working with Wyse Vx0 thin clients:
• Boot priorities can be set on the Advanced BIOS Features page.
• Boot Other Device should be enabled. Alternatively, select Hard Disk as one of the
First/Second/Third Boot Devices. If an IDE hard disk or flash drive is installed, make
sure USB-HDD0 is set to the highest priority under the Hard Disk Boot Priority setting.
Note
Some BIOS do not work well with certain USB keys. Such BIOS may not be
able to read the USB key at all, or experience long delays when writing on
the USB key. If the BIOS fails to read the USB key, WSM non-PXE bootstrap
will not be able to run.
Entering Network Configuration Information for Non-PXE Boot-Ups

In a network that does not have a DHCP server, the WSM non-PXE bootstrap file will fail
to obtain the network configuration information from the standard DHCP server. To provide
this information, the user must enter a valid IP address for the client computer, and,
optionally, the gateway IP, subnet mask, and DNS IP on the opening screen (you can
press Esc to bypass a specific input request if you don’t know the information being
requested). Finally, the user must enter at least one WSM Authentication Server IP so that
the client computer can boot up through the WSM server.
Note
Network configuration information is saved in permanent storage so that it
can be used on subsequent boot-ups. To erase previously entered network
configurations, press the G key on boot-up. Users will then be presented with
a G-key menu with one of the options displayed as “<option number>: Clear
previously saved network configurations and Login Server lists?”. Enter
<option number> and confirm the operation by typing “yes” when prompted.
C Installing Your Own SQL Server
In special cases of a large production environment, it is recommended that you install the
Database Server on a server machine that is separate from the Wyse WSM servers. WSM
supports three databases: SQL Server 2000, SQL Server 2005, and SQL Server 2005
Express. Make sure that your network is configured to allow all servers to communicate
with your database on the configured SQL port. All servers will authenticate with the
database using configured credentials. The following sections include instructions for
installing the supported jdatabases.
Caution
You should refer to the documentation provided by the database vendor for
complete installation instructions, performance enhancements, and setup.
Note
IMPORTANT: 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 InstallShield
Wizard as described in "Installing Microsoft SQL Server Using the WSM
Prerequisites File."
Installing SQL Server 2000

To install the Microsoft SQL Server:
1. Start the SQL Server installation and select the Install SQL Server Components
option.
2. Select the Database Server option, select the Local Computer option, and click Next.
3. Select the Create a new instance of SQL server, or install client tools installation
option and click Next.
4. Enter your name, company name, and click Next.
5. After reading and agreeing to the End User License Agreement, click Yes.
6. Select the Server and Client Tools installation option and click Next.
7. Select the Default installation option and click Next.
8. Select the Typical setup type option and click Next.
9. Within the Service Account window, ensure that the Use the same account for each
service option is selected.
66 Appendix C
10.Select one of the following Service Setting options:

• If you plan to install all of the components of the Wyse WSM Core Server onto one
server, select the Use the Local System Account option and click Next.
• If you have a domain level user account, select the Use a Domain User Account
option, enter the appropriate account information, and click Next.
11. Select the Mixed Mode authentication mode option and click Next.
Note
Verify that the database is configured to run in Mixed Mode for
authentication. Wyse WSM uses both ODBC and JDBC to communicate with
the database using SQL authentication. If Mixed Mode is not chosen, the
servers cannot communicate with the database. This setting is located under
the Security tab of the database properties labelled SQL Server and
Windows NT.
12.Click Next to start the installation.

13.Select a licensing mode and click Next.
14.After the setup is complete click Finish.
Installing SQL Server 2005 or SQL Server 2005 Express

Follow these steps to install SQL Server 2005 or SQL Server 2005 Express:
1. Start the SQL Server 2005 installation.
2. Select the Server Components, Tools, Books Online, and Samples option.
3. Click Next to accept the licensing terms and conditions.
4. Click Install to install software components required prior to installing SQL Server
2005.
5. Click Next when the component installation is complete (it may take several minutes
for the components to be installed and configured).
6. After a system configuration check is complete, the Microsoft SQL Server Installation
dialog appears; click Next. You see the Registration Information dialog box.
7. Clear the Hide Advanced Configuration Options check box.
8. Click Next after the next system configuration check is complete.
9. Enter your name and company name; then click Next.
10.. Select the components Database Services and Workstation Client components;
then click Next.
11. Select Default instance (don’t specify a named instance); then click Next.
12.Select Use the Local System Account; then click Next.
13.Select Mixed Mode as your Authentication mode (an important step); then click Next.
Caution
Make sure that the database is configured to run in Mixed Mode for
authentication. Wyse WSM uses both ODBC and JDBC to communicate with
the database using SQL authentication. If Mixed Mode is not chosen, the
Installing Your Own SQL Server 67
servers cannot communicate with the database. You can verify this setting by
looking under the Security tab of the database properties labeled SQL
Server and Windows NT.
14.Select the SQL Collations option button and Dictionary Order, Case-Insensitive, for
Use with 1252 Character Set; then click Next.
15.Clear both of the error usage and reporting boxes; then click Next.
16.Click Install to start the installation (it may take several minutes).
17.Click Next after all components have been installed and configured.
18.Review the installation summary and click Finish.
19.After installation is complete, be sure to enable the TCP/IP communication protocol for
the SQL Server by opening the SQL Server Configuration Manager and enabling the
protocol.
Figure 57 SQL Server Configuration Manager
Note
If you plan to install the database on a separate server, install the SQL Server
Client Tools on the same machine that will host the WSM server software.
Installing the Latest Microsoft SQL Server Service Pack

It is recommended that you download and install the latest service pack for the SQL
Server version that you are using. For SQL Server 2000, Service Pack 3A or later is
required. For complete information on SQL service packs, refer to the Microsoft Web site.
Note
If you are given the option to modify the Authentication Mode during service
pack installation, select Mixed Mode to allow the Wyse WSM Core Server
software to access the database.
68 Appendix C

Figures
1 Installation Wizard - Core Server 13
2 License Agreement - Core Server 14
3 Destination Folder - Core Server 14
4 Streaming Directory Information - Core Server 15
5 WSM Server Information Window 15
6 Database Server - Core Server 15
7 Database Server and Authentication Method - Core Server 16
8 Ready to Install the Program - Core Server 17
9 Installing WSM Core Server 17
10 WSM Server Configuration - Core Server 17
11 Installation Wizard Completed - Core Server 18
12 Login page 20
13 Import Server License page 20
14 Configure Active Directory page - expanded 21
15 Add Domain page 21
16 Import Groups page 22
17 System Overview Configurations page 22
18 Core Server Details page 23
19 InstallShield Wizard - WSM Client 26
20 License Agreement - WSM Client 27
21 Customer Information - WSM Client 27
22 Destination Folder - WSM Client 28
23 Ready to Install the Program - WSM Client 28
24 Installing WSM Client 28
25 Windows Logo testing message - WSM Client 29
26 Found New Hardware Wizard - WSM Client 29
27 Installing hardware - WSM Client 29
28 Completing the Found New Hardware Wizard - WSM Client 30
29 WSM Client Config Wizard 30
30 InstallShield Wizard Completed - WSM Client 31
31 OSMVDiskImage.exe 32
32 WSM VDisk Image Creation Utility 32
33 Building Virtual Disk 33
34 Done message 33
35 WSM Client Login in progress message 34
36 System Settings Change message 35
37 InstallShield Welcome - Edge Server 37
38 License Agreement - Edge Server 38
39 Destination Folder - Edge Server 38
40 Streaming Directory Information - Edge Server 38
41 WSM Server Information - Edge Server 39
42 Warning message - Edge Server 39
43 Database Server - Edge Server 39
44 Database Server and Authentication Method - Edge Server 40
45 Ready to Install the Program - Edge Server 40
46 Installing WSM Edge Server 41
47 WSM Server Configuration dialog box - Edge Server 41
48 InstallShield Wizard Completed - Edge Server 41
49 InstallShield Wizard - WSM Client Upgrade 46
50 Installing - WSM Client Upgrade 47
51 InstallShield Wizard Completed - WSM Client Upgrade 47
52 WSM Client Installer Information - WSM Client Upgrade 47
53 Missing file message 51
70
54 Services folder and WSM files 53

55 WSMClientPostConfig.exe 54
56 WSM Bootstrap Utility dialog box 62
57 SQL Server Configuration Manager 67
Tables
1 Server Hardware Requirements 8
2 Server Software Requirements 8
3 DHCP server options 11
4 Error codes, symbolic representation, and error description 57
Installation Guide
Wyse WSMTM Release 2.3

Issue: 040609
Written and published by:

Wyse Technology Inc., April 2009
Created using FrameMaker® and Acrobat®

WSM 2.3 Installation Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

WSM 2.3 Installation Guide

Uploaded by

Copyright:

Available Formats

Installation Guide

Wyse WSM™ Release 2.3

End User License Agreement (“License”)

Restricted Rights Legend

3 Preparing for Installation 7

4 Installing and Configuring the WSM Core Server 13

5 Starting Wyse WSM for the First Time 19

6 Installing and Configuring the WSM Client 25

7 Installing and Configuring a WSM Edge Server 37

9 Upgrading Wyse WSM 45

B Booting Wyse WSM on PXE and Non-PXE Networks 59

C Installing Your Own SQL Server 65

About this Guide

Organization of this Guide

Wyse Technical Support

Links to Related Documentation and Services

Introducing Wyse WSM

Wyse WSM Key Components

Wyse WSM Services

General Overview of the Wyse WSM Setup Process

This page intentionally blank.

Recommended Technical Knowledge

Planning for Your Installation

Table 1 Server Hardware Requirements

Category Minimum Requirements Recommended

CPU 1 GHz CPU 3 GHz dual CPU or higher

RAM 512 MB 1 GB or higher

Disk Space 20 GB + AppSets size 20 GB (RAID) + AppSets

Network Interface Card (NIC) 100 Mbps 100 Mbps/1 Gbps

Table 2 Server Software Requirements

Component Software Requirements

Operating System Microsoft Windows 2000 Server SP4 or Windows 2003

Database Server Microsoft SQL Server 2000, 2005, or 2005 Express

Directory Service (optional) Microsoft Active Directory

System Security and Credentials

Server to Server Communication Ports

Server License Files

Installing Microsoft SQL Server Using the WSM Prerequisites File

Configuring a DHCP Server

Table 3 DHCP server options

03 Gateway Specific to the network.

06 IP Address of the Specify the IP address of DNS server that

60 Client Identifier (Use Only if the DHCP Server is on the Same

This page intentionally blank.

Installing the WSM Core Server

Figure 1 Installation Wizard - Core Server

2. Click Next to open the License Agreement window.

Figure 2 License Agreement - Core Server

Figure 3 Destination Folder - Core Server

4. Click Next to open the Streaming Directory Information window.

Figure 4 Streaming Directory Information - Core Server

5. Click Next to open the WSM Server Information window.

Figure 5 WSM Server Information Window

Figure 6 Database Server - Core Server

8. Use the following guidelines:

• Enter the Username for the database (default is wsmdb).

Figure 7 Database Server and Authentication Method - Core Server

9. Use the following guidelines:

Figure 8 Ready to Install the Program - Core Server

10.Click Install to begin the installation.

Figure 9 Installing WSM Core Server

Figure 10 WSM Server Configuration - Core Server

Figure 11 Installation Wizard Completed - Core Server