Академический Документы
Профессиональный Документы
Культура Документы
Issue: 040609
PN: 883875-01 Rev. F
Copyright Notices
© 2009, Wyse Technology Inc. All rights reserved.
This manual and the software and firmware described in it are copyrighted. You may not reproduce, transmit,
transcribe, store in a retrieval system, or translate into any language or computer language, in any form or by any
means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, any part of this publication
without express written permission.
Trademarks
The Wyse logo and Wyse are trademarks of Wyse Technology Inc. Other product names mentioned herein are for
identification purposes only and may be trademarks and/or registered trademarks of their respective companies.
Specifications subject to change without notice.
Ordering Information
For availability, pricing, and ordering information in the United States and Canada, call 1-800-GET-WYSE
(1-800-438-9973) or visit us at http://www.wyse.com. In all other countries, contact your sales representative.
Contents
1 Introduction 1
About this Guide 1
Organization of this Guide 1
Wyse Technical Support 2
Links to Related Documentation and Services 2
2 Overview 3
Introducing Wyse WSM 3
Wyse WSM Key Components 4
Wyse WSM Services 4
General Overview of the Wyse WSM Setup Process 5
8 System Maintenance 43
Passwords 43
Logs 43
Backup Recovery 44
System Monitoring 44
10 Troubleshooting 49
Verifying if the Database Is Operational and Configured Correctly 49
Verifying that WSM Services are Running 49
Verifying if the ODBC is Operational and Configured Properly 50
Audio Problems in the Streaming Environment 50
Unable to Capture an OS Image after Cancelling the Capture Process 51
Error when Enabling Active Directory for the First Time 51
Error when Installing WSM Client on Windows XP 51
Network Devices are Unable to be Created in the Active Directory 51
HTTP Error:404 /admin/ not found RequestURL=/admin/ powered by jetty 52
Verifying the Status of the Wyse WSM Service Files 52
Reconfiguring an OS Image 53
Hostname and IP Address Changes 55
Uninstalling Wyse WSM Software 55
A Error Codes 57
Figures 69
Tables 71
1 Introduction
Wyse WSMTM is an operating system and application distribution and streaming
technology that provides a cost-effective method to rapidly deploy and manage operating
systems and applications to a large pool of users. It provides core functions for streaming
operating systems and applications to subscribers.
Wyse WSM main features include:
• Patented streaming operating system and application technology.
• Anti-piracy protection of operating system and application code.
• Usage metrics collection.
• Licensing policies to enforce all operating system and application usage.
• Scalability and built-in fail-over support.
• Chapter 4, "Installing and Configuring the WSM Core Server," provides the detailed
procedures you must complete to install the Wyse WSM Core Server.
• Chapter 5, "Starting Wyse WSM for the First Time," provides the detailed procedures
you must complete to start Wyse WSM for the first time.
• Chapter 6, "Installing and Configuring the WSM Client," provides the detailed
procedures you must complete to install the Wyse WSM Client.
• Chapter 7, "Installing and Configuring a WSM Edge Server," provides detailed
procedures you must complete to install a Wyse WSM Edge Server.
• Chapter 8, "System Maintenance,", contains information to help you successfully
maintain the Wyse WSM system.
• Chapter 9, "Upgrading Wyse WSM," provides the steps you need to upgrade your
Wyse WSM system from a previous version.
• Chapter 10, "Troubleshooting," contains information and help on installation, setup,
conflicts, and general troubleshooting.
• Appendix A, "Error Codes," includes the most common errors that you may encounter
in a displayed message box or in a log file.
• Appendix B, "Booting Wyse WSM on PXE and Non-PXE Networks," describes how to
boot Wyse WSM clients on networks that don’t support PXE or that have not been
modified to support PXE or standard DHCP.
• Appendix C, "Installing Your Own SQL Server," provides instructions for installing the
supported SQL Servers.
Administrators Guide: Wyse WSMTM is intended for administrators of the Wyse WSM
system. It provides information, and detailed system command and parameter
configurations, to help administrators design and manage a Wyse WSM environment. It
also explains how to use Wyse WSM, manage the availability of software applications for
distribution to subscribers, manage application subscription licenses, install and configure
published applications, provide subscriber profile and billing information for efficient
application usage tracking, and control subscriber access to the Wyse WSM system.
Users Guide: Wyse WSMTM is intended for users of the Wyse WSM Client system. It
provides detailed instructions on using the Wyse WSM Client to manage the applications
available to users from a network server.
Wyse Thin Computing Software is available on the Wyse Web site at:
http://www.wyse.com/products/software.
2 Overview
This chapter provides an overview of the Wyse WSM system. It explains the key
components and services of the system so you can get a feel for how the system works
before you install its various components.
Pre-Installation Checklist
Before you start begin installing, make sure you have met the requirements on this
checklist:
• Obtain and configure all hardware, as necessary.
• Obtain administrator rights on all systems to begin the server installations.
• Install Windows 2000 Server or Windows 2003 Server systems on all server machines.
Make sure all systems are up to date with current Microsoft service packs, patches,
and updates.
• Download and install Microsoft Internet Explorer (IE) 6.0 or later on all machines.
• Obtain a Server License File from Wyse (provided to you by e-mail) for the system (see
"Server License Files").
• Install the Microsoft SQL Server (see "Installing Microsoft SQL Server Using the WSM
Prerequisites File"). Make sure the server is running before you begin installing WSM.
8 Chapter 3
• If needed, download and install the latest Microsoft SQL Server Service Pack (see
"Installing the Latest Microsoft SQL Server Service Pack").
• If you are planning to integrate Active Directory with Wyse WSM (see Administrators
Guide: Wyse WSMTM), make sure that the Core Server and the Active Directory Server
are part of the Domain before the administrator of the local system begins installing
WSM Core Server.
Hardware Requirements
Each machine must meet or exceed the minimum system requirements shown in Table 1.
Note
These requirements may vary due to application and operating system sizes.
Software Requirements
Besides the Wyse WSM software, you must install the software shown in Table 2 on each
server. Installing the most up-to-date version of each software package is highly
recommended.
Note
If you plan to integrate Active Directory with Wyse WSM without SSL, you
must ensure that the WSM OS Authentication service is running with the
credentials of an Active Directory user with privileges to create and manage
computer accounts (for example, a member of the Account Operator group).
For more information about integrating Active Directory with Wyse WSM
without SSL, see Administrators Guide: Wyse WSMTM.
• Wyse WSM: To administer the Wyse WSM provider environment, a default account
named admin must be created in the system. This account enables you to log on for
the first time and to configure the system. You can change the default password
(admin) after you log in for the first time.
Note
Ensure that these ports are open for proper communication between servers.
If you have a firewall enabled on any server where Wyse WSM is installed,
you must also ensure that the following ports are configured as follows:
Content Distribution Service Client Port (Default Port: 10802)
NetBIOS Name Service (Default Port: 137)
TFTP Service (Default Port: 69)
10 Chapter 3
Domain Names
It is important to use DNS entries for mapping IPs to servers. Although you can use IP
addresses, it will make scaling and system changes more difficult. This entry point DNS
will be used to allow the client to talk to the server farm. The DNS name that is used
should be entered into the machine name when configuring the core server (as described
in "Installing and Configuring the WSM Core Server"). Also, the client port configured in
that section will be the port used by the clients and will need to be configured in both the
firewall and load-balancing switch. Wyse WSM requires a minimum of two public IP
addresses with DNS entries.
Caution
During the WSM Prerequisites InstallShield Wizard installation, do not close
the Ready to Install the Program window (which continues to show in the
background during installation) and do not click Install more than once.
Doing either of these will prevent a successful installation.
Note
For instructions on installing your own SQL Server, refer to "Installing Your
Own SQL Server."
Preparing for Installation 11
DHCP
Option
Number Purpose DHCP Option Value for the Thin Client
Note
Be sure you have completed all pre-installation requirements as described in
"Preparing for Installation" before you begin installing the WSM Core Server.
3. After reading the agreement, select the I accept the terms in the license agreement
option and click Next to open the Destination Folder window.
Note
The Streaming Directory is where the Write Cache files, OS Images, and
Application Images will be stored.
Installing and Configuring the WSM Core Server 15
6. Select the This is a new WSM installation option to install the Core Server.
7. Click Next to open the Database Server window.
Note
Do not use special characters for the Database Name.
Warning
If you will be installing a WSM Edge Server in the future, be sure to
remember the information you enter in this Database Server window, as you
will need this information when you install the WSM Edge Server.
• Click Next to open the Database Server and Authentication Method window.
Caution
Do not interrupt the installation.
During the installation, the WSM Server Configuration dialog box opens.
11. Select the Network Adapter to use, select the IP Address list to use, and then click OK
to save the configurations, close the WSM Server Configuration dialog box, and open
the Installation Wizard Completed window.
Note
Be sure you have successfully installed the WSM Core Server before you
complete the procedures in this section.
Note
You can skip any of the configurations in this section and complete the Wyse
WSM system configurations according to your environment needs by
following the appropriate procedures in the Administrators Guide: Wyse
WSMTM.
2. Enter the Admin Username (default is admin) and Password (default is admin) and
click Login to open the Import Server License page.
3. Click Browse to find and select the license.txt file that was provided to you by
Wyse, and then click Import Server License to import the license and view the licence
details.
4. Click Next to open the Configure Active Directory page.
5. Depending on whether or not you want to enable Active Directory integration with
Wyse WSM, select or clear the Enable Active Directory check box.
Note
For information to help you decide whether or not you want to integrate
Active Directory with your Wyse WSM system, refer to the Administrators
Guide: Wyse WSMTM.
If you need to configure or re-configure the Active Directory in the future,
refer to the Administrators Guide: Wyse WSMTM.
If you do not select the Enable Active Directory check box, click Finish to view the
System Overview Congratulations page, and continue with step 15.
If you select the Enable Active Directory check box, the Configure Active Directory
page expands.
Starting Wyse WSM for the First Time 21
6. Enter the Group Synchronizing Polling Frequency time (number of seconds between
synchronizing the members of user groups between the Active Directory and the Wyse
WSM database; the default is 600 seconds, but you can turn off the feature by setting
the time to 0).
7. Click Next to open the Add Domain page.
Note
A user with privileges to create and manage computer accounts is needed
for Active Directory integration. By default, members of the group named
Account Operators or Domain Administrators have the privilege to create and
maintain computers accounts.
Note
The Domain is added to the list of available domains on the Active Directory
Domains page.
22 Chapter 5
13.Select the User Groups you want by using the following guidelines:
• Enter the group name you want in the Group Name Contains text box (use only
letters, numbers, dashes, spaces, the @ character, and periods).
• Enter the LDAP Context Root.
• Enter the Max Results limit (zero to the limit of all Users in Active Directory).
• After entering your filter criteria, click Filter to view the results.
• Scroll through the list of Groups and select the check boxes for the Group Names
you want.
14.After selecting the Groups you want, click Finish to view the System Overview
Configurations page.
Note
Users of these imported groups will automatically be added to the Wyse
WSM User Name list on the Users page.
Note
The Domains link only appears in the Category area if Active Directory is
enabled.
15.After completing the Configuration Wizard, you can view the Core Server Details page
to see that the Core Server Services are successfully running by clicking the Servers
link in the Category list on the System Overview page, and then clicking the Name link
of the Core Server.
Now that the Core Server services are running, you can continue to configure the rest of
the Wyse WSM system according to your environment needs by following the appropriate
procedures in the Administrators Guide: Wyse WSMTM.
24 Chapter 5
Note
Be sure you have completed all pre-installation requirements as described in
"Preparing for Installation" before you begin installing the WSM Client.
Note
The Reference Device is the device from which you initially capture the OS
image; subsequently, the Reference Device is used for applying patches to
this OS image. The Reference Deice has a hard disk and a locally installed
Windows operating system. After an OS image is captured from the
Reference Device, other devices can be configured to boot from this OS
image file in shared mode. Because other devices will boot from the
Reference Device’s OS image, this image should be configured to meet the
needs of all devices that will boot from it. The best practice is to reserve the
Reference Device for use by the Administrator and not assign it to end users.
This way, the Administrator can easily deploy and test OS images by using
the Reference Device.
3. After reading the agreement, select the I accept the terms in the license agreement
option and click Next to open the Customer Information window.
4. Enter the User Name and Organization and click Next to open the Destination Folder
window.
28 Chapter 6
Note
During installation, Windows Logo testing messages may appear in front of
or behind the wizard windows. If these messages appear, click Continue
Anyway to continue the installation.
Installing and Configuring the WSM Client 29
7. Select the Install the software automatically (Recommended) option and click Next
to begin installation.
After the software is installed, the Completing the Found New Hardware Wizard
window appears.
30 Chapter 6
8. Click Finish to close the wizard and open the WSM Client Config Wizard.
9. Use the following guidelines to complete the WSM Client Config Wizard:
• Enter the Authentication Server Info IP address to be used by the WSM OS
Authentication Service (this address is the same as the Core Server). The default
Port information is automatically entered.
• Enter the Imaging Server Info IP address to be used by the WSM OS Streaming
Service (this address is the same as the Authentication Server Info IP Address).
The default Port information is automatically entered.
• Enter the Web Server Info Port address, if necessary. This is the port on which the
Web server runs. The default is entered automatically.
• Enter the IOS Streaming Max Packet Size. This is the maximum data size of OS
streaming packets sent from the server to the client; the default value is 1420. If
your network, to meet encryption or other types of requirements, requires a custom
MTU (Maximum Transmission Unit) for IP packets, you can adjust this number to
restrict the size of the packets. Set the value to 1370 to yield an MTU of 1398 (the
maximum OS streaming data size [1370], plus the UDP header size [8], plus the IP
Installing and Configuring the WSM Client 31
header size [20]). Matching this value to the OS Streaming Max Packet Size setting
on WSM servers is recommended.
Note
The default Client Info IP Address and Port, Subnet Mask, and Gateway IP
Address are automatically entered.
• Click OK to close the WSM Client Config Wizard and open the InstallShield Wizard
Completed window.
Note
Be sure you have all peripherals you want to use (for example, keyboard,
mouse, printers and so on) connected before you begin capturing the OS
Image to the Core Server.
Figure 31 OSMVDiskImage.exe
2. Double-click the OSMVDiskImage.exe to open the WSM VDisk Image Creation Utility
window.
3. Enter the Virtual disk size in MB (if you are running in shared mode, the maximum
virtual disk size is 32 GB).
4. Enter a Disk name.
5. (Optional) Enter a Description for the disk.
6. Depending on whether or not you want to integrate WSM with Active Directory, select
or clear the Enable Active Directory Integration check box.
7. Click OK to begin building the virtual disk.
Installing and Configuring the WSM Client 33
After building is complete, the Done message appears in the WSM VDisk Image
Creation Utility window.
Note
Whichever mode is in use, the OS image itself remains the same; it is not
modified in any way. The Network/Mobile modes apply to devices, not OS
images. The same OS image can be used by Network mode devices and
Mobile mode devices simultaneously. By choosing a mode, you are deciding
how the device receives the OS image — over the network or cached to the
local disk.
34 Chapter 6
Note
When users start the WSM Client device for the first time, they may
encounter a WSM Client Login in progress message. This will occur for all
users who log in and are not yet registered in the WSM Database.
Completing the procedures in this section prevents these users from
encountering these messages.
Note
When adding the OS Image, be sure to select the No Cache (Private Mode)
option for Mode.
2. Reboot the machine to which you installed the WSM Client and use the following
guidelines for the DOS prompts:
• You must enter the client name.
• Entering a description is optional.
• Be sure you select the vdisk you just added in "Capturing an OS Image to the Core
Server."
• Press any key to restart the system.
Note
Upon system restart, close the WSM Client Login in progress message that
appears (right-click the minimized application in the taskbar and select Close
to close the window).
3. Upon system restart, the System Settings Change message appears; when this
message appears, click No to close the window. Note that this is a good time to clean
up or customize your environment (for example, selecting the desktop background,
and so on, prior to sharing the OS Image on multiple client machines).
Installing and Configuring the WSM Client 35
4. After you have completed customizing your environment, shut down the client
machine.
5. After the client machine has shut down, log in to the Administrator Console.
6. Edit the OS Image you created in "Capturing an OS Image to the Core Server," so that
either the Persistent Cache (Shared Mode) or Volatile Cache (Shared Mode) option
is selected for the Mode.
After completing the procedures in this section, the OS Image is ready to be used by
multiple client machines. For more information, see Administrators Guide: Wyse WSMTM.
Note
In the future, if you want to copy or move an OS Image from one streaming
server (for example, a lab environment) to another streaming server (for
example, a production server), or if you want to change the current Active
Directory integration mode (Enabled or Disabled), then that OS Image must
be re-configured as described in "Reconfiguring an OS Image."
Warning
Provisioning a mobile device erases all data currently on the device’s hard
disk. Make sure mobile users understand that they will lose data currently on
the hard disk when they provision an up-to-date OS image from the server.
36 Chapter 6
Note
In order to download an OS image for Mobile mode, the mobile device
requires at least twice the amount of disk space as the OS image plus
100MB. For example, if the OS image being provisioned is 6GB, the mobile
device requires at least 12GB+100MB of free disk space to accommodate
the image.
See Administrators Guide: Wyse WSMTM for more for information about converting a
device from Network mode (the default) to Mobile mode.
7 Installing and Configuring a WSM
Edge Server
This chapter provides the detailed procedures you must complete to install a Wyse WSM
Edge Server. Although you can select custom installation configurations during the
installation, it is recommended that you use the default configurations.
Note
Be sure you have completed all pre-installation requirements as described in
"Preparing for Installation" and installed WSM Core Server before you begin
installing a WSM Edge Server.
3. After reading the agreement, select the I accept the terms in the license agreement
option and click Next to open the Destination Folder window.
Note
The Streaming Directory is where the Write Cache files, OS Images, and
Application Images will be stored.
Installing and Configuring a WSM Edge Server 39
6. Select the This server belongs to the following WSM installation option and enter
the Core server IP address to install the Edge Server and connect to the Core Server.
7. Click Next to open the Database Server and Authentication Method window.
Note
If the WSM Edge Server cannot connect to the Core Server Registry (for
example, the remote registry is disabled on the Core Server for security
reasons), then a warning message appears.
Click OK to close the Warning message and open the Database Server window.
Note
Do not use special characters for the Database Name.
Caution
Do not interrupt the installation.
During the installation, the WSM Server Configuration dialog box opens.
10.Select the Network Adapter to use, select the IP Address list to use, and then click OK
to save the configurations, close the WSM Server Configuration dialog box, and open
the Installation Wizard Completed window.
Passwords
Wyse WSM uses three sets of username and password credentials. The following list
describes how to change the passwords:
Note
It is strongly recommend that administrators implement a password policy.
• Wyse WSM Database – If you need to change the database user account password
(default is wsmdb@123), you must change the account password on the database
itself and then restart the Administrator service (Administrator Console). The next time
you log into the Administrator Console, the Database Configuration page displays
allowing you to edit the database configurations (including the user account password).
After changing the database configurations you must restart all services on all servers
for the changes to take effect.
• Windows Service – If you change the windows system password on the administrator
user, which is used to start the Wyse WSM services servers, then you will need to
update the services. This is can be accomplished under the Management Console for
Windows Services by selecting the Log On tab and changing the account password.
• Wyse WSM – To change the administrator account password for the Wyse WSM
provider environment, log in to the Wyse WSM as an administrator, select Change
Password, and use the Change Password page.
Logs
Errors pertaining to the Wyse WSM and related components are logged to the System
Event Viewer. Descriptions of errors regarding licensing, server connections, database
problems, configuration errors, and so on, are available through the System Event Viewer.
Wyse WSM stores log files in the database and on your file system. These have a set size
and will rollover when they become too large (making the system self-maintaining). The
default size of these logs is 10,000,000 bytes.
The Profile Log is a log of communication statistics on the server side giving information
on how long request queue is at a given time, the effective bandwidth amount of requests
received so far, and the type of requests received so far. It is located at the
/server-install/log folder with the name in the format of:
prof-<erver-id>-<random>.txt. Format: Date [universal-time]
[start-time] [delta-time] [request-count] [S/M] [CLIENT/CACHE]
[IP address] [app-id] [fileID,pageID] (S=single, M=multiple)
44 Chapter 8
Backup Recovery
It is highly recommended that all system data is backed up for recovery purposes. Wyse
WSM stores all system, topology, user, application, and usage data within the database.
Since all information is contained in the Wyse WSM Database, backing up this database
enables you to recover all system data. Use standard backup procedures common to
database servers. For fault-tolerant systems, it is also recommended to replicate the
database for fail-over.
System Monitoring
Wyse WSM comes with built-in monitoring tools that can be used to watch and check the
health of the system. When an administrator logs into the Administrator Console, the
System Overview page is shown. The System Overview page allows you to quickly view
important summary information for each functional area of the Wyse WSM system. It also
provides links to all of the functional areas so you can easily perform many of the
Administrator duties that are required to run and maintain your Wyse WSM environment.
For example, the Overview page allows you to quickly see that a server requires your
attention (since Wyse WSM has noted this server problem in the Requires Attention area
and provides you a link to the Server functional area page that you need to address the
message).
For fault-tolerant provider systems, it is recommended to have system hardware
monitoring in place. Third-party system monitoring software can be configured to watch
and report on system status, including:
• Ping availability and response times
• % CPU Utilization
• Memory Available
• Bandwidth consumption
The following list provides a few examples of system monitoring software:
• Tivoli by IBM
• Big Brother by Quest software
• Nagios by Nagios
• Performance Monitor by Microsoft
9 Upgrading Wyse WSM
This chapter provides the steps you need to complete to upgrade your Wyse WSM system
from a previous version.
Note
Application Images do not need to be upgraded. All Application Images of
previous Wyse WSM versions are compatible with the latest Wyse WSM
version.
Caution
It is recommended that you select the existing database settings and not
change them at this time. If you need to change the location of the database,
you must completely uninstall your current Wyse WSM installation (see
"Uninstalling Wyse WSM Software"), and then install the new Wyse WSM
version on the same machine according to the instructions in this guide.
Caution
During the upgrade installation for the servers, a message may appear
informing you that a reboot is needed after the existing WSM components
have been removed. Do not reboot the servers at this time. Click OK to close
the message.
Note
After the upgrade installation is successfully completed, a message will
appear prompting you to reboot before the new WSM components can be
used from the servers. You must reboot the servers at that time.
3. Click Finish to close the InstallShield Wizard and open the WSM Client Installer
Information message prompting you to restart your system so that configuration
changes made to WSM Client can take effect.
Solution: Obtain winhttp.dll and copy it into the Windows system32 folder. After you
have done this, begin installing the WSM Client as described in "System Maintenance."
Note
To start or stop a service, right-click on the service file (for example, WSM
Administration Web Service) and select Start or Restart (to start the service)
or select Stop (to stop the service).
Reconfiguring an OS Image
If you want to copy or move an OS Image from one Core Server (for example, a lab
environment) to another Core Server (for example, a production server), then that OS
Image must first be re-configured.
Similarly, if you want to change the current Active Directory integration mode (Enabled or
Disabled), then that OS Image must be re-configured.
Note
These re-configuration procedures must be done on a client machine that
has been booted from this OS Image in No Cache (Private Mode). For
procedures on adding an OS Image and assigning it to a server, refer to the
Administrators Guide: Wyse WSMTM.
To re-configure an OS Image:
1. (Only required if you want to change the current Active Directory integration from
Disabled to Enabled) Join the OS Image to the domain you specified (when you added
the OS Image using the Administrator Console as described in "Capturing an OS
Image to the Core Server") by using the Microsoft procedures for joining a domain,
reboot the system, and continue with Step 2.
2. Login as a user with administrator privileges on the client machine and locate the
WSMClientPostConfig.exe (default location is C:\Program Files\Wyse\WSM\os).
54 Chapter 10
Figure 55 WSMClientPostConfig.exe
Note
Some uninstallations may require a reboot.
56 Chapter 10
Note
You cannot create a bootstrap partition on a bootstrap partition previously
created by the WSM Bootstrap Utility. Even if you specify the size of the
partition to be the required 8MB, Windows in most cases rounds the size of
the partition to less than 8MB, rendering the bootstrap invalid. To create a
new bootstrap partition, either erase the old partition and allocate 8MB or
more to it, or create a new partition larger than 8MB.
After you start the utility, you see the WSM Bootstrap Utility dialog box.
Follow these steps to prepare a hard disk or flash drive for a WSM non-PXE bootstrap:
1. On the Available Disks drop-down list, choose a drive connected to the system.
Network drives and mapped drives are not listed.
2. On the Drive to Format drop-down list, choose which drive you want to format as the
drive for the WSM non-PXE bootstrap (if a hard disk has existing partitions, all
available partitions will be listed in the Drive to Format drop-down list).
After you choose a drive, the Drive Details section of the dialog box provides
information about the drive you selected. Review this information to make sure the
drive you selected is sufficient for the WSM non-PXE bootstrap:
· Type: Lists the type of drive you selected. Hard disks and flash drives are fixed.
· Format: Lists the format that the drive supports—FAT, FAT32, or NTFS.
· Capacity: Lists the storage capacity of the drive. The minimum capacity
requirement for a non-PXE boot partition is 8MB.
· Partition: Indicates whether the partition you selected is an active partition.
3. Click the Create button to begin creating a non-PXE bootstrap partition on the drive
you selected.
Booting Wyse WSM on PXE and Non-PXE Networks 63
Note
Even if the drive being partitioned is more than 8MB in size, if you select it as
the WSM non-PXE bootstrap drive, its size is reduced to 8MB and the
remaining capacity is wasted. However, you can reuse the wasted space by
creating another drive using Windows’ Disk Management Console.
2. Formats the drive with the FAT12 format, makes it Active (i.e., bootable), and installs
the WSM non-PXE bootstrap.
Warning
The partition will be repartitioned and reformatted. Any existing files on the
partition will be erased.
In the case of a raw disk with no existing partitions, clicking the Create button begins
creating a non-PXE bootstrap partition on the raw disk. The utility creates an 8MB partition
in FAT12 format, makes it bootable, and installs the non-PXE bootstrap file.
Note
Some BIOS do not work well with certain USB keys. Such BIOS may not be
able to read the USB key at all, or experience long delays when writing on
the USB key. If the BIOS fails to read the USB key, WSM non-PXE bootstrap
will not be able to run.
Note
Network configuration information is saved in permanent storage so that it
can be used on subsequent boot-ups. To erase previously entered network
configurations, press the G key on boot-up. Users will then be presented with
a G-key menu with one of the options displayed as “<option number>: Clear
previously saved network configurations and Login Server lists?”. Enter
<option number> and confirm the operation by typing “yes” when prompted.
C Installing Your Own SQL Server
In special cases of a large production environment, it is recommended that you install the
Database Server on a server machine that is separate from the Wyse WSM servers. WSM
supports three databases: SQL Server 2000, SQL Server 2005, and SQL Server 2005
Express. Make sure that your network is configured to allow all servers to communicate
with your database on the configured SQL port. All servers will authenticate with the
database using configured credentials. The following sections include instructions for
installing the supported jdatabases.
Caution
You should refer to the documentation provided by the database vendor for
complete installation instructions, performance enhancements, and setup.
Note
IMPORTANT: In most cases, you can install an SQL Server on the same
machine as the Wyse WSM servers for a single-server installation. To do so,
it is highly recommended that you use the WSM Prerequisites InstallShield
Wizard as described in "Installing Microsoft SQL Server Using the WSM
Prerequisites File."
Note
Verify that the database is configured to run in Mixed Mode for
authentication. Wyse WSM uses both ODBC and JDBC to communicate with
the database using SQL authentication. If Mixed Mode is not chosen, the
servers cannot communicate with the database. This setting is located under
the Security tab of the database properties labelled SQL Server and
Windows NT.
Caution
Make sure that the database is configured to run in Mixed Mode for
authentication. Wyse WSM uses both ODBC and JDBC to communicate with
the database using SQL authentication. If Mixed Mode is not chosen, the
Installing Your Own SQL Server 67
servers cannot communicate with the database. You can verify this setting by
looking under the Security tab of the database properties labeled SQL
Server and Windows NT.
14.Select the SQL Collations option button and Dictionary Order, Case-Insensitive, for
Use with 1252 Character Set; then click Next.
15.Clear both of the error usage and reporting boxes; then click Next.
16.Click Install to start the installation (it may take several minutes).
17.Click Next after all components have been installed and configured.
18.Review the installation summary and click Finish.
19.After installation is complete, be sure to enable the TCP/IP communication protocol for
the SQL Server by opening the SQL Server Configuration Manager and enabling the
protocol.
Note
If you plan to install the database on a separate server, install the SQL Server
Client Tools on the same machine that will host the WSM server software.
Note
If you are given the option to modify the Authentication Mode during service
pack installation, select Mixed Mode to allow the Wyse WSM Core Server
software to access the database.
68 Appendix C