wdm 4.7.1 install guide dec2008

Installation GuideWyse Device Manager™ Release 4.7.1

Issue: 121508PN: 883886-01 Rev. G

Copyright Notices© 2008, Wyse Technology Inc. All rights reserved.

This manual and the software and firmware described in it are copyrighted. You may not reproduce, transmit, transcribe, store in a retrieval system, or translate into any language or computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise, any part of this publication without express written permission.

End User License Agreement (“License”)A copy of the Wyse Technology End User License Agreement is included in the software and provided for your reference only. The License at http://www.wyse.com/license as of the purchase date is the controlling licensing agreement. By copying, using, or installing the software or the product, you agree to be bound by those terms.

TrademarksThe Wyse logo and Wyse are trademarks of Wyse Technology Inc. Other product names mentioned herein are for identification purposes only and may be trademarks and/or registered trademarks of their respective companies. Specifications subject to change without notice.

Restricted Rights LegendYou acknowledge that the Software is of U.S. origin. You agree to comply with all applicable international and national laws that apply to the Software, including the U.S. Export Administration Regulations, as well as end-user, end-use and country destination restrictions issued by U.S. and other governments. For additional information on exporting the Software, see http://www.microsoft.com/exporting.

Ordering InformationFor 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.

http://www.wyse.com/license

http://www.microsoft.com/exporting

http://www.wyse.com/

Contents

1 Introduction 1About this Guide 1

Organization of this Guide 2Wyse Technical Support 2

Links to Related Documentation and Services 2

2 Preparing for Installation 3Setting Up Your Environment to Use Wyse Device Manager Software 3

System Requirements 3Third-Party Software Requirements 4Port Requirements 6

Installing and Configuring WebDAV on IIS 6.0 8Changing the Isolation Level in IIS 6.0 8Installing WebDAV on IIS 6.0 10Configuring WebDAV on IIS 6.0 12Setting Up a Self-Signed Certificate on IIS 6.0 14

Installing Self SSL 15Creating a Certificate 17

Installing and Configuring WebDAV on IIS 7.0 20Installing the Desktop Experience Feature 20Installing IIS 7.0 22Installing the WebDAV Extension for IIS 7.0 24Configuring WebDAV and IIS 24

Enabling Basic Authentication 27Configuring Site-Level WebDAV Settings 28Configuring the Web.config File 31

Installing the Oracle Client 32

3 Installing Wyse Device Manager 39About Installing Wyse Device Manager Software 39Installing WDM Using the Typical Installation Option 40Installing WDM Using the Custom Installation Option 41Installing WDM 4.7 Enterprise Edition with a SQL Database 43Upgrading a WDM Installation 51Using the Windows Firewall: Windows 2003 Server SP2, Windows 2003 Server R2, and Windows XP SP2 Requirements 54Using an Oracle Database: Windows 2000 Server with SP4 and Windows 2000 Advanced Server with SP4 Requirements 54

Figures 55

Tables 57

iv Contents

This page intentionally blank.

Introduction 1

1 Introduction

Wyse Device ManagerTM (formerly Rapport) software is the premier enterprise solution for managing network intelligent devices simply, remotely, and securely. It enables IT professionals to easily organize, upgrade, control, and support thousands of WTOS, CE, Linux, or XPe devices across any LAN, WAN, or wireless network. The software uses HTTP/HTTPS communications and a component-based architecture to efficiently manage your network devices. It operates as a snap-in to the Microsoft Management Console (MMC) to offer an intuitive, simple, and powerful user interface.

Wyse Device Manager software allows you to:• Discover and then organize your devices into functional groups

Regardless of their physical or network location, Wyse Device Manager software gives you a powerful management tool to organize your devices according to the functional criteria that makes the most sense to your organization.

• Update your devices with new applications, images, and configurations• Schedule device updates

Schedule device updates immediately, at a predetermined time, or when your device next boots (provided it supports Pre-boot EXecution Environment, or PXE).

• Build and administer librariesBuild and administer a library of software, images, and configuration updates for distribution to specified device groups in your enterprise.

• View and modify device informationView and modify device information to generate useful log and device reports.

• Customize with complete controlWyse Device Manager scripting language gives you complete control to customize the software, images, and settings that you can distribute to your devices.

• Provide a secure communications environmentInstall and configure WebDAV on your Windows server to create a secure communications environment between components of WDM using HTTP or HTTPS protocol.

About this GuideThis guide is intended for administrators of the Wyse Device Manager system. It describes the Wyse Device Manager installation process for Windows servers. This guide provides the step-by-step instructions you need to install and configure a Wyse Device Manager environment. It also includes the requirements you must address before you begin the installation procedures.

This installation guide is intended for experienced network administrators and Information Technology professionals who have installed and configured Windows operating systems and applications.

2 Chapter 1

Organization of this GuideThis guide is organized as follows:• Chapter 2, "Preparing for Installation," contains hardware and software requirements

and the procedures you must complete to prepare the environment for the Wyse Device Manager installation.

• Chapter 3, "Installing Wyse Device Manager," provides the detailed procedures you must complete to install Wyse Device Manager.

Wyse Technical SupportTo access Wyse technical resources, visit http://support.wyse.com. If you still have questions, you can submit your questions using the Wyse Self-Service Center, or call Customer Support at 1-800-800-WYSE (toll free in U.S. and Canada). Hours of operation are from 6:00 am to 5:00 pm PST, Monday through Friday.

To access international support, visit http://www.wyse.com/global.

Links to Related Documentation and ServicesWyse Device Manager features can found in the Wyse Device Manager Datasheet. It is available on the Wyse Web site at:http://www.wyse.com/products/software/devicemanager/index.asp.

The Administrators Guide: Wyse Device ManagerTM is intended for administrators of the Wyse Device Manager system. It provides information, and detailed system command and parameter configurations, to help administrators design and manage a Wyse Device Manager environment.

Wyse Thin Computing Software is available on the Wyse Web site at:http://www.wyse.com/products/software.

http://support.wyse.com

http://www.wyse.com/products/software/

https://support.wyse.com/OA_HTML/jtflogin.jsp

http://www.wyse.com/products/software/devicemanager/index.asp

http://www.wyse.com/global

Preparing for Installation 3

2 Preparing for Installation

This section contains hardware and software requirements and the procedures you must complete to prepare the environment for the Wyse Device Manager installation.

