Administrators Guide

Wyse WSM™ Release 3.5

Issue: 070910
PN: 883874-02 Rev. B
Copyright Notices
© 2010, 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
Finding the Information You Need in this Guide 2
Wyse Technical Support 2
Related Online Resources Available at Wyse 2
Wyse Online Community 2

2 Overview 3
WSM Functional Areas 3
Getting Started 4
Logging In 4
Understanding the System Overview Page 5
Changing Your Administrator Password 6
Changing Your Site Administrator Password 6
Navigating in WSM 6
Filtering Feature 7
Using Message Areas and Quick-Links 7
Logging Out 7
About Using Active Directory Integration 7
Understanding the Levels of Active Directory Integration 7
Using Active Directory Integration with and without SSL 8

3 Site Groups 9
Managing Site Groups 10
Adding Site Groups 11
Editing Site Groups 12

4 Sites 13
Managing Sites 14
Creating a Headquarters Site 16
Adding Site Templates 17
Creating a Linked Site 19
Editing Sites 21

5 Operating Systems 25
Managing Operating Systems 25
Adding OS Images 27
Editing OS Images 29
Adding, Editing, or Deleting Operating System Classes 33
Adding, Editing, or Deleting Device Classes 34
iv Contents

6 Applications 35
Managing Application Images and Application Licenses 35
Adding Application Images 37
Editing Application Images 39
Adding Application Licenses 41
Editing Application Licenses 42

7 Server Groups 43
Managing Server Groups 43
Understanding the Default and User-Created Server Groups 44
Adding Server Groups 46
Editing Server Groups 47

8 Servers 49
Managing Servers 49
Editing Servers 51
Managing Services for a Server 54

9 Device Groups 55
Managing Device Groups 55
Understanding the Default and User-Created Device Groups 56
Adding a Device Group 58
Editing Device Groups 59
Reassigning Devices to a Different Device Group 61
Sending Commands to Devices in a Device Group 62

10 Devices 63
Managing Devices 63
Adding Devices 65
Editing Devices 67
Changing the Device Group Assignment for a Device 70
Adding an OS Image to a Device 71
Updating an OS Image Assignment for a Device 72
Sending Commands to Devices 73

11 User Groups 75
If Your WSM is Integrated with Active Directory Read this First 75
Managing User Groups 76
Adding User Groups 78
Adding User Groups without Active Directory Integration 78
Adding User Groups with Active Directory Integration 79
Editing User Groups 80
Editing User Groups without Active Directory Integration 80
Editing User Groups with Active Directory Integration 81

12 Users 83
If Your WSM is Integrated with Active Directory Read this First 83
Managing Users without Active Directory Integration 84
Adding Users without Active Directory Integration 86
Editing Users without Active Directory Integration 87
Changing User Passwords without Active Directory Integration 88
 Contents v

13 System Settings 89
Managing System Settings 89
Managing Device Templates 94
Adding Device Templates 96
Editing Device Templates 98
Changing the Device Group Assignment for a Device Template 100
Adding an OS Image to a Device Template 101
Importing Server Licenses 101
Active Directory Configuration 102
Managing Active Directory Domains 103
Active Directory Domains Page 103
Adding Domains 105
Editing Domains 106
Importing User Groups from a Domain 108
Content Distribution Configuration 109
Database Configuration 110
Site Configuration 111
Renaming an SQL Server 112
Managing Virtual Centers 112
Importing Devices from a File 116

14 Reports 117
Generating Reports 117
Aggregated Servers Report 118
Aggregated Servers/Images Report 119
Aggregated Devices Report 120
Client Report 121
License Usage Report 121
Standard Usage Report 122
Activation Report 122
Subscription Report 123

A System Maintenance 125

Managing Passwords Used by WSM 125
Backing Up the WSM Database for System Recovery 125
About WSM Server Services 126
Understanding and Using the Log Files of WSM 126
About WSM System Monitoring 127

B Load Balancing 129

How Load Balancing Works 129
Using Server Groups and Device Groups 129
How WSM Selects Boot Servers in the Server Group 130
Volatile and Persistent Cache Mode 131
Setup for Load Balancing 131

C Updating OS Images and Application Images 133

Updating an OS Image 133
Updating an Application Image 137
Preparing an Application Image Update 138
vi Contents

D Using Driver Injection 139

Requirements and Known Limitations 139
Overview of Steps 140
Detailed Steps 140

E Using the Wyse UniPlat Tool 145

Installing Wyse UniPlat Tool 145
About the Wyse UniPlat Tool 145
Creating a Backup Windows Partition 146
Restoring a Windows Partition 146
Creating a UniPlat Disk File 147
Creating the Initial File 147
Setting UniPlat Disk File Properties 147
Information Properties Tab 147
Description Properties Tab 147
Options Properties Tab 148
Inserting Files into a UniPlat Disk File 149
Restoring a UniPlat Disk File to a Partition 150
Creating a Single OS Image that Supports Multiple Hardware Platforms 150
Requirements for a UniPlat Disk File and Supported Platforms 150
Creating a Combined UniPlat Disk File 151
Reinstalling Drivers for the Current Platform 153
Creating a “Golden” OS Image from Current OS Images 154
Hardware and Partition Requirements 154
Creating the Golden Image 155
Checking and Changing the HAL of a Computer 156
Checking the HAL on a Computer 156
Changing the HAL on a Computer 157
Limitations and Known Issues 158

Tables 159
1 Introduction
WSM is a software-based thin-computing solution that allows IT staff to deploy a
standardized operating system and applications to stateless thin computers (or
thin-computing devices) from a central location. By streaming the entire operating system
and applications, WSM makes it possible for thin computers to operate just like a PC, but
without the local storage. Streaming the operating system and applications independent of
each other makes it easier for IT to backup, update, manage, maintain, and support many
desktops with minimal staff. This solution improves security, lowers IT costs, and provides
the power and flexibility of a personal computer for the end user while providing the
management benefits of thin computing to the IT administrators.
WSM streams Windows operating systems and applications on-demand from a server to
network computing devices without requiring a local hard drive, local operating system, or
local management. By streaming the Windows operating system and applications when
users request them, WSM provides users with all of the power of a personal computer, but
with lower up-front and ongoing costs, as well as improved security and manageability.
With WSM, you can standardize operating system images across your organization and
deliver applications based on user roles and responsibilities. Administrators can easily
provision new applications or updates to existing applications without having to modify the
operating system image. WSM further expands the portfolio of the thin computing
solutions that are available from Wyse Technology and allows you to expand the benefits
of thin computing throughout your enterprise.
In addition to reducing IT costs associated with deploying and maintaining software across
the enterprise, WSM helps eliminate downtime when deploying patches to both operating
systems and applications. Simply rebooting the device ensures that the client software is
upgraded to the latest version. IT administrators also enjoy granular control to ensure
consistency of the deployed software across the enterprise. The stateless nature of the
devices (unless connected to the corporate network) contribute to a secure environment,
while due to the protected system drive, IT departments can quickly recover from virus
attacks and other security hazards. Wyse Technology products easily recover from either
a hardware failure (by replacing the device) or from a software failure (by overwriting the
virtual system drive).

About this Guide

This guide is intended for administrators of the WSM system. It provides information and
detailed system configurations, to help administrators design and manage a WSM
environment. It also explains how to use 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
WSM system.
2 Chapter 1

Finding the Information You Need in this Guide

You can use either the Search window or Find toolbar to locate a word, series of words, or
partial word in an active PDF document. For detailed information on using these features,
refer to the Help in your PDF reader.

Wyse Technical Support

To access Wyse technical resources, visit http://www.wyse.com/support. If you still have
questions, you can submit your questions using the Wyse Self-Service Center (on the
Wyse.com home page, go to Support > Knowledge Base > Home tab) 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.

Related Online Resources Available at Wyse

Getting Started Guide: Wyse WSM ApplianceTM is intended for administrators of the WSM
system. It provides a setup and configuration overview of the entire WSM system to help
you get your WSM environment up and running quickly and easily.
Installation Guide: Wyse WSMTM is intended for administrators of the WSM system. It
describes the WSM installation process for Windows servers and clients. This guide
provides the step-by-step instructions you need to install and configure a WSM
environment. It also includes the requirements you must address before you begin the
installation procedures.

Publisher Guide: Wyse WSMTM is intended for administrators of the WSM system. It
describes how to use WSM Publisher to publish applications and to make them available
for distribution.

Advanced Administrators Guide: Wyse WSMTM is intended for administrators of the WSM
system. It provides information on various WSM subjects that are outside the scope of the
Administrators Guide: Wyse WSMTM because they require a higher level of expertise and
functional usage. It does not describe how to install, maintain, or perform ordinary
configuration and administration of WSM. However, this guide extends the information
provided in the Administrators Guide: Wyse WSMTM and the Installation Guide: Wyse
WSMTM so that power users can customize their WSM environment for specific needs.
Users Guide: Wyse WSMTM is intended for users of the WSM Client system. It provides
detailed instructions on using the 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.

Wyse Online Community

Wyse maintains an online community where users of our products can seek and exchange
information on user forums. Visit the Wyse Online Community forums at:
http://community.wyse.com/forums.
2 Overview
This chapter provides a brief overview of the functional areas within the WSM system. It
also provides important information on the general features of the system to help you
quickly get started as a WSM administrator. In addition, this chapter contains important
information to help you decide whether or not you want to integrate Active Directory with
your WSM system.

WSM Functional Areas

In addition to the System Overview page, WSM is divided into several functional areas:
• Overview - Allows you to quickly view important summary information for each
functional area of the WSM system.
• Site Groups - Allows you to view and manage the WSM Site Groups.
• Sites - Allows you to view the WSM sites.
• Operating Systems - Allows you to view and manage the WSM Operating Systems.
• Applications - Allows you to view and manage the WSM Application Images and
Application Licenses.
• Server Groups - Allows you to view and manage the WSM Server Groups.
• Servers - Allows you to view and manage the WSM Servers.
• Device Groups - Allows you to view and manage the WSM Device Groups.
• Devices - Allows you to view and manage the WSM Devices.
• User Groups - Allows you to view and manage the WSM User Groups.
• Users - Allows you to view and manage the WSM Users.
• System Settings - Allows you to configure the system settings of WSM.
• Reports - Allows you to create and view the WSM reports.
In WSM, each functional area has a set of automated tools that helps you to perform your
administrator duties and daily activities in that functional area. WSM tracks the status of
each of the functional areas necessary to successfully maintain your WSM environment.

Tip
WSM supports Microsoft IE 6.0 or later.
4 Chapter 2

Getting Started
One of the best ways to get started as a WSM administrator is to become familiar with the
system and learn how to get where you want to go. After you become familiar with the
general features of the system, you can refer to the various sections of this guide for more
details on specific areas.
To begin using WSM you need to know about:
• "Logging In"
• "Understanding the System Overview Page"
• "Changing Your Administrator Password"
• "Navigating in WSM"
• "Logging Out"

Logging In
If you have never started WSM and this is your first log-in, refer to the Installation Guide:
Wyse WSMTM for instructions on starting WSM for the first time.
To log in any time after you have completed your first log-in to WSM, be sure to use your
correct Admin Username (default is admin) and Password (default is admin).

Tip
If your database has connection problems, the Database Configuration page
will automatically appear instead of the Login page. For information on
configuring the database, refer to "Database Configuration."

To log in to the Administrator Console:

1. Open the Administrator Console Login page by clicking Start > WSM Server > WSM
Console 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/).

Figure 1 Login page

2. Enter your Admin Username and Password.

3. Click Login to open the System Overview page.
 Overview 5

Understanding the System Overview Page

The System Overview page allows you to quickly view important status information about
the WSM system. By clicking a link in the Category or Requires Attention columns, you
can undertake a task or address a problem.

Figure 2 System Overview page

Links on the System Overview page include:

• About - Provides information about the WSM software and product license. This link is
also located on the main page of each functional area.
• Logout - Allows you to log out of the WSM system. This link is also located on the
main page of each functional area.
• Category Links - Provides you with quick access to the main functional areas.
Functional area links are also located across the top of the main page of each
functional area.
• System Settings - Opens the System Settings page, where you can configure the
settings of the WSM system.
• Reports - Opens the Reports page, where you can view reports on servers, Sites,
devices, OS, Application, and usage information.
• Change Admin Password - Allows you to change your administrator password. This
link is also located on the System Settings page.
• Change Site Admin Password - (Site Installations Only) Allows you to change your
Site administrator password. This link is also located on the System Settings page.
• Configuration Wizard - Allows you to view and edit the license and Active Directory
configurations.
• Requires Attention Links - Allows you to quickly go to functional areas of the system
that require your attention. These links (marked with a warning sign) are located in the
Requires Attention column on the System Overview page and in the functional area
where attention is required.
6 Chapter 2

Changing Your Administrator Password

After logging in, you can change your Administrator password by clicking the Change
Admin Password link on the System Overview page to open and use the Change Admin
Password page.

Figure 3 Change Admin Password page

Changing Your Site Administrator Password

(If you have Remote Sites) After logging in, you can change your Site Administrator
password by clicking the Change Site Admin Password link on the System Overview
page to open and use the Change Site Admin Password page.

