Professional Documents
Culture Documents
WSM 2.3 Admin Guide
WSM 2.3 Admin Guide
WSM 2.3 Admin Guide
Issue: 040609
PN: 883874-01 Rev. F
Contents
1 Introduction 1
About this Guide 1
Organization of this Guide 2
Wyse Technical Support 3
Links to Related Documentation and Services 3
2 Overview 5
Wyse WSM Functional Areas 5
Getting Started 6
Logging In 6
Using the System Overview Page 7
Changing Your Administrator Password 7
Navigating in Wyse WSM 8
Filtering Feature 8
Using Message Areas and Quick-Links 8
Logging Out 9
About Using Active Directory Integration 9
3 Operating Systems 11
Managing Operating Systems 11
Operating Systems Page 11
Adding OS Images 12
Editing OS Images 14
Assigning an OS Image to a Server Group 17
Adding, Editing, and Deleting Operating System Classes 18
Adding, Editing, and Deleting Device Classes 19
4 Applications 21
Managing Application Images and Application Licenses 21
Applications Page 21
Adding Application Images 23
Editing Application Images 25
Assigning Application Images to Server Groups 27
Adding Application Licenses 28
Editing Application Licenses 30
Assigning Groups for an Application License 31
5 Server Groups 33
Creating and Managing Server Groups 33
Server Groups Page 33
The Default Server Group and User-Created Server Groups 34
OS Image and Application Image Assignments in Server Groups 34
iv Contents
6 Device Groups 47
Managing Device Groups 47
Device Groups Page 47
Understanding the Default and User-Created Device Groups 48
Default Device Group 48
User-Created Device Groups 48
Adding a Device Group 49
Deleting a Device Group 51
Editing and Managing Device Groups 51
Sending a Command to Devices in a Device Group 53
Managing Devices 54
Devices Page 54
Adding Network and Mobile Devices 56
Editing Devices 58
Reassigning a Device to a Different Device Group 62
Adding an OS Image for a Device 62
Updating an OS Image Assignment for a Device 63
Sending Commands to Devices 64
7 User Groups 67
About Active Directory Integration 67
Managing User Groups and Members 67
Managing User Groups and Members with Active Directory Integration 67
User Groups Page 68
Adding User Groups 69
Adding User Groups without Active Directory Integration 69
Adding User Groups with Active Directory Integration 71
Editing User Groups 72
Editing User Groups without Active Directory Integration 72
Assigning Users for User Groups without Active Directory Integration 73
Editing User Groups with Active Directory Integration 73
Assigning Application Licenses for User Groups 74
8 Users 77
About Active Directory Integration 77
Managing Users with Active Directory Integration 77
Managing Users without Active Directory Integration 78
Users Page without Active Directory Integration 78
Adding Users without Active Directory Integration 79
Editing Users without Active Directory Integration 81
Changing User Passwords without Active Directory Integration 82
Assigning User Groups for a User without Active Directory Integration 82
Contents v
9 System Settings 85
Managing System Settings 85
System Settings Page 85
Importing Server Licenses 89
Active Directory Configuration 89
Database Configuration 90
Moving Servers 91
Renaming an SQL Server 92
Importing Devices from a File 93
Managing Device Templates 94
Adding Device Templates 94
Editing Device Templates 96
Choosing a Different Device Group for a Device Template 98
Adding an OS Image for a Device Template 99
Managing Active Directory Domains 100
Active Directory Domains Page 100
Adding Domains 102
Editing Domains 103
Importing Groups from a Domain 104
Adding a Device Organizational Unit 105
Importing Certificates to Allow SSL Connections with Active Directory 106
Managing Virtual Centers 106
10 Reports 111
Client Report 112
License Usage Report 112
Standard Usage Report 113
Activation Report 113
Subscription Report 114
Figures 141
2 Overview
This chapter provides a brief overview of the functional areas within the Wyse WSM
system. It also provides important information on the general features of the system to
help you quickly get started as the Wyse WSM Administrator. In addition, this section
contains important information concerning Active Directory integration.
Note
Wyse WSM currently supports Microsoft IE 6.0 or later.
6 Chapter 2
Getting Started
One of the best ways to get started as the Wyse 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 Wyse WSM you need to know about:
• "Logging In"
• "Using the System Overview Page"
• "Changing Your Administrator Password"
• "Navigating in Wyse WSM"
• "Logging Out"
Logging In
If you have never started Wyse WSM and this is your first log-in, refer to the Installation
Guide: Wyse WSMTM for instructions on starting Wyse WSM for the first time.
To log in any time after you have completed your first log-in to Wyse WSM, be sure to use
your correct Admin Username (default is admin) and Password (default is admin).
Note
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."
Filtering Feature
While in Wyse 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 Wyse 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.
Logging Out
To log out of Wyse WSM, click the Logout link. This link is always available in the
upper-right corner of the screen.
Note
If the Active Directory integration is not enabled, then the 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 Wyse WSM.
For an OS Image mode of Volatile Cache (Shared Mode) - Each time they
log-in to Wyse WSM.
Using Active Directory Integration with and without Secure Sockets Layer (SSL)
Wyse WSM can operate with or without 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 you, Active
Directory, and the 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 should also
have the 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 the Active Directory and perform
all operations on the device/computer accounts in Active Directory.
In Active Directory integration with SSL, Wyse WSM uses SSL (a secure protocol) 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.
In Active Directory integration with SSL, you have the flexibility to:
10 Chapter 2
• Trust any secure Domain Controller - In this case, the WSM Server will work with
any Domain Controller which has a digital certificate installed.
• Enforce the Domain Controller certificate - In this case, the digital certificate
installed on the Domain Controller must be imported into Wyse WSM. After the
certificate is imported into Wyse 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 Wyse WSM before the communication between Wyse WSM and the
Domain Controller can be established.
3 Operating Systems
This chapter describes how to perform routine operating system tasks on the Wyse WSM
system. It provides information on managing operating systems, OS Classes, and Device
Classes.
Initially, the Operating Systems page shows you all of the operating systems available on
the Wyse WSM system, but you can use these tools 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 Operating System Class to which an operating system is
assigned (for example, Windows 2000 or Windows XP).
• Device Class - Class value of the network device to which the operating system is
assigned (for example, Wyse V00).
12 Chapter 3
After entering your criteria, click Filter to view the results. You can then select the OS
Images you want, and begin performing your tasks.
Use the following guidelines to perform available tasks on the Operating Systems page:
• Click the Add OS Image link to open the Add OS Image page (for details on adding an
OS Image, refer to "Adding OS Images").
• Click the Manage OS Classes link to open the Manage OS Classes page (for details
on adding, editing, and deleting OS Classes, refer to "Managing Operating Systems").
• Click the Manage Device Classes link to open the Manage Device Classes page (for
details on adding, editing, and deleting Device Classes, refer to "Managing Devices").
• Click a Name link in the OS Images area to edit the OS Image (for details on editing an
OS Image, refer to "Editing OS Images").
• Delete an OS Image by selecting the check box next to the name of the OS Image you
want in the OS Images area (you can use Select All or Deselect All as needed to help
you select all OS Images), clicking Delete Selected, and confirming the deletion. The
OS Image is deleted and is no longer shown in the list of available OS Images on the
Operating Systems page.
Adding OS Images
To add an OS Image to the system for use, you must add the OS Image and assign it to a
server or server group.
2. Enter the Name of the OS Image for client support (use only letters, numbers, dashes,
spaces, the @ character, and periods).
Operating Systems 13
3. 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\OSimages).
4. (Optional) Enter a Description.
5. Enter the Version.
6. Select the OS Class.
7. Select the Device Class.
8. Select the 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 - 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 the Private
Mode on the OS Image, select the No Cache (Private Mode) option
· Shared Mode - The mode 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 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.
9. (Volatile Cache (Shared Mode) 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).
10.Click Next to open the Assign to a Server Group page.
1. In the Servers of Default Group list, select the servers that will be assigned the OS
Image.
2. Click Add.
3. Click Finish. The OS Image is added to the list of available OS Images on the
Operating Systems page and can now be streamed.
Editing OS Images
With Wyse WSM you can easily edit operating system settings, including the OS Images
and servers assigned to the operating system.
To edit OS Image settings:
Note
You must turn off all streaming clients before editing an OS Image.
1. On the Operating Systems page, click the Name link of the operating system you want
to edit. The OS Image Details page opens.
Operating Systems 15
Note
The File Name is shown.
Note
The OS Image ID is shown.
7. Select the Mode for the OS Image ID (either No Cache (Private Mode), Persistent
Cache (Shared Mode), or Volatile Cache (Shared Mode)).
Note
No Cache (Private Mode), Persistent Cache (Shared Mode), or Volatile
Cache (Shared Mode) are the three operating system options in which OS
Images can be delivered to the device.
Private Mode is 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 that you will 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 the Private Mode on the OS
Image, select the No Cache (Private Mode) option.
Shared Mode is the mode in which a single OS Image is shared between
multiple devices. The original OS Image is in read-only mode. That is, any
16 Chapter 3
changes made by any user on any device are not added to the base image.
For each device, a separate file is created in the Write Cache directory which
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.
8. (Volatile Cache (Shared Mode) 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).
9. (Optional) Click the Add a New OS Image link to open the Add OS Image page (for
details on adding an OS Image, refer to "Adding OS Images").
10.(Optional) Click the Start Patch Process for this OS Image link to open the Update
OS Image page (for details on updating an OS Image, refer to "Updating an OS
Image").
11. (Optional) Click the Delete this OS Image link to delete the OS Image.
12.(Optional) Click the Change Server/Server Group Assignment link to open the
Assign Server Groups For OS Image page (for details on changing a server group
assignment, refer to "Assigning an OS Image to a Server Group").
13.(Optional) Click a Name link the Server Groups Hosting area to edit the Server Group
associated with the OS Image (for details on editing a server group, refer to "Creating
and Managing Server Groups").
14.(Optional) Click a Name link in the Servers Streaming area to edit the Server
associated with the OS Image (for details on editing a server, refer to "Editing
Servers").
15.(Optional) Click the Release Lock link to reset the lock on the server.
Note
Wyse 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
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
Operating Systems 17
16.You can view the details about the hierarchy of an OS Image in the Hierarchy area.
17.After editing the settings, click Save Changes. The OS Image is modified and can be
viewed in the list of available OS Images on the Operating Systems page.
2. In the All Server Groups list, select the server group to which you want to assign the
OS Image; if you want to assign the image to a server or servers in the Default server
group, select Default.
3. Click Add. The server group or Default server group is added to the Assigned Server
Groups list.
4. Add the OS Image to the server group you selected or to servers in the Default server
group.
• The server group you selected - Click Next and then click Finish in the message box
that tells you to which server group or groups the OS image was assigned.
• Servers in the Default group - Click Next. A list of servers in the Default server group
appears in the Assign Server Groups For OS Image window. In the Servers of Default
Group list, select the servers to which you want to assign the OS Image. Then click
Add, and click Finish.
Note
If you have installed and are editing an Edge Server, you must also complete
the following:
On the server details page of the Edge Server, click the To be Scheduled
link in the Status column to open the Schedule Content page, select the date
and time you want the server to start the content distribution, and then click
Schedule. Until the content become available on the Edge server, the
18 Chapter 3
content will not be available to Users (completion of the process will show a
Status of Ready on the Edge Server Details page).
Applications Page
Clicking the Applications link from any functional area opens the Applications page. This
page allows you to view and manage the Wyse WSM Application Images and Application
Licenses that are available. It also allows you to easily display the Application Images and
Application Licenses you want by using the filtering feature.
Although the Applications page shows you all of the Application Images and Application
Licenses available on the Wyse WSM system, you can use the following guidelines to
view the Application Images and Application Licenses you want:
Note
You can use the Filter Application Images By filter or the Filter Application
Licenses By filter or both (one at a time).
Note
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.
• Click a Name link in the Application Licenses area to edit the Application License (for
details on editing an Application License, refer to "Editing Application Licenses").
• Delete an Application License by selecting the check box next to its name in the
Application Licenses area (you can use Select All or Deselect All as needed to help
you select all Application Licenses), clicking Delete Selected, and then confirming the
deletion.
Note
You can also delete an Application License by using the Delete this
Application License link on the Application License Details page.
Applications 23
1. 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).
2. Enter the Name of the Application Image for client support (use only letters, numbers,
dashes, spaces, the @ character, and periods).
3. (Optional) Enter a Description.
4. Enter the Version.
5. 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 into 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).
6. 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 into
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 appears saying that the application is mandatory and cannot be
unsubscribed).
7. Click Next to open the Assign to a Server page.
24 Chapter 4
In the All Server Groups list, select the server group you want to add the application to:
• Default server group - Select Default, click Add, and then click Next to open the
Assign to a Server page (see Step 3).
• User-created server group - Select the name of the server group (or groups), click
Add, click Next to open the Assign to a Server window, and then click Finish.
1. In the Servers of Default Group list, select the servers that will be assigned the
Application Image.
2. Click Add.
3. Click Finish. The Application Image is added to the list of available Application Images
on the Operating Systems page and can now be streamed.
After an Application Image is added, it is available to be used by an Application License
(for example, an update) and assigned to a User Group.
Applications 25
Note
The File Name, Application Image ID, and File ID are shown.
7. (Optional) Click the Add an Application License for this Image link to open the Add
Application License page (for details on adding an Application License, refer to "Adding
Application Licenses").
Note
For convenience, the Add an Application License for this Image link also
appears on the bottom of the Application Image Details page.
8. (Optional) Click the Add a Patch for this Application Image link to open the Updating
Application Image page (for details on adding an Application Image, refer to "Updating
an Application Image").
9. (Optional) Click the Add a New Application Image link to open the Add Application
Image page (for details on adding an Application Image, refer to "Adding Application
Images").
10.(Optional) Click the Delete this Application Image link to delete the Application
Image.
Note
Before you can delete an Application Image, it must be unassigned from a
server. You cannot delete an Application Image that is assigned to a server.
11. (Optional) Click the Change Server/Server Group Assignment link to open the
Assign Server Groups For App Image page (for details on changing a server
assignment, refer to "Assigning Application Images to Server Groups").
12.(Optional) Click a Name link in the Servers Streaming area to edit the Server
associated with the Application Image (for details on editing a server, refer to "Editing
Servers")
13.(Options) 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
"Creating and Managing Server Groups").
14.(Optional) Click a Name link in the Application Licenses Using area to edit the
Application Licenses associated with the Application Image (for details on editing an
Application License, refer to "Editing Application Licenses").
15.After editing the Application Image settings, click Save Changes. The Application
Image is modified and can be viewed in the list of available Application Images on the
Applications page.
Applications 27
2. In the All Server Groups list, select the server group to which you want to assign the
Application Image; if you want to assign the image to a server or servers in the Default
server group, select Default.
3. Click Add. The server group or Default server group is added to the Assigned Server
Groups list.
4. Add the Application Image to the server group you selected or to servers in the Default
server group.
• The server group you selected - Click Next and then click Finish in the message
box that tells you to which server group or groups the Application Image was
assigned.
• Servers in the Default group - Click Next. A list of servers in the Default server
group appears in Assign Server Groups For App Image window. In the Servers of
Default Group list, select the servers to which you want to assign the OS Image.
Then click Add, and click Finish.
Note
If you have installed and are editing an Edge Server, you must also complete
the following:
On the server details page of the Edge Server, click the To be Scheduled
link in the Status column to open the Schedule Content page, select the date
and time you want the Application Image to become available, and then click
Schedule (until the time the Application Image is copied to Edge Server, the
Status will be displayed as Copy in Progress on the Edge Server Details
page). Until the content become available on the Edge server, the content
will not be available to Users (completion of the process will display a Status
of Ready on the Edge Server Details page).
28 Chapter 4
2. Enter the Name of the Application License you want to add (use only letters, numbers,
dashes, spaces, the @ character, and periods).
3. Click the Select an Application Image link, and on the Select an Application Image
page, select the Application Image you want to assign to the application in the list; then
click Done to return to the Add Application License page.
Applications 29
4. 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.
5. Select a Duration option (either a custom amount or Unlimited). If you select a custom
amount, enter the number of Days.
6. Select a Maximum Concurrent Sessions option (either a custom amount or Unlimited).
If you select a custom amount, enter the number of Sessions.
7. Click Next to open the Assign to a Group page.
1. In the All Groups list, select the User Group you want to assign to the Application
License.
2. Click Add to move the group to the Assigned Groups list.
Note
You can use Add and Remove to move as many groups as you want to (and
from) the Assigned Groups list.
3. Click Finish. The Application License is added to the list of available Application
Licenses on the Applications page.
30 Chapter 4
Note
After an Application License is added, it is available to be used by an
Application Image and assigned to a user group.
2. Enter s Name for the application if you want to change the name.
Note
The Application Image and Sessions per User are shown.
3. Select a Duration option (either a custom amount or Unlimited). If you select a custom
amount, enter the number of Days.
4. Select a Maximum Concurrent Sessions option (either a custom amount or Unlimited).
If you select a custom amount, enter the number of Sessions.
5. (Optional) Click the Add a New Application License link to open the Add Application
License page (for details on adding an Application License, refer to "Adding Application
Licenses").
6. (Optional) Click the Delete this Application License link to delete the Application
License.
7. (Optional) Click the Change Group Assignment link to open the Assign User Groups
For Application page (for details on changing a server assignment, refer to "Assigning
Groups for an Application License").
Applications 31
8. (Optional) Click a Name link in the Assigned Groups area to edit the User Groups
associated with the Application (for details on editing a user group, refer to "Editing
User Groups").
9. After editing the Application settings, click Save Changes. The Application License is
updated and can be viewed in the list of available Application Licenses on the
Applications page.
2. Select the User group you want to assign to the Application License in the All Groups
list.
3. Use Add to move the user group to the Assigned Groups list.
Note
You can use Add and Remove to move as many user groups as you want to
(and from) the Assigned Groups list.
1. Select the servers you want to assign to the server group in the Servers of Default
Group list.
2. Click Add to move the servers to the Assigned Servers list.
3. Click Finish. The Server Group is added to the list of Server Groups on the Server
Groups page.
On the Server Group Details page, you can do the following tasks:
• Change the name and description of a server group – Enter a new Name, enter a
Description, and click Save Changes.
• Assign a server to the server group – Click Change Server Assignment. The
Assign Servers For Group window appears. In the Servers of Default Group list, select
the server you want to add to the group. Then click Add and click Done.
Note
If you want to move a server from one user-created server group to another,
first move the server to the Default group. Then open Server Group Details
page of the server group to which you want to move the server, click Change
Server Assignment, and move the server from the Default group to your
user-created server group.
Server Groups 37
• Remove a server from the server group – Click Change Server Assignment. In the
Assign Servers For Group window, select the Server in the Assigned Servers list. Then
click Remove and click Done to move the server to the Default group.
Note
For information on adding servers by using the installation procedures in the
Installation Guide: Wyse WSMTM, refer to "Adding Servers by Using the
Installation Procedures."
Servers Page
To see the complete list of installed servers, go to the Server Groups page and click the
View All Servers. The Servers page opens. This page allows you to view and manage the
Wyse WSM servers that are available. It also allows you to easily display the servers you
want by using the filtering feature.
38 Chapter 5
Although the Servers page shows you all of the servers available on the Wyse 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.
• Server Group - Server group that the sever belongs to.
• OS Image - Name of the OS Image to which the server is assigned. Use the OS Image
Select link to select the OS Image you want.
• Application Image - Name of the Application Image to which the server is assigned.
Use the Application Image Select link to select the Application Image you want.
• Status - Status of the server (all, Up, or Down).
After entering your criteria, click Filter to view the results. You can then select the servers
you want, and begin performing your tasks.
Use the following guidelines to perform available tasks on the Servers page:
• For information on adding servers by using the installation procedures in the
Installation Guide: Wyse WSMTM, refer to "Adding Servers by Using the Installation
Procedures."
• Click a Name link in the Servers area to edit the server (for details on editing a server,
refer to "Editing Servers").
• Delete a server by selecting 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 to help you select
all servers), clicking Delete Selected, and then confirming the deletion. The server is
deleted and is no longer shown in the list of available servers on the Servers page.
Note
You can also delete a Server by using the Delete this Server link on the
Server Details page.
Server Groups 39
Note
If 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.
Editing Servers
With Wyse WSM you can easily edit server settings including the licenses, operating
systems, and applications assigned to the server.
To edit server settings:
1. On the Servers page, click the Name of the server you want to edit to open the Server
Details page.
Note
The Name and Type of server are shown. For example, Core Server (or
Streaming for an Edge Server) can be shown as the Type for the server you
are editing.
4. Enter the Streaming Directory containing your OS Images and Application Images
(before editing the server Streaming Directory settings, you must stop all of the server
services; after all server editing is complete, be sure to start all of the server services).
Note
The Status of server is shown.
5. (Optional) Click Manage Server to open a Remote Desktop Connection dialog box
which allows you to specify the server that you want to access and manage.
Note
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.
Note
For Windows 2000 users only - The Manage Server command button looks
for the mstsc.exe in the %systemroot%\system32 folder. However, when
you load the terminal service client on Windows 2000, the mstsc.exe is
loaded at C:\Progam files\Remote desktop by default. To make the Manage
Server command button execute correctly, you must copy mstsc.exe and
mstscax.dll to the %systemroot%\system32 folder.
6. (Optional) Click the Delete this Server link to delete the server.
Note
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.
7. (Optional) Click a Service Name link in the Services area to manage that service
associated with the server (for details on managing a Service, refer to "Managing
Services for a Server").
Note
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
Server Groups 41
8. (Optional) 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.
9. (Optional) Click the View Log link to view the service log you want in the Services
area.
10.(Optional, for servers in Default server groups only) Click the Change OS Image
Assignment link to open the Assign OS Images For Server page (for details on
changing an OS Image assignment, refer to "Assigning OS Images for a Server").
11. (Optional, for servers in Default server groups only) Click a Name link in the OS
Images Streamed By area to edit the OS Image associated with the server (for details
on editing an OS Image, refer to "Editing OS Images").
Caution
Wyse 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 in
the OS Image Details page allows you to reset the lock on the OS Image and
make the modifications you want.
12.(Optional, for servers in Default server groups only) Click the Change Application
Image Assignment link to open the Assign Application Images For Server page (for
details on changing an Application Image assignment, refer to "Assigning Application
Images for a Server").
13.(Optional, for servers in Default server groups only) Click a Name link in the Application
Images Streamed By area to edit the Application Images associated with the server
(for details on editing an Application Image, refer to "Editing Application Images").
14.(Optional, for servers in Default server groups only) Click the View Log link to view the
Application Image log you want in the Application Images Streamed By area.
15.After editing the Server settings, click Save Changes. The server is modified and can
be viewed in the list of available servers on the Servers page.
Note
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.
42 Chapter 5
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.
Note
You can use Add and Remove to move as many OS Images as you want to
(and from) the Assigned OS Images list (removing an OS Image in the
Administrator Console does not remove the OS Image from the Edge Server
Streaming Directory; it is when you un-assign an OS Image from an Edge
Server, that the OS Image is removed from the Edge Server Streaming
Directory).
Note
If you have installed and are editing an Edge Server, you must also complete
the following:
On the server details page of the Edge Server, click the To be Scheduled
link in the Status column to open the Schedule Content page, select the date
and time you want the server to start the content distribution, and then click
Schedule (until the time the OS Image is copied to Edge Server, the Status
will be displayed as Copy in Progress on the Edge Server Details page). Until
the content become available on the Edge server, the content will not be
available to Users (completion of the process will show a Status of Ready on
the Edge Server Details page).
Note
You can use Add and Remove to move as many Application Images as you
want to (and from) the Assigned Application Images list (removing an
Application Image in the Administrator Console does not remove the
Application Image from the Edge Server Streaming Directory).
Note
If you have installed and are editing an Edge Server, you must also complete
the following:
On the server details page of the Edge Server, click the To be Scheduled
link in the Status column to open the Schedule Content page, select the date
and time you want the Application Image to become available, and then click
Schedule (until the time the Application Image is copied to Edge Server, the
Status will be displayed as Copy in Progress on the Edge Server Details
page). Until the content become available on the Edge server, the content
will not be available to Users (completion of the process will show a Status of
Ready on the Edge Server Details page).
Server Groups 45
The Device Groups page lists all Device Groups. You can filter the list with the following
criteria:
• Name Contains - Name of a Device Group (use only letters, numbers, dashes,
spaces, the @ character, and periods).
• Server Group - Name of the Server Group that is assigned to Device Group. Use the
Server Group Select link to select the Server Group
48 Chapter 6
• OS Image - Name of the OS Image that is assigned to Device Group. Use the OS
Image Select link to select the OS Image.
After entering your criteria, click Filter to view the results.
Use the following guidelines to perform available tasks on the User Groups page:
• Click on Add Device Group Link to open the Add Device Group Wizard (for details on
adding a Device Group, refer to “Adding a Device Group”).
• Click on All Devices to view all devices within WSM by clicking on All Devices link.
• Delete Device Group(s) by selecting the check box next to the name of the Device
Group you want in the Device Groups area (you can use Select All or Deselect All as
needed to help you select all Device Groups except for default), clicking Delete
Selected, and then confirming the deletion. The Device Group is deleted and is no
longer shown on the Device Groups page. You cannot delete the Default device group.
Caution
Deleting a Device Group moves the devices in the group to the Default
device group. It also clears the image assignment from devices that belong
to the device group being deleted. Deleting a Device Group is irreversible.
By default, Load Balanced is the boot selection mode for devices 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. For
more information about Load Balancing, see "Load Balancing."
Devices and device templates in user-created device groups cannot update their
attributes, including image assignments, on their respective pages. Because these
attributes are shared among all devices in the same device group, they can only be
changed on the Device Group Details page.
1. Enter or select a Name, Description, Device Class, and Connection Type. If you
select Mobile from the Connection Type menu, you are asked to select a Force
Provision option (either Enabled or Disabled).
2. Click Next.
50 Chapter 6
Which type of device group you assign determines which choices you make next:
• User-created device group – Select a user-created device group and click Next. The
device is assigned the OS Image and streaming server assigned to the device group.
Moreover, the device is assigned the device class and connection type of the device
group. Click Finish. You go to the Device Group Details page.
• Default device group – Select the Default device group and click Next to open the
Assign an OS Image page (see Step 3).
1. Select the OS Image you want to assign to the Default device group.
2. Click Next to open the Select Streaming Server page.
Device Groups 51
Step 4: Selecting a Server to Stream the OS Image (Default device group only)
1. Select a server on the list. The list contains servers from the Default server group that
can stream the OS Image you selected in Step 3.
2. Click Finish.
1. In the All Devices from Group list, select the devices you want to reassign to a different
device group.
2. Click Add to move the devices to the Selected Devices list.
3. Click Next to open the Select a Device Group page.
Device Groups 53
Which type of device group you assign determines which choices you make next:
• User-created device group – Select a user-created device group and click Next. The
device is assigned the OS Image and streaming server assigned to the device group.
Moreover, the device is assigned the device class and connection type of the device
group. Click Finish. You go to the Device Group Details page.
• Default device group – Select the Default device group and click Next to open the
Assign an OS Image page.
Step 4: Selecting a Server to Stream the OS Image (Default device group only)
1. Select a server on the list. The list contains servers from the Default server group that
can stream the OS Image you selected in Step 3.
2. Click Finish.
3. Select the command (Reboot, Shut down, or Wake on LAN) you want to send to the
devices.
4. Send the command now or schedule the command to be sent later:
· Send the command now - Enter a Time Delay in seconds (the default is 300).
· Send the command later - Click the schedule link to open the Schedule Device
Command page. Then select a date, enter a time, and click Schedule.
5. Click Send Command.
Note
To abort previously scheduled commands, select the devices with
commands you want to abort and click Abort Command. In the message
confirming the removal of the commands, click OK.
Managing Devices
With Wyse WSM you can easily add, edit, and delete devices by using the Devices page.
Note
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.
Devices Page
To open the Devices page, start on the Device Groups pages and click the All Devices
link. The Devices page allows you to view and manage network devices and mobile
devices. It also allows you to easily display the devices you want by using the filtering
feature. The names of network devices appear on the top half of the page; the names of
mobile devices appear on the bottom half.
Device Groups 55
Note
You can also delete a device by using the Delete this Device link on the
Device Details page.
56 Chapter 6
Note
You can only configure a device to run an existing OS image. For information
on creating an OS image, refer to "Adding OS Images."
To add a device to the system for use, you must add the device, assign an OS Image to be
streamed to the device, and then select a streaming server to stream the OS Image.
2. Enter the Name of the device for client support (use only letters, numbers, dashes,
spaces, the @ character, and periods).
3. (Optional) Enter a Description for the device.
4. Enter the MAC Address of the device.
Device Groups 57
5. Select the Device Class you want to assign to the device (for example, Wyse V00).
6. (For Active Directory integration only) Select the Active Directory Organizational Unit
(for example, wsm.com/CN=Computers).
7. Select a Connection Type (either Network or Mobile Disconnected). If you select
Mobile Disconnected to add a mobile device, select a Force Provision option for the
device:
· Disabled: In this type of provision, the user decides when to provision the mobile
device with an OS image. (To initiate the provisioning, the user can right-click the
WSM Client icon in the system tray and select Provision Disk.)
· Enabled: In this type of provision, the mobile device connects to the server
automatically each time it boots up. If a new or updated OS image is detected for
this device, the image is provisioned automatically to the mobile device.
8. Click Next to open the Assign OS Image page.
Note
Provisioning does not start automatically when you add or configure a device
for Mobile mode. A device’s provisioning status is reflected on its Device
Details page.
Which type of device group you assign the device to determines whether you can make a
choice for an OS Image and streaming server for the device:
• User-created device group – Select a user-created device group and click Next. The
device is assigned the OS Image and streaming server assigned to the device group.
Moreover, the device is also assigned the device class and connection type of the
device group. Click Finish. You go to the Device Details page.
• Default device group – Select the Default device group and click Next to open the
Assign an OS Image page.
58 Chapter 6
Step 4: Selecting a Server to Stream the OS Image (Default device group only)
1. Select a server on the list. The list contains servers from the Default server group that
can stream the OS Image you selected in Step 3.
2. Click Finish.
Warning
If you added a mobile device, do not use the device while the provisioning
process is being completed. A message box tells 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 to Windows. Applications will be
provisioned automatically. Users must not disconnect from the network or
use their devices for any purpose while applications are being provisioned.
Editing Devices
While editing a device, you can modify the settings of the device.
Note
Editing a device instructions are for any device, including network devices,
mobile devices, and the Reference Device.
Note
You can select more than one device to configure at the same time by
selecting check boxes next to the names of the devices and clicking
Configure Devices.
Device Groups 59
Note
The IP Address and Reference Device of the device are shown.
5. Select the Device Class you want to assign to the device (this option is only available
for devices assigned to the Default device group).
6. Select the Connection Type you want to assign to the device (either Network or
Mobile Disconnected). If you select Mobile Disconnected, also select a Force
Provision option (either Disabled or Enabled - this option is only available for devices
assigned to the Default device group.)
7. Select the Boot Selection Mode for the device (First Disk, First Available, or User
Select). (This option is only available for devices assigned to the Default device
group.)
Note
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
60 Chapter 6
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.
Note
(For Active Directory integration only) The Active Directory Organizational
Unit is shown (for example, wsm.com/CN=Computers).
8. Depending on whether or not you want to schedule a device command, select or clear
the Schedule Device Command check box (for more information on scheduling a
device command, refer to "Sending Commands to Devices").
9. View the Status of the device shown as one of the following:
• 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.
10.(Optional) Click the Add a New Device link to open the Add Device page (for details
on adding a new device, refer to "Adding Network and Mobile Devices").
11. (Optional) Click the Delete this Device link to delete the device.
12.(Optional) Click the Make this a Reference Device link to make the device the
Reference Device.
Note
The Make this a Reference Device link does not appear if the device you
are editing is currently designated as the Reference Device.
A Reference Device is used as a default device when updating an OS Image,
as described in "Updating an OS Image."
Device Groups 61
13.(Optional, devices in the 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.
Note
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."
14.(Optional, devices in the 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 (for details on adding an OS Image, refer to "Adding an OS Image for a
Device").
15.(Optional, devices in the 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 (for details on updating an OS Image, refer to "Updating an OS Image
Assignment for a Device").
16.(Optional, devices in the 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).
Note
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.
Caution
Using the Reset Device State link will cause all changes made to the OS
Image by this device to be lost.
17.After you have completed setting the device configurations, click Save Changes. The
device is modified and can be viewed in the list of available devices on the Devices
page.
62 Chapter 6
Step 3: Selecting a server to stream the OS Image (Default device group only)
1. Select a server on the list. The list contains servers from the Default server group that
can stream the OS Image you selected in Step 3.
2. Click Finish. You go to the Device Details page.
Note
Only one OS image can be added for a mobile device.
Note
You can clear the schedule for the command you just scheduled by clicking
the now link in the Send Device Command page.
3. Click Send Command to send the command (according to your Time Delay or
schedule) and return to the Devices page.
Note
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.
7 User Groups
This chapter describes how to perform routine User Group management tasks on the
Wyse WSM system. It provides information on managing User Groups, both with and
without Active Directory integration.
Although the User Groups page shows you all of the User Groups available on the Wyse
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.
Use the following guidelines to perform available tasks on the User Groups page:
• (Without Active Directory Integration Only) Click the Add User Group link to open the
Add User Group page (for details on adding a User Group, refer to "Adding User
Groups").
• (With Active Directory Integration Only) Click the Import a Groups from Active
Directory link to open the Import Group from Active Directory page (for details on
adding a User Group using this link, refer to "Adding User Groups with Active Directory
Integration").
• Click a Name link in the Groups area to edit the User Group (for details on editing a
User Group, refer to "Editing User Groups").
• You can enable or disable a User Group by using the Enable or Disable link in the
Status list for the User Group.
• Delete a User Group by selecting the check box next to the name of the User Group
you want in the Groups area (you can use Select All or Deselect All as needed to
help you select all User Groups), clicking Delete Selected, and then confirming the
deletion. The User Group is deleted and is no longer shown in the list of available User
Groups on the User Groups page.
User Groups 69
Note
You can also delete a User Group by using the Delete this Group link on the
User Groups 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.
If Wyse WSM is integrated with Active Directory, deleting a User Group by
using the Wyse WSM removes the User Group and Users of that group from
the Wyse WSM system only; it does not remove the User Group or Users of
that group from the Active Directory.
Note
You can only add a member (User) to an existing User Group. If Wyse 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."
Note
If no User exists in the system, "Step 2: Assigning Users," will not appear.
If no Application License exists in the system, "Step 3: Assigning Application
Licenses," will not appear.
2. Enter the Name of the User Group (use only letters, numbers, dashes, spaces, the @
character, and periods).
3. Click Next to open the Assign Users page.
1. Select the User you want to assign to the User Group in the All Users list.
2. Use Add to move the User to the Assigned Users list.
Note
You can use Add and Remove to move as many Users as you want to (and
from) the Assigned Users list.
1. Select the application license you want to assign to the User Group in the All
Application Licenses list.
User Groups 71
2. Use Add to move the application licenses to the Assigned Application Licenses list.
Note
You can use Add and Remove to move as many applications as you want to
(and from) the Assigned Application Licenses list.
3. Click Finish to return to the User Group Details page. The User Group is added to the
list of available User Groups on the User Groups page and can now subscribe,
activate, and run Wyse WSM operating systems and applications for that User Group.
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 Groups you selected
are added to the Wyse WSM Group Name list.
Note
Users of these imported groups will automatically be added to the Wyse
WSM User Name list on the Users page.
72 Chapter 7
8. (Optional) Click a Name link in the Application Licenses Assigned To area to edit the
Application License associated with the User Group (for details on editing an
application license, refer to "Editing Application Licenses").
9. (Optional) Click the Change Application License Assignment link to open the
Assign Application Licenses For Group page (for details on changing an application
license assignment, refer to "Assigning Application Licenses for User Groups").
10.After editing the User Group settings, click Save Changes. The User Group is
modified and can be viewed in the list of available User Groups on the User Groups
page.
Note
You can click Add and Remove to move as many Users as you want to (and
from) the Assigned Users list.
Note
The Name of the User Group is shown.
Note
You can use Add and Remove to move as many Application Licenses as
you want to (and from) the Assigned Application Licenses list.
Note
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 Active Directory will automatically
update in Wyse WSM according to the settings you configure as described in "Active
Directory Configuration."
78 Chapter 8
Although the Users page shows you all of the Users available on the Wyse 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.
Although the Users page shows you all of the Users available on the Wyse 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.
Use the following guidelines to perform available tasks on the Users page:
• Click the Add User link to open the Add User page (for details on adding a User, refer
to "Adding Users without Active Directory Integration").
• Click a Name link in the Users area to edit the User (for details on editing a User, refer
to "Editing Users without Active Directory Integration").
• Enable or disable a User by using the Enable or Disable link in the Status list.
• Delete a User by selecting 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 to help you select all
Users), clicking Delete Selected, and then confirming the deletion. The User is deleted
and is no longer shown in the list of available Users on the Users page.
Note
You can also delete a User by using the Delete this User link on the User
Details page.
Note
You can only add a User to an existing User Group. For information on
creating a User Group, refer to "Adding User Groups."
To add a User to the system for use, you must add the User, and then assign the User to a
User Group.
80 Chapter 8
Note
If no User Group exists in the system, then "Step 2: Assigning to a Group,"
will not be included and the User Status will be Disabled.
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.
4. Click Next to open the Assign to a Group page.
1. Select the User Group you want to assign to the User in the All Groups list.
2. Use Add to move the User Group to the Assigned Groups list.
Note
You can use Add and Remove to move as many User Groups as you want
to (and from) the Assigned Groups list.
3. Click Finish to return to the Users Details page. The User is added to the list of
available Users on the User page and can now subscribe, activate, and run Wyse
Users 81
WSM operating systems and applications for the User Groups to which you have
assigned that User.
Application License Details page (for details on editing an Application License, refer to
"Editing Application Licenses").
10.(Optional) Click the Change Group Assignment link to open the Assign User Groups
For User page (for details on changing an OS Image assignment, refer to "Assigning
User Groups for a User without Active Directory Integration").
11. After editing the User settings, click Save Changes. The User is modified and can be
viewed in the list of available Users on the Users page.
1. Select the User Group you want to assign to the User in the All Groups list.
2. Use Add to move the User Group to the Assigned Groups list.
Note
You can use Add and Remove to move as many User Groups as you want
to (and from) the Assigned Groups list.
Note
This setting will not take effect until the service (that is logging) is restarted.
• Enter the Log File size Limit (in kilobytes) up to a maximum of 5120 KB.
Note
This setting will not take effect until the service (that is logging) is restarted. If
the log exceeds the maximum limit, then a .bak file is created.
Note
If there are many streaming servers upon which synchronization must occur,
it is recommended that this option be set to Asynchronously.
Note
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.
System Settings 87
• Depending on whether or not you want to enable the DHCP Proxy Service, select or
clear the Enable DHCP Proxy Service check box. If checked, the DHCP Proxy
Service will be enabled and managed by the WSM Admin Service. If checked, be sure
to shut down other DHCP Proxy Services that may be running on all the core and edge
servers.
Note
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.
• Depending on whether or not you want to enable the TFTP Service, select or clear the
Enable TFTP Service check box. If checked, the TFTP Service will be enabled and
managed by the WSM Admin Service. If checked, be sure to shut down other TFTP
Services that may be running on all the core and edge servers.
Note
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.
• Select the Core Server Configuration that will be designated as the WSM Core Server.
There is only one server designated as the core server in a WSM system. The core
server is the server that has file access to the Image Repository. This repository is
used for content distribution and to add images to the system.
Caution
Extreme caution must be used when changing the designated WSM Core
Server, as you must ensure that the Master Repository information is also
located on the selected Core Server machine.
• Use Reset to clear any changes you made (before clicking Update System Settings).
• After you have finished configuring the settings, be sure to click Update System
Settings to save your settings.
Quick-Links on the System Settings page include:
• Change Admin Password - Allows you to change your Administrator password. This
link is also located on the Overview page (see "Changing Your 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 Wyse WSM
system (see "Importing Server Licenses").
• Active Directory Configuration - Allows you to enable or disable the Active Directory
(see "Active Directory Configuration").
• Database Configuration - Allows you to access and edit the database configuration of
a Core Server or Edge Server (see "Database Configuration").
• Move Server - Allows you to move a WSM server from one WSM installation to
another. (see "Moving Servers").
• 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 create virtual machines by using the
Wyse WSM in conjunction with VMWare Virtual Center software (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").
System Settings 89
To import a Server License, click Browse to find and select the license.txt file that
was provided to you by Wyse, and then click Import Server License to import the license
and view the valid dates of the license.
Note
To select or clear the Enable Active Directory check box, all Devices, Users,
and User Groups must be deleted from the Wyse WSM system.
Note
If you select the Enable Active Directory check box, the Active Directory
Configuration page expands.
90 Chapter 9
To configure Active Directory integration with Wyse WSM, use the following guidelines:
• Enter the Synchronizing Polling Frequency time (number of seconds between
synchronizing the members of user groups between the Active Directory and the Wyse
WSM database; the default is 600 seconds, however, you can turn off the feature by
setting the time to 0).
• Depending on whether or not you want to enable SSL, select or clear the Enable SSL
Connection check box (for information on using Active Directory integration with SSL,
refer to "About Using Active Directory Integration").
Note
If you enable SSL, be sure to import a certificate to allow SSL connections to
be established with Active Directory as described in "Importing Certificates to
Allow SSL Connections with Active Directory."
• (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").
• Use Reset to clear any changes you made (before clicking Update Active Directory
Settings).
• After you have finished configuring the settings, be sure to click Update Active
Directory Settings to save your settings.
Note
You can verify that the Active Directory integration is correctly configured
when you can successfully import groups and users from the Active
Directory.
Database Configuration
During the installation and configuration of a Core Server or Edge Server installation,
database configuration settings are made through an installation wizard. After the Wyse
WSM system installation is complete, you can then edit the database configurations by
using the Database Configuration page.
Caution
Changing configuration parameters from the Database Configuration page
will attempt to change database configuration for all active WSM servers in
your system.
Note
For information on the initial installation and configuration settings of a
database, refer to the procedures in the Installation Guide: Wyse WSMTM..
System Settings 91
Note
When editing the database configuration of an existing WSM Core Server, all
of the WSM related services (except for the WSM Administration Service) in
the Core Server as well as in an Edge Server must first be stopped. For
information on stopping services from within the Administrator Console, refer
to "Managing Services for a Server."
Moving Servers
While on the System Settings page, you can click the Move Server link to open and use
the Move Server page to move a WSM server from one WSM installation to another.
Before you move a server be aware of the following guidelines and requirements:
• While you can move any WSM edge server from one WSM installation to another, you
can move the WSM core server from one installation to another only if the WSM core
server is the only server in the installation (that is you must move all existing edge
servers before you can move the core server).
• All WSM services on a WSM server that you are moving must be shut down before you
move the server.
• Both WSM installations involved in the server move (the installation you are moving a
WSM server from and the installation you are moving the WSM server to) must have
the same product version.
• To move one server to another server (for example an edge server to another core
server), both servers must have the same WSM product version.
• After the WSM server has been moved, it becomes an edge server of the WSM
installation to which it was moved.
• Registry entries for a moved WSM server are updated accordingly.
92 Chapter 9
• A server entry for the moved WSM server is created on the WSM installation WSMDB
to where the server is moved.
• The server entry for a moved WSM server is deleted on WSM installation WSDB from
where the server is moved. If a server cannot be deleted, a warning message is
provided so that an administrator can delete the server entry from the UI of the WSM
installation from where the WSM server is moved.
• After the WSM server has been moved, an administrator must either restart/stop the
SQL Server Service in the WSM installation from where the WSM server has been
moved or restart the Admin Service on the server where the move occurred (this is to
ensure that all the DB connections to the database are reset to the new connections).
Note that this is a manual step.
• After the WSM server has been moved, an administrator must restart all of the WSM
services on that server. Note that this is a manual step.
To move a server:
1. Select the IP address of the server you want to move in the Server to Move IP box.
2. Enter the IP address you want to move the server to in the Move to Server IP box.
3. Enter the username and password of the remote server (the server with the IP address
you entered in the Move to Server IP box).
4. Click Move Server.
Note
Be sure the Device Template you want to use exists in the system (see
"Adding Device Templates") before importing devices.
Note
The Description, Device Class, and Boot Mode for the Device Template are
shown.
3. Click Import Devices to import the devices into the system. The devices are shown in
the list of available devices on the Devices page.
94 Chapter 9
Note
You can only add a device template to an existing operating system. For
information on adding an operating system, refer to "Adding OS Images."
3. Enter the Name of the Device Template for client support (use only letters, numbers,
dashes, spaces, the @ character, and periods).
4. (Optional) Enter a Description for the device template.
5. Select the Device Class you want to assign to the device template (for example, Wyse
V00).
6. Select a Connection Type (either Network or Mobile Disconnected). If you select
Mobile Disconnected, you must select a Force Provision option.
7. Depending on whether or not you want to specify a subnet range, select or clear the
Specify a Subnet Range check box (if you enable Specify a Subnet Range, you
System Settings 95
must enter the Subnet Address and Subnet Mask). Be aware that you cannot have
two device templates with the same Subnet Address.
Note
Only one device template without a subnet mask can be added to the WSM
system.
8. (For Active Directory integration only) Select the Active Directory Organizational Unit
(for example, WSM1.COM/OU=Marketing Computers).
9. Click Next to open the Assign a Device Group page.
Which type of device group you assign determines whether you can make a choice for an
OS Image and streaming server for the device template:
• User-created device group - Select a user-created device group and click Next. The
device is assigned the OS Image and streaming server assigned to the device group
you selected. Click Finish. You go 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.
Step 4: Selecting a Server to Stream the OS Image - Device Template (Default device
group only)
Note
Some fields on the Device Template details page can be edited only if you
are working with a Default device group template.
Note
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.
Note
(For Active Directory integration only) The Active Directory Organizational
Unit is shown (for example, wsm.com/CN=Computers).
• Image Name (user-created device group templates only) - List the name of the OS
Image.
• Specify a subnet range - If you want to specify a subnet range, select the Specify a
Subnet Range check box, and then enter the Subnet Address and Subnet Mask.
• Status - Select Enabled or Disabled. For a device template to be Enabled you must
assign an OS Image to it.
After you have completed setting the device template configurations, click Save Changes.
The device template is modified and can be viewed in the list of available device templates
on the Device Templates page.
98 Chapter 9
Which type of device group you select determines whether you can make a choice for an
OS Image and streaming server for the device template:
• User-created device group - Select a user-created device group and click Next. The
device is assigned the OS Image and streaming server assigned to the device group
you selected. Click Finish. You go 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.
Step 3: Selecting a Server to Stream the OS Image - Device Template (Default device
group only)
2. Select the Streaming Server you want to assign to the device template.
3. Click Finish to return to the Device Template Details page.
Although the Active Directory Domains page shows you all of the Domains managed by
the Wyse 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.
Use the following guidelines to perform available tasks on the Active Directory Domains
page:
• Click the Add Domain link to open the Add Domain page (for details on adding a
Domain, refer to "Adding Domains").
• Use the Import Certificate link to import a certificate to allow SSL connections to be
established with Active Directory (for details on importing a certificate, refer to
"Importing Certificates to Allow SSL Connections 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.
• Click a Name link in the Domains area to edit the Domain (for details on editing a
domain, refer to "Editing Domains").
• Click the Enable or Disable links (in the Status list) for the domain you want, to enable
or disable a Domain.
• You can delete a domain by selecting 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 to
help you select all domains), clicking Delete Selected. and then confirming the
deletion. You can also delete a domain by using the Delete this domain link on the
Active Directory Domain Details page. The domain is deleted and is no longer shown in
the list of available domains on the Active Directory Domains page.
Note
Domains can be only deleted from a WSM Server if all of the groups
imported from that domain are deleted from the WSM system as described in
"User Groups Page."
• You can delete a certificate by selecting 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 to help you select all certificates), clicking Delete Selected. and then
confirming the deletion. The certificate is deleted and is no longer shown in the list of
available certificates on the Active Directory Domains page.
102 Chapter 9
Adding Domains
To add a Domain:
1. On the Active Directory Domains page, click the Add Domain link to open the 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.
System Settings 103
Editing Domains
To edit a Domain:
1. 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.
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.
5. Enter the Password.
Note
The connection status is shown.
10.(Optional) Click the Import Groups from this Domain link to open the Import Groups
from Active Directory page (for details on importing groups from the domain, refer to
"Importing Groups from a Domain").
11. (Optional) Click a Name link in the Contains These Groups area to edit the User
Groups associated with the Domain (for details on editing a User Group, refer to
"Editing User Groups with Active Directory Integration").
12.(Optional) Click the Add a device OU link to open the Add Device Organizational Unit
page (for details on adding a device organizational unit where new devices can be
added to the Active Directory, refer to "Adding a Device Organizational Unit").
13.You can delete a device organizational unit managed by the Active Directory Domain
by selecting 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 to help you select all device organizational units), clicking
Delete Selected. and then confirming 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.
Note
Device OUs can only be deleted if the Device OU does not contain computer
accounts for the devices added in the WSM system.
14.After editing the Active Directory Domain Details settings, click Save Changes. The
Domain is modified and can be viewed in the list of available Domains on the Active
Directory Domains page.
Note
Users of these imported groups will automatically be added to the Wyse
WSM User Name list on the Users Groups Details page.
Note
The Device OU added is available for you to use when adding and editing
devices and device templates.
106 Chapter 9
Note
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).
Note
In future use after adding a virtual center, you can click on a virtual center link
to open the Virtual Center Details page and view its details.
2. Click the Add Virtual Center link to open the Adding Virtual Center page.
Note
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.
Note
If the virtual center is only accessible by SSL (default), an administrator must
be sure to import an SSL certificate as stated earlier.
• 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. Select the template you want from the list of All Unassigned Templates, click Add to
assign the template, and then click Finish.
Note
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.
System Settings 109
3. Click Create Virtual Machine to open the Create Virtual Machine page.
Note
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.
Note
After you click Create, the virtual machines are added to the list of virtual
machines on the Virtual Machines page.
Note
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.
10 Reports
This chapter contains information and instructions to help you generate various reports on
your Wyse WSM environment.
Clicking the Reports link from any functional area main page opens the Reports page.
The Reports page allows you to view and use all of the reports that are supported.
• Client - Report includes detailed information on all the unique clients that have
connected to the server.
• License Usage - Report includes detailed information on all current application usage.
• Standard Usage - Report includes detailed information on past application usage for
all Users and User Groups.
• Activation - Report includes detailed information on all application activations and
deactivations.
• Subscription - Report includes detailed information on which users are subscribed to
which applications.
Note
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.
Client Report
To create a Client Report:
1. On the Reports page, click Client Report to open the Client Reports page.
2. Select the report criteria you want by using the following guidelines:
• Enter a user group name or a user name.
• 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.
2. Select the report criteria you want by using the following guidelines:
• Enter a user group name or a user name.
• 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 113
2. Select the report criteria you want by using the following guidelines:
• Enter a user name or a user group name.
• 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
To create an Activation Report:
1. On the Reports page, click Activation Report to open the Activation Reports page.
2. Select the report criteria you want by using the following guidelines:
• Enter a user name or a user group name.
• 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.
114 Chapter 10
Subscription Report
To create a Subscription Report:
1. On the Reports page, click Subscription Report to open the Subscriptions Report
page.
2. Select the report criteria you want by using the following guidelines:
• Enter a user name or a user group name.
• 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.
11 Load Balancing
This chapter provides information on the load balancing feature of the Wyse WSM. It
explains how load balancing works and how to set up your system for load balancing.
Note
In previous versions of Wyse 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.
Note
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 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).
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.
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 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.
Note
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 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 (in cases of upgrades from WSM 1.1 to
WSM 1.2, the first device that is recognized from the database and added to
the WSM system after the WSM installation is updated to be 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, 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 before you can use the Start patch process
for this OS Image link (on the OS Image Details page) 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).
120 Chapter 12
Note
The updating process is designed so that it does not interfere with your
current Wyse WSM environment. During the updating process your Wyse
WSM environment continues to stream the currently active OS Image. Your
Wyse WSM environment will stream the new updated OS Image only after
the updated OS Image is ready and you schedule it for deployment.
Note
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).
Note
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.
3. (Optional) If you receive an error message that the OS Image cannot be assigned to
the Reference Device, the OS Image Details page will display the Assign Patch to the
Reference Device link. This error will display if there is no Reference Device or if the
Reference Device is full (there is a limit of four OS Images that can be assigned to a
Reference Device).
Figure 108 OS Image Details page - Assign Patch to the Reference Device
If there is no Reference Device, you must denote the Reference Device you want to
use as described in "Editing Devices," and then return to this 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 full, you must remove one of the OS Images and add the OS
Image patch as described in "Editing Devices," and then return to this 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."
122 Chapter 12
Note
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.
Note
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).
Note
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.
2. On the OS Image Details page (for the OS Image you want to update), click the
Schedule Patch Deployment Date link to open the Schedule Patch Deployment Date
page.
3. Select the date and time you want the server to start the content distribution and
deploy the patch, and then click Schedule. Until the patch becomes available on the
servers now running the currently active OS Image, the patch will not be available to
users.
Note
You can reschedule a scheduled patch by using the Reschedule Patch
Deployment Date link on the OS Image Details page (for the OS Image you
want to update).
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
which have been previously assigned the OS Image. Once this delta file copy is
completed, the process on the Edge server 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 Edge servers.
Note
On the OS Image Details page, you will see that the old OS Image (for
example, Base Image) has a Status of Retired, while the new updated OS
Image (Base Image 2) has a Status of Active. As the devices using the OS
Image in your Wyse WSM are rebooted, they will begin using the new
updated OS Image.
124 Chapter 12
Note
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 reboots the Network Device. Once the Network
Device reboots, it will begin using the newly patched OS image.
Note
If you need to prepare an Application Image update for use as a patch, refer
to "Preparing an Application Image Update."
Updating OS Images and Application Images 125
Note
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.
Note
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.
126 Chapter 12
Note
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, you see the UPT application window. It is 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.
128 Chapter 13
Note
Alternatively, one can boot the machine with an OS image using Wyse 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.
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.
Note
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 called New File.wup.
4. Select the file, click Rename, and enter a new name for the UniPlat disk file.
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 Wyse 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 131
Note
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.
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.
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.
Note
You cannot back up from a Windows session that is currently streamed from
Wyse 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.
132 Chapter 13
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.
Note
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).
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).
134 Chapter 13
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 platform 2’s Windows session (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 platform 2’s
Windows session 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.
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.
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 Wyse 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.
Optionally, boot up each platform from the corresponding OS image using Wyse 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.
138 Chapter 13
With PF3 booted from the local hard disk, install WSM Client on PF3. Use WSM’s 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 Wyse WSM technology.
Note
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.
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.
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 WSM’s virtual disk capturing tool to capture the OS image.
Windows will install the new HAL and reboot the computer. After the reboot, you may be
prompted to install newly found hardware drivers.