Setting Up Your Environment to Use Wyse Device Manager SoftwareBefore installing the Wyse Device Manager software, ensure that your network and server meet the system, third-party, and port requirements.

Beginning with WDM release 4.7, you need to install WebDAV for Windows to provide a secure communications environment for the components of Wyse Device Manager.

NoteInstall WebDAV before you install the WDM software.WebDAV is already configured in Windows XP.

CautionFor XPe Devices Only: If you have an existing installation of XPe devices with the Write Filter enabled and you install Wyse Device Manager in production, after the device discovery process (which could be automated or administrator initiated) the XPe devices will automatically reboot to register with the new WDM Server without notifying you. Therefore, install Wyse Device Manager in your production environment at an appropriate time.

System RequirementsAny one of the following operating systems is required for WDM release 4.7.1:• Windows Server 2003• Windows Server 2003 SP2• Windows Server 2003 R2• Windows Server 2008• Windows XP Professional with SP2 or later

4 Chapter 2

Ensure that your system has the minimum system requirements shown in Table 1.

NoteThe actual free space required depends on the number and size of the packages you register as well as the number of devices you will be managing (the Wyse Device Manager Database size). This minimum space assumes the Wyse Device Manager Database and packages consume 500 MB.

Third-Party Software RequirementsWyse Device Manager software uses third-party software to operate properly. During installation, Wyse Device Manager software checks the system to determine whether the third-party components are present. If they are not, Wyse Device Manager indicates which components are missing. Some of the third-party software is included with the Wyse Device Manager software. The other software is available from your OS CD-ROM or from the network location for your system files (often grouped under the I386 folder).

NoteEnsure that no other applications requiring IIS are running on the server to which Wyse Device Manager is installed. Any conflicts between these applications could prevent normal Wyse Device Manager functioning.

Wyse Device Manager software uses the following third-party software:• Microsoft Data Access Components (MDAC) version 2.8 - Microsoft Data Access

Components (MDAC) is the key technology that enables Universal Data Access. Data-driven, client/server applications deployed over the Web or a LAN can use these components to integrate information from a variety of relational (SQL) and non-relational sources. These components include Microsoft ActiveX Data Objects (ADO), OLE DB, and Open Database Connectivity (ODBC).

NoteWyse Device Manager software requires MDAC 2.8. Wyse Device Manager installs MDAC 2.8 if it is not already present.

• Internet Information Services (IIS) - Microsoft’s Web Server and FIle Transfer Server required for communication between components of WDM and for file transfer.

• WebDAV - A set of extensions to the HTTP protocol required for HTTP- and HTTPS-based communication between WDM components.

Table 1 Required Hardware Configuration

Requirement Minimum Recommended

CPU 1GHz Intel or AMD X86 2.4 GHz Dual Core Intel or AMD X86

RAM 512 MB 2 GB

Minimum Free Space 500 MB 720 MB


• Microsoft Internet Explorer 5.5 - The MDAC installation requires Microsoft Internet Explorer (IE) 5.5 or later. In addition, IE 5.5 enables the Visual Basic components used by the Wyse Device Manager installation wizard and procedures included in the Administrators Guide: Wyse Device Manager.

• SQL Server 2000/Microsoft SQL Server Desktop Engine 2000 (MSDE 2000) - The Wyse Device Manager Database can be installed into an existing installation of SQL Server 2000 or it can be attached to an instance of MSDE 2000.

• SQL Server 2005/Microsoft SQL Server Desktop Engine 2005 (MSDE 2005) - The Wyse Device Manager Database can be installed into an existing installation of SQL Server 2005 or it can be attached to an instance of MSDE 2005.

• SQL Server 2008 - Beginning with WDM release 4.7.1, the Wyse Device Manager Database can be installed into an existing installation of SQL Server 2008.

• Oracle Data Access Components (ODAC) version 9.2.0.7.0 - Oracle Data Access Components (ODAC) offer high performance and efficient access to Oracle data from Microsoft Windows.

NoteWDM supports only English editions of the databases listed above.

NoteFor upgrading older versions of Oracle instances of Wyse Device Manager - The ODAC component will be detected by the Wyse Device Manager installation program. If the ODAC component is not already installed on the target machine, then it will be installed by the Wyse Device Manager installation program. After the ODAC component is installed, the Wyse Device Manager installation program must be re-launched to finish the installation process for an Oracle upgrade installation.

• Oracle 9i or later database - The Wyse Device Manager Database can be installed into an existing installation of an Oracle 9i or later database.

About the Desktop Engine

The Desktop Engine is a distributable version of the MS SQL Server relational database engine. To learn more about the Desktop Engine, refer to the Administrators Guide: Wyse Device Manager.

About MS SQL Server

Wyse Device Manager software supports the following MS SQL Server versions:• SQL Server Enterprise Edition • SQL Server Developer Edition • SQL Server Desktop Engine (also known as MSDE)• SQL Server 2005 Express• SQL Server 2008

NoteBy default, Wyse Device Manager software installs MSDE. To use an SQL Server Personal Edition or an SQL Server Developer Edition, you must perform a custom installation (for custom installation procedures, refer to "Installing WDM Using the Custom Installation Option").

6 Chapter 2

Port RequirementsTo perform their full range of management functions, Wyse Device Manager software components require certain ports to remain open on your servers, routers, and switches. Table 2 lists the ports Wyse Device Manager software uses and describes the respective communication protocols and their function.

Table 2 Port requirements

Wyse Device Manager Component Protocol Port Function

GUI Hyper-Text Transfer Protocol (HTTP)

80280

Communicate with the Web Service and Standard Service.

File Transfer Protocol (FTP)

21 Register new packages into the Master Software Repository.

OLE DB or ODAC 1433 for SQL or1521 for Oracle

Communicate with the Wyse Device Manager Database.

VNC 550058005900

Remote shadows devices.

Web Service Hyper-Text Transfer Protocol (HTTP)

80280

Communicate with the Web Agent, the GUI, and the Standard Service.

HTTPS 4438443

Secure Communication with theWeb Agent, the GUI, and theStandard Service



Web Agent Hyper-Text Transfer Protocol (HTTP)

80280

Communicate with the Web Service.


21 Read and write files to the Master and Remote Software Repositories.

Standard Service



Hyper-Text Transfer Protocol (HTTP)

8008 Communicate with the GUI and Web Service.