Tip
While a Headquarters administrator can always change the Site Admin
Password, the Headquarters administrator can prevent the Site administrator
from changing the Site Admin Password by selecting the HQ manages Site
Admin Password check box on the System Settings page (see "Managing
System Settings").

Figure 4 Change Password for Site Admin page

Navigating in WSM
Navigating in WSM is as easy as clicking your mouse button. WSM is a fully integrated
system, allowing you to perform your daily administrator activities quickly and efficiently.
WSM is easy to use because common navigation and process features are available
throughout the system. For example, you can sort lists according to a heading by clicking
on the column heading you want. You can also list your selected heading in ascending or
descending order by clicking on that column heading again.
 Overview 7

Filtering Feature
While in WSM, you can filter and sort through various lists to organize items in ways that
are helpful to you. For example, you can filter and sort a list of servers by Name, IP
Address, OS Image, Application Image, and Status. The WSM filtering feature allows you
to locate and go to what you want quickly and efficiently.
In some areas, there are multiple filtering steps to help you find the item you want. For
example, on the Applications page you can filter by server first, and then filter by
application name.

Using Message Areas and Quick-Links

In addition to the Requires Attention column on the System Overview page, message
areas and Quick-Links are also available throughout the system to help you run and
maintain your WSM environment.

Logging Out
To log out of WSM, click the Logout link. This link is always available in the upper-right
corner of the Administrator Console.

About Using Active Directory Integration

This section contains important information about Active Directory to help you decide
whether or not you want to integrate Active Directory with your WSM system.

Understanding the Levels of Active Directory Integration

WSM integrates with Active Directory on two major levels:
• Device (Computer Account) Level - On a device level, WSM will automatically
manage the creation and maintenance of the computer accounts in the appropriate
Active Directory Organizational Unit.
• User Level - On a user level, WSM will re-use the group structure that is created in
Active Directory. You do not have to re-create the users and groups, that are needed
for application assignment, within WSM. An additional user level benefit is single
sign-on capability; where user credentials entered during the Windows log-on are used
for WSM application streaming authentication.

Tip
If Active Directory integration is not enabled, then a user must enter user
credentials as follows:
For an OS Image mode of Persistent Cache (Shared Mode) - Only the first
time they log in to WSM.
For an OS Image mode of Volatile Cache (Shared Mode) - Each time they
log in to WSM.
8 Chapter 2

Using Active Directory Integration with and without SSL

WSM can operate with or without Secure Sockets Layer (SSL) with respect to the Active
Directory connection. This option is controlled through a WSM system setting (Enable
SSL Connection) on the Active Directory Configuration page (see "Active Directory
Configuration").
In Active Directory integration without SSL, the communication between the Administrator
Console, Active Directory server, and a WSM Server occurs using a non-SSL protocol.
The OS Authentication Service must be run with a domain account that has privileges to
add and modify computer accounts in Active Directory (members of the default group
named Account Operators or Domain Administrators have the privilege to create and
maintain computers accounts). The user account and password used while adding the
domain must also have these same privileges. For convenience, you can use the same
username and password for both the computer account and user account, although it is
not necessary. The WSM Server will use these credentials to connect to Active Directory
and perform all operations on the device/computer accounts in Active Directory.
In Active Directory integration with SSL, WSM uses SSL for communications with the
Active Directory server. The digital certificate installed on the Domain Controller can be
either a third party certificate or a Microsoft Certificate Authority (CA). In the Microsoft
Certificate Authority case, the certificate must be an Enterprise Root CA. Using Active
Directory integration with SSL, you have the flexibility to:
• Trust any secure Domain Controller - The WSM Server will work with any Domain
Controller which has a digital certificate installed.
• Enforce the Domain Controller certificate - The digital certificate installed on the
Domain Controller must be imported into WSM. After the certificate is imported into
WSM, the WSM Server will communicate only with the Domain Controllers that have
this certificate. Thus, the enforcement of the certificate is carried out by WSM before
the communication between WSM and the Domain Controller can be established.
3 Site Groups
This chapter describes how to perform routine Site Group management tasks using the
Administrator Console. It provides information on managing the Site Groups in your WSM
system.

Tip
Site Groups are intended only for environments with a large number of WSM
Sites. First time users and or users with small deployments can skip this
section.

Site Groups enable you to organize or group together several Sites for easier
management. The grouping of Sites can be done in any manner that suits your needs.
There are no hard rules on the number of Sites per Site Group. Some groups may have
just one Site each, while other groups may have dozens or even hundreds of Sites.
Typically, grouping is based on the following factors:
• Geographic - Where Sites may be grouped together based on their location (such as
a building, campus, city or state).
• Load-balancing and Throttling of Content Distribution (deployment of OS
Images, Application Images, and Patches) - Images can be deployed on a Site
Group basis (one or more groups at a time). For deployments with hundreds or
thousands of Sites, this is a convenient way to deploy images to many remote Sites
with a single mouse click. Administrators can control the load on their WAN by using
smaller numbers of Sites in each group.
• Customized OS Images for Different Sites - If one set of Sites will share a common
OS Image, and a different set will be using a different OS Image, it would be
convenient to organize them into different Site Groups (note that in this case, you
would use a different Site Template for each group).
10 Chapter 3

Managing Site Groups

Clicking the Site Groups link from any functional area main page opens the Site Groups
page. This page allows you to quickly view and manage the Site Groups that are available
(see Table 1). It also allows you to easily display the Site Groups you want by using the
filtering feature.

Figure 5 Site Groups page

Although the Site Groups page shows you all of the Site Groups available in the WSM
system, you can use the following guidelines to view the Site Groups you want:
• Name Contains - Name of a Site Group (use only letters, numbers, dashes, spaces,
the @ character, and periods).
After entering your criteria, click Filter to view the results. You can then select the Site
Groups you want, and begin performing your tasks.
Table 1 provides a quick overview of what you can do using the Site Groups page.

Table 1 Routine Site Group Tasks - Site Groups page

Tasks You Can Do How Details

Add a Site Group to the system. Click the Add Site Group link “Adding Site Groups” on page 11.
and follow the wizard.

Edit a Site Group in the system. Click a Name link in the Site “Editing Site Groups” on page 12.
Groups area and make your
changes.

Delete a Site Group from the Select the check box next to the
system. name of the Site Group you want
in the Site Groups area (you can
use Select All or Deselect All as
needed), click Delete Selected,
and confirm the deletion. The Site
Group is deleted and is no longer
shown in the list of available Site
Groups on the Site Groups page.
You can also delete a Site Group
by using the Delete this Site
Group link on the Site Group
Details page.
Deleting a Site Group reassigns
all Sites in the group to the
Default Site group.
IMPORTANT: You cannot delete
the Default Site group.
 Site Groups 11

Adding Site Groups

To add a Site Group for WSM use, click the Add Site Group link on the Site Groups page
and follow the wizard.
Use the following guidelines:
1. On the Site Groups page, click the Add Site Group link to open the Add Site Group
wizard.

Figure 6 Add Site Group wizard

2. Enter a Name (use only letters, numbers, dashes, spaces, the @ character, and
periods).
3. (Optional) Enter a Description.
4. Click Next to open the Assign Sites page.
5. Determine the Sites you want to include in the Site Group using the assignment page.
6. Click Finish. The Site Group is added to the list of Site Groups on the Site Groups
page.
12 Chapter 3

Editing Site Groups

On the Site Groups page, click the Name link of the Site Group you want to edit to open
the Site Group Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Site Group is
then modified and can be viewed in the list of available Site Groups on the
Site Groups page).

Figure 7 Site Group Details page

• Enter the Name.

• (Optional) Enter a Description.
• Optional Related Tasks you can perform using the Site Group Details page:
• Move Sites to a Different Site Group - Click the Move Sites to Different Site
Group link to open and use the Move Sites wizard.

Caution
You cannot move the Headquarters Site from the Default Site Group to
another user-created Site Group.
4 Sites
This chapter describes how to perform routine Site management tasks using the
Administrator Console. It provides information on managing the Sites in your WSM
system.
WSM supports the concept of Sites, whereby geographically dispersed locations can run
WSM independently; each with its own database instance, yet configured and managed
from a central location (Headquarters). Each WSM Site includes a Core Server, database,
and optionally, streaming servers. This allows remote offices or locations to continue
normal operations even if network connectivity to the central-office or Headquarters is
interrupted.
Each WSM Site receives its entire configuration information from a Site Template. A Site
Template specifies the OS and Application Images as well as Server Group, Device
Group, Device Template, User Groups, and other key parameters. Any change made to
the Site Template is propagated automatically to all of the Sites that are “linked” to that
Site Template. Thus, Site Templates make it easy to configure and manage large numbers
of Sites. Some large WSM deployments may configure and manage hundreds of remote
Sites through just one or two Templates. Other deployments may choose to use one
Template for each Site Group or use a unique Template for each of their individual Sites.
The high-level sequence of steps for setting up a Site-based deployment is:
1. Select one of your Sites to be designated as Headquarters. This is the central Site from
which all configuration, deployment, and management operations are initiated. Convert
this Site from a Stand-Alone Site to a Headquarters Site using the steps in "Creating a
Headquarters Site."
2. From the WSM Administrator Console at the Headquarters Site, create one or more
Site Templates. This includes registering and configuring OS and Application Images,
Server Groups, Device Groups, Device Templates, and User Groups that will be used
by the Site Templates. These Site Templates will be used during the creation and
configuration of remote Sites.
3. From the WSM Administrator Console at each remote WSM installation, convert its
Site category from a Stand-Alone Site to a Linked Site, as described in "Creating a
Linked Site." Note that remote Sites cannot be added directly from Headquarters; the
operation must be initiated from the remote Site.
14 Chapter 4

Managing Sites
Clicking the Sites link from any functional area main page opens the Sites page. This
page allows you to quickly view and manage the WSM Sites that are available (see
Table 2). It also allows you to easily display the Sites you want by using the filtering
feature.

Tip
During a Core Server installation for a Site, configuration settings to assign a
Site category are made through an installation wizard. If ever needed in the
future (after your Core Server installation is complete for your Site), you can
reassign a Site category by using the WSM Sites Configuration page as
described in "Site Configuration."

Figure 8 Sites page

Although the Sites page shows you all of the Sites available in the WSM system, you can
use the following guidelines to view the Sites you want:
• Name Contains - Name of a Site (use only letters, numbers, dashes, spaces, the @
character, and periods).
• Site Category - Category of a Site (all, Stand-Alone, Linked, Site Template,
Headquarters)
• Site Group - Name of the Site Group to which the Site is assigned. Use the Site Group
Select link to select the Site Group.
• Max Rows - Maximum number of rows to display on a page (enter the number).
After entering your criteria, click Filter to view the results. You can then select the Sites
you want, and begin performing your tasks.
Table 2 provides a quick overview of what you can do using the Sites page.
 Sites
Table 2 Routine Site Tasks - Sites page
Tasks You Can Do
Add a Stand-Alone Site to the
system.
Create a Headquarters Site.
(Headquarters Only) Add a Site
Template to the system to
manage the Linked Sites
associated with it.
Create a Linked Site.
Edit a Site in the system.
Delete a Site from the system.
How
Use the Core Server installation
procedures in Installation Guide:
Wyse WSMTM.
Use the Core Server installation
procedures in Installation Guide:
Wyse WSMTM to add a
Stand-Alone Site, and then
convert it to a Headquarters Site.
Click the Add Site Template link
and follow the wizard.
Use the Core Server installation
procedures in Installation Guide:
Wyse WSMTM to add a
Stand-Alone Site, and then
convert it to a Linked Site.
Click a Name link in the Sites
area and make your changes.
Select the check box next to the
name of the Site you want in the
Sites area (you can use Select
All or Deselect All as needed),
click Delete Selected, and
confirm the deletion. The Site is
deleted and is no longer shown in
the list of available Sites on the
Sites page.
15
Details
After adding a Stand-Alone Site,
you can keep it, or convert it to a
Headquarters Site or a Linked
Site.
To configure a Site to be a
Headquarters, see “Creating a
Headquarters Site” on page 16.
To configure a Site to be a Linked
Site, see “Creating a Linked Site”
on page 19.
NOTE: You can reassign a Site
category by using the WSM Sites
Configuration page as described
in "Site Configuration."
“Creating a Headquarters Site” on
page 16.
“Adding Site Templates” on
page 17.
“Creating a Linked Site” on
page 19.
“Editing Sites” on page 21.
You cannot delete a Site that has
Servers or Server Groups
assigned to it. However, you can
use the WSM Sites Configuration
page as described in “Site
Configuration” on page 111 to
change a Linked Site to a
Stand-Alone Site and remove the
Site entry from the Headquarters
list of available Linked Sites.
You can also delete a Site by
using the Delete this Site link on
the Site Details page.
IMPORTANT: You cannot delete
the Default Site.
16 Chapter 4

Creating a Headquarters Site

Use the following guidelines:
1. After using the Core Server installation procedures in the Installation Guide: Wyse
WSMTM to add a Stand-Alone Site, log in to the WSM Administrator Console at the
location of the installation.
2. Click System Settings to open the System Settings page, and then click the Site
Configuration link to open the WSM Sites Configuration page.

Figure 9 Site Configuration page - Headquarters Site example

3. Select the Headquarters Site option.

4. Enter the Name of the Site.
5. Enter the Site Description.
6. Click Setup Site. After creating the Headquarters Site, you can view the Server Details
page to see that the Headquarters Core Server Services are successfully running
(Status is Up on each service) by clicking the Servers tab, and then clicking the Name
link of the Headquarters Core Server.
 Sites 17

Adding Site Templates

(Headquarters Only) Site Templates allow you to easily manage the Linked Sites
associated with them. The high-level sequence of steps for creating a Site Template is:
1. From the Sites page, add a Site Template. This Site Template will contain information
to be used by the Linked Sites. A Site Template must have one Device Group, one
Server Group, one Device Template, and one or more OS and Application Images.
2. Create a Server Group for the Site Template.
3. Add an OS Image and assign it to the Site Template.
4. Assign the OS Image to the Server Group of the Site Template.
5. Once the OS Image is ready, change the mode from Private to Shared Persistent or
Shared Volatile and click the Allow Content Distribution link on the OS Image Details
page.
6. Create a Device Group for the Site Template and assign it to the Server Group you
created.
7. Assign the OS Image to the Device Group.
8. Create a Device Template for the Site Template and assign the Device Group to it.
9. Now you have the minimum information needed for a Site. At this point, you can also
assign Application Images to the Site Template and the Server Group of the Site
Template.
To add a Site Template for WSM use, click the Add Site Template link on the Sites page
and follow the wizard. Use the following guidelines:
1. On the Sites page, click the Add Site Template link to open the Add Site Template
wizard.

Figure 10 Add Site Template wizard

2. Enter a Name (use only letters, numbers, dashes, spaces, the @ character, and
periods).
3. (Optional) Enter a Description.
4. Click Next to open the Assign Site Group page.
5. Determine the Site Group you want using the assignment page.
6. Click Finish. The Site is added to the list of Sites on the Sites page.

Caution
A Site Template configuration is not complete (so you can use it to manage
your Linked Sites) until you add the following:
Server Group - On the Site Template Details page, click the Add Server
18 Chapter 4

Group to this Site link to open and use the Add Server Group wizard (see
"Adding Server Groups").
Device Group - On the Site Template Details page, click the Add Device
Group to this Site link and follow the wizard (see "Adding a Device Group").
Device Template - On the System Settings page, click the Manage Device
Templates link, and then add a device template (see "Adding Device
Templates").
OS Image - On the Operating Systems page, click the Add OS Image link to
open and use the Add OS Image wizard (see "Adding OS Images").
 Sites 19

Creating a Linked Site

Use the following guidelines:
1. After using the Core Server installation procedures in the Installation Guide: Wyse
WSMTM to add a Stand-Alone Site, log in to the WSM Administrator Console at the
location of the installation.

Tip
These instructions are provided to help you convert a Stand-Alone Site to a
Linked Site. Advanced users can also use the Core Server installation
procedures in the Installation Guide: Wyse WSMTM to add a Linked Site, and
then follow the installation Configuration Wizard to configure the site using
the same site information as described in step 3 (all items/instructions should
be provided by the Headquarters Administrator).

2. Click System Settings to open the System Settings page, and then click the Site
Configuration link to open the WSM Sites Configuration page.

Figure 11 Site Configuration page - Linked Site example

3. Select the Linked Site option, and then configure the following (all items/instructions
should be provided by the Headquarters Administrator):
• Enter the Name of the Site. Note that the site name must be unique, and not
already registered at Headquarters.
• Enter the Site Description.
• Enter the Site Code.

Tip
This can be a maximum of five characters, and is used as a prefix to the
device-template name, when creating names for new devices in the system.
It is recommended that this code is an abbreviation of the Site name, or
otherwise indicative of this Site. This will result in device-names that clearly
20 Chapter 4

indicate which Site they belong to. Note that the device-name is also used as
the hostname of the device, and will be registered into Active Directory if
Active Directory integration is enabled.

• Enter the Headquarters Server IP.

• Select or clear the Headquarter in Https check box.

Caution
Selecting this option will cause the remote Site to use HTTPS for all
communication with the Headquarters site. If you select this option, you must
have registered a server certificate at the Headquarters Site. Further, if the
server certificate is not signed by a well-known CA, you will need to register
the Root CA certificate with WSM before attempting to convert this remote
Site to a Linked Site.

• Enter the Site Template Name.

• Enter the Site Group Name.
4. Click Setup Site. After creating the Linked Site, you can view the Server Details page
to see that the Linked Site Core Server Services are successfully running (Status is Up
on each service) by clicking the Servers tab, and then clicking the Name link of the
Linked Site Core Server.
 Sites 21

Editing Sites
On the Sites page, click the Name link of the Site you want to edit to open the Site Details
page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Site is then
modified and can be viewed in the list of available Sites on the Sites page).

Figure 12 Site Details page - local Site view

22 Chapter 4

Figure 13 Site Details page - Linked Site view from Headquarters

Caution
The Site Details page you see depends on which Site you select. If you click
on a “local” Site name (using either the Administrator Console at
Headquarters, or using the Administrator Console at a remote Site), the local
Site view will be displayed (Figure 12). However, if you click on the Site name
of any Linked Site using the Administrator Console at Headquarters, the
Linked Site view will be displayed (Figure 13).
Tasks (links) available for use on the Site Details page depend on the type of
Site you are modifying (you will only see links that are relevant to your task).

• Enter a Name (you cannot change the name of a Linked Site until after you reassign a
Linked Site category to a Stand-Alone Site by using the WSM Sites Configuration page
as described in "Site Configuration").
• (Optional) Enter a Description.
• The Site Group of the Site is shown.
• The Site Type of the Site is shown.
• (Headquarters Only) The Site Template of the Headquarters is shown.
• Optional Related Tasks you can perform using the Site Details page:
• (Remote Site Details page, at Headquarters) Refresh Site - Click the Refresh Site
link to send a message to the remote Site to synchronize with Headquarters (to
obtain updated configuration information from Headquarters and send updated
status information to Headquarters).
• (Site Details page at the Administrator Console of a Remote Site - not
Headquarters) Sync with Template - Click the Sync with Template link to have
the remote Site synchronize with Headquarters (to obtain updated configuration
information from Headquarters and send updated status information to
Headquarters.
• (Local Site Only) Change the Core Server Assignment - Click the Change Core
Server Assignment link to open and use the Select Core Server page.
• (Site Templates Only) Generate a Site Template XML - Click the Generate Site
Template XML link to open and use the File Download dialog box (Site Template
XMLs are used for disaster recovery purposes in large WSM environments with
complex Site designs and are discussed in Advanced Administrators Guide: Wyse
WSMTM).
• (Local Site and Templates Only) Add a Server Group to this Site - Click the Add
Server Group to this Site link to open and use the Adding Server Group wizard
(see "Adding Server Groups").
Sites 23

• (Local Site and Templates Only) Add a Device Group to this Site - Click the Add
Device Group to this Site link and follow the wizard (see "Adding a Device
Group").
• (Local Site and Templates Only) Edit a Server Group belonging to this Site -
Click a Name link in the Server Groups Belonging to area to open and use the
Server Group Details page (see "Editing Server Groups").
• (Local Site and Templates Only) Edit a Device Group associated with this Site -
Click a Name link in the Device Groups Associated with area to open and use the
Device Group Details page (see "Editing Device Groups").
• (Local Site Only) Edit a Server belonging to this Site - Click a Name link in the
Servers Belonging to area to open and use the Server Details page (see "Editing
Servers").
• (Local Site Only) Edit a Device belonging to this Site - Click a Name link in the
Devices Belonging to area to open and use the Devices Details page (see "Editing
Devices").
• (Local Site Only) Delete a Device belonging to this Site - Select the check box
next to the name of the Device you want in the Devices Belonging to area (you can
use Select All or Deselect All as needed), click Delete Selected, and confirm the
deletion.
• (Local Site Only) Send supported commands to Devices in the system - Select
the Devices you want and click Send Command to open and use the Send Device
Command page (see "Sending Commands to Devices").
• (Local Site Only) Abort the previously scheduled commands to Devices in the
system - Select the Devices you want, click Abort Command to open a message
confirming the removal of the commands, and then click OK to abort the
commands.
• (Local Site Only) Edit an OS Image associated with this Site - Click a Name link
in the OS Images Associated with area to open and use the OS Image Details page
(see "Editing OS Images").
• (Local Site Only) Edit an Application Image associated with this Site - Click a
Name link in the Application Images Associated with area to open and use the
Application Image Details page (see "Editing Application Images").
24 Chapter 4

This page intentionally blank.

5 Operating Systems
This chapter describes how to perform routine operating system management tasks using
the Administrator Console. It provides information on managing the OS Images, OS
Classes, and Device Classes in your WSM system.

Managing Operating Systems

Clicking the Operating Systems link from any functional area main page opens the
Operating Systems page. This page allows you to quickly view and manage the WSM
operating systems that are available (see Table 3). It also allows you to easily display the
operating systems you want by using the filtering feature.

Figure 14 Operating Systems page

Although, the Operating Systems page shows you all of the operating systems available in
the WSM system, you can use the following guidelines to view the operating systems you
want:
• Name Contains - Name of an operating system for client support (use only letters,
numbers, dashes, spaces, the @ character, and periods).
• OS Class - Name of the OS Class to which an operating system is assigned (for
example, Windows XP or Windows 7).
• Device Class - Class value of the network device to which the operating system is
assigned (for example, Wyse V00).
After entering your criteria, click Filter to view the results. You can then select the OS
Images you want, and begin performing your tasks.
26 Chapter 5
Table 3 provides a quick overview of what you can do using the Operating Systems page.
Table 3 Routine Operating System Tasks - Operating Systems page
Tasks You Can Do How
Add an OS Image to the system Click the Add OS Image link and
for streaming. follow the wizard.
Edit an OS Image in the system. Click a Name link in the OS
Images area and make your
changes.
Delete an OS Image from the Select the check box next to the
system. name of the OS Image you want
in the OS Images area (you can
use Select All or Deselect All as
needed), click Delete Selected,
and confirm the deletion. The OS
Image is deleted and is no longer
shown in the list of available OS
Images on the Operating
Systems page.
Add, edit, or delete an OS Class. Click the Manage OS Classes
link and use the Manage OS
Classes page.
Add, edit, or delete a Device Click the Manage Device
Class. Classes link and use the Manage
Device Classes page.
Details
“Adding OS Images” on page 27.
IMPORTANT: To allow the OS
Image to be streamed, be sure to
use the Change Server Group
Assignments link to open and
use the Assign Server Groups For
OS Image page as described in
"Editing OS Images."
“Editing OS Images” on page 29.
NOTE: Before you can delete an
OS Image, it must be unassigned
from a Site. You cannot delete an
OS Image which is assigned to a
Site.
“Adding, Editing, or Deleting
Operating System Classes” on
page 33.
“Adding, Editing, or Deleting
Device Classes” on page 34.
 Operating Systems 27

Adding OS Images
To add a OS Image for WSM use, click the Add OS Image link on the Operating Systems
page and follow the wizard.
Use the following guidelines:
1. On the Operating Systems page, click the Add OS Image link to open the Add OS
Image wizard.

Figure 15 Add OS Image wizard

2. Complete the Add OS Image page using the following guidelines:

• Enter the Name of the OS Image (use only letters, numbers, dashes, spaces, the @
character, and periods).
• Select the File Name of the OS Image you want to add (if no file exists for you to
select, you must capture an OS Image and place the file into the OS Images folder
located where you installed the WSM Core Server as described in the Installation
Guide: Wyse WSMTM - for example,
C:\Program Files\Wyse\WSM\StreamingDir\OSOS Images).
3. Click Next to open the Select Site Groups page.
4. Determine the Site Groups you want to include using the filter page.
5. Click Next to open the Select Sites page.
6. Determine the Sites you want to include using the assignment page.
7. Click Finish. The OS Image is added to the list of available OS Images on the
Operating Systems page. The OS Image Details page is displayed to allow you to
make further configurations if necessary (see "Editing OS Images").
At this point, the OS Image has been registered at the Core Server only. It is not yet
available at streaming servers or at remote Sites. You may want to customize this OS
Image further, before making it available to other servers. The following are possible next
steps.
• If this is a newly captured OS Image, it will be in private mode (No Cache (Private
Mode)) at this time. It is recommended that you boot a device from this OS Image at
least once, before setting it in shared mode (either Persistent Cache (Shared Mode)
or Volatile Cache (Shared Mode)). This will allow peripheral discovery and driver
registration to finish, and avoids messages such as new hardware discovered or
reboot your system. This is also a good time to review and customize the OS Image to
suit your needs. After customizing has been completed, shut down the device.
• If the OS Image is a copy or has been used earlier, this is still a good time to customize
the it. If necessary, set the OS Image to No Cache (Private Mode), boot up a device
and modify the OS Image as appropriate. After customizing has been completed, shut
down the device.
28 Chapter 5

At this point, the OS Image can be prepared for deployment to remote servers and Sites (if
any), and for streaming. Follow these steps:
• Edit the OS Image settings to set the OS Image to shared mode (either Persistent
Cache (Shared Mode) or Volatile Cache (Shared Mode)). If the OS Image has
multiple partitions, all of them must be in shared mode. You can use a mix of
Persistent Cache (Shared Mode) and Volatile Cache (Shared Mode), based on your
needs. Be sure to click Save Changes after making your changes.
• Click the Allow Distribution of this OS Image link at the top of the page. Until you
click this link, the OS Image will not be copied to streaming servers or to remote Sites.
Note that this is a one-time operation for each OS Image. Once you have clicked the
Allow Distribution of this OS Image link for an OS Image, the OS Image is effectively
locked down, and no configuration changes can be made to the OS Image from that
point onward. In particular, the OS Image cannot be put back into private mode (No
Cache (Private Mode)) again. Changes to the content of the OS Image can be done
only through the OS Image Patch Process.
• To allow the OS Image to be streamed from streaming servers, the OS Image must be
assigned to those servers. Click the Change Server Group Assignments link to open
and use the Assign Server Groups For OS Image page as described in "Editing OS
Images." Note that if the OS Image has been assigned to a Site Template, be sure to
assign the OS Image to the Server Group that is associated with that Site Template.

Tip
Once an OS Image has been assigned to a Server Group, the OS Image will
automatically be copied to all of the streaming servers in that Sever Group.
You can track the distribution process by clicking the Track Content
Distribution link on the System Settings page to open and view the Content
Distribution Summary page.

(Content Distribution Features: For Remote Sites Only) After adding the OS Image to the
system for use and preparing the image for distribution as described above, you must
assign the image to the Site Groups and schedule the distribution of the image to those
Site Groups. Follow these steps:
• Click the Change Site Group Assignment link, and then select the Site Groups to
which you want to deploy the OS Image.
• Click the Deploy New OS Image Version for Site Group link, and then select the
version of the OS Image to deploy and the Site Groups to which you want the OS
Image deployed (for newly registered OS Images, there will be only one version).
Verify that the Version Deployed column lists the correct OS Image for each Site
Group.
• Click the Schedule link in the Deployment Date column on the OS Image Details page
to open and use the Deployment Date page (select the date and time you want the Site
Group to start the content distribution, and then click Schedule). A copy will be
scheduled to all Sites in the Site Group(s). The Core Server at each of the remote Sites
will copy the OS Image, and then automatically schedule a copy to each of the
streaming servers that belong to the Server Groups to which the OS Image was
assigned.
• You can track the progress of the copy operations using the Aggregated Servers/
Images Report page (found on the Reports page). Note that data in this report is
updated periodically, based on the Aggregation Period specified in the Systems
Settings page.
Note that until the OS Image becomes available at a remote Site, it cannot be streamed to
devices at that Site. You can track up-to-date progress information at the remote Site,
using the WSM Administrator Console at that remote Site (click the Track Content
Distribution link on the System Settings page to open and view the Content Distribution
Summary page).
 Operating Systems 29

Editing OS Images

Caution
You must turn off all streaming clients of the OS Image before editing the OS
Image.

On the Operating Systems page, click the Name link of the operating system you want to
edit to open the OS Image Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the OS Image is
then modified and can be viewed in the list of available OS Images on the
Operating Systems page).

Figure 16 OS Image Details page - Edit OS Image

30 Chapter 5

• Enter the Name of the OS Image for client support (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• The File Name is shown.
• (Optional) Enter a Description.
• The Image Version is shown for the WSM VDisk Image Creation Utility.
• Enter the Version you want for the OS Image.
• Select the OS Class.
• Select the Device Class.
• Depending on whether or not you want to enable safe boot for the OS Image, select or
clear the Enable Safe Boot check box.
• The OS Image ID is shown.
• Select the First Partition Mode, Second Partition Mode, and Third Partition Mode for
the OS Image (either No Cache (Private Mode), Persistent Cache (Shared Mode),
or Volatile Cache (Shared Mode)).
No Cache (Private Mode), Persistent Cache (Shared Mode), and Volatile Cache
(Shared Mode) are the three operating system options in which OS Images can be
delivered to the device:
· Private Mode option - An administrator mode that allows complete read-write
access to the OS Image. Any changes made in the OS Image are permanent. This
is the mode to use when you need to make any configuration changes or when you
are applying patches to the OS Image (as described in "Updating an OS Image"). In
this mode, only one device can boot from the OS Image at any time. To use Private
Mode on the OS Image, select the No Cache (Private Mode) option
· Shared Mode options - The modes in which a single OS Image is shared between
multiple devices. The original OS Image is in read-only mode. That is, any changes
made by any user on any device are not added to the base OS Image. For each
device, a separate file is created in the Write Cache directory that will store the
changes that are made by the user using this device. These changes include 1)
changes made by the operating system itself (including swapping files or other
operations that the operating system performs, such as updating the registry for
specific operations, and so on); and 2) changes made by the users who log in to the
device (including changes to the files stored in the virtual C: drive, user profile
information, or temporary files created by different applications, and so on). Shared
Mode options include Persistent Cache (Shared Mode) and Volatile Cache
(Shared Mode). In Persistent Cache (Shared Mode) the Write Cache is persistent
across reboots (that is, any changes made on the OS Image are stored and are
available to users when they reboot the device). To use this mode on the OS Image,
select the Persistent Cache (Shared Mode) option. In Volatile Cache (Shared
Mode) the Write Cache is discarded when the device reboots (that is, after the
device reboots the device is always returned to the original base OS Image). To use
this mode on the OS Image, select the Volatile Cache (Shared Mode) option.
• (Volatile Cache (Shared Mode) For All Partitions Only) Depending on whether or not
you want to enable multicast for the OS Image, select or clear the Enable Multicast
check box (if you enable multicast, you must enter the Multicast IP Address and
Multicast Time To Live, select the Multicast Invite Type, and enter the Multicast
Invite Period). For more information on using multicast, go to the Wyse Knowledge
Base and search for “WSM Multicast Streaming: Best Practices.”
Operating Systems 31

• Optional Related Tasks you can perform using the OS Image Details page:
• Add a New OS Image - Click the Add a New OS Image link to open and use the
Add OS Image page (see "Adding OS Images").
• Start Patch Process for this OS Image - Click the Start Patch Process for this
OS Image link to open and use the Select OS Image Copy page (see "Updating an
OS Image").
• Start Patch Process for this OS Image with an existing delta file - Click the
Start Patch Process for this OS Image With Existing Delta File link to open and
use the Select OS Image Copy page. Use this process only with OS Images for
which a delta already exists on file system.
• Generate an OS Image XML - Click the Generate OS Image XML link to open and
use the File Download dialog box (OS Image XMLs are used for disaster recovery
purposes in large WSM environments with complex Site designs and are discussed
in Advanced Administrators Guide: Wyse WSMTM).
• Rollback an OS Image to the previous version - Click the Rollback this OS
Image link and confirm.
• Allow Distribution of this OS Image - Click the Allow Distribution of this OS
Image link and confirm (allows the distribution and use of the OS Image).
• Change a Site Group Assignment for the OS Image - Click the Change Site
Group Assignment link to open and use the Assign Site Groups for OS Image
page (allows you to assign/un-assign an OS Image to a Site Group).
• Deploy a New OS Image Version for a Site Group - Click the Deploy New OS
Image Version For Site Group link to open and use the wizard.
• Edit a Site Group associated with the OS Image - Click a Name link in the Site
Groups Assigned area to edit the Site Group associated with the OS Image (see
"Editing Site Groups").
• Edit an OS Image Deployment Date for a Site Group - Click the Schedule link in
the Deployment Date area to open and use the Deployment Date page.
• Edit a Site associated with the OS Image - Click a Name link in the Sites
Assigned area to edit the Site associated with the OS Image (see "Editing Sites").
• Change a Site Assignment for the OS Image - Click the Change Site
Assignment link to open and use the Assign Sites for OS Image page.
• Change a Server Group Assignment - Click the Change Server Group
Assignments link to open and use the Assign Server Groups For OS Image page.
• Synch the Server Group Assignments for the OS Image - Click the Synch
Server Group Assignments link to open and use the Synch Server Group
Assignment page.
• Edit the Server Group associated with the OS Image - Click a Name link the
Server Groups Hosting area to edit the Server Group associated with the OS Image
(see "Managing Server Groups").
• Edit the Server associated with the OS Image - Click a Name link in the Servers
Streaming area to edit the Server associated with the OS Image (see "Editing
Servers").
• Reset the lock on the server - Click the Release Lock link to reset the lock on the
server. About Release Lock: WSM helps you avoid making changes to servers
that are currently in use by others. In some cases where you want to modify a
server (but receive a message that you are unable to modify a server at this time)
and you know that no one else is using it, clicking the Release Lock link allows you
to reset the lock on the server and make the modifications you want.

Caution
Release locks should be used only as a last resort. If the locks are released
for devices that are actively using the OS Image, it may cause operating
32 Chapter 5

system failures (BSOD issues). In general, it is recommended that if you

want to delete the OS Image assignment or change the OS Image assigned
to a device, then you should use device commands to shut down the device
before making these changes. For information on using device commands,
refer to "Sending Commands to Devices." For information on updating an OS
Image, refer to "Updating an OS Image Assignment for a Device."

• View the details about the hierarchy of an OS Image - Hierarchy details are
shown in the Hierarchy area.
 Operating Systems 33

Adding, Editing, or Deleting Operating System Classes

Clicking the Manage OS Classes link on the Operating Systems page opens the Manage
OS Classes page. You can use the Manage OS Classes page to add, edit, or delete OS
Classes.

Figure 17 Manage OS Classes page

Use the following guidelines:

• Adding - Enter a new OS Class name in the Add a new OS Class box, click Add, and
then click Close. The OS Class is added to the list of available OS Classes on the
Operating Systems page.
• Editing - Enter a new name for an existing OS Class, click Rename, and then click
Close.
• Deleting - Select the check box of the OS Class you want to delete (you can use
Select All or Deselect All as needed), click Delete Selected, and then click Close.
34 Chapter 5

Adding, Editing, or Deleting Device Classes

Clicking the Manage Device Classes link on the Operating Systems page opens the
Manage Device Classes page. You can use the Manage Device Classes page to add, edit,
or delete Device Classes.

Figure 18 Manage Device Classes page

Use the following guidelines:

• Adding - Enter the new Device Class name in the Add a new Device Class box, click
Add, and then click Close. The Device Class is added to the list of available Device
Classes on the Operating Systems page.
• Editing - Enter a new name for an existing Device Class, click Rename, and then click
Close.
• Deleting - Select the check box of the Device Class you want to delete (you can use
Select All or Deselect All as needed), click Delete Selected, and then click Close.
6 Applications
This chapter describes how to perform routine application management tasks using the
Administrator Console. It provides information on managing the Application Images and
Application Licenses in your WSM system.

Managing Application Images and Application Licenses

Clicking the Applications link from any functional area main page opens the Applications
page. This page allows you to quickly view and manage the WSM Application Images and
Application Licenses that are available (see Table 4). It also allows you to easily display
the Application Images and Application Licenses you want by using the filtering feature.

Figure 19 Applications page

Although the Applications page shows you all of the Application Images and Application
Licenses available in the WSM system, you can use the following guidelines to view the
Application Images and Application Licenses you want:

Tip
You can use the Filter Application Images By filter or the Filter Application
Licenses By filter or both (one at a time).

• Name Contains - Name of an Application Images or Application Licenses for client

support (use only letters, numbers, dashes, spaces, the @ character, and periods).
36 Chapter 6

• Server - Name of the Server to which the Application Image is assigned. Use the
Server Select link to select the server.
• Group - Name of the User Group to which the Application License is assigned. Use the
Group Select link to select the User Group.
After entering your criteria, click Filter to view the results. You can then select the
Application Images and Application Licenses you want, and begin performing your tasks.
Table 4 provides a quick overview of what you can do using the Applications page.

Table 4 Routine Application Tasks - Applications page

Tasks You Can Do How Details

Add an Application Image to the Click the Add Application Image “Adding Application Images” on
system for streaming. link and follow the wizard. page 37.

Edit an Application Image in the Click a Name link in the “Editing Application Images” on
system. Application Images area and page 39.
make your changes.

Delete an Application Image from
the system.
Select the check box next to the
name of the Application Image
you want in the Application
Images area (you can use Select
All or Deselect All as needed),
click Delete Selected, and
confirm the deletion. The
Application Image is deleted and
is no longer shown in the list of
available Application Images on
the Applications page.
Before you can delete an
Application Image, it must be
unassigned from a server. You
cannot delete an Application
Image which is assigned to a
server.
You can also delete an
Application Image by using the
Delete this Application Image
link on the Application Image
Details page.

Add an Application License to the Click the Add Application “Adding Application Licenses” on
system to enforce application License link and follow the page 41
licensing policies. wizard.

Edit an Application License in the Click a Name link in the “Editing Application Licenses” on
system. Application Licenses area and page 42.
make your changes.

Delete an Application License
from the system.
Select the check box next to the You can also delete an
name of the Application License Application License by using the
you want in the Application Delete this Application License
Licenses area (you can use link on the Application License
Select All or Deselect All as Details page.
needed), click Delete Selected,
and confirm the deletion. The
Application License is deleted
and is no longer shown in the list
of available Application Licenses
on the Applications page.
 Applications 37

Adding Application Images

To add a Application Image for WSM use, click the Add Application Image link on the
Applications page and follow the wizard.
Use the following guidelines:
1. On the Applications page, click the Add Application Image link to open the Add
Application Image wizard.

Figure 20 Add Application Image wizard

2. Complete the Add Application Image page using the following guidelines:
• Select the File Name of the Application Image you want to add (if no file exists for
you to select, you must copy an Application Image and place the file into the
Application Images folder located where you installed the WSM Core Server; for
example, C:\Program Files\Wyse\WSM\StreamingDir\APPimages).
• Enter the Name of the Application Image (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• (Optional) Enter a Description.
• Enter the Version.
• Depending on whether or not you want to automatically subscribe this Application
Image (with user unsubscribe flexibility) to an end user when the user first logs on
to the WSM Client, select or clear the Auto Subscribe Application check box
(note that after the user has been subscribed to the application during the first login,
the user has the option of unsubscribing from this application at any time
thereafter).
• Depending on whether or not you want to automatically subscribe this Application
Image (without user unsubscribe flexibility) to an end user when the user first logs
on to the WSM Client, select or clear the Mandatory Application check box (note
that after the user has been subscribed to the application during the first login, the
user will not have the option of unsubscribing from this application; if the user tries
to unsubscribe, a message displays stating that the application is mandatory and
cannot be unsubscribed).
3. Click Next to open the Select Site Groups page.
4. Determine the Site Groups you want to include using the filter page.
5. Click Next to open the Select Sites page.
38 Chapter 6

6. Determine the Sites you want to include using the assignment page.
7. Click Finish. The Application Image is added to the list of available Application Images
on the Applications page.
At this stage, the Application Image has been registered at the Core Server only. It is not
yet available at streaming servers or at remote Sites. To prepare the Application Image for
deployment to remote servers and Sites (if any), follow these steps:
• Click the Allow Distribution of this Application Image link at the top of the page.
Until you click on this link, the Application Image will not be copied to streaming servers
or to remote Sites. Note that this is a one-time operation for each Application Image.
Once you have clicked the Allow Distribution of this Application Image link for an
Application Image, the Application Image is effectively locked down, and no
configuration changes can be made to the Application Image from that point onward.
• To allow the Application Image to be streamed from streaming servers, the Application
Image must be assigned to those servers. Click the Change Server Group
Assignments link to open and use the Assign Server Groups For Application Image
page as described in "Editing Application Images." Note that if the Application Image
has been assigned to a Site Template, be sure to assign the Application Image to the
Server Group that is associated with that Site Template.
(Content Distribution Features: For Remote Sites Only) Unlike OS Images, Application
Images are automatically copied to all remote Sites to which the Application Image has
been assigned. You can track the progress of the copy operations using the Aggregated
Servers/Images Report page (found on the Reports page). Note that data in this report is
updated periodically, based on the Aggregation Period specified in the Systems Settings
page.
Note that until the Application Image becomes available at a remote Site, it cannot be
streamed to devices at that Site. You can track up-to-date progress information at the
remote Site, using the WSM Administrator Console at that remote Site (click the Track
Content Distribution link on the System Settings page to open and view the Content
Distribution Summary page).
 Applications 39

Editing Application Images

On the Applications page, click the Name link of the Application Image you want to edit to
open the Application Image Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Application
Image is then modified and can be viewed in the list of available Application
Images on the Applications page).

Figure 21 Application Image Details page

40 Chapter 6

• Enter the Name.

• (Optional) Enter a Description.
• Enter the Version.
• Depending on whether or not you want to automatically subscribe this Application
Image (with user unsubscribe flexibility) to an end user when the user first logs on to
the WSM Client, select or clear the Auto Subscribe Application check box (note that
after the user has been subscribed to the application during the first login, the user has
the option of unsubscribing from this application at any time thereafter).
• Depending on whether or not you want to automatically subscribe this Application
Image (without user unsubscribe flexibility) to an end user when the user first logs on to
the WSM Client, select or clear the Mandatory Application check box (note that after
the user has been subscribed to the application during the first login, the user will not
have the option of unsubscribing from this application; if the user tries to unsubscribe,
a message displays stating that the application is mandatory and cannot be
unsubscribed).
• The File Name, Application Image ID, and File ID are shown.
• Optional Related Tasks you can perform using the Application Image Details page:
• Add an Application License for this Image - Click the Add an Application
License for this Image link to open and use the Add Application License page (see
"Adding Application Licenses").
• Add a Patch for this Application Image - Click the Add a Patch for this
Application Image link to open and use the Updating Application Image page (see
"Updating an Application Image").
• Add a New Application Image - Click the Add a New Application Image link to
open and use the Add Application Image page (see "Adding Application Images").
• Allow Distribution of this Application Image - Click the Allow Distribution of
this Application Image link and confirm (this will allow the distribution and use of
the Application Image).
• Change a Site Assignment for the Application Image - Click the Change Site
Assignment link to open and use the Assign Sites for Application Image page.
• Change a Server Group Assignment - Click the Change Server Group
Assignment link to open and use the Assign Server Groups For App Image page.
• Synch the Server Group Assignment for the Application Image - Click the
Synch Server Group Assignments link to open and use the Synch Server Group
Assignment page.
• Edit the Server Group associated with the Application Image - Click a Name
link the Server Groups Hosting area to edit the Server Group associated with the
Application Image (for details on editing a server group, refer to "Managing Server
Groups").
• Edit the Servers associated with the Application Image - Click a Name link in
the Servers Streaming area to edit the Servers associated with the Application
Image (for details on editing a server, refer to "Editing Servers")
• Add an Application License for this Image - Click the Add an Application
License for this Image link to open and use the Add Application License page (see
"Adding Application Licenses").
• Edit the Application Licenses associated with the Application Image - Click a
Name link in the Application Licenses Using area to edit the Application Licenses
associated with the Application Image (see "Editing Application Licenses").
 Applications 41

Adding Application Licenses

To add a Application License for WSM use, click the Add Application License link on the
Applications page and follow the wizard.
Use the following guidelines:
1. On the Applications page, click the Add an Application License link to open the Add
Application License wizard.

Figure 22 Add Application License wizard

2. Complete the Add Application License page using the following guidelines:
• Enter the Name of the Application License you want to add (use only letters,
numbers, dashes, spaces, the @ character, and periods).
• Select an Application Image (click the Select an Application Image link to open
use the Select an Application Image page).
• Select a Sessions per User option (either a custom amount or Unlimited). If you
select a custom amount, enter the number of Sessions. Be aware that once an
Application License is in use, Sessions per User cannot be edited.
• Select a Duration option (either a custom amount or Unlimited). If you select a
custom amount, enter the number of Days.
• Select a Maximum Concurrent Sessions option (either a custom amount or
Unlimited). If you select a custom amount, enter the number of Sessions.
3. Click Next to open the Assign to a Group page.

Tip
If you do not have User Groups, click Finish to complete adding the
Application License. The Application License is added to the list of available
Application Licenses on the Applications page and can now be used to
enforce application licensing policies.

4. Determine the User Groups you want to include using the assignment page.
5. Click Finish. The Application License is added to the list of available Application
Licenses on the Applications page and can now be used to enforce application
licensing policies.
42 Chapter 6

Editing Application Licenses

On the Applications page, click the Name link of the Application License you want to edit
to open the Application License Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Application
License is then modified and can be viewed in the list of available Application
Licenses on the Applications page).

Figure 23 Application License Details page

• Enter the Name for the application.

• The Application Image and Sessions per User are shown.
• Select a Duration option (either a custom amount or Unlimited). If you select a custom
amount, enter the number of Days.
• Select a Maximum Concurrent Sessions option (either a custom amount or Unlimited).
If you select a custom amount, enter the number of Sessions.
• Optional Related Tasks you can perform using the Application License Details page:
• Add a New Application License - Click the Add a New Application License link
to open and use the Add Application License page (see "Adding Application
Licenses").
• Delete this Application License - Click the Delete this Application License link
to delete the Application License.
• Change Group Assignment - Click the Change Group Assignment link to open
and use the Assign User Groups For Application page.
• Edit the User Groups associated with the Application License - Click a Name
link in the Assigned Groups area to edit the User Groups associated with the
Application License (for details on editing a user group, refer to "Editing User
Groups").
7 Server Groups
This chapter describes how to perform routine Server Group management tasks using the
Administrator Console. It provides information on managing the Server Groups in your
WSM system.

Managing Server Groups

Clicking the Server Groups link from any functional area main page opens the Server
Groups page. This page allows you to quickly view and manage the WSM Server Groups
that are available (see Table 5). It also allows you to easily display the Server Groups you
want by using the filtering feature.

Tip
Server Groups make it easier to assign OS Images, Application Images, and
Device Groups because you can assign them to all of the Servers in a Server
Group at the same time rather than to each Server individually. For example,
to assign the same OS Image to five different Servers, first create a Server
Group that includes the Servers and then assign the OS Image to the Server
Group. Additionally, whenever you add a Server to an existing Server Group,
that Server is automatically assigned the OS Images and Application Images
of that Server Group.

Figure 24 Server Groups page

44 Chapter 7

Although the Server Groups page shows you all of the Server Groups available in the
WSM system, you can use the following guidelines to view the Server Groups you want:
• Name Contains - Name of a Server Group (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• Site Group - Name of the Site Group to which the Server Group is assigned. Use the
Site Group Select link to select the Site Group.
• Site - Name of the Site to which the Server Group is assigned. Use the Site Select link
to select the Site.
After entering your criteria, click Filter to view the results. You can then select the Server
Groups you want, and begin performing your tasks.
Table 5 provides a quick overview of what you can do using the Server Groups page.

Table 5 Routine Server Group Tasks - Server Groups page

Tasks You Can Do How Details

Add a Server Group to the Click the Add Server Group link “Adding Server Groups” on
system. and follow the wizard. page 46.

Edit a Server Group in the Click a Name link in the Server “Editing Server Groups” on
system. Groups area and make your page 47.
changes.

Delete a Server Group from the
system.
Select the check box next to the
name of the Server Group you
want in the Server Groups area
(you can use Select All or
Deselect All as needed), click
Delete Selected, and confirm the
deletion. The Server Group is
deleted and is no longer shown in
the list of available Server Groups
on the Server Groups page.
You can also delete a Server
Group by using the Delete this
Server Group link on the Server
Group Details page.
Deleting a Server Group
reassigns all Servers in the group
to the Default Server Group.
IMPORTANT: You cannot delete
the Default Server Group.

View all Servers in the system. Click the View All Servers link. Use the information in “Servers”
on page 49 to perform Server
tasks.

Understanding the Default and User-Created Server Groups

WSM provides two types of Server Groups, Default and user-created. The Default Server
Group is created automatically. Administrators can create user-created Server Groups as
needed. Servers cannot belong to more than one Server Group. Each Server must be in
the Default Server Group or a user-created Server Group.

Tip
You can move Servers in and out of the Default Server Group as they are
needed in user-created Server Groups. However, you cannot move Servers
directly from one user-created Server Group to another. To move a Server to
a different user-created Server Group, you must first move it to the Default
Server Group and then move it from the Default Server Group to a
user-created Server Group.
Server Groups 45

Attributes of each Server Group include:

• Default Server Group:
• WSM creates the Default Server Group during installation or during an upgrade.
The Default Server Group is automatically assigned to the first Core Server
installation. There is only one Default Server Group. Its purpose is to store Servers
until, if necessary, they are assigned to a user-created Server Group.
• All Servers in the Default Server Group must be treated the same and share OS
Image, Application Image, and Default Device Group assignments.
• Servers in the Default Server Group must be managed (for OS Image, Application
Image, and Default Device Group attributes) using the Server Group Details page in
the Administrator Console.
• You can move Servers in and out of the Default Server Group as they are needed in
user-created Server Groups.
• When you reassign a Server to the Default Server Group, you must click the Synch
Server Group Assignment link on the OS Image Details page to assign the OS
Image of the group, and click the Synch Server Group Assignment link on the
Application Image Details page to assign the Application Image of the group.
• You cannot delete or modify the Default Server Group.
• User-Created Server Group:
• Administrators create user-created Server Groups as needed.
• All Servers in a user-created Server Group must be treated the same and share OS
Image, Application Image, and Device Group assignments.
• Servers in a user-created Server Group must be managed (for OS Image,
Application Image, and Device Group attributes) using the Server Group Details
page in the Administrator Console.
• You cannot move Servers directly from one user-created Server Group to another.
To move a Server to a different user-created Server Group, you must first move it to
the Default Server Group and then move it from the Default Server Group to a
user-created Server Group.
• When you reassign a Server to a user-created Server Group, its previous OS
Image, Application Image, and Device Group assignments are automatically
stripped away; it adopts the OS Image, Application Image, and Device Group
assignments of the user-created Server Group to which it was reassigned.
• You can delete or modify a user-created Server Group. Deleting a user-created
Server Group reassigns all Servers in it to the Default Server Group.
46 Chapter 7

Adding Server Groups

To add a Server Group for WSM use, click the Add Server Group link on the Server
Groups page and follow the wizard.
Use the following guidelines:
1. On the Server Groups page, click the Add Server Group link to open the Add Server
Group wizard.

Figure 25 Add Server Group wizard

2. Complete the Add Server Group page using the following guidelines:
• Enter a Name.
• Enter a Description.
3. Click Next to open the Select Site Groups page.
4. Determine the Site Groups you want to include using the assignment page.
5. Click Next to open the Select Sites page.
6. Determine the Sites you want to include using the assignment page.
7. Click Next to open the Assign Servers page.
8. Determine the Servers you want to include using the assignment page.
9. Click Finish. The Server Group is added to the list of available Server Groups on the
Server Groups page.
 Server Groups 47

Editing Server Groups

On the Server Groups page, click the Name link of the Server Group you want to edit to
open the Server Group Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Server Group
is then modified and can be viewed in the list of available Server Groups on
the Server Groups page).

Figure 26 Server Group Details page

• Enter the Name.

• (Optional) Enter a Description.
• Site Name is shown.
• Optional Related Tasks you can perform using the Server Group Details page:
• Add a Server Group - Click the Add Server Group link to open and use the
Adding Server Group wizard (see "Adding Server Groups").
• Add or remove a Server to or from the Server Group - Click the Change Server
Assignment link to open and use the Assign Servers For Group page.

Caution
If you want to move a Server from one user-created Server Group to another,
you must first move the Server to the Default Server Group, open the Server
48 Chapter 7

Group Details page of the Server Group to which you want to move the
Server, click Change Server Assignment, and then move the Server from
the Default group to the user-created Server Group you want.

• Manage the Servers of the Server Group - Click the Manage Servers of this
Group link to open and use the Assign Servers to Server Group page.
• Edit an Server associated with this Server Group - Click a Name link in the
Servers Belonging to area to open and use the Server Details page (see "Editing
Servers").
• Edit an Device Group associated with this Server Group - Click a Name link in
the Device Groups Associated with area to open and use the Device Group Details
page (see "Editing Device Groups").
• Edit an OS Image associated with this Server Group - Click a Name link in the
OS Images Associated with area to open and use the OS Image Details page (see
"Editing OS Images").
• Edit an Application Image associated with this Server Group - Click a Name
link in the Application Images Associated with area to open and use the Application
Image Details page (see "Editing Application Images").
8 Servers
This chapter describes how to perform routine Server management tasks using the
Administrator Console. It provides information on managing the Servers in your WSM
system.

Managing Servers
Clicking the Servers link from any functional area main page opens the Servers page.
This page allows you to quickly view and manage the WSM Servers that are available
(see Table 6). It also allows you to easily display the Servers you want by using the
filtering feature.

Tip
During a Server installation, configuration settings are made through an
installation wizard. After your Server installation is complete, you can then
edit and delete a Server by using the Servers page. For information on
adding a Server by using the installation procedures in the Installation Guide:
Wyse WSMTM, refer to Table 6.

Figure 27 Servers page

Although the Servers page shows you all of the Servers available in the WSM system, you
can use the following guidelines to view the Servers you want:
• Name Contains - Name of a Server for client support (use only letters, numbers,
dashes, spaces, the @ character, and periods).
• IP Address - IP Address of the Server.
50 Chapter 8

• Server Group - Name of the Server Group to which the Server is assigned. Use the
Server Group Select link to select the Server Group.
• Site - Name of the Site to which the Server is assigned. Use the Site Select link to
select the Site.
• OS Image - Name of the OS Image to which the Server is assigned. Use the OS Image
Select link to select the OS Image.
• Application Image - Name of the Application Image to which the Server is assigned.
Use the Application Image Select link to select the Application Image.
• Status - Status of the Server (all, Up, or No Response).
• Site Group - Name of the Site Group to which the Server is assigned. Use the Site
Group Select link to select the Site Group.
After entering your criteria, click Filter to view the results. You can then select the Servers
you want, and begin performing your tasks.
Table 6 provides a quick overview of what you can do using the Servers page.

Table 6 Routine Server Tasks - Servers page

Tasks You Can Do How Details

Add a Server to the system.
Use the Edge Server installation
procedures in the Installation
Guide: Wyse WSMTM (you cannot
manually add an Edge Server).
After you have installed an Edge
Server according to the
procedures in the Installation
Guide: Wyse WSMTM, the Edge
Server is automatically added to
the list of Servers available on the
Servers page and the Default
Server Group. NOTE: To assign
an OS Image use the Synch
Server Group Assignment link
on the OS Image Details page; to
assign an Application Image use
the Synch Server Group
Assignment link on the
Application Image Details page.

Edit a Server in the system. Click a Name link in the Servers “Editing Servers” on page 51.
area and make your changes.

Delete a Server from the system.
Select the check box next to the
name of the Server you want in
the Servers area (you can use
Select All or Deselect All as
needed), click Delete Selected,
and confirm the deletion. The
Server is deleted and is no longer
shown in the list of available
Servers on the Servers page.
You cannot delete the Core
Server. Only Edge Servers can
be deleted.
You can also delete a Server by
using the Delete this Server link
on the Server Details page.
 Servers 51

Editing Servers
On the Servers page, click the Name link of the Server you want to edit to open the Server
Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Server is then
modified and can be viewed in the list of available Servers on the Servers
page).

Figure 28 Server Details page

• The Name and Type (for example, Core Server—or Streaming Server for an Edge
Server) of the Server are shown.
• (Optional) Enter a Description.
• Enter the IP Address of the Server (before editing the Server IP Address, you must
stop all of the Server services; after all Server editing is complete, be sure to start all of
the Server services).
• Enter the Streaming Directory containing your OS Images and Application Images
(before editing the Server Streaming Directory, you must stop all of the Server
services; after all Server editing is complete, be sure to start all of the Server services).
• The Status of the Server is shown.
• The WSM Version running on the Server is shown.
52 Chapter 8

• Optional Related Tasks you can perform using the Server Details page:
• Manage Server - Click Manage Server to open a Remote Desktop Connection
dialog box allowing you to specify the Server that you want to access and manage.

Caution
To use the Manage Server command button, you must ensure that the
following requirements are completed on the machine from which you are
accessing the Administrator Console:
1) The Microsoft Remote Desktop Connection Client software must be
installed according to the Microsoft instructions found on the Microsoft Web
site (also be sure that the Microsoft Remote Desktop Connection service is
enabled on the target Server, and on the Core Server).
2) Open the Trusted sites dialog box in Microsoft Internet Explorer (click
Tools > Internet Options > Security > Trusted Sites > Sites), clear the
Require server verification (https:) for all sites in this zone check box,
and then add the following Web sites to the zone: http://<coreserver ip
address> and http://localhost.

Tip
For Windows 2000 users only - The Manage Server command button looks
for the mstsc.exe in the %systemroot%\system32 folder. However, when
you install the terminal service client on Windows 2000, the mstsc.exe is
installed at C:\Progam files\Remote desktop by default. To make the Manage
Server command button execute correctly, you must copy the mstsc.exe
and mstscax.dll to the %systemroot%\system32 folder.

• Delete this Server - (Edge Servers Only) Click the Delete this Server link to delete
the Server.

Caution
Before deleting a Server, all of the assigned OS Images and Application
Images must be unassigned from the Server. In addition, you must also shut
down the devices which are booted from that Server.

• Manage a Service associated with the Server - Click a Service Name link in the
Services area (see "Managing Services for a Server").
For example, the Enable Device Discovery feature of the DHCP Proxy Service
allows you to configure the WSM Server to automatically add new devices to the
system (this feature setting is on a per Server basis). You can use the Enable
Device Discovery feature by selecting the Enable Device Discovery check box in
the DHCP Proxy Service page (click the DHCP Proxy Service link in the Services
area to open the DHCP Proxy Service page). If the Enable Device Discovery
check box is cleared, the WSM Server will only respond to devices which are
already included in the WSM Database. If the Enable Device Discovery check box
is selected, any new device will be added to the WSM system using the WSM
device templates (for information on using device templates, refer to "Adding
Device Templates"). If Active Directory integration is enabled, the new device will be
added to the WSM system based on the appropriate device template that is
applicable.
• Stop or Start a Service - Click the Start link (to start the service) or Stop link (to
stop the service) for the service you want in the Services area (you can also use the
Start All link or Stop All link). The Status list shows whether or not a service is
running (Up) or stopped (Down) for the Server.
Servers 53

• View a Service log - Click the View Log link to view the service log you want in the
Services area.
• Edit the OS Image associated with the Server - (Servers in Default Server Group
Only) Click a Name link in the OS Images Streamed By area (see "Editing OS
Images").

Caution
WSM helps you avoid making changes to OS Images that are currently in
use by others. In some cases where you want to modify an OS Image (but
receive a message that you are unable to modify an OS Image at this time)
and you know that no one else is using it, clicking the Release Lock link on
the OS Image Details page allows you to reset the lock on the OS Image and
make the modifications you want.

• Edit the Application Images associated with the server - (Servers in Default
Server Group Only) Click a Name link in the Application Images Streamed By area
to open and use the Application Image Details page (see "Editing Application
Images").
• View an Application Image log - (Servers in Default Server Group Only) Click the
View Log link to view the Application Image log you want in the Application Images
Streamed By area.
54 Chapter 8

Managing Services for a Server

While editing a Server, you can quickly access and manage a Service for a Server by
clicking a Service Name link in the Services area.

Tip
You can also use the Start All link (to start all of the services) or Stop All link
(to stop all of the services) in the Services area.

Figure 29 Service Details page

The Service Details page shows you the Service Type, Server, Port, and Status of the
Service you selected. Depending on the Service you selected, you may be allowed to
modify the Port that the Service uses. However, in all Service cases you will be able to use
the Start link (to start the service) or Stop link (to stop the service), and the View Log link
(to view the log for the service). After you complete your modifications on the Service
Details page, be sure to click Save Changes. The Service is then modified and can be
viewed in the list of Services on the Server Details page.

Caution
If your DHCP Server and DHCP Proxy Service are running on the same
machine, be sure to select the 4011 Port option.
9 Device Groups
This chapter describes how to perform routine Device Group management tasks using the
Administrator Console. It provides information on managing the Device Groups in your
WSM system (with and without Active Directory integration).

Managing Device Groups

Clicking the Device Groups link from any functional area main page opens the Device
Groups page. This page allows you to quickly view and manage the WSM Device Groups
that are available (see Table 7). It also allows you to easily display the Device Groups you
want by using the filtering feature.

Tip
Device Groups allow you to easily group and manage devices with similar
attributes from a single place, the Device Groups page.

Figure 30 Device Groups page

Although the Device Groups page shows you all of the Device Groups available in the
WSM system, you can use the following guidelines to view the Device Groups you want:
• Name Contains - Name of a Device Group (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• OS Image - Name of the OS Image that is assigned to Device Group. Use the OS
Image Select link to select the OS Image.
• Site Group - Name of the Site Group to which the Device Group is assigned. Use the
Site Group Select link to select the Site Group.
56 Chapter 9

• Server Group - Name of the Server Group that is assigned to the Device Group. Use
the Server Group Select link to select the Server Group.
• Site - Name of the Site to which the Device Group is assigned. Use the Site Select link
to select the Site.
After entering your criteria, click Filter to view the results. You can then select the Device
Groups you want, and begin performing your tasks.
Table 7 provides a quick overview of what you can do using the Device Groups page.

Table 7 Routine Device Group Tasks - Device Groups page

Tasks You Can Do How Details

Add a Device Group to the Click the Add Device Group link “Adding a Device Group” on
system. and follow the wizard. page 58.

Edit a Device Group in the Click a Name link in the Device “Editing Device Groups” on
system. Groups area and make your page 59.
changes.

Edit a Site in the system. Click a Site link in the Device “Editing Sites” on page 21
Groups area and make your
changes.

Delete a Device Group from the Select the check box next to the
system. name of the Device Group you
want in the Device Groups area
(you can use Select All or
Deselect All as needed), click
Delete Selected, and confirm the
deletion. The Device Group is
deleted and is no longer shown in
the list of available Device Groups
on the Device Groups page.
You can also delete a Device
Group by using the Delete this
Device Group link on the Device
Group Details page.
Deleting a device group reassigns
all devices in the group to the
Default device group. You cannot
delete the Default server group.
CAUTION: Deleting a device
group also clears all image
assignments from the devices in
the device group.

View all devices in the system. Click the View All Devices link. Use the information in “Devices”
on page 63to perform device
tasks.

Understanding the Default and User-Created Device Groups

WSM provides two types of Device Groups, Default and user-created. The Default Device
Group is created automatically. Administrators can create user-created Device Groups as
needed. Devices cannot belong to more than one Device Group. Each Device must be in
the Default Device Group or a user-created Device Group.

Tip
You can move Devices in and out of the Default Device Group as they are
needed in user-created Device Groups. However, you cannot move Devices
directly from one user-created Device Group to another. To move a Device to
a different user-created Device Group, you must first move it to the Default
Device Group and then move it from the Default Device Group to a
user-created Device Group.
Device Groups 57

Attributes of each Device Group include:

• Default Device Group:
• WSM creates the Default Device Group during installation or during an upgrade.
The Default Device Group is automatically assigned to the Default Server Group.
There is only one Default Device Group. Its purpose is to store Devices until, if
necessary, they are assigned to a user-created Device Group.
• All Devices in the Default Device Group can be treated individually and can have
their own unique Device Class, Connection Type, Server Group, and OS Image
assignments.
• Devices and Device Templates in the Default Device Group cannot boot in Load
Balanced mode.
• Devices in the Default Device Group can be managed (for Device Class,
Connection Type, Server Group, and OS Image attributes) using their respective
Administrator Console pages.
• You can move Devices in and out of the Default Device Group as they are needed
in user-created Device Groups.
• Because the Default Device Group permits individual Devices to have unique
Device Class, Connection Type, Server Group, and OS Image assignments, a
Device in a user-created Device Group retains its Device Class, Connection Type,
Server Group, and OS Image assignments when it is reassigned to the Default
Device Group.
• You cannot delete or modify the Default Device Group.
• User-Created Device Group:
• Administrators create user-created Device Groups as needed.
• All Devices in a user-created Device Group must be treated the same and share
Device Class, Connection Type, Server Group, and OS Image assignments.
• By default, Load Balanced is the boot selection mode for Devices and Device
Templates in a user-created Device Group. In Load Balanced boot mode, the
system notes which Server in a Server Group is least loaded and assigns that
Server Group to a particular Device in the Device Group (see "System
Maintenance").
• Devices in a user-created Device Group must be managed (for Device Class,
Connection Type, Server Group, and OS Image attributes) using the Device Group
Details page in the Administrator Console.
• You cannot move Devices directly from one user-created Device Group to another.
To move a Device to a different user-created Device Group, you must first move it
to the Default Device Group and then move it from the Default Device Group to a
user-created Device Group.
• When you assign a Device to a user-created Device Group, its previous Device
Class, Connection Type, Server Group, and OS Image assignments are stripped
away; it adopts the Device Class, Connection Type, Server Group, and OS Image
assignments of the user-created Device Group to which it was reassigned.
• You can delete or modify a user-created Device Group. Deleting a user-created
Device Group reassigns all Devices in it to the Default Device Group.
58 Chapter 9

Adding a Device Group

To add a Device Group for WSM use, click the Add Device Group link on the Device
Groups page and follow the wizard.
Use the following guidelines:
1. On the Device Groups page, click the Add Device Group link to open the Add Device
Group wizard.

Figure 31 Add Device Group wizard

2. Complete the Add Device Group page using the following guidelines:
• Enter a Name (use only letters, numbers, dashes, spaces, the @ character, and
periods).
• Enter a Description.
• Select a Device Class.
• Select a Connection Type (either Network or Mobile Disconnected; if you select
Mobile Disconnected, select a Force Provision option of either Enabled or
Disabled).

Tip
In Network mode, the device must always have a LAN connection to a WSM
Server. In Mobile mode, the device can be disconnected from a WSM Server
and still be operational. A Force Provision option of Enabled automatically
provisions the mobile device with an OS Image when connected to, and
booting from, a WSM Server. A Force Provision option of Disabled allows the
user to provision the mobile device with an OS Image when desired (by
right-clicking the WSM Client icon in the system tray and selecting Provision
Disk).

3. Click Next to open the Select Site Groups page.

4. Determine the Site Groups you want to include using the assignment page.
5. Click Next to open the Select Sites page.
6. Determine the Sites you want to include using the assignment page.
7. Click Next to open the Assign Devices page.
8. Determine the Devices you want to include using the assignment page.
9. Click Next to open the Assign Server Group page.
10.Determine the Server Groups you want to include using the assignment page.
11. Click Next to open the Assign Image page.
 Device Groups 59

12.Determine the OS Images you want to include using the assignment page.
13.Click Finish. The Device Group is added to the list of available Device Groups on the
Device Groups page.

Editing Device Groups

Tip
You can edit a user-created Device Group only; you cannot edit the Default
Device Group.

On the Device Groups page, click the Name link of the Device Group you want to edit to
open the Device Group Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Device Group
is then modified and can be viewed in the list of available Device Groups on
the Device Groups page).

Figure 32 Device Group Details page

• Enter the Name.

• (Optional) Enter a Description.
• Select a Device Class.
• Select a Connection Type (either Network or Mobile Disconnected; if you select Mobile
Disconnected, select a Force Provision option of either Enabled or Disabled).

Tip
In Network mode, the device must always have a LAN connection to a WSM
Server. In Mobile mode, the device can be disconnected from a WSM Server
and still be operational. A Force Provision option of Enabled automatically
provisions the mobile device with an OS Image when connected to, and
60 Chapter 9

booting from, a WSM Server. A Force Provision option of Disabled allows the
user to provision the mobile device with an OS Image when desired (by
right-clicking the WSM Client icon in the system tray and selecting Provision
Disk).

• Site Name is shown.

• Site Group Name is shown.
• Select a Server Group (selecting a new Server Group clears the previous OS Image
assignment for all the devices in Device Group).
• Select an Image Name (selecting a new OS Image Name clears the previous OS
Image assignment for all the devices in Device Group).
• Optional Related Tasks you can perform using the Device Group Details page:
• Add a Device Group - Click the Add a New Device Group link to open and use
the Add Device Group wizard (see "Adding a Device Group").
• Delete this Device Group - Click the Delete this Group link to delete the Device
Group.
• Add or remove a Device to or from the Device Group - Click the Change Device
Assignment link to open and use the wizard (see "Reassigning Devices to a
Different Device Group").
• Edit a Device belonging to this Device Group - Click a Name link in the Devices
Belonging to area to open and use the Device Details page (see "Editing Devices").
• Edit a Site belonging to this Device Group - Click a Site link in the Devices
Belonging to area and make your changes (see "Editing Sites").
• Send supported commands to Devices in the system - Select the Devices you
want and click Send Command to open and use the Send Device Command page
(see "Sending Commands to Devices in a Device Group").
• Abort the previously scheduled commands to Devices in the system - Select
the Devices you want, click Abort Command to open a message confirming the
removal of the commands, and then click OK to abort the commands.
Device Groups 61

Reassigning Devices to a Different Device Group

While editing a Device Group, you can reassign devices in a Device Group to a different
Device Group by clicking the Change Device Assignment link on the Device Group
Details page and following the wizard.
Use the following guidelines:
1. On the Device Group Details page, click the Change Device Assignment link to open
the Select Devices wizard.

Figure 33 Select Devices wizard

2. Determine the Devices you want to include using the assignment page.
3. Click Next to open the Select Device Group page.
4. Determine the Device Groups you want to include using the assignment page.
5. Click Next to open the Assign an OS Image page.
6. Determine the OS Image you want to include using the assignment page.
7. Click Next to open the Assign a Server page.
8. Determine the Server you want to include using the assignment page.
9. Click Finish.
62 Chapter 9

Sending Commands to Devices in a Device Group

WSM administrators can send supported commands (and schedule supported commands
to be sent) to selected Device Groups (supported commands include Reboot, Shut down,
and Wake on LAN).
Use the following guidelines:
1. On the Device Group Details page, select the Device Groups to which you want to
send a command.
2. Click Send Command to open the Send Device Command page.

Figure 34 Send Device Command page

3. Select the command (Reboot, Shut down, or Wake on LAN) you want to send to the
devices.
4. Complete one of the following:
• To send the command now, enter a Time Delay in seconds (default is 300).
• To send the command later, click the schedule link to open the Schedule Device
Command page (select the date, enter a time, and click Schedule).
5. Click Send Command to send the command (according to your Time Delay or
schedule) and return to the Device Group Details page.

Tip
You can remove previously scheduled commands by going to the Device
Group Details page, selecting the devices, clicking Abort Command to open
a confirmation message, and then clicking OK.
10 Devices
This chapter describes how to perform routine device management tasks using the
Administrator Console. It provides information on managing the devices in your WSM
system (with and without Active Directory integration).

Managing Devices
Clicking the Devices link from any functional area main page opens the Devices page.
This page allows you to quickly view and manage the WSM Devices that are available
(see Table 8). It also allows you to easily display the devices you want by using the
filtering feature.

Tip
Depending on whether or not Active Directory is enabled, some procedures
may be different. For example, while adding a device with Active Directory
enabled, you must select an Active Directory Organizational Unit.

Figure 35 Devices page

Although the Devices page shows you all of the Devices available in the WSM system,
you can use the following guidelines to view the Devices you want:
• Name Contains - Name of a device (use only letters, numbers, dashes, spaces, the @
character, and periods).
• IP Address - IP Address of the device.
• Device Status - Status of the device.
• Connection Type - (all, Network, or Mobile Disconnected)
64 Chapter 10

• MAC Address - MAC Address of the device.

• Active Server - Name of the server to which the device is assigned. Use the Active
Server Select link to select the server.
• Device Class - Class of the device.
• Server - Name of the server to which the device is assigned. Use the Server Select
link to select the server.
• OS Image - Name of the OS Image that is assigned to device. Use the OS Image
Select link to select the OS Image.
• Device Group - Name of the Device Group to which the device is assigned. Use the
Device Group Select link to select the Device Group.
• Site - Name of the Site to which the device is assigned. Use the Site Select link to
select the Site.
• Site Group - Name of the Site Group to which the device is assigned. Use the Site
Group Select link to select the Site Group.
After entering your criteria, click Filter to view the results. You can then select the Devices
you want, and begin performing your tasks.
Table 8 provides a quick overview of what you can do using the Devices page.

Table 8 Routine Device Tasks - Devices page

Tasks You Can Do How Details

Add a Device to the system.
Click the Add Device link and
follow the wizard.
“Adding Devices” on page 65.
NOTE: The first Device you add
to the system is automatically
assigned as the Reference
Device. The Reference Device is
used as a Default device when
updating an OS Image, as
described in "Updating an OS
Image."

Edit a Device in the system.
Click a Name link in the Devices
area and make your changes.
“Editing Devices” on page 67.
NOTE: You can also edit multiple
devices at the same time by
selecting the check boxes next to
the name of the Devices you want
in the Devices area, and then
clicking Configure Devices to
open and use the Multiple Device
Configuration page.

Edit a Site in the system. Click a Site link in the Device “Editing Sites” on page 21.
Groups area and make your
changes.

View or edit the Reference Device Click the View / Edit Reference “Editing Devices” on page 67.
details. Device link to open the Device This link is shown after you have
Details page for the current added the first Device to the
Reference Device. system.

Edit multiple Devices in the
system at the same time for
Description, Device Class,
Connection Type, and Boot
Selection Mode configurations.
Select the check boxes next to
the name of the Devices you want
in the Devices area, click
Configure Devices, and then
use the Multiple Device
Configuration page.
Refer to the Description, Device
Class, Connection Type, and
Boot Selection Mode
configuration details in “Editing
Devices” on page 67.
 Devices 65

Table 8 Routine Device Tasks - Devices page , Continued

Tasks You Can Do How Details

Delete a Device from the system.
Select the check box next to the
name of the Device you want in
the Devices area (you can use
Select All or Deselect All as
needed), click Delete Selected,
and confirm the deletion. The
Device is deleted and is no longer
shown in the list of available
Devices on the Devices page.
You can also delete a Device by
using the Delete this Device link
on the Device Details page.
With Active Directory integration,
deleting a Device also deletes the
computer account of the Device
from Active Directory.

Send supported commands to
Devices in the system.
Select the Devices you want and
click Send Command and use
the Send Device Command page.
“Sending Commands to Devices”
on page 73.
You can also schedule a device
command by using the Schedule
Device Command check box on
the Device Details page.

Abort the previously scheduled
commands to Devices in the
system.
Select the devices for which you
want to abort previously
scheduled commands, click
Abort Command to open a
message confirming the removal
of the commands, and then click
OK to abort the commands.

Configure multiple devices at the Select the check boxes next to

same time. the name of the Devices you want
in the Devices area, and then
click Configure Devices to open
and use the Multiple Device
Configuration page.

Adding Devices
To add a Device for WSM use, click the Add Device link on the Devices page and follow
the wizard.
Use the following guidelines:
1. On the Devices page, click the Add Device link to open the Add Device wizard.

Figure 36 Add Device wizard

66 Chapter 10

2. Complete the Add Device page using the following guidelines:

• Enter a Name.
• Enter a Description.
• Enter a Mac Address.
• Select a Device Class.
• Select a Connection Type (either Network or Mobile Disconnected; if you select
Mobile Disconnected, select a Force Provision option of either Enabled or
Disabled).

Tip
In Network mode, the device must always have a LAN connection to a WSM
Server. In Mobile mode, the device can be disconnected from a WSM Server
and still be operational. A Force Provision option of Enabled automatically
provisions the mobile device with an OS Image when connected to, and
booting from, a WSM Server. A Force Provision option of Disabled allows the
user to provision the mobile device with an OS Image when desired (by
right-clicking the WSM Client icon in the system tray and selecting Provision
Disk).

• (For Active Directory integration only) Select the Active Directory Organizational
Unit (for example, wsm.com/CN=Computers).
3. Click Next to open the Select Site Groups page.
4. Determine the Site Groups you want to include using the assignment page.
5. Click Next to open the Select Sites page.
6. Determine the Sites you want to include using the assignment page.
7. Click Next to open the Assign Device Groups page.
8. Determine the Device Groups you want to include using the assignment page.
9. Click Next to open the Assign an OS Image page.
10.Determine the OS Images you want to include using the assignment page.
11. Click Next to open the Select Streaming Server page.
12.Determine the Streaming Server you want to include using the assignment page.
13.Click Finish. The Device is added to the list of available Devices on the Devices page.

Warning
If you added a mobile device, do not use the device while the provisioning
process is being completed. A message informs you when OS provisioning is
complete. Moreover, although the OS has been provisioned for Mobile mode,
users still need to provision the applications that will run on the mobile device
when their device is disconnected. To provision applications, the user must
reboot the device and log on while the device is connected to the network.
Applications will be provisioned according to your Force Provision option.
Users must not disconnect the device from the network or use the device for
any purpose while applications are being provisioned.
 Devices 67

Editing Devices
Instructions in this section are for a network device, mobile device, or Reference Device.
On the Devices page, click the Name link of the Device you want to edit to open the
Device Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Device is then
modified and can be viewed in the list of available Devices on the Devices
page).

Figure 37 Device Details page

Tip
Some fields on the Device Details page can be edited only if you are working
with Devices assigned to the Default Device Group.

• Enter the Name.

• (Optional) Enter a Description.
• Select the MAC address of the device.
• The IP Address of the device (and Reference Device for the Reference Device) is
shown.
• (Devices assigned to the Default Device Group Only) Select the Device Class you
want to assign to the device.
• (Devices assigned to the Default Device Group Only) Select a Connection Type (either
Network or Mobile Disconnected; if you select Mobile Disconnected, select a Force
Provision option of either Enabled or Disabled).

Tip
In Network mode, the device must always have a LAN connection to a WSM
Server. In Mobile mode, the device can be disconnected from a WSM Server
and still be operational. A Force Provision option of Enabled automatically
provisions the mobile device with an OS Image when connected to, and
booting from, a WSM Server. A Force Provision option of Disabled allows the
user to provision the mobile device with an OS Image when desired (by
68 Chapter 10

right-clicking the WSM Client icon in the system tray and selecting Provision
Disk).

• (Devices assigned to the Default Device Group Only) Select the Boot Selection Mode
for the device (First Disk, First Available, or User Select).

Tip
First Disk (default) specifies that the device will always boot from the first
OS Image that is assigned to it.
First Available is the mode that is used for failover purposes. In this mode
you can specify the same OS Image on multiple servers and use that
specification as the assignment for two or more OS Images available. Thus,
the device will try and connect to the first server, and if the server is not
available, the device will try and connect to the remaining assigned servers
as specified.
User Select is the mode that allows users to specify from which OS Image
the device should boot. A menu is displayed for the user when the device
boots, allowing the user to specify the OS Image and server combination.

• (For Active Directory Integration Only) The Active Directory Organizational Unit is
shown (for example, wsm.com/CN=Computers).
• Device Group, Server Group, and Image Name are shown.
• Depending on whether or not you want to schedule a device command, select or clear
the Schedule Device Command check box (if selected, you must also configure
Schedule Date, Schedule Command, and Time Delay). For more information on
sending supported commands to Devices, refer to "Sending Commands to Devices."
• Status is shown:
• Authenticated - WSM Server has authenticated the device and identified the
operating system image assigned to it.
• Boot Aborted - Boot process has aborted for some reason (such as a network
connection failure between the device and WSM Server, no VDisk is available,
insufficient resource at the WSM Server to process the device request, or a timeout
is reached on waiting for user input from the device).
• Booting - Device is booting up and trying to connect to the WSM Server for
authentication (new device or existing device).
• Disconnected - WSM Server is not receiving heartbeats from the device beyond
the Device Heartbeat Timeout as defined in the Systems Setting page. The
resources held by the device are released and the device can be treated as down.
The device can reconnect to the WSM Server later without reboot provided that the
VDisk image associated to the device has not been changed.
• Down - Device has been shut down. The shutdown process can be initiated by a
WSM administrator from the administrator UI or the user of the device. Down
indicates a clean shutdown.
• No Response - Device is not sending heartbeats to the WSM Server indicating a
forced shutdown, power failure, or network connection failure.
• Reconnect aborted - Reconnection attempts have failed. The device is not
functional until a successful reboot.
• Reconnecting - Device is trying to reconnect to the WSM Server after a connection
failure.
• Starting OS - WSM Server has transferred control to the Operating System for the
device and Operating System is starting up.
• Up - Device is up and sending heartbeats to the WSM Server.
Devices 69

• Optional Related Tasks you can perform using the Device Details page:
• Add a New Device - Click the Add a New Device link to open and use the Add
Device wizard (see"Adding Devices").
• Delete this Device - Click the Delete this Device link to delete the device.
• Make this device the Reference Device - Click the Make this a Reference
Device link to make the device the Reference Device.

Tip
The Make this the Reference Device link does not appear if the device you
are editing is currently designated as the Reference Device.
The Reference Device is used as a Default device when updating an OS
Image, as described in "Updating an OS Image."

• Change the Device Group assignment of a Device - Click the Change Device
Group link to open and use the Select Device Group wizard (see"Changing the
Device Group Assignment for a Device").
• Remove an OS Image - (Devices in Default Device Group Only) Click the Remove
OS Image link in the Assigned Operating System Images area for the OS Image
you want to remove from the device.

Caution
In order to prevent any loss of work for the end user, the ability to remove an
OS Image (the Remove OS Image link) is not available for any OS Image
that is currently being used by a device. If an OS Image assignment needs to
be changed immediately for a device in this case, you must shut down the
device to make the Remove OS Image link available for use to remove the
OS image assignment, and then use the Add OS Image link to add a new
OS image assignment to the device. If you want to change an OS Image
assignment for the next device boot (no immediate change needed), then
you can use the Update OS Image link and follow the procedures in
"Updating an OS Image Assignment for a Device."

• Add OS Image - (Devices in Default Device Group Only) Click the Add OS Image
link in the Assigned Operating System Images area and select the OS Image you
want to assign to the device (see "Adding an OS Image to a Device").
• Update OS Image- (Devices in Default Device Group Only) Click the Update OS
Image link in the Assigned Operating System Images area for the OS Image you
want to update for the device (see "Updating an OS Image Assignment for a
Device").
• Reset Device State - (Devices in Default Device Group Only) Click the Reset
Device State link in the Assigned Operating System Images area for the OS Image
and OS Server association you want to clear the Write Cache for the device (to
clear all Write Caches associated with the device be sure to click each Reset
Device State link that appears).

Caution
You cannot successfully use the Reset Device State link if the OS Image
and OS Server combination is currently being used (a currently being used
message appears at the top of the Network Device Details page). In such a
case, you must first shut down the device, and then use the Reset Device
State link. Using the Reset Device State link will cause all changes made to
the OS Image by this device to be lost.
70 Chapter 10

Changing the Device Group Assignment for a Device

While editing an Device on the Device Details page, you can assign a Device to all
Devices in a user-created Device Group or to individual Devices in the Default Device
Group by using the following guidelines:
1. Click the Change Device Group link to open the Select Device Groups For Device
wizard.

Figure 38 Select Device Groups for Device wizard

2. Determine the Device Groups you want to include using the assignment page:
• User-created Device Group - Select a user-created Device Group and click Next.
The Device is assigned the OS Image and Streaming Server that is assigned to the
Device Group you selected. Click Finish to return to the Device Details page.
• Default Device Group - Select the Default Device group and click Next to open the
Assign an OS Image page.
3. Determine the OS Image you want to include using the assignment page.
4. Click Next to open the Assign a Server page.
5. Determine the Server you want to include using the assignment page.
6. Click Finish.
Devices 71

Adding an OS Image to a Device

While editing a Device in the Default Device Group on the Device Details page, you can
add an OS Image to a Device by using the following guidelines:
1. Click the Add OS Image link to open the Add OS Image wizard.

Figure 39 Adding an OS Image - Device

2. Select the OS Image you want and click Next to open the Select a Streaming Server
page.

Tip
Only one OS image can be added for a mobile device.

3. Select the Streaming Server you want to assign to the Device.

4. Click Finish to return to the Device Details page (when the device reboots, the new OS
Image assignment will take effect).
72 Chapter 10

Updating an OS Image Assignment for a Device

While editing a Device in the Default Device Group on the Device Details page, you can
update an OS Image assignment for a Device by using the following guidelines:
1. Click the Update OS Image link to open the Add OS Image wizard.

Figure 40 Updating an OS Image - Device

2. Select the OS Image you want and click Next to open the Select a Streaming Server
page.
3. Select the Streaming Server you want to assign to the Device.
4. Click Finish to return to the Device Details page (when the device reboots, the new OS
Image assignment will take effect).
 Devices 73

Sending Commands to Devices

WSM administrators can send supported commands (and schedule supported commands
to be sent) to selected Devices (supported commands include Reboot, Shut down, and
Wake on LAN).

Tip
You can also schedule a device command by using the Schedule Device
Command check box on the Device Details page.

Use the following guidelines:

1. On the Device Details page, select the Devices to which you want to send a command.
2. Click Send Command to open the Send Device Command page.

Figure 41 Send Device Command page

3. Select the command (Reboot, Shut down, or Wake on LAN) you want to send to the
devices.
4. Complete one of the following:
• To send the command now, enter a Time Delay in seconds (default is 300).
• To send the command later, click the schedule link to open the Schedule Device
Command page (select the date, enter a time, and click Schedule).
5. Click Send Command to send the command (according to your Time Delay or
schedule) and return to the Devices page.

Tip
You can remove previously scheduled commands by going to the Devices
page, selecting the devices, clicking Abort Command to open a
confirmation message, and then clicking OK.
74 Chapter 10

This page intentionally blank.

11 User Groups
This chapter describes how to perform routine User Group management tasks using the
Administrator Console. It provides information on managing the User Groups in your WSM
system (with and without Active Directory integration).

If Your WSM is Integrated with Active Directory Read this First

Tip
If your WSM system is not integrated with Active Directory, you can skip this
section.

If your WSM system is integrated with Active Directory, be aware of the following rules and
relationships:
• WSM integrates with Security Groups.
• Security Groups are flat in structure and unique across all organizational structures.
• Access to application licenses is granted through Security Groups (this model is based
on the Windows file sharing security model).
• User Groups are created in Active Directory, not in WSM.
• To be included in WSM, User Groups must be marked in Active Directory.
• User Passwords are set and verified using/within Active Directory.
• User Groups cannot be deleted from Active Directory using WSM.
• You can add and delete User Groups using WSM. You can edit the OS Images,
Application Images, and Application Licenses associated with the User Group using
WSM. However, you cannot edit User Groups and other User Group settings using
WSM (you must use Active Directory).
• User group settings and modifications you make using/within Active Directory will
automatically update in WSM according to the settings you configure as described in
"Active Directory Configuration."
76 Chapter 11

Managing User Groups

Clicking the User Groups link from any functional area main page opens the User Groups
page. This page allows you to quickly view and manage the WSM User Groups that are
available (see Table 9). It also allows you to easily display the User Groups you want by
using the filtering feature.

Figure 42 User Groups page

Although the User Groups page shows you all of the User Groups available in the WSM
system, you can use the following guidelines to view the User Groups you want:
• Name Contains - Name of a User Group (use only letters, numbers, dashes, spaces,
the @ character, and periods).
• Application - Name of the application to which the User Group is assigned. Use the
Application Select link to select the application you want.
• Status - Status of the User Group (all, Enabled, or Disabled).
After entering your criteria, click Filter to view the results. You can then select the User
Groups you want, and begin performing your tasks.
Table 9 provides a quick overview of what you can do using the User Groups page.

Table 9 Routine User Group Tasks - User Groups page

Tasks You Can Do How Details

Add a User Group to the system Click the Add User Group link “Adding User Groups without
(your WSM system is not and follow the wizard. Active Directory Integration” on
integrated with Active Directory). page 78.

Add a User Group to the system Click the Import a Group from “Adding User Groups with Active
(your WSM system is integrated Active Directory link and use the Directory Integration” on page 79.
with Active Directory). Import Group from Active
Directory page.

Edit a User Group in the system Click a Name link in the Device “Editing User Groups without
(your WSM system is not Groups area and make your Active Directory Integration” on
integrated with Active Directory). changes. page 80.

Edit a User Group in the system Click a Name link in the User “Editing User Groups with Active
(your WSM system is integrated Groups area and make your Directory Integration” on page 81.
with Active Directory). changes.
 User Groups
Table 9 Routine User Group Tasks - User Groups page , Continued
Tasks You Can Do
Edit a Domain in the system (your
WSM system is integrated with
Active Directory).
Quickly enable or disable a User
Group in the system (it does not
matter whether or not your WSM
system is integrated with Active
Directory).
Delete a User Group from the
system (your WSM system is not
integrated with Active Directory).
Delete a User Group from the
system (your WSM system is
integrated with Active Directory).
How
Click a Domain link in the User
Groups area and make your
changes.
Click the Enable or Disable link
in the Status list for the User
Group.
Select the check box next to the
name of the User Group you want
in the User Groups area (you can
use Select All or Deselect All as
needed), click Delete Selected,
and confirm the deletion. The
User Group is deleted and is no
longer shown in the list of
available User Groups on the
Device Groups page.
Select the check box next to the
name of the User Group you want
in the User Groups area (you can
use Select All or Deselect All as
needed), click Delete Selected,
and confirm the deletion. The
User Group is deleted and is no
longer shown in the list of
available User Groups on the
User Groups page.
77
Details
“Editing Domains” on page 106.
While you can enable or disable a
User Group while editing a User
Group (on the User Group Details
page), you can quickly do this
task directly on the User Groups
page.
IMPORTANT: Active Directory is
not involved with this procedure,
enabling or disabling a User
Group by using WSM does not
affect User Groups and Users in
Active Directory.
You can also delete a User Group
by using the Delete this User
Group link on the User Group
Details page.
After deleting a User Group, a
User attempting to access a
subscribed application (or
refreshing the list of available
applications) will receive a
message informing the User that
the subscription to the application
is no longer active.
IMPORTANT: Deleting a User
Group by using WSM does not
remove the Users of that group
from the WSM system.
You can also delete a User Group
by using the Delete this User
Group link on the User Group
Details page.
After deleting a User Group, a
User from that group attempting
to access a subscribed
application (or refreshing the list
of available applications) will
receive a message informing the
User that the subscription to the
application is no longer active.
IMPORTANT: Deleting a User
Group by using WSM does
remove the Users of that group
from the WSM system, however,
it does not remove the User
Group or Users of that group from
Active Directory.
78 Chapter 11

Adding User Groups

As a WSM administrator you can add a User Group. Once a User Group is added, you
can then add members (Users) who can subscribe, activate, and run WSM operating
systems and applications for that User Group.

Tip
You can only add a member (User) to an existing User Group. If WSM is
integrated with Active Directory, members (Users) are automatically added to
the group according to your Active Directory settings.

For information on adding User Groups without Active Directory integration, refer to
"Adding User Groups without Active Directory Integration."
For information on adding User Groups with Active Directory integration, refer to "Adding
User Groups with Active Directory Integration."

Adding User Groups without Active Directory Integration

To add a User Group for WSM use, click the Add User Group link on the User Groups
page and follow the wizard.
Use the following guidelines:
1. On the User Groups page, click the Add User Group link to open the Add User Group
wizard.

Figure 43 Add User Group wizard

2. Enter a Name (use only letters, numbers, dashes, spaces, the @ character, and
periods).
3. Click Next to open the Assign Users page.
4. Determine the Users you want to include using the assignment page.
5. Click Next to open the Assign Application Licenses page.
6. Determine the Application Licenses you want to include using the assignment page.
7. Click Finish. The User Group is added to the list of available User Groups on the User
Groups page.
User Groups 79

Adding User Groups with Active Directory Integration

To add (import) a User Group for WSM use, click the Import a Group from Active
Directory link on the User Groups page to open and use the Import Group from Active
Directory page.
Use the following guidelines:
1. On the User Groups page, click the Import a Group from Active Directory link to
open the Import Group from Active Directory page.

Figure 44 Import Group from Active Directory page

2. 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 User Groups and select the Group Names you want.
3. After selecting the User Groups you want, click Finish. The User Group is added to the
list of available User Groups on the User Groups page.

Tip
Users of these imported User Groups will automatically be added to the
WSM User Name list on the Users page.
80 Chapter 11

Editing User Groups

For information on editing User Groups without Active Directory integration, refer to
"Editing User Groups without Active Directory Integration."
For information on editing User Groups with Active Directory integration, refer to "Editing
User Groups with Active Directory Integration."

Editing User Groups without Active Directory Integration

On the User Groups page, click the Name link of the User Group you want to edit to open
the User Group Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the User Group is
then modified and can be viewed in the list of available User Groups on the
User Groups page).

Figure 45 User Group Details page - without Active Directory integration

•

• Enter the Name.

• Select the Status of the User Group (Enabled or Disabled).
• Optional Related Tasks you can perform using the User Group Details page:
• Add a New User Group - Click the Add a New User Group link to open and use
the Add Group page (see "Adding User Groups without Active Directory
Integration").
• Delete this Group - Click the Delete this Group link to delete the User Group.
• Change a User Assignment - Click the Change User Assignment link to open
and use the Assign Users For Group page.
• Edit a User associated with the User Group - Click a Name link in the Users
Belonging To area to open and use the User Details page (see "Editing Users
without Active Directory Integration").
User Groups 81

• Change an Application License Assignment - Click the Change Application

License Assignment link to open and use the Assign Application Licenses For
Group page.
• Edit the Application License associated with the User Group - Click a Name
link in the Application Licenses Assigned To area to open and use the Application
License Details page (see "Editing Application Licenses").

Editing User Groups with Active Directory Integration

If you are using WSM integrated with Active Directory, you can edit the OS Images,
Application Images, and Application Licenses associated with the group. In addition, you
can select the Status of a group (Enabled or Disabled) and delete a User Group from
WSM.
On the User Groups page, click the Name link of the User Group you want to edit to open
the User Group Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the User Group is
then modified and can be viewed in the list of available User Groups on the
User Groups page).

Figure 46 User Group Details page - with Active Directory integration

• The Name and Organizational Unit of the User Group are shown.
• The Domain of the User Group is shown, however, you can edit the Domain. Click the
link of the Domain to open and use the Active Directory Domain Details page (see
"Editing Domains").
• Select the Status of the User Group (Enabled or Disabled).
• Optional Related Tasks you can perform using the User Group Details page:
• Delete this Group - Click the Delete this Group link to delete the User Group.
• Import a User Group from Active Directory - Click the Import a User Group
from Active Directory link to open and use the Import Groups from Active
Directory page (see "Importing User Groups from a Domain").
82 Chapter 11

• View a User associated with the User Group - Click a Name link in the Users
Belonging To area to view the User Details page.
• Change an Application License Assignment - Click the Change Application
License Assignment link to open and use the Assign Application Licenses For
Group page.
• Edit the Application License associated with the User Group - Click a Name
link in the Application Licenses Assigned To area to open and use the Application
License Details page (see "Editing Application Licenses").
12 Users
This chapter describes how to perform routine user management tasks using the
Administrator Console. It provides information on managing the users in your WSM
system (with and without Active Directory integration).

If Your WSM is Integrated with Active Directory Read this First

Tip
If your WSM system is not integrated with Active Directory, you can skip this
section and go directly to "Managing Users without Active Directory
Integration."

If your WSM system is integrated with Active Directory, be aware of the following rules and
relationships:
• Users of the imported User Groups will automatically be added to the WSM User Name
list on the Users page.
• You must manage all Users by using Active Directory, not WSM.
• Users must exist in Active Directory before they can exist in WSM.
• To be included in WSM, Users must be marked as active in Active Directory.
• User passwords are set and verified using/within Active Directory.
• Users cannot be deleted from Active Directory using WSM.
• Deleting a User Group by using WSM also removes the Users of that group from the
WSM system.
• You can filter and view Users using WSM (Users page). You can also click on a Name
link on the Users page to view User details. However, you cannot edit Users or User
settings using WSM.

Tip
On the User Details page, you can also click the link of the Domain name to
open the Active Directory Domain Details page (for details on editing a
domain, refer to "Editing Domains").

• User settings and modifications you make using/within Active Directory will
automatically update in WSM according to the settings you configure as described in
"Active Directory Configuration."
84 Chapter 12

Managing Users without Active Directory Integration

Clicking the Users link from any functional area main page opens the Users page. This
page allows you to quickly view and manage the WSM Users that are available (see
Table 10). It also allows you to easily display the Users you want by using the filtering
feature.

Figure 47 Users page - without Active Directory integration

Although the Users page shows you all of the Users available in the WSM system, you
can use the following guidelines to view the Users you want:
• Name Contains - Name of a User (use only letters, numbers, dashes, spaces, the @
character, and periods).
• Status - Status of the User (all, Enabled, or Disabled).
After entering your criteria, click Filter to view the results. You can then select the Users
you want, and begin performing your tasks.
 Users
Table 10 provides a quick overview of what you can do using the Users page.
Table 10 Routine User Tasks - Users page
Tasks You Can Do
Add a User to the system (your
WSM system is not integrated
with Active Directory).
Edit a User in the system (your
WSM system is not integrated
with Active Directory).
Quickly enable or disable a User
in the system (your WSM system
is not integrated with Active
Directory).
Delete a User from the system
(your WSM system is not
integrated with Active Directory).
How
Click the Add User link and follow
the wizard.
Click a Name link in the Users
area and make your changes.
Click the Enable or Disable link
in the Status list for the User.
Select the check box next to the
name of the User you want in the
Users area (you can use Select
All or Deselect All as needed),
click Delete Selected, and
confirm the deletion. The User is
deleted and is no longer shown in
the list of available Users on the
Users page.
85
Details
“Adding Users without Active
Directory Integration” on page 86.
“Editing Users without Active
Directory Integration” on page 87.
While you can enable or disable a
User while editing a User (on the
User Details page), you can
quickly do this task directly on the
Users page.
You can also delete a User by
using the Delete this User link on
the User Details page.
After deleting a User, a User
attempting to access a
subscribed application (or
refreshing the list of available
applications) will receive a
message informing the User that
the subscription to the application
is no longer active.
86 Chapter 12

Adding Users without Active Directory Integration

To add a User for WSM use, click the Add User link on the Users page and follow the
wizard.
Use the following guidelines:
1. On the Users page, click the Add User link to open the Add User wizard.

Figure 48 Add Users wizard

2. Enter the User Name, Password, and password confirmation (Re-enter Password).
3. (Optional) Enter the First Name, Last Name, and Email address of the User.

Tip
If User Groups exist in your WSM system, you can click Next and use the
assignment page to determine the User Groups to which you want to assign
the User.

4. Click Finish. The User is added to the list of available Users on the User page and can
now subscribe, activate, and run WSM operating systems and applications.
 Users 87

Editing Users without Active Directory Integration

On the Users page, click the Name link of the User you want to edit to open the User
Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the User is then
modified and can be viewed in the list of available Users on the Users page).

Figure 49 User Details page - without Active Directory integration

• Enter the User Name.

• (Optional) Enter the First Name, Last Name, and Email address of the User.
• Select the Status of the User (Enabled or Disabled).
• Optional Related Tasks you can perform using the User Details page:
• Add a New User - Click the Add a New User link to open and use the Add User
page (see "Adding Users without Active Directory Integration").
• Change the Password of a User - Click the Change Password link to open and
use the System Settings Change Password page (see "Changing User Passwords
without Active Directory Integration").
• Delete this User - Click the Delete this User link to delete the User.
• Change a Group Assignment for a User - Click the Change Group Assignment
link to open and use the Assign User Groups For User page.
• Edit the User Groups associated with the User - Click a Name link in the Users
Belonging To These Groups area to open and use the User Group Details page
(see "Editing User Groups without Active Directory Integration").
• Show or hide the Application Licenses associated with the User - Click the
Show or Hide link for a User in the Applications list to show or hide the Application
Licenses associated with the User. If you show the Application Licenses of a User,
you can then click on the link for an Application License to open and use the
Application License Details page (see "Editing Application Licenses").
88 Chapter 12

Changing User Passwords without Active Directory Integration

While editing a User, you can change a User password by using the following guidelines:
1. Click the Change Password link to open and use the System Settings Change
Password page.

Figure 50 Change Password For User page

2. Enter the New Password.

3. Enter the password again in the Re-enter Password box.
4. Click Update Password.
13 System Settings
This chapter describes how to perform routine system management tasks using the
Administrator Console. It provides information on managing the system settings of your
WSM system.

Managing System Settings

Clicking the System Settings link on any functional area main page opens the System
Settings page. This page allows you to quickly view and manage the WSM system
settings that are available.

Figure 51 System Settings page

90 Chapter 13

To configure your WSM system settings, use the following guidelines:

Tip
After you have finished configuring the settings, be sure to click Update
System Settings to save your settings. Use Reset to clear any changes you
made (before clicking Update System Settings)

• Log Level for Log Files - Select the either Error, Warning, Info, Notify, Verbose, or
Debug. The log level is a system-wide setting that determines the lowest level of
messages to be logged in all log files for Services and applications. For example: if set
to Error, only error messages will be logged; if set to Debug all messages will be
logged.

Tip
This setting will not take effect until the WSM Administration Service is
restarted.

• Log File Size Limit - Enter the size (in kilobytes) up to a maximum of 102400 KB.

Tip
This setting will not take effect until the WSM Administration Service is
restarted. If the log exceeds the maximum limit, then a .bak file is created.

• Connection Timeout for Synchronizing OS Image Properties - Enter the time in

seconds (default is 10 seconds). When changing OS image property information (such
as mode) on the OS Image Details page, a connection is established with each
streaming server hosting the same OS image to synchronize the changes.
• Use Alias for OU - If desired, you can select to display the alias name of the
organization unit rather than the full name.
• Re-use Device Names in AD - If desired, you can select to reuse a device entry in
Active Directory while adding a device.

Tip
This setting will not take effect until the WSM Administration Service is
restarted.

• Client Status Log - If desired, you can select to record boot time statistics (such as
last boot time, number of reboots, and so on) for a client.
• Connection Timeout for Adding a Virtual Center - Enter the time in seconds (default
is 30 seconds). When adding a Virtual Center, WSM tries to establish a connection to
the Virtual Center to validate the input data. If the connection details are incorrect, it
can take a significant amount of time for the HTTP connection to time out. This field
allows the administrator to set a time-out value in addition to the HTTP connection
time-out value so that the UI does not remain in waiting mode for a long time.
• Perform OS Image Synchronization- Select either Synchronously or
Asynchronously. Synchronization of OS Image property changes can happen either
synchronously or asynchronously upon submitting the form on the OS Image Details
page.

Tip
If there are many streaming servers upon which synchronization must occur,
it is recommended that this option be set to Asynchronously.
System Settings 91

• Enable OS Image Synchronization Daemon - If desired, you can select to enable the
OS Image Synchronization Daemon. If you enable the OS Image Synchronization
Daemon, enter the Retry Failed OS Image Synchronization Every time in seconds
(default is 60 seconds).

Tip
If synchronization of OS Image property changes fails on a streaming server
for any reason, a daemon thread (if enabled) will retry the synchronization for
a specified interval until successful.

• Enable DHCP Proxy Service - If desired, you can select to enable the DHCP Proxy
Service. If checked, the DHCP Proxy Service will be enabled and managed by the
WSM Administration Service. If checked, be sure to shut down other DHCP Proxy
Services that may be running on all the Core and Edge Servers.

Tip
After enabling the DHCP Proxy Service, you must restart the Admin Service
on each WSM Server (both Core and Edge Servers). The Admin Service
starts the DHCP thread during start-up if the appropriate flags are set in the
WSM database.
In addition, note that the enabled DHCP Proxy Service will appear in the
Services list on the Server Details page where you can start and stop the
service as described in "Editing Servers." However, you cannot view a
separate log file for the DHCP Proxy Service as logs for this service are
integrated with the other service logs listed on the Server Details page.

• Enable TFTP Service - If desired, you can select to enable the TFTP Service. If
checked, the TFTP Service will be enabled and managed by the WSM Administration
Service. If checked, be sure to shut down other TFTP Services that may be running on
all the Core and Edge Servers.

Tip
After enabling the TFTP Service, you must restart the Admin Service on each
WSM Server (both Core and Edge Servers). The Admin Service starts the
TFTP thread during start-up if the appropriate flags are set in the WSM
database.
In addition, note that the enabled TFTP Service will appear in the Services
list on the Server Details page where you can start and stop the service as
described in "Editing Servers." However, you cannot view a separate log file
for the TFTP Service as logs for this service are integrated with the other
service logs listed on the Server Details page.

• DeviceHeartbeat Interval - Enter the time in seconds (default is 30 seconds). A client

device that is up and running periodically informs its status to the server via a
heartbeat. This heartbeat interval defines the number of seconds between two
heartbeats sent by the device.
• DeviceHeartbeat Timeout - Enter the time in minutes (default is 30 minutes). If the
server does not receive a heartbeat within this allowed time limit, it will treat the client
as Down and release resources held by the client. Note that if the client device later
attempts to reconnect to the server and the resources are still available, the reconnect
request will be granted and the client device will resume processing from where it was
interrupted.
92 Chapter 13

• Device Boot Timeout - Enter the time in minutes (default is 5 minutes). If a client
device does not complete boot-up processing within this time limit, it is marked as
Down and its resources are released. Note that if the device is still actively booting up
and if it is far enough along in the initialization process, it may re-establish
communications with the server and complete its boot process.
• Server Monitoring Tasks Interval - Enter the time in seconds (default is 120
seconds). This interval defines the number of seconds between these tasks being run.

Tip
This setting will not take effect until the WSM Administration Service is
restarted.

• Services Monitoring Tasks Interval - Enter the time in seconds (default is 10

seconds). This interval defines the number of seconds between these tasks being run.

Tip
This setting will not take effect until the WSM Administration Service is
restarted on all Core and Edge Servers.

• Database Backup Interval - Enter the time in minutes (default is 5 minutes). This
interval defines the number of minutes between database backups.

Tip
This setting will not take effect until the WSM Administration Service is
restarted on the Core Server of a Site.

• Synchronization Log Retention Period - Enter the time in days (default is 5 days).
This interval defines the number of days synchronization logs are kept in the database.
• Log Cleanup Interval - Enter the time in hours (default is 24 hours). This interval
defines the interval for the task that cleans up the synchronization logs in the WSM
database.
• Synchronization Period (with Site Template) - Enter the time in minutes (default is
60 minutes). This interval defines the number of minutes between two occurrences of
the synchronization process that synchronizes this site with its site template at
Headquarters.

Tip
You can view the synchronization process log entries for Site to
Headquarters (and the Site Template synchronizations) on the Database
Synchronization page (click the Site Configuration link on the System
Settings page, and then click the Synchronization Logs link on the WSM
Sites Configuration page to open the Database Synchronization page).

• Max Rows per Page - Enter the maximum number of entries displayed in the
aggregation reports and Sites page.
• Aggregation Period - Enter the time in minutes (default is 5 minutes). This interval
defines the time period between two occurrences of the aggregation process that
propagates this site data to Headquarters.
• HQ manages Site Admin Password - If selected, WSM will not allow a Site
Administrator (siteadmin) user password change from a Linked Site. It can only be
managed from Headquarters.
• Content Scheduler Interval - Enter the time in minutes (default is 5 minutes). This
interval defines the interval for the task that automatically schedules OS Image, OS
Image Patch, and Application Image content distribution to remote WSM Servers.
System Settings 93

• Content Distribution Client Interval - Enter the time in minutes (default is 1 minutes).
This interval defines the interval for the task that checks for scheduled or pending OS
and Application Image copy or patch operations, including retries.
• Abort Site Conversion on Conflict - If selected, any conflict between a Stand-Alone
Site and template on OS and/or Application Images will stop the conversion to a Linked
Site.
• Allow Template Change - If not selected, Site Templates are locked down at
Headquarters.
• Optional Related Tasks you can perform using Quick-Links on the System Settings
page:
• Change Admin Password - Allows you to change your administrator password.
This link is also located on the Overview page (see "Changing Your Administrator
Password").
• Change Site Admin Password - Allows you to change your Site administrator
password. This link is also located on the Overview page (see "Changing Your Site
Administrator Password").
• Manage OS Classes - Allows you to add, edit, and delete OS Classes (see
"Managing Operating Systems").
• Manage Device Classes - Allows you to add, edit, and delete Device Classes (see
"Managing Devices").
• Manage Device Templates - Allows you to view and manage the available WSM
templates (see “Managing Device Templates”).
• Server License - Allows you to view and add a Server License for the WSM system
(see "Importing Server Licenses").
• Active Directory Configuration - Allows you to enable or disable Active Directory
(see "Active Directory Configuration").
• Content Distribution Configuration - Allows you to open and use the Content
Distribution Setting page to enable compression and http based distribution for
Sites (see "Content Distribution Configuration").
• Track Content Distribution - Allows you to open and use the Content Distribution
Summary page to track content distribution status and progress (you can click on
the Name link of a Content Entry to view the Content Distribution Details page for
the entry).
• Database Configuration - Allows you to access and edit the database
configuration of a Core Server or Edge Server (see "Database Configuration").
• Database Backup Configuration - Allows you to open and use the Backup DB
Configuration page to enable and configure the database backup for the current
Site.
• Site Configuration - Allows you to select a Site category for the current WSM
installation (see "Site Configuration").
• Rename SQL Server - Allows you to rename an SQL Server Metadata name so
that it is consistent with the name of the host it is running on. (see "Renaming an
SQL Server").
• Virtual Center Configuration - Allows you to configure virtual center access from
WSM (see "Managing Virtual Centers").
• Import Devices from File - Allows you to import Devices into the system from a file
(see "Importing Devices from a File").
• Apply a Site Template - Allows you to open and use the Apply Site Template page
to apply a Site template (XML file that has been generated by WSM) to a Site (Site
template XMLs are used for disaster recovery purposes in large WSM
environments with complex Site designs and are discussed in Advanced
Administrators Guide: Wyse WSMTM).
94 Chapter 13

Managing Device Templates

Clicking the Manage Device Templates link on the System Settings page opens the
Device Templates page. This page allows you to quickly view and manage the WSM
Templates that are available (see Table 11). It also allows you to easily display the Device
Templates you want by using the filtering feature.

Figure 52 Device Templates page

Although the Device Templates page shows you all of the Device Templates available in
the WSM system, you can use the following guidelines to view the Device Templates you
want:
• Name Contains - Name of a Device Template (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• Subnet Address - Subnet Address of the Device Template.
• Connection Type - (all, Network, or Mobile Disconnected)
• Device Class - Class of the Device Template.
• Server - Name of the server to which the Device Template is assigned. Use the Server
Select link to select the server.
• Device Group - Name of the Device Group to which the Device Template is assigned.
Use the Device Group Select link to select the Device Group.
After entering your criteria, click Filter to view the results. You can then select the Device
Templates you want, and begin performing your tasks.
 System Settings 95

Table 11 provides a quick overview of what you can do using the Device Templates page.

Table 11 Routine Device Template Tasks - Device Templates page

Tasks You Can Do How Details

Add a Device Template to the Click the Add Device Template “Adding Device Templates” on
system. link and follow the wizard. page 96.

Edit a Device Template in the Click a Name link in the Device “Editing Device Templates” on
system. Templates area and make your page 98.
changes.

Edit a Site in the system. Click a Site Name link in the “Editing Sites” on page 21.
Device Templates area and make
your changes.

Delete a Device Template from
the system.
Select the check box next to the You can also delete a Device
name of the Device Template you Template by using the Delete this
want in the Device Templates Device Template link on the
area (you can use Select All or Device Template Details page.
Deselect All as needed), click
Delete Selected, and confirm the
deletion. The Device Template is
deleted and is no longer shown in
the list of available Device
Templates on the Device
Templates page.
96 Chapter 13

Adding Device Templates

To add a Device Template for WSM use, click the Add Device Template link on the
Device Templates page and follow the wizard.
Use the following guidelines:
1. On the Device Templates page, click the Add Device Template link to open the Add
Device Template wizard.

Tip
After a device template is added for WSM use, the Device Template can be
used to set the attributes you want on Devices that are automatically added
(whether through discovery or importing from files). You can only add a
Device Template to an existing OS Image. For information on adding an OS
Image, refer to "Adding OS Images." For information on importing Devices
from a file, refer to "Importing Devices from a File."

Figure 53 Add Device Template wizard

2. Complete the Add Device page using the following guidelines:

• Enter a Name.
• Enter a Description.
• Select a Device Class.
• Select a Connection Type (either Network or Mobile Disconnected; if you select
Mobile Disconnected, select a Force Provision option of either Enabled or
Disabled).

Tip
In Network mode, the device must always have a LAN connection to a WSM
Server. In Mobile mode, the device can be disconnected from a WSM Server
and still be operational. A Force Provision option of Enabled automatically
provisions the mobile device with an OS Image when connected to, and
booting from, a WSM Server. A Force Provision option of Disabled allows the
user to provision the mobile device with an OS Image when desired (by
right-clicking the WSM Client icon in the system tray and selecting Provision
Disk).
System Settings 97

• If desired, select Specify a Subnet Range to enable, and then enter the Subnet
Address and Subnet Mask.

Tip
Only one Device Template without a Subnet Mask can be added to the WSM
system.

• (For Active Directory integration only) Select the Active Directory Organizational
Unit (for example, wsm.com/CN=Computers).

Tip
The Organizational Unit you assign to the template will take precedence over
the Default OU for the Domain.

3. Click Next to open the Select Site Groups page.

4. Determine the Site Groups you want to include using the assignment page.
5. Click Next to open the Select Sites page.
6. Determine the Sites you want to include using the assignment page.
7. Click Next to open the Assign Device Groups page.
8. Determine the Device Groups you want to include using the assignment page.
9. Click Next to open the Assign an OS Image page.
10.Determine the OS Images you want to include using the assignment page.
11. Click Next to open the Select Streaming Server page.
12.Determine the Streaming Server you want to include using the assignment page.
13.Click Finish. The Device is added to the list of available Device Templates on the
Device Templates page.
98 Chapter 13

Editing Device Templates

On the System Settings page, click the Manage Device Templates link to open the
Device Templates page, click the Name link of the Device Template you want to edit to
open the Device Template Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Device
Template is then modified and can be viewed in the list of available Device
Templates on the Device Templates page).

Figure 54 Device Template Details page

Tip
Some options on the Device Template Details page can be edited only if you
are working with Device Templates assigned to the Default Device Group or
a User-Created Device Group.

• Enter the Name.

Caution
A device template name cannot exceed 5 characters for a Site Template.

• (Optional) Enter a Description.

• (Device Templates assigned to the Default Device Group Only) Select the Device
Class you want to assign to the device.
• (Device Templates assigned to the Default Device Group Only) Select a Connection
Type (either Network or Mobile Disconnected; if you select Mobile Disconnected,
select a Force Provision option of either Enabled or Disabled).

Tip
In Network mode, the device must always have a LAN connection to a WSM
Server. In Mobile mode, the device can be disconnected from a WSM Server
and still be operational. A Force Provision option of Enabled automatically
System Settings 99

provisions the mobile device with an OS Image when connected to, and
booting from, a WSM Server. A Force Provision option of Disabled allows the
user to provision the mobile device with an OS Image when desired (by
right-clicking the WSM Client icon in the system tray and selecting Provision
Disk).

• (Device Templates assigned to the Default Device Group Only) Select the Boot
Selection Mode for the device (First Disk, First Available, or User Select).

Tip
First Disk (default) specifies that the device will always boot from the first
OS Image that is assigned to it.
First Available is the mode that is used for failover purposes. In this mode
you can specify the same OS Image on multiple servers and use that
specification as the assignment for two or more OS Images available. Thus,
the device will try and connect to the first server, and if the server is not
available, the device will try and connect to the remaining assigned servers
as specified.
User Select is the mode that allows users to specify from which OS Image
the device should boot. A menu is displayed for the user when the device
boots, allowing the user to specify the OS Image and server combination.

• The Device Group, Server Group, and Image Name are shown.
• (Device Templates assigned to the Default Device Group Only) Select an Image Name
(selecting a new OS Image Name clears the previous OS Image assignment).
• (For Active Directory Integration Only) The Active Directory Organizational Unit is
shown (for example, wsm.com/CN=Computers).
• If desired, select Specify a Subnet Range to enable, and then enter the Subnet
Address and Subnet Mask.
• Select the Status of the device template (Enabled or Disabled). For a device template
to be Enabled you must assign an OS Image to it.
• Optional Related Tasks you can perform using the Device Template Details page:
• Add a Device Template - Click the Add Device Template link to open and use the
Add Device Template wizard (see"Adding Device Templates").
• Delete this Device Template - Click the Delete this Device Template link to
delete the device template.
• Add or remove a Device Template to or from the Device Group - Click the
Change Device Group link to open and use the wizard (see "Changing the Device
Group Assignment for a Device Template").
• (Device Templates assigned to the Default Device Group Only) Add an OS Image -
Click the Add OS Image link to open and use the Add OS Image page (see "Adding
an OS Image to a Device Template").
100 Chapter 13

Changing the Device Group Assignment for a Device Template

While editing an Device Template on the Device Template Details page, you can assign a
Device Template to all Devices in a user-created Device Group or to individual Devices in
the Default Device Group by using the following guidelines:
1. Click the Change Device Group link to open the Assign Device Groups For Device
Template wizard.

Figure 55 Assign Device Groups For Device Template wizard

2. Determine the Device Groups you want to include using the assignment page:
• User-created Device Group - Select a user-created Device Group and click Next.
The Device Template is assigned the OS Image and Streaming Server that is
assigned to the Device Group you selected. Click Finish to return to the Device
Template Details page.
• Default Device Group - Select the Default Device group and click Next to open the
Assign an OS Image page.
3. Determine the OS Image you want to include using the assignment page.
4. Click Next to open the Assign a Server page.
5. Determine the Server you want to include using the assignment page.
6. Click Finish.
 System Settings 101

Adding an OS Image to a Device Template

While editing a Device Template in the Default Device Group on the Device Template
Details page, you can add an OS Image to a Device Template by using the following
guidelines:
1. Click the Add OS Image link to open the Add an OS Image wizard.

Figure 56 Add an OS Image wizard - Device Templates

2. Select the OS Image you want and click Next to open the Select a Streaming Server
page.
3. Select the Streaming Server you want to assign to the Device Template.
4. Click Finish to return to the Device Template Details page.

Importing Server Licenses

After initially logging in to the installation of a WSM Core Server and importing a Server
License (see Installation Guide: Wyse WSMTM), you can view the Server License
information (valid dates and so on) or import a new Server License by clicking the Server
License link on the System Settings page and using the Server License page.

Figure 57 Server License page

102 Chapter 13

Active Directory Configuration

WSM can be integrated with an Active Directory server for improved User and User Group
management. You can enable or disable Active Directory use within the WSM system by
clicking the Active Directory Configuration link on the System Settings page and using
the Active Directory Configuration page.

Tip
To select or clear the Enable Active Directory check box, all Devices,
Device Templates, Users, and User Groups must be deleted from the WSM
system.

Figure 58 Active Directory Configuration page

Tip
If you select the Enable Active Directory check box, the Active Directory
Configuration page expands.

To configure Active Directory integration with WSM, use the following guidelines:

Tip
After configuring the settings, be sure to click Update Active Directory
Settings to save your settings. You can verify that Active Directory
integration is correctly configured when you can successfully import User
Groups and Users from Active Directory.

• Synchronizing Polling Frequency - Enter the Synchronizing Polling Frequency

(number of seconds between synchronizing the members of User Groups between
Active Directory and the WSM database; the default is 600 seconds, however, you can
turn off the feature by setting the time to 0).
• Enable SSL Connection - If desired, select to enable SSL (for information on using
Active Directory integration with SSL, refer to "About Using Active Directory
Integration"). IMPORTANT: If you enable SSL, be sure to import a certificate to allow
SSL connections to be established with Active Directory as described in Table 12,
"Routine Active Directory Domain Tasks - Active Directory Domains page."
• Active Directory Domains - (Optional) Click the Active Directory Domains link to
open the Active Directory Domains page (for details on managing Active Directory
Domains, refer to "Managing Active Directory Domains").
• Reset - Use Reset to clear any changes you made (before clicking Update Active
Directory Settings).
 System Settings 103

Managing Active Directory Domains

This section describes how to perform routine Active Directory Domains tasks in the WSM
system. It provides information on adding, editing, and deleting Active Directory Domains
by using the Active Directory Domains page.

Active Directory Domains Page

Clicking the Active Directory Domains link from the Active Directory Configuration page
(or the Domains link in the Category area of the Overview main page) opens the Active
Directory Domains page. This page allows you to view and manage Active Directory
Domains that are managed by WSM. It also allows you to easily display the Active
Directory Domains you want by using the filtering feature.

Figure 59 Active Directory Domains page

Although the Active Directory Domains page shows you all of the Domains managed by
the WSM system, you can use the following guidelines to view the domains you want:
• Name Contains - Name of a Domain (use only letters, numbers, dashes, spaces, the
@ character, and periods).
• Status - Status of the Domain (all, Enabled, or Disabled).
After entering your criteria, click Filter to view the results. You can then select the
Domains you want, and begin performing your tasks.
104 Chapter 13
Table 12 provides a quick overview of what you can do using the Active Directory
Domains page.
Table 12 Routine Active Directory Domain Tasks - Active Directory Domains page
Tasks You Can Do
Add a Domain to the system.
Edit a Domain in the system.
Quickly enable or disable a
Domain in the system.
Delete a Domain from the
system.
Import a certificate to allow SSL
connections to be established
with Active Directory (you are
using Active Directory integration
with SSL).
Delete a certificate from the
system (you are using Active
Directory integration with SSL).
How
Click the Add Domain link and
follow the wizard.
Click a Name link in the Domains
area and make your changes.
Click the Enable or Disable link
in the Status list for the Domain.
Select the check box next to the
name of the Domain you want in
the Domains area (you can use
Select All or Deselect All as
needed), click Delete Selected,
and confirm the deletion. The
Domain is deleted and is no
longer shown in the list of
available Domains on the Active
Directory Domains page.
Click the Import Certificate link
and use the Import Certificates
page.
Select the check box next to the
name of the certificate you want
in the Certificates area (you can
use Select All or Deselect All as
needed), click Delete Selected,
and confirm the deletion. The
certificate is deleted and is no
longer shown in the list of
available certificates on the Active
Directory Domains page.
Details
“Adding Domains” on page 105.
“Editing Domains” on page 106.
While you can enable or disable a
Domain while editing a Domain
(on the Active Directory Domain
Details page), you can quickly do
this task directly on the Active
Directory Domains page.
You can also delete a Domain by
using the Delete this Domain
link on the Active Directory
Domain Details page.
IMPORTANT: Domains can be
only deleted from a WSM Server
if all of the User Groups imported
from that domain are deleted from
the WSM system as described in
"Managing User Groups."
After importing the certificate into
the system. The certificate is
shown in the list of available
certificates on the Active
Directory Domains page (the
certificate now allows SSL
connections to be established
with Active Directory).
If you are using Active Directory
integration without SSL, you will
not see the Import Certificate
link as it is not needed for this
mode of operation.
 System Settings 105

Adding Domains
To add a Domain:
1. On the Active Directory Domains page, click the Add Domain link to open the Add
Domain page.

Figure 60 Add Domain page

2. Enter the Domain Name (use the full Domain Name; for example, wsm1.com).
3. (Optional) Enter the DC Hostname or IP Address.
4. Enter the Active Directory User (be sure that this User is a member of the Account
Operators group).
5. Enter the Password.
6. (Optional) Select the Enable Kerberos Authentication to enable verification of a user or
host identity.
7. Select the Status (Enabled or Disabled).
8. Click Finish. The Domain is added to the list of available domains on the Active
Directory Domains page.
106 Chapter 13

Editing Domains
On the Active Directory Domains page, click the Name link of the Domain you want to edit
to open the Active Directory Domain Details page, and then use the following guidelines:

Tip
After editing the settings, be sure to click Save Changes (the Domain is then
modified and can be viewed in the list of available Domains on the Active
Directory Domains page).

Figure 61 Active Directory Domain Details page

• Enter the Domain Name (use the full Domain Name; for example, wsm1.com).
• (Optional) Enter the DC Hostname or IP Address.
• Enter the Active Directory User.
• Enter the Password.
• The Connection Status is shown.
• (Optional) Select the Enable Kerberos Authentication to enable verification of a user or
host identity.
• Select the Status (Enabled or Disabled).
• Default OU (for new devices) is shown, however, you can click the Select link to open
the Select an Organization Unit dialog box and select the an OU from the list (be sure
to click Done to save your selection).
System Settings 107

• Optional Related Tasks you can perform using the Active Directory Domain Details
page:
• Add a new Domain - Click the Add a new Domain link to open and use the Add
Domain wizard (see "Adding Domains").
• Import User Groups from a Domain - Click the Import Groups from this
Domain link to open and use the Import Groups from Active Directory page (see
"Importing User Groups from a Domain").
• Edit the User Groups associated with a Domain - Click a Name link in the
Contains These Groups area to open and use the User Group Details page (see
"Editing User Groups with Active Directory Integration").
• Add a Device OU where new devices can be added to Active Directory - Click
the Add a device OU link to open and use the Add Device Organizational Unit
page.

Tip
When entering the Name of the OU, use only letters, numbers, dashes,
spaces, the @ character, and periods, as special characters may cause
problems when importing User Groups and Users. When entering the
Context Path of the OU, use the following examples for formatting,
ou=FinanceOU,dn=wsm1, dn=com. The Device OU added is available for
you to use when adding and editing Devices and Device Templates.

• Delete an OU managed by the Active Directory Domain - Select the check box
next to the name of the device organizational unit you want in the Device
Organizational Unit Managed by area (you can use Select All or Deselect All as
needed), click Delete Selected, and confirm the deletion. The device organizational
unit is deleted and is no longer shown in the list of available device organizational
units on the Active Directory Domain Details page.

Tip
Device organizational units can only be deleted if the Device OU does not
contain computer accounts for the devices added to the WSM system.
108 Chapter 13

Importing User Groups from a Domain

While editing a Domain Active Directory Domain Details page, you can import User
Groups from a Domain by using the following guidelines:
1. Click the Import Groups from this Domain link to open the Import Groups from Active
Directory page.

Figure 62 Import User Groups from Active Directory page

2. Select the User Groups you want by using the following guidelines:
• Enter the Group Name Contains (use only letters, numbers, dashes, spaces, the @
character, and periods).
• (Optional) Enter the LDAP Context Root.
• Enter the Max Results Limit (zero to the limit of all User Groups in Active Directory
Domain).
• After entering your filter criteria, click Filter to view the results.
• Scroll through the list of User Groups and select the check box for the User Group
Name you want (you can use the Select All or Deselect All links to select User
Groups in the list).
3. After selecting the User Groups you want, click Import Selected. The User Groups
you selected are added to the Name list on the Active Directory Domain Details page.

Tip
Users of these imported User Groups will automatically be added to the
WSM User Name list on the User Group Details page.
 System Settings 109

Content Distribution Configuration

While on the System Settings page, you can click the Content Distribution
Configuration link to open and use the Content Distribution Settings page. This page
allows you to enable compression and http based distribution for Sites.

Figure 63 Content Distribution Settings page

Use the following guidelines:

Tip
After configuring the settings, be sure to click Change Configuration to save
your settings.

• Enable Compression - Select to enable transfer of the OS Images and Application

Images in a compressed format. The images will be uncompressed after they have
been transferred to the destination. A folder for the compressed images will be created
under the osimages and appimages directories where the compressed images will be
stored.

Tip
There is a size limitation of 2 GB for the image files you want to compress.
Image files larger than 2 GB will not be compressed.

• Enable http based distribution for Sites - Select if you want to distribute content to
the Core Server of a Linked Sites using HTTP. This feature is only available for a
Headquarters-based architecture.

Tip
The Core Server of each Linked Site will download content using http. Edge
Servers for each Linked Site will use TCP/IP to download content from the
Core Server of the Linked Site.

• URL - (Only enabled after Enable http based distribution for Sites is enabled) Enter the
Streaming Directory URL of the Headquarters Core Server.
• Username and Password - (Only enabled after Enable http based distribution for
Sites is enabled) Enter the Username and Password of the Headquarters Core Server.
110 Chapter 13

Database Configuration
During the installation of a Core Server or Edge Server, database configuration settings
are made through an installation wizard (for information on the initial installation and
configuration settings of a database, refer to the procedures in the Installation Guide:
Wyse WSMTM). After the WSM system installation is complete, you can edit the database
configurations by clicking the Database Configuration link on the System Settings page
and using the Database Configuration page.

Caution
Changing configuration parameters from the Database Configuration page
will attempt to change database configurations for all active WSM servers in
your system.

Figure 64 Database Configuration page

Use the following guidelines:

Tip
After configuring the settings, be sure to click Change DB Configuration to
save your settings.

Caution
When editing the database configuration of an existing WSM Core Server, all
of the related WSM Services (except for the WSM Administration Service) in
the Core Server (as well as in any Edge Servers) must first be stopped. For
information on stopping WSM Services from within the Administrator
Console, refer to "Managing Services for a Server."

• Enter the Primary Database Server (default is localhost).

• (Optional) Enter the SQL Server Port. The SQL Server port is optional if you are using
the default port or SQL Browser service is running and no firewall is blocking the
Browser service (UDP port 1434) access from WSM.
• Enter the Database Server IP.
• Enter the Database Name (default is StreamingDB).
• Enter the User Name (default is wsmdb).
• Enter the Password (default is password@123).
 System Settings 111

Site Configuration
During the installation of a Core Server or Edge Server, Site configuration settings are
made through an installation wizard. After the WSM system installation is complete, you
can edit the Site configurations by clicking the Site Configuration link on the System
Settings page and using the Site Configuration page.

Figure 65 Site Configuration page - Headquarters Site example

Use the following guidelines:

Tip
After configuration is complete, be sure to click Setup Site.
If you want to change a Headquarters to a Linked Site you must first change
the Headquarters to a Stand-Alone Site and then change it to a Linked Site.

• Synchronization Logs - Click the Synchronization Logs link to open the Database
Synchronization page and view the synchronization process log entries for
Headquarters to Site and Site to Headquarters.
• Change Remote Service Password - Click the Change Remote Service Password
link to open and use the Change Password page. If you change the Remote Service
Password at Headquarters, you must change it on all Linked Sites. All Linked Sites
must match the Headquarters Remote Service Password.
• Choose a Site Category - You can select the Site category you want using the
following guidelines:
· Stand-Alone Site to Headquarters Site - See "Creating a Headquarters Site."
· Stand-Alone Site to Linked Site - When changing a Stand-Alone Site to a Linked
Site, be aware that the database will be periodically refreshed by the Headquarters
of the Linked Site and all Linked Site operations will be conducted from
Headquarters (see "Creating a Linked Site").
· Linked Site to Stand-Alone Site - When changing a Linked Site to a Stand-Alone
Site, be aware that all SQL Server replication setup done by WSM is dropped, the
Linked Site data is deleted from Headquarters, and non-site data is deleted from
the Linked Site.
· Headquarters Site to Stand-Alone Site - When changing a Headquarters Site to a
Stand-Alone Site, be aware that all SQL Server replication setup done by WSM is
dropped, and that the Headquarters cannot be changed if it is currently linked to
other Linked Sites.
112 Chapter 13

Renaming an SQL Server

While on the System Settings page, you can click the Rename SQL Server link to open
and use the Rename SQL Server page. This page allows you to rename an SQL Server
Metadata name (so that it is consistent with the name of the host on which it is running).

Figure 66 Rename an SQL Server page

Managing Virtual Centers

This section describes how to create virtual machines by using the WSM in conjunction
with the VMWare Virtual Center software. To create virtual machines in WSM, you must
first create a template from a “model” virtual machine in the VMWare Virtual Center and
then use the template in WSM. The virtual machines you create in WSM can then be
managed from the System Settings page by clicking Virtual Center Configuration and
using the Virtual Centers page.

Tip
After your initial virtual machine creation, you can skip the steps that are not
necessary (for example, you can skip to step 3 and continue to create virtual
machines based on the same configurations you originally made in steps 1
and 2).

Step 1: Create a Virtual Machine Template in VMWare

Using the VMWare Virtual Center, create a “model” virtual machine with the parameters
you want for the virtual machines you want to create in WSM. That is, select the operating
system type, memory settings, and so on that you want to duplicate later in the virtual
machines you will create in WSM.
After creating the model, create a template from that virtual machine to use in WSM.
 System Settings 113

Step 2: Add a Virtual Center in WSM

To add a virtual center in WSM (where you will use the template):
1. On the Systems Settings page, click the Virtual Center Configuration link to open the
Virtual Centers page.

Tip
In future use after adding a virtual center, you can click on a virtual center
Host link to open the Virtual Center Details page and view its details.

Figure 67 Virtual Centers page

2. Click the Add Virtual Center link to open the Adding Virtual Center wizard.

Figure 68 Add Virtual Center wizard

3. Complete the Add Virtual Center page using the following guidelines:
· If you need to import a certificate in order to communicate with the Virtual Center
over SSL, click the import the SSL certificate link to open and use the Import
Certificate page (enter the Name, Certificate File location, and click Finish).
114 Chapter 13

Tip
The default location of the certificate is C:\Documents and Settings\All
Users\Application Data\VMWare\VMWare VirtualCenter\SSL.

• Enter the Virtual Center Hostname or IP Address (the address of the server where
the virtual center will run).
• (Optional) Enter the Virtual Center Port (port number).
• Select the Enable SSL Connection check box if the virtual center is only
accessible by SSL.

Tip
If the virtual center is only accessible by SSL (default), an administrator must
be sure to import an SSL certificate.

• Select the Validate Server Certificate check box if you want to enable certificate
validation.
• Enter the User ID (your user ID).
• Enter the Password (your password).
• Enter the Data Center Name.
4. Click Next to open Assign Templates page.
5. Determine the templates you want to include using the assignment page.
6. Click Finish.

Tip
After you click Finish, WSM tests the connection to the virtual center to
ensure that it is valid, and then adds the valid virtual center to the list of
virtual centers on the Virtual Centers page.

Step 3: Create Virtual Machines

1. On the Systems Settings page, click the Virtual Center Configuration link to open the
Virtual Centers page.
2. Click on a virtual center link to open the Virtual Center Details page

Figure 69 Virtual Center Details page

System Settings 115

3. Click Create Virtual Machine to open the Create Virtual Machine page.

Tip
For future creations or when editing a Virtual Center, you can use the
Change Template Assignment link to open the Assign Templates page and
select the template you want from the list of All Unassigned Templates, click
Add to assign the template, and then click Done.

Figure 70 Create Virtual Machine page

4. Use the following guidelines:

• Select the Template Name (the template on which you want to base the virtual
machine).
• Enter the VM Name prefix (used for the first half of the name you want to use for the
virtual machine).
• Enter the Start sequence number (used for the second half of the name you want to
use for the virtual machine).
• Enter the Number of Virtual Machines that you want to create.
• Enter the Folder for the VMs (you can enter the folder name or full folder path
excluding the data center name in the format:
Engineering/Software/Virtual Machines).
• Click Create.

Tip
After you click Create, the virtual machines are added to the list of virtual
machines on the Virtual Machines page.

Tip
In future use after adding a virtual machine, you can open the Virtual Centers
page and click on the View status of last virtual machine creation request
link to open the Virtual Machines page and view its details.
116 Chapter 13

Importing Devices from a File

While on the System Settings page, you can click the Import Devices from File link to
open and use the Import Devices page. This page allows you to import devices into your
WSM system. WSM requires that the import file has a list of all MAC addresses of the
devices present in this file. The separators supported are comma, space, or end of line
(that is, each MAC address of the device is on a new line in the file). You can find the MAC
ID of a Wyse thin client on a sticker on the device (Wyse thin client MAC addresses start
with 00 80 64). For MAC addresses of other WSM supported devices, contact the
manufacturer.

Caution
Be sure the Device Template you want to use exists in the system (see
"Adding Device Templates") before importing devices.

Figure 71 Import Devices page

Use the following guidelines:

1. Select the Device Template you want to use (to set the attributes you want on Devices
that are automatically added to the WSM system).
2. Enter the Device Import File (you can use Browse to find and select a file).

Tip
The Description, Device Class, and Boot Mode for the Device Template are
shown.

3. Click Import Devices. The devices are imported into the system and are shown in the
list of available Devices on the Devices page.
14 Reports
This chapter describes how to create WSM reports using the Administrator Console. It
provides information and instructions to help you generate various reports on your WSM
environment.

Generating Reports
Clicking the Reports link from any functional area main page opens the Reports page.
The Reports page allows you to quickly generate all of the WSM reports that are available.
• Aggregated Servers - Details on server and service status information aggregated
from all linked sites.
• Aggregated Servers/Images - Details on server and image information aggregated
from all linked sites.
• Aggregated Devices - Details on device information aggregated from all linked sites.
• Client Report - Details on all the unique clients that have connected to the server.
• License Usage Report - Details on all current application usage.
• Standard Usage Report - Details on past application usage for all Users and User
Groups.
• Activation Report - Details on all application activations and deactivations.
• Subscription Report - Details on which users are subscribed to which applications.

Tip
You can sort report lists according to a heading by clicking on the column
heading you want. You can also list your selected heading in ascending or
descending order by clicking on that column heading again.

Figure 72 Reports page

118 Chapter 14

Aggregated Servers Report

On the Reports page, click Aggregated Servers to open and view the Aggregated
Servers Report page.

Figure 73 Aggregated Servers Report page

Although the Aggregated Servers Report page shows you server and service status
information aggregated from all linked sites, you can use the following guidelines to view
the information you want:
• Name Contains - Name of a Server for client support (use only letters, numbers,
dashes, spaces, the @ character, and periods).
• IP Address - IP Address of the Server.
• Site Group - Name of the Site Group to which the Server is assigned. Use the Site
Group Select link to select the Site Group.
• Site - Name of the Site to which the Server is assigned. Use the Site Select link to
select the Site.
• OS Service Status - Status of the OS Service (all, Up, or Down).
• App Service Status - Status of the Application Service (all, Up, Down, Idle, or
Error).
• Status - Status of the Server (all, Up, or No Response).
• Max Rows - Maximum number of rows to display on a page (enter the number).
After entering your criteria, click Filter to view the results.

Tip
You can click the Name link of the server you want to log in to the Linked Site
and view the server details.
 Reports 119

Aggregated Servers/Images Report

On the Reports page, click Aggregated Servers/Images to open and view the
Aggregated Servers/Images Report page.

Figure 74 Aggregated Servers/Images Report page

Although the Aggregated Servers/Images Report page shows you server and image
information aggregated from all linked sites, you can use the following guidelines to view
the information you want:
• Name Contains - Name of a Server for client support (use only letters, numbers,
dashes, spaces, the @ character, and periods).
• IP Address - IP Address of the Server.
• Site Group - Name of the Site Group to which the Server is assigned. Use the Site
Group Select link to select the Site Group.
• Max Rows - Maximum number of rows to display on a page (enter the number).
• OS Image - Name of the OS Image to which the Server is assigned. Use the OS
Image Select link to select the OS Image.
• Application Image - Name of the Application Image to which the Server is
assigned. Use the Application Image Select link to select the Application Image.
• Site - Name of the Site to which the Server is assigned. Use the Site Select link to
select the Site.
After entering your criteria, click Filter to view the results.
120 Chapter 14

Aggregated Devices Report

On the Reports page, click Aggregated Devices to open and view the Aggregated
Devices Report page.

Figure 75 Aggregated Devices Report page

Although the Aggregated Devices Report page shows you device information aggregated
from all linked sites, you can use the following guidelines to view the information you want:
• Name Contains - Name of a device (use only letters, numbers, dashes, spaces,
the @ character, and periods).
• IP Address - IP Address of the device.
• Device Status - Status of the device.
• MAC Address - MAC Address of the device.
• Site Group - Name of the Site Group to which the device is assigned. Use the Site
Group Select link to select the Site Group.
• Site - Name of the Site to which the device is assigned. Use the Site Select link to
select the Site.
• OS Image - Name of the OS Image to which the device is assigned. Use the OS
Image Select link to select the OS Image.
• Max Rows - Maximum number of rows to display on a page (enter the number).
After entering your criteria, click Filter to view the results.
 Reports 121

Client Report
1. On the Reports page, click Client Report to open the Client Report page.

Figure 76 Client Report page

2. Select the report criteria you want by using the following guidelines:
• Enter a user Group Name or a User Name (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• To view usage for all Users in all User Groups, leave the corresponding entries
blank.
3. After entering your report criteria, click Display Report to generate the report.

License Usage Report

1. On the Reports page, click License Usage Report to open the License Usage Report
page.

Figure 77 License Usage Report page

2. Select the report criteria you want by using the following guidelines:
• Enter a user Group Name or a User Name (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• To view usage for all Users in all User Groups, leave the corresponding entries
blank.
3. After entering your report criteria, click Display Report to generate the report.
122 Chapter 14

Standard Usage Report

1. On the Reports page, click Standard Usage Report to open the Standard Usage
Report page.

Figure 78 Standard Usage Report page

2. Select the report criteria you want by using the following guidelines:
• Enter a user Group Name or a User Name (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• To view usage for all Users in all User Groups, leave the corresponding entries
blank.
3. After entering your report criteria, click Display Report to generate the report.

Activation Report
1. On the Reports page, click Activation Report to open the Activation Report page.

Figure 79 Activation Report page

2. Select the report criteria you want by using the following guidelines:
• Enter a user Group Name or a User Name (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• To view usage for all Users in all User Groups, leave the corresponding entries
blank.
3. After entering your report criteria, click Display Report to generate the report.
 Reports 123

Subscription Report
1. On the Reports page, click Subscription Report to open the Subscription Report
page.

Figure 80 Subscription Report page

2. Select the report criteria you want by using the following guidelines:
• Enter a user Group Name or a User Name (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• To view usage for all Users in all User Groups, leave the corresponding entries
blank.
3. After entering your report criteria, click Display Report to generate the report.
124 Chapter 14

This page intentionally blank.

A System Maintenance
This appendix contains information to help you successfully maintain your WSM system.

Managing Passwords Used by WSM

WSM uses three sets of username and password credentials. Use the following guidelines
to manage the passwords used by WSM:

Caution
It is strongly recommended to use an appropriate password security policy.

• WSM Database – If you need to change the database user account password (default
is password@123), you must change the account password on the database itself and
then restart the WSM Administration Web Service (on the server go to Start |
Administrative Tools | Services, right-click WSM Administration Web Service, and
click Restart). The next time you login to 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 (see Administrators
Guide: Wyse WSMTM).
• Windows Service – If you change the Windows system password for the administrator
user account and it affects any WSM services, then you must update any affected
WSM service listed in the Windows Services Console. For example, if the WSM
Administration Web Service is started by that administrator user account, then you
must change the password in the Properties dialog box of the WSM Administration
Web Service (on the server go to Start | Administrative Tools | Services, right-click
WSM Administration Web Service, click Properties, click the LogOn tab, and then
enter and confirm the new password for the account).
• WSM Administrator Console – To change the administrator account password for the
WSM Administrator Console, log in to the Administrator Console, click the System
Settings tab, click the Change Admin Password, and use the Change Admin
Password page (if you have remote Sites, you can also use the Change Site Admin
Password link to change your Site administrator password).
• WSM Remote Service Account - To provide authentication between the
Headquarters and Linked Sites for communication over https.

Backing Up the WSM Database for System Recovery

It is highly recommended that you back up the WSM Database for system recovery
purposes. WSM stores all system, topology, user, application, and usage data in the WSM
Database. By backing up the WSM Database you can recover all WSM 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.
126 Appendix A

About WSM Server Services

Each WSM server (Core Server or Edge Server) provides these services:
• WSM Administration Web Service - Provides an administration interface
(Administrator Console) for WSM.
• OS Authentication Service - Prevents unauthorized devices from connecting to the
WSM system. It informs each device which OS Image it is 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 WSM services on the WSM server. This
service detects errors and outages, allows you to stop and start the servers, and
monitors server load.
• Content Distribution Service - Synchronizes the repositories of OS Images 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 WSM
servers from responding to PXE requests from “outside” devices that are not part of the
WSM system.
• TFTP Service - Allows for thin client booting, data transfer, and so on.

Understanding and Using the Log Files of WSM

Errors pertaining to 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.
WSM stores log files in the WSM Database and on your file system. These files have a set
size limit (default is 10,000,000 bytes) and will rollover when they become larger than the
limit (making the system self-maintaining).
The Profile Log is a log of communication statistics on the server side providing
information on how long the 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-<server-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)
 System Maintenance 127

About WSM System Monitoring

WSM includes built-in monitoring tools that can be used to watch and check the health of
the WSM system. After login to the Administrator Console, the System Overview page
appears allowing you to quickly view important summary information for each functional
area of the WSM system. The System Overview page 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 WSM environment. For example, the System Overview
page allows you to quickly see that a server requires your attention (as WSM notes this
server issue in the Requires Attention area) and provides you a link to the server page that
you need to address the issue.
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
128 Appendix A

This page intentionally blank.

B Load Balancing
This appendix provides information on the load balancing feature of the WSM system. It
explains how load balancing works and how to set up your system for load balancing.

How Load Balancing Works

Load balancing permits a device to be boot from and be serviced by more than one server.
In this way, Application Images and OS Images can be delivered more reliably and quickly
from servers to thin clients. When the load is too heavy on one server, requests made to
that server are given to a different server instead. The workload is distributed evenly—it is
balanced—across all the servers in the group so that each server does roughly the same
amount of work. If a server goes down, the thin client can boot from a different server and
still obtain the OS Images and Application Images it needs.
Load balancing offers these benefits:
• Faster response time because servers share the workload. No single server is
overloaded when others are idling.
• Improved scalability because adding servers only requires you to place the servers in a
server group. Thin clients can start using the server as soon as images are ready.
• Improved fault tolerance because there is no single point of failure as there is when
only one server serves all clients.

Using Server Groups and Device Groups

Load balancing makes use of server groups and device groups to stream OS Images to
thin clients. Because each device in a device group is assigned the same server group
and OS Image, each device in the group can boot from any server in the server group to
which it belongs. If one server in the group is overworked, another server can take on its
workload. This setup ensures that devices are always being served efficiently by servers.
130 Appendix B

Figure 81 Load balancing setup

Tip
In previous versions of WSM, you could configure a device to boot from up to
four servers. However, administrators had to configure the devices to boot
from the different servers and track where devices boot. Load balancing
replaces this boot configuration process with the server group and device
group concept.

How WSM Selects Boot Servers in the Server Group

With load balancing, WSM selects a server in a server group to provision the device when
you boot it. This selection is based on the number of devices currently booted from the
server and the responsiveness of the server.
WSM uses this process to select which server in the server group to boot from:
1. Finds out the load (number of devices booted from a server) for each server from the
server group.
2. Selects a few of the least loaded servers from all servers in the server group.
3. Sends a request to the servers.
4. Selects the server that responds first.

Tip
WSM may select a different server for a device each time it boots up.
However, if a network outage occurs, WSM reconnects the device to the
same server it was connected to when the outage occurred. This ensures
that any write cache maintained for the device is preserved as long as the
device is up for a session (until the next boot).
 Load Balancing 131

Volatile and Persistent Cache Mode

The load balancing setup works seamlessly when the OS Image is in Volatile Cache
mode. In this mode, each boot deletes changes made during the previous session.
However, if the OS Image is Persistent Cache mode (and is required to preserve the
changes made across multiple sessions), the write cache folder must be shared across all
the servers. If it is not shared across all server, the device may select a different server
during the next boot, and if the new server does not have access to the same write cache
file, changes made during the previous session are not available.

Setup for Load Balancing

Follow these general guidelines to use the load balancing feature of WSM:
1. Create a server group with all the servers that you want to configure for load balancing.
Typically, this server group includes all servers on the same site or location. Load
balancing requires servers to have good network connectivity with the devices they
serve. For more information, see "Adding Server Groups."
2. Assign OS Images to the server group you created. For more information on using the
the Change Server/Server Group Assignment link on the OS Image Details page,
see "Editing Device Groups."
3. Schedule a copy of the OS Image to the destination servers and make sure destination
servers are in ready state.
4. Create a device group and assign all the devices that you want to configure for load
balancing to the device group.If devices need different OS Images, assign them to
different groups. For more information, see "Adding a Device Group."
5. Assign the server group you created in Step 1 to the device group you created in Step
4. For more information, see "Editing Device Groups."
6. Assign the OS Image to the device group. For more information, see "Editing Device
Groups."
132 Appendix B

This page intentionally blank.

C Updating OS Images and
Application Images
This appendix provides information and instructions on updating the OS Images and
Application Images in your WSM system.

Updating an OS Image
While editing an OS Image, you can update the OS Image by using the Start Patch
Process for this OS Image link (or the Start Patch Process for this OS Image With
Existing Delta File link) and completing the required steps. Changes to an existing OS
Image can be either configuration changes or operating system patches that are delivered
by the vendor which are deemed to be necessary by you the administrator.

Tip
Before you begin updating an OS Image, be sure you have denoted the
Reference Device you want to use, as described in "Editing Devices."
The Reference Device is a device of the Default Device Group which you
denote as the Default device that will be used to apply updates or patches
that are needed to an OS Image. By default, the first device that is added to
the WSM system is denoted as the Reference Device. However, you can
change the Reference Device at any time.
On the Network Device Details page for a Reference Device, you can view
the Reference Device notice in the Attention area at the top of the page.
On the Network Device Details page for all other devices of a Default Device
Group, you can use the Make this the Reference Device link to make a
device the Reference Device.
Having a Reference Device is optional for the normal operation of WSM.
However, if you want to update an operating system, you must denote a
device as the Reference Device (on the OS Image Details page) before you
can use the Start Patch Process for this OS Image link (or the Start Patch
Process for this OS Image With Existing Delta File link) and proceed with
updating the OS Image. For example, if a Reference Device does not exist in
the system, you must specify a Reference Device from the available devices
in the system before updating an OS Image.
It is recommended that you do not select an end-user device for use as the
Reference Device. This will allow you to apply updates to an operating
system without affecting end users. The Reference Device must be on the
same network as that of the WSM Core Server (that is, the Reference Device
must be able to boot directly from the WSM Core Server).
134 Appendix C

Updating an OS Image consists of:

• "Step 1: Preparing the OS Image for Updating"
• "Step 2: Starting the Patch Process"
• "Step 3: Applying the Patch on the Reference Device"
• "Step 4 Finalizing and Scheduling the Deployment of the Patch"

Tip
The updating process is designed so that it does not interfere with your
current WSM environment. During the updating process your WSM
environment continues to stream the currently active OS Image. Your WSM
environment will stream the new updated OS Image only after the updated
OS Image is ready and you schedule it for deployment.

Step 1: Preparing the OS Image for Updating

1. Go to the WSM Core Server machine where the OS Image that you want to update
resides (for example, Base Image).

Tip
Ensure that this OS Image is either in Persistent Cache (Shared Mode) or
Volatile Cache (Shared Mode), as described in "Editing OS Images."

2. Create a copy of the OS Image in the same directory (be sure to rename the OS Image
so that you can recognize it later - for example, Base Image v2).

Step 2: Starting the Patch Process

1. On the OS Image Details page (for the OS Image you want to update), click the Start
Patch Process for this OS Image link (or the Start Patch Process for this OS
Image With Existing Delta File link) to open the Select OS Image Copy page.

Caution
If there is no Reference Device, you will receive an error. You must denote
the Reference Device you want to use as described in "Editing Devices," and
then return to this page to start the patch process.

Figure 82 Select OS Image Copy page

 Updating OS Images and Application Images 135

2. Use the following guidelines:

• Enter the Patch Name.
• Select the File Name (be sure to select the OS Image you created in "Step 1:
Preparing the OS Image for Updating" (for example, Base Image 2).
• Enter the Version.
• Select No Cache (Private Mode) for the partition you want. At least one of the
partitions (First Partition Mode, Second Partition Mode, or Third Partition Mode)
must be set to No Cache (Private Mode).
• After completing the entries, click Finish. The OS Image patch is automatically
assigned to the Reference Device.

Tip
You can be sure to identify that the OS Image patch copy was created by
clicking the Name link of the OS Image on the Operating Systems main page
to open the OS Image Details page, and then viewing the Status of the OS
Image patch copy as Patch Copy Created in the Image Hierarchy area.

Caution
If the Reference Device is full or if the Reference Device is not a device of the
Default Device Group, you will receive an error.
If the Reference Device is full (there is a limit of four OS Images that can be
assigned to a Reference Device), you must remove one of the OS Images
and add the OS Image patch as described in "Editing Devices," and then
return to the OS Image Details page to click the Assign Patch to the
Reference Device link. The OS Image patch is now assigned to the
Reference Device. Continue with "Step 3: Applying the Patch on the
Reference Device."
If the Reference Device is not a device of the Default Device Group, you
must change the Device Group assignment of the device (so that the device
is of the Default Device Group) as described in "Editing Devices," and then
return to the OS Image Details page to click the Assign Patch to the
Reference Device link. The OS Image patch is now assigned to the
Reference Device. Continue with "Step 3: Applying the Patch on the
Reference Device."

Step 3: Applying the Patch on the Reference Device

This is a manual step. After the Reference Device (which is in the User Select Boot
Selection Mode) completes the boot process and connects to the WSM Server, it provides
you with an option to select the proper OS Image patch from which to boot.
1. Select the OS Image patch (for example, Base Image V2) that you have added to the
system.

Tip
Be aware that you are in No Cache (Private Mode) for the OS Image, which
means any modifications that you have made will be permanent.

2. Apply the OS Image patch (be sure you have completed any changes that you want to
be available for all users).
3. Shut down the Reference Device.
136 Appendix C

Step 4 Finalizing and Scheduling the Deployment of the Patch

Tip
This step compares the original OS Image and the patch OS Image, and then
creates a delta file (a file which includes only the changes that were made to
the original OS image) that will be sent to the servers (this reduces the
bandwidth requirements for patch deployment in cases where you have
multiple servers to which this image must be deployed).

1. On the OS Image Details page (for the OS Image you want to update), click the
Finalize Patch link to create the delta between the Active OS Image that is currently
Streaming your operating system (for example, Base Image) and the patched OS
Image (for example, a patched Base Image 2).

Tip
After clicking the Finalize Patch link, a warning appears for finalizing a patch
before the patch has been deployed to all servers.
The process of creating the delta file may take several minutes. You can
check to see that the process has been completed by viewing the OS Image
Details page for the OS Image (showing the Status of the OS Image patch
copy as Patch Finalized). When the process is complete, you will have a
delta file (between the currently active OS Image and the OS Image patch)
ready to be scheduled for deployment.

Tip
You can track the distribution process by clicking the Track Content
Distribution link on the System Settings page to open use the Content
Distribution Summary page. If you click the Cancel link in the Schedule
column of the Content Distribution Summary page, the content distribution
will be cancelled and show a state of Cancellation Requested. After the state
changes to a canceled state, you can use the Reschedule link to schedule
the distribution of the OS Image. If you have missed the opportunity to cancel
the content distribution, you can use the Rollback this OS Image link on the
OS Image Details page.

Once the schedule is completed, the WSM Content Distribution Service will
automatically schedule the copy of the patch (delta) file to the different Edge servers
(or remote servers in the case of Linked Sites) which have been previously assigned
the OS Image. Once this delta file copy is completed, the process on the servers will
then merge these changes into a copy of the original OS Image in its own repository
and make it available for the devices that are using these servers.

Tip
To see that the patch has been deployed by the servers, you can check the
Version Deployed column of the servers in the Servers Streaming area of the
OS Image Details page. As the devices using the OS Image in your WSM are
rebooted, they will begin using the new updated OS Image.

The design of the patch process reduces end-user downtime during patch deployment.
The newly patched OS Image is only applied as a pending update to the Network Device
OS assignment. Users can continue to use the original OS Image until they reboot the
Network Device. Once the Network Device reboots, it will begin using the newly patched
OS image.
 Updating OS Images and Application Images 137

Updating an Application Image

While editing an Application Image, you can update the Application Image by using the
Add a Patch for this Application Image link.

Tip
If you need to prepare an Application Image update for use as a patch, refer
to "Preparing an Application Image Update."

Figure 83 Updating Application Image page

Use the following guidelines:

1. Select the File Name you want to use for the Application Image update (patch).
2. Enter the Name.
3. (Optional) Enter the Description.
4. Enter the Version.
5. Click Finish. The Application Image is updated and can be viewed in the list of
available Application Images on the Applications page.

Tip
The updated Application Image is immediately deployed to all of the Edge
servers to which the original image was assigned. As soon as the
deployment is completed, the end user will see a message that the
application has been updated and to save their work if they are actively using
this application. The end user will see the original Application Image being
unsubscribed and the new Application Image being subscribed. This update
process has been automated to ensure that the user has the latest
Application Image, once you update the Application Image.
138 Appendix C

Preparing an Application Image Update

Tip
In general, it is recommended that you store the application environment in
which you originally create an Application Image for future use.

If you are using an existing application environment, complete the following (if you do not
have an existing application environment, create a new Application Image and copy the
Application Set to the repository as described in the Publisher Guide: Wyse WSMTM):
1. Apply the patch or make updates to the existing application environment.
2. Take a snapshot of the changes.
3. Create an Application Set using the snapshot created before the application was
installed and the new snapshot (see the Publisher Guide: Wyse WSMTM).
4. Create an Application Set.
5. Be sure to create a new GUID for the Application Set ID.
6. Copy the Application Set created to the repository.
D Using Driver Injection
This appendix describes how to use driver injection to create “golden” OS images for use
with WSM.

Tip
While you can still use the Wyse UniPlat Tool to create golden OS images for
use with WSM (see "Using the Wyse UniPlat Tool"), using the driver injection
process to create a golden image to support client devices in large
environments with multiple hardware platforms is recommended in most
cases.

Requirements and Known Limitations

Driver injection has the following requirements and known limitations:
• Each client platform must have a reference device with a PXE-enabled network
adapter and a hard disk available.
• Each reference device must have a Windows OS installed on a hard disk.
• The Windows OS version installed on all reference devices must bear the same major
version number (cannot have a mix between XP and Windows 7).
• The final golden VDisk image will have the lowest HAL (Hardware Abstraction Layer)
among all supported platforms.
• Depending on the characteristics of the target platforms, the presence of a PS2 mouse
and keyboard interface on the target platforms may be mandatory.
• Some wireless network adapters may need to be disabled on the golden VDisk.
Installing some wireless network drivers can cause network stack re-bind, which in turn
causes VDisk hang. If wireless network adapter functionality is needed, you must use
the Wyse UniPlat Tool to create a gold VDisk image. The network stack re-bind issue
can also occur on VPN client installations. If VPN is needed, you must use the Wyse
UniPlat Tool to create a gold VDisk image (see "Using the Wyse UniPlat Tool").
• Driver injection is available for Windows XP only for the current release of the
operating system.
• The WSM Server must be a release 3.5 or later.
• The WSM Client installed on the hard disk of the target platforms must be a release 3.5
or later.
140 Appendix D

Overview of Steps
Using driver injection to prepare a golden virtual disk for streaming requires that you:
1. Prepare a VDisk from one of the target platforms (the first target platform). This is the
Base VDisk.
2. Install WSM Client on a second target platform.
3. Boot the second target platform from a hard disk, run VDiskImageCreation.exe to inject
the NIC driver of the second target platform to the Base VDisk of the first target
platform.
4. Boot the second target platform from the VDisk.
5. Install the rest of the drivers of the second target platform to the VDisk.
6. (Persistent Cache or Volatile Cache Only) If the Base VDisk is in persistent or volatile
cache mode (Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode)),
commit the driver injection changes to the VDisk by merging the cache file of the
second platform into the VDisk.
7. Repeat steps 2 through 6 for each additional platform you want.

Detailed Steps
Step 1: Preparing the Base VDisk
The driver injection process starts with a VDisk from the first platform.
Use the following guidelines:
• The first platform must bear the lowest HAL among all target platforms. For example, if
the native HAL for three target platforms are: Advanced Configuration and Power
Interface (ACPI) PC, ACPI Uniprocessor PC, and ACPI Multiprocessor PC, then the
final golden VDisk must use the Advanced Configuration and Power Interface (ACPI)
PC HAL.
• The Base VDisk can be a new disk created from the first platform, or any existing
VDisk streamable to the first platform. The Base VDisk can contain any number of
partitions.
• If a platform does not have a PS2 keyboard/mouse interface, it is recommended that
you use such a platform as the first platform to avoid possible problems with installing
drivers for the new platform later due to any inability to use a USB keyboard/mouse.

Caution
Driver upgrades for the PXE-enabled Ethernet network adapter should be
done before driver injection when the device is booted from hard disk.

• During the driver injection process, the Base VDisk can be configured to private,
persistent or volatile cache mode. However using each cache mode has a different
implication:
• If the Base VDisk is in private mode (No Cache (Private Mode)), driver injection
changes will be written to the VDisk directly. If there is any error during the injection
process, the Base VDisk may become unusable even for the original first platform.
However, if the driver injection process succeeds, you can save the step to commit
the driver injection changes to the Base VDisk. Therefore, it is recommended that if
the Base VDisk is in private mode, a backup copy of the Base VDisk should be
made before starting the driver injection process.
 Using Driver Injection 141

• If the Base VDisk is in persistent cache mode (Persistent Cache (Shared Mode)),
driver injection changes will be written to the cache file for the new device. If the
driver injection fails, the cache file will be discarded automatically. If the driver
injection succeeds, you must commit the changes by merging the cache file to the
Base VDisk explicitly. Once the changes are committed, the cache file for the first
platform will no longer be usable. This means any changes made on the first
platform during previous streaming sessions will be lost. If such changes are
desirable, you should consider merging the cache file from first platform to the Base
VDisk before starting the driver injection process.
• If Base VDisk is in volatile cache mode (Volatile Cache (Shared Mode)), driver
injection changes will be written to the cache file for the new device. By default,
such a cache file will be discarded upon client device reboot. This nature of volatile
cache mode makes it impossible to test the changes made by driver injection.
Therefore, an exception has been made: If the driver injection is successful, the
created cache file will be renamed to <cache file name>_TMPUSE automatically.
The WSM Server will use this TMPUSE cache file for subsequent streaming
sessions of the target device, and treat it as persistent cache mode. Once the driver
injection changes are confirmed working on the new device, you must commit the
changes by merging the TMPUSE cache file to the Base VDisk explicitly, then
delete the TMPUSE cache file.

Step 2: Install WSM Client on a Second Target Platform

Use the WSM Client installation instructions in Installation Guide: Wyse WSMTM to install
the WSM Client on a second target platform.

Step 3: Inject the NIC Driver of the Second Target Platform to the Base VDisk
Use the following guidelines:
• Boot the second target platform from a hard disk.
• Navigate Windows Explorer to the <WSM Client install folder>\OS folder, and run
VDiskImageCreation.exe.

Figure 84 Add/Edit Virtual Disk Utility dialog box

• Select the Existing Disk option, enter the Base VDisk Name, select the Inject
Network Driver into Existing VDisk Image check box, select the From Current
Platform option, and then click Start.
142 Appendix D

Tip
If you want to extend the VDisk size at the same time (VDisk must be in
private mode for this adjustment), fill in the VDisk Size field. Otherwise leave
this field blank.

• On the message displaying the current cache mode of the Base VDisk, click Yes.
• After the driver injection process is complete, click OK, and then close the Add/Edit
Virtual Disk Utility dialog box. The NIC driver of the second target platform is now
injected into the Base VDisk of the first target platform. Now the VDisk is ready to
stream to the target device.

Step 4: Boot the Second Target Platform from the VDisk

Refer to "Adding OS Images" and "Adding Devices" for information to help you stream the
VDisk to the second target platform.

Tip
In order to install drivers for newly discovered hardware, you must use a
keyboard/mouse to make menu selections from the hardware discovery
wizard. If the USB controller driver is not already installed on the VDisk, you
will not be able to use the USB keyboard and mouse. In such a case, it is
recommended that a PS2 keyboard and mouse be attached to the device
when it first boots from the new VDisk. Once the USB controller driver is
installed, a USB keyboard/mouse can be used in subsequent boots. If your
device does not have a PS2 keyboard/mouse interface, you will not be able
to proceed with driver installations.

Step 5: Install the Rest of the Drivers of the Second Target Platform to the VDisk
Use the following guidelines:
• Once the second target platform successfully boots from the new VDisk, the Windows
hardware discovery wizard will prompt you to install drivers for the hardware found in
the device. The drivers and corresponding .inf files can usually be found in the local
hard disk.
• Occasionally the local hard disk volume is not assigned a driver letter. If this is the
case, right-click My Computer, select Manage to open the Computer Management
dialog box, select Disk Management in the left pane, right-click on the local hard disk
in the left pane, select Change Driver Letter and Paths, and then add a drive letter.
• You can point the hardware installation wizard to the local disk drive (<local
disk>:\windows\inf), which contains all the driver .inf files. Driver binaries are usually
under <local disk>:\windows\system32\drivers, <local disk>:\windows\system32, or
<local disk>:\windows folders.
• On some devices, installing video and audio drivers from binaries found in the local
disk causes display or audio hardware malfunction. It is recommended that you install
these drivers from complete driver installation packages provided by the hardware
vendor, if possible.

Caution
Do not upgrade the driver for a PXE-enabled Ethernet network adapter.
Doing so causes VDisk hang. Driver upgrades for the PXE-enabled Ethernet
network adapter should be done before driver injection when the device is
booted from hard disk. If the new platform is a VM session and you need to
re-install VMTools, select a custom installation, and then skip updates to the
network adapter.
 Using Driver Injection 143

• Installing some wireless network drivers can cause network stack re-bind, which in turn
causes VDisk hang. If this is the case, you must roll back the driver injection changes
by deleting the cache file for second target device, re-injecting the NIC driver to the
VDisk, and prevent the wireless network adapter driver from being installed on the new
VDisk. If wireless network adapter functionality is needed, you must use the Wyse
UniPlat Tool to create a gold VDisk image. The network stack re-bind issue can also
occur on VPN client installations. If VPN is needed, you must use the Wyse UniPlat
Tool to create a gold VDisk image (see "Using the Wyse UniPlat Tool").
• After all drivers are installed, reboot the device once to the new VDisk to confirm
proper functionality.

Step 6 (Persistent Cache or Volatile Cache Only): Commit the Driver Injection Changes to the
VDisk
After the VDisk is confirmed for proper functionality, if the Base VDisk is in persistent or
volatile cache mode (Persistent Cache (Shared Mode) or Volatile Cache (Shared
Mode)), you must commit the driver injection changes to the VDisk by merging the cache
file of the second platform into the VDisk.

Caution
The merge tool can only be used on disk images that are not being streamed
at that time (all devices must be shut down first).

Use the following guidelines:

• The merge tool is a command line application available as part of the WSM Server
package version 3.5 and later. If the WSM Server installation location is C:\Program
Files\Wyse\WSM (the default), then the location of the merge tool is C:\Program
Files\Wyse\WSM\os\MergeTool.exe. You can display the usage of the tool by entering
MergeTool.exe -? at the command prompt.
• The NIC driver injection and drivers installation process described in the previous steps
typically updates only the system partition (partition 0). Therefore, only the partition 0
cache file must be merged into the Base VDisk. To identify the cache file to merge, use
the following steps:
• Discover the Base VDisk version from the Image Version field on the OS Image
Details page of the WSM Administrator Console.
• Find out the NIC MAC address of the platform from which the driver was injected.
(for example, 000C290046D7).
• If the Base VDisk is in WSM v2.x or earlier, it supports only a single partition. The
cache file naming convention is <VDisk name>_<client device mac address>. For
example, if MultiWin7 is the VDisk to which platform 000C290046D7's driver was
injected into, then cache file MultiWin7_000C290046D7 is the file that must be
merged into the MultiWin7 VDisk.
• If Base VDisk is in WSM v3.x or later, it supports multi-partitions. The cache file
naming convention is <VDisk name>_<client device mac address>_<cache region
start sector number>_<cache region end sector number>. To merge partition 0's
cache file from platform 000C290046D7 to VDisk MultiWin7, search for the cache
file with the name MultiWin7_000C290046D7_0_xxxx, and then merge this file into
the VL Vdisk.
• To merge the write cache into the VDisk, open a command prompt and change the
directory to the tool installation location (typically something such as C:\Program
Files\Wyse\WSM\os with a command similar to: cd C:\Program Files\Wyse\WSM\os).
From this location you can run the merge tool to merge the appropriate write cache into
the VDisk.
144 Appendix D

This page intentionally blank.

E Using the Wyse UniPlat Tool
This appendix describes how to install and use the Wyse UniPlat Tool. It provides
information on how to create backup files with the tool and use the backup files to create
“golden” OS images for use with WSM.
Wyse UniPlat Tool (UPT) is part of the WSM Client Utilities package. Using the UPT, you
can create a single hard-disk image (“golden” image) that can be used on multiple
hardware platforms. After you create the golden image, you can convert it into an OS
image and stream the image to multiple platforms using WSM. This process allows you to
easily create a universal image for use with various platforms.

Installing Wyse UniPlat Tool

Use the following guidelines:
1. Double-click the WSM Client Utilities.exe to open the installation wizard and click
Next.
2. Click Install to start the installation.
3. Click Finish when the installation is complete.

About the Wyse UniPlat Tool

Use UPT to create and handle UniPlat disk files. A UniPlat disk file is an image (or copy)
of a disk or directory. You use UniPlat disk files to re-create disks or directories on different
systems.

Tip
To run Wyse UniPlat Tool, you must have an account with administrator
privileges.

To launch Wyse UniPlat Tool, click Start and select All Programs | Wyse | WSM Client
Utilities | Wyse Universal Platform Tool.
After you launch Wyse UniPlat Tool, the UPT application window appears divided
vertically into two panes:
• On the left-hand pane, you can browse directories and select UniPlat disk files.
• On the right-hand pane, you can see the properties of the currently selected file (if a file
is selected).
To perform actions on a UniPlat disk file, click an icon on the toolbar or select an option on
the File menu.
146 Appendix E

Figure 85 Wyse UniPlat Tool Interface

Creating a Backup Windows Partition

Use the following guidelines to use UPT to back up a Windows partition on a client
machine:
1. Install and run UPT on the machine on which you will back up the Windows partition.
2. In UPT, create a UniPlat disk file on a mapped drive on the network or an external hard
disk (see "Creating a UniPlat Disk File").
3. In UPT, back up the Windows partition on the client machine (typically the C: drive) to
the newly created UniPlat disk file. You can use this file to restore the partition.

Restoring a Windows Partition

In order to restore a Windows partition, the machine to which the partition will be restored
needs at least two pre-formatted partitions:
• The partition from which Windows currently boots up (named the boot partition).
• The partition to which UPT will restore the backed-up Windows partition (named the
destination partition).

Tip
Alternatively, one can boot the machine with an OS image using WSM
technology, and restore the backed-up Windows partition to a physical hard
disk attached to the machine. In this case, only one partition is needed in the
local hard disk.

Use the following guidelines to restore a Windows partition to a hard drive:

1. On the machine to which the Windows partition is to be restored, install and launch
Wyse UniPlat Tool.
2. Using UPT, restore the UniPlat disk file from a mapped network drive or external hard
disk to the destination partition.
 Using the Wyse UniPlat Tool 147

After the restore, the destination partition is made the active partition, and the machine
boots up from the destination partition on this and subsequent reboots (in order for this to
happen, you must have selected the This Image Is Bootable option in the Properties
dialog box; see "Setting UniPlat Disk File Properties").
Wyse UniPlat Tool can also be used to back up or restore only a selected subfolder within
the Windows partition.

Creating a UniPlat Disk File

A UniPlat disk file contains backup files. Initially when you create the file, it is empty. After
you create it, the next step is to insert backup files into the UniPlat disk file with the Wyse
UniPlat Tool backup feature.

Creating the Initial File

Use the following guidelines to create the initial UniPlat disk file:
1. On the client machine with the files you want to copy, start Wyse UniPlat Tool.
2. In the left-hand pane, select the directory where you want the UniPlat disk file to reside.

Tip
Store UniPlat disk files on a mapped drive or external hard disk; the UniPlat
disk file should not reside on the hard disk being copied. You can click the
Map Drive icon in the toolbar to create a new mapped drive to another
computer.

3. Click Create on the toolbar. UPT creates a new UniPlat disk file named New File.wup.
4. Select the file, click Rename, and enter a new name for the UniPlat disk file.

Setting UniPlat Disk File Properties

The properties of a UniPlat disk file help you identify the file, and more importantly, allow
you to prepare the file for use with WSM. To establish the properties of a UniPlat disk file,
select it and click Properties on the toolbar. You see the Properties dialog box. Select a
tab — Information, Description, or Options — and adjust the values.

Information Properties Tab

Use the Information tab of the Properties dialog box to describe the UniPlat disk file. For
example, you can enter an author and company name. UPT does not interpret these
fields; they are for use by administrators.

Description Properties Tab

Use the Description tab of the Properties dialog box to write a description of the UniPlat
disk file. UPT does not interpret these fields; they are for use by administrators.
148 Appendix E

Options Properties Tab

Use the Options tab of the Properties dialog box to set the capture and restore options.
Capture options are found at the top of the dialog box; restore options are on the bottom.

Figure 86 Properties dialog box - Options tab

Capture Options:
Capture options are used for backups. The Capture option on the Options tab is:
• Prepare Image for Wyse OS Streaming: Check this box if you intend to use this
image to generate an OS image to deploy with WSM technology. UPT will launch
SelectNIC.exe to select the network adapter that will connect to the WSM Server
before backing up the Windows session. (This option has no effect if you are not
backing up a bootable image.)
Restore Options:
Restore options are used for restorations. The Restore options on the Options tab are:
• Delete All Files Before Restoring: Clears the destination directory of all files and
subfolders prior to the restoration of a UniPlat disk file.
• This Image Is Bootable: Makes the destination partition bootable after the restoration.
Check this field if you are restoring an entire bootable partition. Checking it ensures
that the destination partition is made active. The boot.ini and drive letter assignment for
the destination partition will be fixed accordingly so that Windows can boot from this
partition after the restoration.
· Keep Critical Drivers from Current Windows Session: Check this box if you are
installing a UniPlat disk file that was captured from a different platform. Due to
hardware differences between the restored image and the current platform, the
current platform may become unbootable after the restoration because it may lack
the appropriate disk controller driver necessary for booting up. This option causes
all drivers and binaries critical for booting up the current platform to be copied from
the current Windows session to the destination partition. It also copies over driver
installation files (such as .inf files and driver binaries) from the current Windows
session to the destination partition. These files may come in handy when
re-installing drivers for the current platform after the image is restored and booted
up. Note that the current Windows session should be the same Windows version as
the restored image; otherwise, the driver files copied from the current Windows
session may not be usable on the restored image.
 Using the Wyse UniPlat Tool 149

Tip
You do not need to enable this option if you are restoring a UniPlat disk file
that was captured from the same platform because all the drivers should
already be in place in the UniPlat disk file.

· Perform Post Restore Fix Up Only: This option is mainly for debugging purposes.
Enabling it causes all post-restoration fix-up operations that make the destination
partition bootable to be performed without restoring files from the UniPlat disk file
first. This option can be used if you have gone through the restoration operation
once but Windows failed to boot up from the destination partition. In this case, one
or more post-restoration operations may not have completed successfully. Select
this option to attempt the post-restoration fix-ups again without going through the
whole restore process.

Inserting Files into a UniPlat Disk File

After creating a UniPlat disk file, the next task is to insert one or more files (up to and
including a backup of an entire partition) into the UniPlat disk file. Use the following
guidelines to insert files into a UniPlat disk file:
1. Start Wyse UniPlat Tool.

Warning
Close all open applications except Wyse UniPlat Tool before inserting files in
the UniPlat disk file. Otherwise, you may capture locked or intermediate files.

2. Select a UniPlat disk file on the left side of the window.

3. Examine the Capture options of the file. Make sure the correct options are selected.
4. Click Backup on the toolbar to open the Backup dialog box.

Figure 87 Backup dialog box

5. Enter the directory you want to back up or use Browse to find and select the directory
you want. Select the root drive of the current Windows session if you want to capture a
bootable Windows image.

Tip
You cannot back up from a Windows session that is currently streamed from
WSM. You can, however, restore a UniPlat disk file to the hard disk while you
are booting up from a streaming Windows session.

6. Click Go. All files and subdirectories in the directory you selected are added to the
UniPlat disk file.
150 Appendix E

Restoring a UniPlat Disk File to a Partition

Use the following guidelines to restore a UniPlat disk file to a partition:
1. In Wyse UniPlat Tool, select the UniPlat disk file with the backup files.
2. Examine the Restore options of the UniPlat disk file to make sure you selected the
correct options (see "Setting UniPlat Disk File Properties").
3. Click Restore on the toolbar to open the Restore dialog box.

Figure 88 Restore dialog box

4. Enter the directory where the files will be restored. If you are dealing with a bootable
image that captured the entire partition of a Windows session, you normally restore it to
the root of the destination partition.
5. Click Go to restore the files.

Creating a Single OS Image that Supports Multiple Hardware Platforms

This section explains how to create a single UniPlat disk file that supports multiple
Windows-based hardware platforms. It describes the requirements and how to create a
combined OS UniPlat disk file that supports multiple platforms.

Requirements for a UniPlat Disk File and Supported Platforms

In order to support multiple hardware platforms with the UniPlat disk file, the platforms
must meet these requirements:
• The HAL (Hardware Abstraction Layer) of the UniPlat disk file must be compatible with
all platforms being supported, and for this to occur, the Windows OS installed on each
platform must use the lowest common HAL across all platforms (see "Checking and
Changing the HAL of a Computer" for details on how to select the lowest common
HAL).
• The Windows OS on all supported platforms must be the same version and service
pack level. Windows XP Home or Professional with Service Pack 2 or above is
recommended.
• In order to use Wyse UniPlat Tool to prepare a single UniPlat disk file for multiple
hardware platforms, each platform needs at least two partitions formatted to the
appropriate file system (NTFS is recommended). The partitions must be large enough
to accommodate Windows installations for all platforms being supported. (If you are
able to boot up a platform from an OS image using Wyse Streaming technology, only
one local hard disk partition is required.)
 Using the Wyse UniPlat Tool 151

Creating a Combined UniPlat Disk File

This section explains how to create a combined UniPlat disk file to support multiple
hardware platforms if an OS image does not already exist for any of the target platforms.
Creating the combined image involves backing up the Windows installation to a UniPlat
disk file, restoring it to a partition on another platform, and then rebooting from a second
partition on the other platform. Figure 89 shows an overview of the steps required to
create a combined UniPlat disk file (PF1 represents Platform 1, Part 1 represents Partition
1, and so on).

Figure 89 Overview of steps to create a combined UniPlat disk file

To create a single OS image that supports multiple hardware platforms:

Step 1: Create and back up the UniPlat disk file

1. Install Windows OS, required drivers, and Wyse UniPlat Tool on one of the partitions
on the platform. In the illustration, install on Platform 1 (PF1), Partition 1 (Part1).
2. Launch UPT from Platform 1 to back up the Windows root drive (e.g., C:\) of this
platform to a UniPlat disk file (IMG1.wup in the illustration) on a shared network folder
or external hard disk (see "Creating a UniPlat Disk File" for details).

Tip
If you intend to create an OS image for streaming from the final combined
image, select the Prepare Image for Wyse OS Streaming option on the
Options tab of the Properties dialog box before starting the back up process
(see "Setting UniPlat Disk File Properties" for details).
152 Appendix E

Step 2: Restore the UniPlat disk file to a partition on the next platform
1. Install Windows OS, required drivers, and Wyse UniPlat Tool on one of the partitions
on the next platform. In the illustration, install on Platform 2 (PF2), Partition 1 (Part1).
Make sure both platforms have the same HAL, Windows OS version, and service
packs.
2. Launch UPT from Platform 2 (PF2) to restore the UniPlat disk file (IMG1.wup in the
illustration) to the root drive of Partition 2 (e.g. D:\) (this partition must be
pre-formatted). Make sure the following options are chosen on the Options tab of the
Properties dialog box:
· Select Delete All Files Before Restoring. This option ensures that all files from
destination partition (Part2 of Platform 2) are deleted before the restoration.
· Select This Image Is Bootable. This option ensures that the destination partition
(Part2 of Platform 2) is bootable after the restoration.
· Select Keep Critical Drivers from Current Windows Session. This option
ensures that critical drivers and registries (e.g., disk controller driver) required for
platform 2 to boot up are copied over from the Windows session of platform 2 (Part1
of Platform 2) to the destination partition, and that driver installation files (e.g.,
network/display/audio/… drivers) for platform 2 are copied over from the Windows
session of platform 2 to the destination partition.
· Do Not select Perform Post Restore Fix Up Only.
3. After the restoration, make sure that no error message is displayed in the UPT dialog
box.

Step 3: Reboot the platform

1. Reboot the platform (PF2 in the illustration). This platform boots to the newly installed
partition (Part 2 in the illustration). When Windows discovers new hardware on the
platform, it starts the Found New Hardware Wizard and prompts you to install drivers.
2. Direct the Found New Hardware Wizard to the C:\Windows\inf folder to find the
appropriate driver installation files (see "Reinstalling Drivers for the Current Platform"
for details). After all drivers for platform 2 are re-installed, the resulting image can run
on platform1 and 2.
Repeat steps these for more platforms if needed. You can reuse the UniPlat disk file to
back up the new combined image.
Optionally, use UPT to restore the final image to each supported platform to verify the
functionality.
 Using the Wyse UniPlat Tool 153

Reinstalling Drivers for the Current Platform

After you restore a UniPlat disk file that was not captured from the current platform, you
have to reinstall drivers for the platform. You have to do this because the newly restored
partition does not have the drivers to support the current platform. If you selected the Keep
Critical Drivers from Current Windows Session option when you created the UniPlat disk
file (see "Setting UniPlat Disk File Properties"), drivers for the current platform are already
in the newly restored partition. You just need to point the Windows Found New Hardware
Wizard to the correct location of these drivers for installation.
Use the following guidelines to point Windows to drivers for the current platform:
1. When the Found New Hardware Wizard appears, select the Yes, This Time Only
option and click Next.
2. Select the Install from a List or Specific Location (Advanced) option and click Next.
3. Select the Include this Location in the Search check box.

Figure 90 Found New Hardware Wizard

4. Enter the path to C:\WINDOWS\inf in the text box, and click Next.
After Windows finds the appropriate .inf file for the target hardware, it looks for the driver
binaries. These binaries are typically located either in the C:\WINDOWS\system32 or
C:\WINDOWS\system32\drivers folder. Some hardware components need to install .hlp
files. These files are typically located in the C:\WINDOWS\help folder. You can use
Browse to find the needed file. If the needed file does not exist in the destination partition,
look for it in the other partition from which Windows used to boot up, if this partition is still
accessible.
154 Appendix E

Creating a “Golden” OS Image from Current OS Images

This section explains how to prepare a single OS image for multiple hardware platforms
when individual OS images are currently available for some of the target platforms. For the
purposes of this discussion:
• There are three different hardware platforms named PF1, PF2, and PF3.
• Each platform has a corresponding OS image named OS1, OS2, or OS3 from which
the platform can be booted up using WSM technology.
• The goal is to prepare a single OS image (named OS123) from which all three
platforms (PF1, PF2, and PF3) can be booted up using WSM technology. This image is
referred to as the “golden” OS image.

Figure 91 Using a golden OS image to boot all platforms

Hardware and Partition Requirements

The minimum hardware requirements for creating a golden OS image are as follows:
• Each platform device must have a local hard disk with one primary Master Boot Record
(MBR)-type partition formatted to NTFS.
• The partitions must be large enough to accommodate the desired Windows installation
of all platforms (PF1, PF2, and PF3 in our example).
• The requirements on existing OS images for platform 2 and 3 (i.e., OS2 and OS3 in our
example, but not OS1; because hard disk Windows installation is required for platform
1, OS1 is not used) are as follows:
· In order to share the same Windows OS image across multiple hardware platforms,
the HAL (Hardware Abstraction Layer) of the golden image must be compatible with
all platforms. This means the OS Image for PF2 and PF3 must already be using the
lowest common HAL across all three platforms (see "Checking and Changing the
HAL of a Computer" for details on how to confirm that the lowest common HAL is
used). If the OS images are using different HALs, they cannot be used to create a
golden image.
· The Windows OS on all supported platforms must be the same version and service
pack level (Windows XP Home or Professional with Service Pack 2 or above is
recommended). If the platforms are of different service pack levels, you can bring
the OS images up to sync by installing the appropriate service pack while the
images are in private mode.
 Using the Wyse UniPlat Tool 155

Creating the Golden Image

Use the following guidelines to create a golden OS Image that supports multiple
Windows-based hardware platforms:
1. Install Windows OS, required drivers, and Wyse UniPlat Tool on a hard disk partition of
PF1. Make sure this Windows installation is the same version and service pack level as
OS2 and OS3. Make sure as well that the lowest common HAL across all three
platforms are used in this Windows installation.
2. Boot up PF1 from the hard disk, and launch UPT to back up the Windows root drive
(e.g., C:\) of PF1 to a UniPlat disk file (e.g., IMG123.wup) on a shared network folder or
an external hard disk. Before you start the back up process, select the Prepare Image
for Wyse OS Streaming option on the Options tab of the Properties dialog box.
3. Boot up PF2 from OS2 using WSM technology. If it is not installed already, install Wyse
UniPlat Tool on OS2. Launch UPT from OS2 to restore IMG123.wup to the root drive of
the PF2 local hard disk. Make sure the following Restore options on the Options tab of
the Properties dialog box are selected before you start the restore process:
· Select Delete All Files Before Restoring. This option ensures that all files from the
destination partition are deleted before the restoration. In this case, all files from the
PF2 local hard disk partition are deleted before the restoration.
· Select This Image Is Bootable. This option ensures that the PF2 hard disk partition
is bootable.
· Select Keep Critical Drivers from Current Windows Session. This option
ensures that critical drivers and registries (e.g., disk controller driver) required for
PF2 boot up are copied over from OS2 to the PF2 local hard disk partition, and that
driver installation files (e.g., network/display/audio/… drivers) for PF2 are copied
over from OS2 to the PF2 local hard disk partition
· Do Not select Perform Post Restore Fix Up Only.
4. After the restoration, make sure that no error message is displayed in the UPT dialog
box.
5. Reboot PF2 to the local hard disk. PF2 boots to the newly restored local hard disk
partition. When Windows discovers new hardware on PF2, it starts the Found New
Hardware Wizard and prompts the user to install drivers.
6. Direct the Wizard to the C:\Windows\inf folder to find the appropriate driver installation
files (see "Reinstalling Drivers for the Current Platform" for details).
7. After all drivers for PF2 are re-installed, reboot PF2 to the local hard disk if prompted
by Windows. This PF2 hard disk Windows installation can now run on both PF1 and
PF2.
8. Repeat Steps 2 through 7, but this time boot up PF3 and complete the process with this
platform so that the PF3 installation can now run on PF1, PF2, and PF3.
Optionally, with PF3 booted up from a local hard disk, you can launch UPT to back up the
Windows root drive (e.g., C:\) of PF3 to a UniPlat disk file (e.g., IMG123.wup) on a shared
network folder or an external hard disk. Check the Prepare Image for Wyse OS Streaming
option on the Options tab of the Properties dialog box before you start the back up process
(see "Setting UniPlat Disk File Properties" for details). The resulting IMG123.wup file is
good for PF1, PF2 and PF3. This UniPlat disk file can be useful for disaster recovery or to
generate a golden image for additional hardware platforms.
156 Appendix E

Optionally, boot up each platform from the corresponding OS image using WSM
technology, and use UPT to restore IMG123.wup to the hard-disk partition of PF1, PF2
and PF3. Verify that each restoration of IMG123.wup is bootable and functional for all
three platforms.
With PF3 booted from the local hard disk, install WSM Client on PF3. Use the WSM virtual
disk capturing tool to capture an OS image (VD123) from the PF3 hard disk. The resulting
OS image is capable of booting up all three platforms using WSM technology.

Tip
When installing WSM Client on PF3, you may see an error message telling
you that “the file osmsmdf.sys on (unknown) is needed.” To locate the
requested file, use Browse to locate and enter the following in the Copy
files From field: c:\windows\system32\drivers.

Checking and Changing the HAL of a Computer

To share the same golden OS image across multiple hardware platforms, the HAL
(Hardware Abstraction Layer) of the image must be compatible with all platforms. HAL is
the OS programming interface that serves as an interface between a system's hardware
and software.
Windows XP offers six HALs. From most to least compatible, they include:
• Standard PC
• MPS Uniprocessor PC
• MPS Multiprocessor PC
• Advanced Configuration and Power Interface (ACPI) PC
• ACPI Uniprocessor PC
• ACPI Multiprocessor PC

Warning
Standard PC, the most compatible HAL, lacks some important features such
as automatic computer turn off upon shutdown.

This section explains how to check which HAL a PC uses and change the HAL if
necessary.

Checking the HAL on a Computer

Use the following guidelines to check the HAL on each computer for which you want to
create a golden OS image:
1. Start the PC.
2. Click Start and select Control Panel.
3. In the Control Panel, select the System icon to open the System Properties dialog
box. (If you do not see the System icon, click the Switch to Classic View link.)
4. Select the Hardware tab.
 Using the Wyse UniPlat Tool 157

5. Click Device Manager to open the Device Manager window.

6. Open the Computer folder to view the HAL. Note the HAL on each PC and which is
the lowest common HAL.

Figure 92 Device Manager window

Changing the HAL on a Computer

Caution
You cannot change the HAL on an OS image directly because doing so
yields an unbootable OS image. To change the HAL on an OS image, start
by changing the HAL on a Windows session booted from your local hard
disk. Then, after all drivers for the new HAL are installed, install the WSM
Client and use the WSM virtual disk capturing tool to capture the OS Image.

Use the following guidelines if you need to change the HAL on a PC:
1. Open the Control Panel and select the System icon to open the System Properties
dialog box.
2. Select the Hardware tab and click Device to open the Device Manager window.
3. Open the Computer folder to view the HAL.
4. Right-click the HAL and select Properties to open the Properties dialog box.
5. Select the Drivers tab and click Update Driver.
6. Select the Yes, This Time Only option and click Next
7. Select the Install from the List or Specific Location (Advanced) option and click
Next.
8. Select the Don’t Search, I Will Choose the Driver to Install option and click Next.
9. Make sure the Show Compatible Hardware check box is selected
10.Select the desired HAL and click Next.
Windows will install the new HAL and reboot the computer. After the reboot, you may be
prompted to install newly found hardware drivers.
158 Appendix E

Limitations and Known Issues

These issues apply to bootable UniPlat disk files only. If you are not backing up and
restoring the entire Windows partition, these issues do not apply.
• Restoring a bootable UniPlat disk file on a live partition (the partition from which
Windows is currently running) is not supported.
• The destination partition on which the UniPlat disk file restores must be a primary
MBR-type partition. UPT does not support GPT-type partitions or dynamic-disk or
non-simple volumes (i.e., a spanned/Mirrored/Striped/RAID-5 volume).
• Wyse UniPlat Tool does not provide a unique computer name or IP address for the
restored Windows session. All configurations, including computer name and IP
configurations from captured Windows sessions, are carried over. Enabling DHCP in
your source Windows session is recommended.
• When the Keep Critical Drivers from Current Windows Session option is enabled, UPT
attempts to copy driver binaries and registries from the current Windows session to
destination partition. If the current Windows session is of a different version or service
pack level than the target restored image, the copied drivers and registries may not be
compatible.
• If the first client device has PS2 kbd/mouse and the second has USB kbd/mouse, after
restoring the first client image to the second client device, the kbd/mouse of the second
client device may not function because it is missing the necessary USB controller
driver even if the Keep Critical Drivers from Current Windows Session option is elected
before restoring. This is because when the second device boots up with many
uninstalled drivers, the hardware manager enumerates new hardware. It may find
other cards (e.g., display, audio, or network) before the USB Controller. At that time,
the OS will prompt the user to install the new hardware automatically. The user is
supposed to click OK to let Windows install the driver automatically, but because the
USB controller is not installed yet, the USB kbd/mouse does not function, and the user
cannot get the Hardware Installation Wizard to move on. The workaround is to make
sure that the PS2 kbd/mouse is available on the second device. After getting past this
point, the USB controller is enumerated and installed on the second device, and the
USB kbd/mouse will work.
 159

Tables
1 Routine Site Group Tasks - Site Groups page 10
2 Routine Site Tasks - Sites page 15
3 Routine Operating System Tasks - Operating Systems page 26
4 Routine Application Tasks - Applications page 36
5 Routine Server Group Tasks - Server Groups page 44
6 Routine Server Tasks - Servers page 50
7 Routine Device Group Tasks - Device Groups page 56
8 Routine Device Tasks - Devices page 64
9 Routine User Group Tasks - User Groups page 76
10 Routine User Tasks - Users page 85
11 Routine Device Template Tasks - Device Templates page 95
12 Routine Active Directory Domain Tasks - Active Directory Domains page 104
Administrators Guide

Wyse WSMTM Release 3.5

Issue: 070910

Written and published by:

Wyse Technology Inc., July 2010

Created using FrameMaker® and Acrobat®