Port Requirements for HTTP/HTTPS

Wyse Device Manager software relies on the HTTP communications port designated by your Web service (for example, Microsoft Internet Information Service) for push operations. Push refers to operations initiated by Wyse Device Manager and sent (pushed) to devices.

Push operations include:• Issuing quick device commands (such as Refresh Device Information, Reboot, Change

Device or Network Information, Get Device Configuration, and so on)• Distributing packages at a specific time (either immediately or at a specific date and

time)

NoteTypically, port 80 is designated as the HTTP port and port 443 is designated as the HTTPS port. However, if port 80 (or the designated HTTP port), or port 443 (or the designated HTTPS port) is closed, Wyse Device Manager will be unable to push updates or quick commands to devices.

Standard Service and PXE

Dynamic Host Communication Protocol (DHCP)

67684011

Process UDP requests from PXE-enabled devices to the Standard Service.

Trivial File Transfer Protocol

69 Download bootable image to enable management processing.

Hyper-Text Transfer Protocol (HTTP)

80 Communicate with Web Service regarding actions and status of current task.


21 Download and upload files to Master and Remote Software Repositories.

Standard Service and legacy support for older WDM Agents

Universal Datagram Protocol (UDP)

4495644957

Discover devices (using subnet directed broadcasts) that have older WDM Agents (5.0.0.x and earlier) installed.

Transmission Control Protocol (TCP)

44955 Discover devices using IP Range Walking. Upgrade devices that have an older WDM Agent (5.0.0.x and earlier) installed.

Table 2 Port requirements, Continued

Wyse Device Manager Component Protocol Port Function

8 Chapter 2

Installing and Configuring WebDAV on IIS 6.0To use the HTTP or secure HTTP (HTTPS) protocol with Wyse Device Manager, install WebDAV before you install WDM on the server. The installation process includes:• “Changing the Isolation Level in IIS 6.0” • “Installing WebDAV on IIS 6.0” • “Configuring WebDAV on IIS 6.0” • “Setting Up a Self-Signed Certificate on IIS 6.0”

Changing the Isolation Level in IIS 6.0Because one of the components of WDM is supported only in IIS 5.0, if the server is using IIS 6, you need to configure IIS to work in isolation mode.

Check to make sure the isolation level in IIS 6.0 is configured properly.

To change the isolation level in IIS 6.0, complete these steps:

1. From the Start menu, navigate to All Programs | Administrative Tools | Internet Information Services (IIS) Manager.

2. In the Computer Management window, expand Internet Information Services.

Figure 1 Computer Management Window

3. Right-click the Web Sites folder and select Properties.


Figure 2 Web Sites Properties Window

4. In the Web Sites Properties window, click the Service tab.

5. In the Isolation Mode section, make sure “Run WWW service in IIS 5.0 isolation mode” is checked.

6. Restart the IIS service. (See Figure 3.)

Figure 3 Restart IIS

7. Select and right-click Internet Information Services in the Computer Management window. Select All Tasks | Restart IIS.

10 Chapter 2

8. Click the Home Directory tab in the Web Site Properties window. Check the last line in the Applications Settings area at the bottom of the window. The Application protection field should display Low (IIS Process) as shown in Figure 4.

Figure 4 Application Protection

Installing WebDAV on IIS 6.0After you change the isolation level, you can install WebDAV on IIS 6.0.

NoteThese steps are required for both master and remote repositories.

To install WebDAV on IIS 6.0, follow these steps:

1. Select Add or Remove Programs from the Control Panel.

2. Select Add/Remove Windows Components.

3. Select Application Server and click the Details button.

4. Select Internet Information Services (IIS) and click the Details button.

5. Select World Wide Web Service and click the Details button. The World Wide Web Service window appears.


Figure 5 World Wide Web Service Window

6. Check WebDAV Publishing and click OK, as shown in Figure 5.

7. Right click My Computer and select Manage.

8. Expand the Services and Applications menu.

9. Expand the Internet Information Services menu and choose Web Service Extensions. The window shown in Figure 6 appears.

Figure 6 Web Service Extensions

10.Look in the right pane of the window to verify that the status column shows Allowed for WebDAV.

12 Chapter 2

Configuring WebDAV on IIS 6.0This section describes the steps to configure WebDAV on IIS 6.0.

NoteYou must install WDM 4.7.1 before configuring WebDAV. For instructions on installing WDM, see Chapter 3 in this guide, "Installing Wyse Device Manager."

Follow these steps to configure WebDAv:

1. Right click My Computer and select Manage from the context menu.

2. Expand the Services and Applications menu.

3. Expand the Internet Information Services menu and choose Web Sites.

4. Select Rapport HTTP Server and right click New and select Virtual Directory. The Virtual Directory Creation Wizard appears.

Figure 7 Virtual Directory Creation Wizard

5. Click Next. The Virtual Directory Alias window appears.


Figure 8 Virtual Directory Alias Window

6. If a master repository is installed on the same machine as WebDAV, you must create a virtual directory alias under the Rapport HTTP server. For example, MyWDM is the virtual directory alias shown in Figure 8. Enter a name for the alias, and click Next. The Web Site Content Directory window appears.

Figure 9 Web Site Content Directory Window

7. Enter the path to the directory you want WebDAV to access. In the example in Figure 9, the directory for WebDAV is the same as the FTP root (c:\inetpup\ftproot).

NoteYou can direct WebDAV to any directory on the server.

After you enter the path, click Next. The Access Permissions window appears.

14 Chapter 2

Figure 10 Virtual Directory Access Permission Window

8. Select the checkboxes to configure Read, Write, and Browse access permissions and then click the Next and Finish buttons.

NoteAll the WDM packages reside in a folder called “Rapport” under the root directory. If you do not find the Rapport folder in the root directory, you must create one.

9. To verify the WebDAV configuration, open Internet Explorer, and enter this address:

http://localhost/MYWDM

The browser window displays the virtual directory contents.

NoteTo create or update a master repository using HTTP protocol, see the instructions in Chapter 3 in the WDM Administration Guide.

Setting Up a Self-Signed Certificate on IIS 6.0This section explains how to create a self-signed SSL certificate for your intranet. A self-signed certificate can secure your intranet as well as a purchased certificate because the self-signed certificate has never existed outside your intranet.

To configure a self-signed SSL certificate, download the Microsoft IIS 6.0 Resource Kit Tools from this URL:

http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en

NoteThe steps described in the “Installing Self SSL” section are required only when you do not already have a Certificate. Use of a self-signed certificate is not recommended for production environments. Use an SSL only for testing purposes.

http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en


Installing Self SSL After you download the tools, follow these steps:

1. Run the iis60rkt.exe executable file. The welcome screen appears.

Figure 11 IIS Resource Kit Tools Wizard

2. Click Next. The License Agreement dialog box appears. Select I agree and click Next. The Customer Information window appears.

Figure 12 Customer Information Window

3. Enter your information, (it may appear automatically) and click Next. The Setup Type window appears.

16 Chapter 2

Figure 13 Setup Type Window

4. Select Custom and press Next. In the window that follows, the default location for the installation is displayed. You can change the path, if desired, then click Next. The Select Features window appears.

Figure 14 Select Features Window

5. To install SelfSSL only, deselect all the other choices.

NoteHighlight a feature to display a description of it in the right pane of the window. Select any features you wish to install.

After selecting the feature(s) to install, click Next to begin the installation. When the installation is complete, click Finish.


Creating a CertificateAfter the SelfSSL software is installed, you can create a certificate by following these steps:

1. From the Start menu, navigate to SelfSSL as shown in Figure 15.

Figure 15 Navigate to Self SSL

The SelfSSL window appears.

18 Chapter 2

Figure 16 SelfSSL Window

2. At the prompt, type selfssl /T and press Enter. When asked if you want to replace the SSL settings for site 1, press y.

NoteIf you type selfssl /T /N:CN=<computer or domain name> you will be prompted only once in Internet Explorer to accept the security certificate.

3. Close the DOS window.

4. Open Internet Explorer, and type https://localhost/MyWDM in the address space, and click Yes when asked about viewing a secure site. The warning shown in Figure 17 appears, along with a display of the software repository contents.

Figure 17 Security Alert

The security alert shown in Figure 17 appears because SelfSSL creates a certificate for use during testing only. The connection is secured, but every time you try to connect, you will see the alert. For your final deployment, you need to generate a certificate for secure communication.


NoteIf you specify the same server name in both IIS and SelfSSL you will never see a security warning (because the name of the certificate matches the server name). If you try to access the site from another computer, you will get a security warning (indicating the access request does not come from a trusted authority). To avoid the security warning, export the certificate to a file and then import the file on the computer from which you want to access the site. Make sure in the WDM GUI Configuration Manager | Preferences | Service | Port Settings window, the field value for Web Server HTTPS Port is set to 443 or the designated HTTPS secure port and the Secure Communications check box is checked. See Figure 19.

Figure 18 Port Setting Preferences

5. To view the SSL Certificate, right click My Computer and select Manage from the context menu.

6. Expand the Service and Applications menu and click Internet Information Service (IIS) Manager and expand the Web Sites menu. Right click Rapport HTTP Server and select Properties.

7. Select the Security directory from the Rapport HTTP Properties window.

8. Click View Certification in the Secure Communication section.

9. The certificate appears, as shown in Figure 19, and the HTTP over SSL configuration is ready to be used with WDM.

20 Chapter 2

Figure 19 Security Certificate

After the self-signed certificate is created, stop the www service and start the HServerInit service.

NoteIf you generate the certificate after installing WDM, you must restart the HServerInit service.

Installing and Configuring WebDAV on IIS 7.0To use the HTTP or secure HTTP (HTTPS) protocol with Wyse Device Manager, install WebDAV before you install WDM on the server. The installation process includes:• “Installing the Desktop Experience Feature” • “Installing IIS 7.0” • “Installing the WebDAV Extension for IIS 7.0” • “Configuring WebDAV and IIS”

Installing the Desktop Experience FeatureTo enable WebDAV redirection, install the Desktop Experience feature.

1. From the Start menu, choose Server Manager.


Figure 20 Server Manager Window

2. In the left pane, select Features and double click Add Features in the right pane. The Add Features Wizard appears.

Figure 21 Add Features Wizard

3. Select the Desktop Experience check box and click Install.

4. The wizard installs the Desktop Experience feature on your server.

5. Restart the server to complete the installation.

22 Chapter 2

Installing IIS 7.0Follow these steps to install IIS 7.0:

1. From the Start menu, choose Server Manager. (See Figure 20.)

2. In the left pane, select Roles and double click Add Roles in the right pane. The Add Roles Wizard appears.

3. In the left pane, double click Server Roles, select the Web Server (IIS) check box and click Next.

Figure 22 Add Roles Wizard

4. Select Role Services in the left pane. The Select Role Services window appears.


Figure 23 Select Role Services

5. Select all the options except Request Filtering, as shown in Figure 24.

Figure 24 Role Services Options

6. Click Next, then Install, and then Close. IIS 7.0 is now installed on your server.

Next, install the WebDAV Extension for IIS 7.0

24 Chapter 2

Installing the WebDAV Extension for IIS 7.0Follow these steps to download and install the WebDAV Extension for IIS 7.0:

1. Download the WebDAV Extension for IIS7.0 from this URL:http://blogs.iis.net/robert_mcmurray/archive/2008/03/12/webdav-extension-for-windows-server-2008-rtm-is-released.aspx.

NoteMake sure you download the 32-bit Installation Package.

2. To install WebDAV Extension for IIS 7.0, double click webdav_x86_rtw.msi. The Microsoft WebDAV Extension For IIS 7.0 Setup wizard appears.

Figure 25 WebDAV Extension

3. Accept the license agreement and click Install.

4. The wizard installs the WebDAV Extension for IIS7.0. Click Finish to complete the installation.

Next, install WDM 4.7.1. For instructions on installing WDM, see Chapter 3 in this guide, "Installing Wyse Device Manager."

Configuring WebDAV and IISAfter installing WDM 4.7.1, follow these steps to configure IIS and WebDAV:

1. Navigate to Start | Administrative Tools | Internet Information Services (IIS) Manager. The Internet Information Services (IIS) Manager window appears.

2. Expand the Server node (shown with the name of the IIS server).

3. Expand the Sites node and select Rapport HTTP Server.


Figure 26 IIS Manager

4. Double click Authentication and make sure the Anonymous and Windows authentications are both enabled. If they are not, you must enable them.

Figure 27 Authentication

5. Expand Rapport HTTP Server and select MyWDM.

6. Repeat Step 4 to enable authentication for MyWDM.

26 Chapter 2

Figure 28 MyWDM Authentication

7. Select WebDAV Authoring Rules for Rapport HTTP Server.

8. Right click in the right pane and select Add Authoring Rule…. The Add Authoring Rule… window appears.

9. Select the options shown in Figure 29.

Figure 29 Add Authoring Rules - HTTP Rapport Server

10.Verify that the WebDAV Extension is enabled by running the following command at the command prompt: net use * http://localhost.


Figure 30 Verify WebDAV Redirection

11. If the WebDAV installation is successful, a drive on your server is mapped to the site. This shows WebDAV redirection is active.

Figure 31 WebDAV Redirection

Enabling Basic AuthenticationTo enable basic authentication for any node, repeat steps 1-4 in the “Configuring WebDAV and IIS” section, and change the status of Basic Authentication to Enabled. (See Figure 27.)

28 Chapter 2

Configuring Site-Level WebDAV Settings1. Navigate to Start | Administrative Tools | Internet Information Services (IIS)

Manager to display the Internet Information Services (IIS) Manager window.

2. Expand the Server node (shown with the name of the IIS server).

3. Expand the Sites node and select Rapport HTTP Server.

Figure 32 IIS Manager Window

4. Select Web DAV Authoring Rules for Rapport HTTP Server.

5. On the far right pane, double click WebDAV Settings….


Figure 33 WebDAV Settings

6. Set all WebDAV settings to True. If you have a remote repository, configure these settings on both the master and remote repositories.

30 Chapter 2

Figure 34 WebDAV Settings

7. Select MIME Types for the Rapport HTTP Server, locate the extension .txt and click Edit.


Figure 35 Edit MIME Types

8. Change the MIME type for the .txt extension to application/doc. If you have a remote repository, change the MIME type on both the master and remote repositories.

9. Select the Rapport HTTP Server and double click Directory Browsing. Enable directory browsing on both the master and remote repositories, if you have a remote repository.

Configuring the Web.config FileModify the Web.config file to prevent the following errors:• Upload fails for files larger than 30 MB.• Merlin imaging fails when the URL and query string sizes are not adequate.

The Web.config file is in the inetpub\wwwroot folder:

Add the following contents to the Web.config file:

<security>

<requestFiltering>

<requestLimitsmaxAllowedContentLength="2000000000" maxUrl="8000" maxQueryString="8000" />

</requestFiltering>

</security>

32 Chapter 2

This example shows the web.config file with the contents added:

<?xml version="1.0" encoding="UTF-8"?>

<configuration>

<system.webServer>

<directoryBrowse enabled="true" showFlags="Date, Time, Size, Extension, LongDate" />

:

:

<security>

<requestFiltering>

<requestLimitsmaxAllowedContentLength="2000000000" maxUrl="8000" maxQueryString="8000" />

</requestFiltering>

</security>

</system.webServer>

</configuration>

Installing the Oracle ClientIf you want to use an Oracle 9i or later database with WDM and do not have an existing installation of Oracle 9i or later, you must install the Oracle Client as described in this section before installing WDM. This requirement applies only when the database server and WDM server are running on different machines.

NoteIf you already have the Oracle Provider for OLE DB 9.2.0.7.0 and the Oracle Objects for OLE 9.2.0.7.0 installed, and you intend to select the Oracle 9i Or Higher option (for Databases Supported) during the WDM installation, you will be prompted during the WDM installation to use the Oracle Net Configuration Assistant to set up the Data Source as described in "Step 2 Setting Up the Data Source."If you already have the Oracle Provider for OLE DB 9.2.0.7.0 installed but not the Oracle Objects for OLE 9.2.0.7.0, and you intend to select the Oracle 9i Or Higher option (for Databases Supported) during the WDM installation, you will be prompted during the WDM installation to use the Oracle Net Configuration Assistant to set up the Data Source as described in "Step 2 Setting Up the Data Source." However, you must also install Oracle Objects for OLE 9.2.0.7.0 by completing the procedures in "Step 3 Installing Oracle Objects for OLE 9.2.0.7.0."

To install the Oracle Client you must:

1. Install Oracle Provider for OLE DB 9.2.0.7.0 as described in "Step 1 Installing Oracle Provider for OLE DB 9.2.0.7.0."


2. Use the Oracle Net Configuration Assistant to set up the Data Source as described in "Step 2 Setting Up the Data Source."

3. Install Oracle Objects for OLE 9.2.0.7.0 as described in "Step 3 Installing Oracle Objects for OLE 9.2.0.7.0."

Step 1 Installing Oracle Provider for OLE DB 9.2.0.7.0

1. Double-click the setup.exe from the Disk1\oraoledb\Disk1 folder to start the installation wizard and open the Welcome window.

Figure 36 Welcome

2. Click Next to open the File Locations window.

Figure 37 File Locations

3. Click Next to open the Available Products window.

34 Chapter 2

Figure 38 Available Products

4. Select Oracle Provider for OLE DB 9.2.0.7.0, and then click Next to open the Component Locations window.

Figure 39 Component Locations

5. Click Next to open the Summary window.

Figure 40 Summary

6. Click Install to install Oracle Provider for OLE DB 9.2.0.7.0.

7. After installation is complete, continue with "Step 2 Setting Up the Data Source."


Step 2 Setting Up the Data Source

1. Open the Oracle Net Configuration Assistant to set up the Data Source.

Figure 41 Oracle Net Configuration Assistant - Welcome

2. Click Next to open the Directory Usage Configuration window.

Figure 42 Directory Usage Configuration

3. Select the No, I want to defer this configuration to another time option, and then click Next to open the Database Version window.

Figure 43 Database Version

4. Select the Oracle 8i or later database or service option, and then click Next to open the Service Name window.

36 Chapter 2

Figure 44 Service Name

5. Enter wyse for the Service Name, and then click Next to open the Select Protocols window.

Figure 45 Select Protocols

6. Select TCP for data transfer, and then click Next to open the TCP/IP Protocol window.

Figure 46 TCP/IP Protocol

7. Enter the Host name (IP address of the machine on which the WDM Database is installed), select the Use the standard port number of 1521 option, and then click Next.

8. Click Yes to test the connection (be sure you use the correct user name and password to test the connection).


9. After your connection test is successful, enter wyse for the Service Name, and then click Next (the Net Configuration Assistant enters the details in TNSnames.ora). Your configuration steps end here (select No and do not configure any other net service). Continue with "Step 3 Installing Oracle Objects for OLE 9.2.0.7.0."

Step 3 Installing Oracle Objects for OLE 9.2.0.7.0

10.Double-click the setup.exe from the Disk1\oraoledb\Disk1 folder to start the installation wizard and open the Welcome window.

Figure 47 Welcome

11.Click Next to open the File Locations window.

Figure 48 File Locations

NoteThe full Source Path in the screen shown above is: C:\Documents and Settings\shuvra\Desktop\WDM 4.5-build 46\Disk1\oraoledb\Disk1\stage\Products.jar

12.Click Next to open the Available Products window.

38 Chapter 2

Figure 49 Available Products

13.Select Oracle Objects for OLE 9.2.0.7.0, and then click Next to complete the Oracle Objects for OLE 9.2.0.7.0 installation.

14.Click Exit to complete and exit the Oracle Client installation.

15.Change the security settings for either the WDM user or the WDM group to allow access to the installation folder and sub directories where the Oracle Client software was installed.

16.Reboot the system before you continue with installing Wyse Device Manager as described in "Installing Wyse Device Manager."

Installing Wyse Device Manager 39

3 Installing Wyse Device Manager

This section provides the detailed procedures you must complete to install Wyse Device Manager using either the Typical or Custom installation option.

NoteBe sure you have completed all pre-installation requirements as described in "Preparing for Installation" before you begin installing Wyse Device Manager.

About Installing Wyse Device Manager SoftwareThe Wyse Device Manager installation wizard automatically detects whether or not a new installation or an upgrade installation is needed. If you launch the installation wizard on a system without Wyse Device Manager software components, it automatically helps you to perform a new installation. If you launch the installation wizard on a system with Wyse Device Manager software components, it automatically helps you to perform an upgrade installation. In an upgrade case however, you can still choose to install the software over an existing installation of Wyse Device Manager (formerly Rapport software).

NoteWyse Device Manager software supports upgrades of version 4.4.1 and later. If you need to upgrade from a version prior to 4.4.1, you must upgrade to version 4.4.1 (using the upgrade instructions for your version in the Wyse Device Manager documentation) before you can upgrade to WDM version 4.5.3. Wyse Device Manager software also supports upgrades of older Oracle installations of Wyse Device Manager. For upgrading older versions of Oracle instances of Wyse Device Manager - The ODAC component will be detected by the Wyse Device Manager installation program. If the ODAC component is not already installed on the target machine, then it will be installed by the Wyse Device Manager installation program. After the ODAC component is installed, the Wyse Device Manager installation program must be re-launched to finish the installation process for an Oracle upgrade installation.

NoteWyse Device Manager release 4.7 supports new installations and upgrades from WDM 4.5.2 and WDM 4.5.3 to WDM 4.7 or from WDM 4.6 (HF04053008908) to hot fix HF04053022008 and then to WDM 4.7.

40 Chapter 3

CautionIt is highly recommended that you DO NOT install Wyse Device Manager software on any server which is currently dedicated to other tasks (such as a Domain Controller, Backup Controller, Mail Server, Production Web Server, DHCP Server, MSMQ Server, Application Server, and so on). It is highly recommended that Wyse Device Manager software be installed on a server that is dedicated to Wyse Device Manager services.

NoteUsing the Windows Firewall - If you are using the Windows Firewall and you are running WIndows® Server 2003 SP2, WIndows® Server 2003 R2, or WIndows® XP SP2, you must also complete the procedures in "Using the Windows Firewall: Windows 2003 Server SP2, Windows 2003 Server R2, and Windows XP SP2 Requirements" after installing and before using Wyse Device Manager. Using an Oracle Database - If you are installing the WDM Server on a Windows 2000 Server with SP4 or a Windows 2000 Advanced Server with SP4 and you are using an Oracle database, you must also complete the procedures in "Using an Oracle Database: Windows 2000 Server with SP4 and Windows 2000 Advanced Server with SP4 Requirements" after installing and before using Wyse Device Manager

Wyse Device Manager uses five major components to deploy its management functions:• Database - The Database stores and provides access to all of the information for

device management, including logging, packages, user data, and Remote Software Repository information.

• Software Repository - The Software Repository stores Wyse Device Manager packages.

• Web Services - Web Services uses HTTP/HTTPS to enable push and pull communications to devices equipped with the Wyse Device Manager Web Agent.

• Standard Services - Standard Services allows Wyse Device Manager software to:· Execute pre-boot management functions on devices that support the Preboot

EXecution Environment (PXE).· Upgrade older Wyse Device Manager (formerly Rapport) Web Agents (5.0.0.x) to

the new Wyse Device Manager Web Agent.• User Interface - The User Interface allows you to perform all device-management

functions and provide visual feedback to your operations.

Installing WDM Using the Typical Installation OptionIn a Typical installation, the installation wizard selects the default installation options.

NoteYou can only use the Typical installation option when using an SQL Server database or instance of MSDE. If you are using an Oracle database, you must use the Custom installation option as described in "Installing WDM Using the Custom Installation Option."


During a Typical installation, the installation wizard will help you to install the following on a single server (in the order shown):

1. Wyse Device Manager Database - The wizard installs an instance of MSDE as the database.

2. Software Repository - The wizard re-configures Microsoft Internet Information Services (IIS) FTP service, creates a local Wyse Device Manager user, and assigns the user read/write permissions to FTP.

3. Web (HTTP) Service - The wizard re-configures Microsoft Internet Information Services (IIS) Web service.

4. Standard Services - The wizard installs Standard Services.

5. Wyse Device Manager User Interface - The wizard installs the Wyse Device Manager User Interface, an MMC snap-in.

Installing WDM Using the Custom Installation OptionIn a Custom installation, the installation wizard allows you to select the configuration options other than the default options. Custom installations options may differ depending on the Sales Key (license) used.

NoteAn Enterprise Sales Key allows the components to be installed on one to five servers in any combination. An Enterprise Sales Key is also required to allow the Wyse Device Manager Database to be installed on the Oracle 9i or later instance. An Enterprise Sales Key is required to support secure communication between the components of WDM.

With a Custom installation, be aware of the following:• Web Services, Standard Service, and User Interface require MDAC 2.8.• Wyse Device Manager software utilizes Mixed Mode authentication. Be aware that if

you are using an existing SQL Server that was installed using Windows authentication mode only, the Wyse Device Manager Database user will be unable to log-in to the SQL database, and the installation will fail.

• Enterprise Edition only - If your network has multiple subnets, consider deploying a copy of the Wyse Device Manager Software Repository on each subnet. A Software Repository on each subnet allows you to store large device applications and image files locally. When you distribute upgrades to one or more devices on a subnet from a local repository, you reduce network traffic.

During a Custom installation, the installation wizard will help you to install and configure the following (in the order shown):

1. Wyse Device Manager Database - The Workgroup Edition allows you to use an SQL Server or an instance of MSDE when installing the WDM database. The Enterprise Edition allows you to use an Oracle 9i or later database, an SQL Server, or an instance of MSDE when installing the WDM database.

42 Chapter 3

NoteIf you want to use an Oracle 9i or later database with WDM and do not have an existing installation of Oracle 9i or later, you must install the Oracle Client as described in "Installing the Oracle Client" before installing WDM.If you already have the Oracle Provider for OLE DB 9.2.0.7.0 and the Oracle Objects for OLE 9.2.0.7.0 installed, and you intend to select the Oracle 9i Or Higher option (for Databases Supported) during the WDM installation, you will be prompted during the WDM installation to use the Oracle Net Configuration Assistant to set up the Data Source as described in "Step 2 Setting Up the Data Source."If you already have the Oracle Provider for OLE DB 9.2.0.7.0 installed but not the Oracle Objects for OLE 9.2.0.7.0, and you intend to select the Oracle 9i Or Higher option (for Databases Supported) during the WDM installation, you will be prompted during the WDM installation to use the Oracle Net Configuration Assistant to set up the Data Source as described in "Step 2 Setting Up the Data Source." However, you must also install Oracle Objects for OLE 9.2.0.7.0 by completing the procedures in "Step 3 Installing Oracle Objects for OLE 9.2.0.7.0."

NoteIf you use SQL Server 2005 Express Edition for database, make sure the "Log on as" account for the SqlExpress service is set to "Local System.” To configure this, do the following:

• From the Start menu, navigate to Administrative Tools | Services.• Select SQL Server (SQLEXPRESS) Service and right click it.• Select Properties.

Figure 50 SQL Server Properties

· Click the Log On tab and select the Local System account radio button, as shown in Figure 50.


· Restart the SQL Server (SQLEXPRESS) service.

2. Server Roles - You can select which Wyse Device Manager components to install on the target machine (machine to which you are installing Wyse Device Manager) and to which folder on the machine to install the component.• Web Service - The wizard re-configures Microsoft Internet Information Services

(IIS) Web service.• Standard Services - The wizard installs Standard Services.• Wyse Device Manager User Interface - The wizard installs the Wyse Device

Manager User Interface, an MMC snap-in.

3. Software Repository - You can select an existing FTP service or allow the wizard to reconfigure Microsoft's Internet Information Services (IIS) FTP service.• If you are using an existing FTP service, the wizard prompts you for an IP address,

username, and password (Workgroup licenses allow local IP addresses only). • The wizard attempts to connect to the FTP service to ensure connectivity and read/

write permissions. The Wyse Device Manager software verifies an existing connection. It does not configure FTP.

• If you are using IIS FTP, the wizard creates a local Wyse Device Manager user and assigns the user read/write permissions to FTP.

Installing WDM 4.7 Enterprise Edition with a SQL DatabaseThe options shown in the following installation instructions are valid for the following conditions:• WDM 4.7 Enterprise Edition• A new installation of the WDM software (not an upgrade from an earlier WDM release)• SQL database instance• All components are installed on the same server

NoteTo perform an installation with different conditions, select alternate options as appropriate.

Follow these steps for a new installation of WDM 4.7 Enterprise Edition software:

1. Click the executable file name to extract the files to a local folder.

2. Navigate to the folder where you extracted the files and run the Setup.exe.

44 Chapter 3

Figure 51 Preparing Setup

3. The screen shown in Figure 51 appears, and the software checks for a prior installation of WDM. When the Install Shield Wizard screen appears, click Next to begin the installation.

Figure 52 License Agreement

4. When the License Agreement window appears, read the license agreement carefully, and select the first option (“I accept the terms of the license agreement”), if you agree to the license terms. Click Next to continue.


Figure 53 Customer Information

5. Enter the license key. Based on the license key you provide, the installer will install the Workgroup or Enterprise Edition. This example uses an Enterprise Edition License key. Enter your user name and company name.

Figure 54 Database Configuration

6. Choose the database you want to use. For this example, the selection is Microsoft SQL Server 2000 or higher, and the steps that follow are for a SQL database instance.

If you select the Oracle 9i or higher option, you will be instructed to install the Oracle client. To install the Oracle Client please refer to the section “Installing the Oracle Client” on page 32.

46 Chapter 3

NoteThis database option is not available with a Workgroup license installation. By default, a Workgroup installation installs MSDE as the database.

7. Click Next.

Figure 55 Setup Type

8. Select the Custom option. For more details on Typical and Custom options please refer to “Installing WDM Using the Typical Installation Option” on page 40 and “Installing WDM Using the Custom Installation Option” on page 41. Click Next.

Figure 56 Enterprise Database Confirmation


9. The default option is The Wyse Device Manager database has not been installed. If you have already installed the database on a different server, choose the other option “The Wyse Device Manager database has been installed on the following server:” and provide the corresponding information for that server. For this example, the first option is selected. Click Next.

Figure 57 Select Server Role

10.By default, all the components are selected. To install the database on a different server, select the appropriate options. In this example, all the components are installed on one sever. Click Next.

Figure 58 Select Repository Communication Protocol

48 Chapter 3

11.Select the protocol to use for Repository communication. The options are:• FTP - Download packages from the repository using the FTP protocol.• HTTP - Download packages from the repository using the HTTP protocol.• FTP and HTTP - Download packages from repository using either FTP or HTTP

protocol. If both are enabled, HTTP is tried first; if HTTP fails, the FTP protocol is used.

NoteIf you do not want to use FTP at all, select only HTTP in the window shown in Figure 58.

Figure 59 Repository Authentication

12.Select the authentication option(s) to apply to software repositories. You can select any or all of the options. If you select all three options, Windows authentication is applied. The authentication options are:• Anonymous access - This mode does not require a username or password to

access the repository.• Windows authentication - This is the most secure form of authentication in IIS.

when you log in, NT validates your login and only your username is transmitted over the network. No password is transmitted, so your password cannot be compromised.

• Basic Authentication - This authentication mode requires you to enter a valid NT login and password to gain access to the system. When Basic Authentication is enabled, you are prompted for your username and password when you try to access the virtual directory. The password is sent in CLEAR TEXT.

13.To change the password for the user “rapport,” check the Change Repository Password checkbox, and provide the password.

14.To use an Active Directory user instead of rapport, select the second radio button and provide the required information.


Figure 60 Database Configuration

15.By default, WDM deploys an MSDE instance. Because this example is for a SQL server installation, the second radio button (Use an existing SQL server with the following settings) is selected.

16.Enter the server name, user name and password for the SQL database server. Click Next.

Figure 61 Ready to Install

17.Click Install. A progress bar appears during the installation, as well as message boxes describing the process.

50 Chapter 3

Figure 62 Install Complete

18.Click Finish.

Figure 63 Restart Computer

19.Select Yes, I want to restart my computer now.

NoteYou must restart your computer before using WDM.


Upgrading a WDM InstallationThe options shown in the following upgrade instructions are valid for the following conditions:• Upgrade from a clean installation of WDM release 4.7 Enterprise Edition to WDM

release 4.7.1• SQL database instance• All components are installed on the same server

NoteTo perform an upgrade under different conditions, select alternate options as appropriate.

Follow these steps to upgrade from WDM 4.7 to WDM 4.7.1:

1. Double click the executable file name to extract the files to a local folder.

2. Navigate to the folder where you extracted the files and run the Setup.exe.

3. The WDM installer prepares for installation.

Figure 64 Preparing Setup

4. When the welcome screen appears, click Next to upgrade WDM 4.7 to WDM 4.7.1.

52 Chapter 3

Figure 65 Welcome Screen

5. The installer notifies the components to be upgraded. Click Next and then Install to proceed with the upgrade.

Figure 66 WDM Upgrade

6. The wizard shows the installation progress.

7. The installer prompts for the SA password for the database.


Figure 67 SA Password

8. Provide the SA password and click Next to proceed.

9. The installer displays the setup status.

10.When you are prompted to restart the computer, select the first option, as shown in Figure 68 and click Finish.

Figure 68 Upgrade Complete

11.The computer restarts and the upgrade is complete.

54 Chapter 3

Using the Windows Firewall: Windows 2003 Server SP2, Windows 2003 Server R2, and Windows XP SP2 Requirements

If you are using the Windows firewall and are running WIndows® 2003 Server SP2, WIndows® 2003 Server R2, or WIndows® XP SP2, you must log on as an administrator after installing and before using Wyse Device Manager and add the Rapport4service, Inetinfo, and Rptservicelogs programs to the Programs and Services list on the Exceptions tab of the Windows Firewall dialog box (for procedures on adding programs to the Programs and Services list on the Exceptions tab of the Windows Firewall dialog box, refer to the Windows Firewall documentation on the Microsoft® Web site).

Using an Oracle Database: Windows 2000 Server with SP4 and Windows 2000 Advanced Server with SP4 Requirements

If you are installing the WDM Server on a Windows 2000 Server with SP4 or a Windows 2000 Advanced Server with SP4 and you are using a supported Oracle database, the following changes must be made after installing and before using Wyse Device Manager:

Comment out the line below in the configuration file SQLnet.ora (this file exists in the Oracle home directory under ora92\network\admin):# SQLNET.ORA Network Configuration File: C:\oracle\ora92\network\admin\sqlnet.ora# Generated by Oracle configuration tools.NAMES.DEFAULT_DOMAIN = rap45.com#SQLNET.AUTHENTICATION_SERVICES= (NTS) (Must be commented as “#” for Windows 2000 Server with SP4 or a Windows 2000 Advanced Server with SP4)NAMES.DIRECTORY_PATH= (TNSNAMES, HOSTNAME)

55

Figures1 Computer Management Window 82 Web Sites Properties Window 93 Restart IIS 94 Application Protection 105 World Wide Web Service Window 116 Web Service Extensions 117 Virtual Directory Creation Wizard 128 Virtual Directory Alias Window 139 Web Site Content Directory Window 1310 Virtual Directory Access Permission Window 1411 IIS Resource Kit Tools Wizard 1512 Customer Information Window 1513 Setup Type Window 1614 Select Features Window 1615 Navigate to Self SSL 1716 SelfSSL Window 1817 Security Alert 1818 Port Setting Preferences 1919 Security Certificate 2020 Server Manager Window 2121 Add Features Wizard 2122 Add Roles Wizard 2223 Select Role Services 2324 Role Services Options 2325 WebDAV Extension 2426 IIS Manager 2527 Authentication 2528 MyWDM Authentication 2629 Add Authoring Rules - HTTP Rapport Server 2630 Verify WebDAV Redirection 2731 WebDAV Redirection 2732 IIS Manager Window 2833 WebDAV Settings 2934 WebDAV Settings 3035 Edit MIME Types 3136 Welcome 3337 File Locations 3338 Available Products 3439 Component Locations 3440 Summary 3441 Oracle Net Configuration Assistant - Welcome 3542 Directory Usage Configuration 3543 Database Version 3544 Service Name 3645 Select Protocols 3646 TCP/IP Protocol 3647 Welcome 3748 File Locations 3749 Available Products 3850 SQL Server Properties 4251 Preparing Setup 4452 License Agreement 44

56

53 Customer Information 4554 Database Configuration 4555 Setup Type 4656 Enterprise Database Confirmation 4657 Select Server Role 4758 Select Repository Communication Protocol 4759 Repository Authentication 4860 Database Configuration 4961 Ready to Install 4962 Install Complete 5063 Restart Computer 5064 Preparing Setup 5165 Welcome Screen 5266 WDM Upgrade 5267 SA Password 5368 Upgrade Complete 53

57

Tables1 Required Hardware Configuration 42 Port requirements 6

Installation Guide

Wyse Device ManagerTM Release 4.7.1Issue: 121508

Written and published by: Wyse Technology Inc., December 2008

Created using FrameMaker® and Acrobat®