Surgient Install 54

8/8/2019 Surgient Install 54

1/170

S u r g i e n t

I n s t a l l a t i o n a n d

C o n f i g u r a t i o n G u i d e

V e r s i o n 5 . 4


2/170

This document and the software described in this document constitute confidential information of Surgient, Inc. and itslicensors, and are furnished under a license from Surgient, Inc. This document and the software may be used and copiedonly as permitted by such license. The software is also protected by U.S. Patents 6,880,002 and 6,990,666 and is subjectto other pending patents.

Copyrights

Copyright 2002-2008 Surgient, Inc. All Rights Reserved.

This software includes the following third-party software:

Outlook Bar, version 0.9.3.0. Copyright Tim Dawson.

properJavaRDP Copyright 2003 Propero Ltd. www.propero.net. Licensed under GNU General Public License. The li-cense and the source code are included on the Surgient software media.

Software developed by the Apache Software Foundation (www.apache.org). Copyright 2001-2004 The Apache Soft-ware Foundation. Licensed under the Apache License, Version 2.0, a copy of which is included on the Surgient softwaremedia.

TightVNC Java Viewer version 1.2.9. Copyright 2001 - 2003 HorizonLive.com, Inc. Copyright 2001, 2002, 2003Constantin Kaplinsky. Copyright 1999 AT&T Laboratories Cambridge. Licensed under GNU General Public License.The license and the source code are included on the Surgient software media.

ViewerX VNC ActivX Control version 2.5.71.1. Copyright 2003-2005 SmartCode Solutions. All Rights Reserved.

Perl Kit, Version 5.8 Copyright 1989-1999, Larry Wall, licensed under GNU Library GPL 2.0 or Perl Artistic License.

Software developed by the Mono project (www.mono-project.com). Runtime libraries licensed under GNU Library GPL2.0. Class libraries licensed under MIT X11. The license and the source code are included with the Surgient software.

TightVNC 1.2.9 for Windows. Copyright 1999 AT&T Laboratories Cambridge. Copyright 2000 Tridia Corp. Copy-right 2002 RealVNC Ltd. Copyright 2000 - 2003 Constantin Kaplinsky. Copyright 2001 - 2003 HorizonLive.com,Inc. All rights reserved. Licensed under GNU General Public License. The license and the source code are included withthe Surgient software.

Trademarks

Surgient, the Surgient logo, Surgient VCS, Virtualization Control Server, VDMS, VTMS and VQMS are trademarks orregistered trademarks of Surgient, Inc. in the United States and other countries.

Microsoft, Windows and Windows NT are registered trademarks of Microsoft Corporation in the United States and othercountries.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

All other products or services mentioned in this document are trademarks or registered trademarks of their respective com-panies.

Disclaimers

This document is furnished AS IS. Surgient, Inc. disclaims all warranties regarding the contents of this document, in-cluding, but not limited to, implied warranties of merchantability and fitness for any particular purpose. This documentmay contain technical or other inaccuracies or typographical errors. Surgient, Inc. reserves the right to revise the infor-mation in this document at any time without notice.

Surgient, Inc. 8303 N. MoPac Expy., Suite C-300 Austin, Texas 78759


3/170

Surgient Installation and Configuration Guide ii

Contents

Target Audience ......................................................................................................... iv

About This Book ......................................................................................................... iv

Surgient Documentation .............................................................................................. v

Typeface Conventions ............................................................................................... vi

Acronyms and Abbreviations ..................................................................................... vi

Surgient Contact Information ....................................................................................viii

1 Before You Start ..................................................................................1Surgient Components and Solutions ...........................................................................2

Determining the Scope of Your Installation .................................................................4

System Requirements .................................................................................................7

Additional Considerations .........................................................................................11Network Communication ...........................................................................................15

Choosing a Windows Account for the Agent Service ................................................18

Pre-installation Checklists .........................................................................................19

2 Product Installation...........................................................................23Installing the VCS and Management Console ..........................................................25

Installing the Management Console on a Separate Server .......................................37

Installing Surgient Applications .................................................................................43

Installing Surgient Agents .........................................................................................49

Installing the VQMS CLI Server ................................................................................59

Next Steps and Getting Started ................................................................................63

3 Verifying the Installation...................................................................65Quick Start Using the Surgient Sample Image ..........................................................66

Workflow Summary ...................................................................................................67

Copy the Sample Image into the Library Location ....................................................67

Launch the Surgient Management Console ..............................................................68

Add a Library Location ..............................................................................................69

Create Network Resources and Add to Default Resource Pool ................................70Assign the Host to the Default Pool ..........................................................................74

Creating a Server Configuration ................................................................................76

Creating an Application Configuration .......................................................................78

Deploying a Sample Configuration ............................................................................79

Connecting to the Deployed Configuration ...............................................................80

Launching the Application .........................................................................................80


4/170

iii Surgient Installation and Configura-

Congratulations .........................................................................................................82

4 Remote Access..................................................................................83Universal Remote Access .........................................................................................84

Classroom Readiness Test .......................................................................................93

User Readiness Test ..............................................................................................105

5 Advanced Installation and Administration ................................... 107Moving an Existing Library Location ....................................................................... 108

Configuring NAIL Server Advanced Mode ..............................................................110

Using a VMFS-based (SAN) Library Location ......................................................... 118

Using NFS Servers .................................................................................................121

Installing the Add-In for HP Quality Center .............................................................124

Installing the Command Line Interface (CLI) ..........................................................124

Editing Advanced Configuration Settings ................................................................129

6 Troubleshooting the Installation.................................................... 131General Troubleshooting First Steps ...................................................................... 132

New Host Does Not Appear in Management Console ............................................ 132

Error While Adding Host to Pool .............................................................................133

.NET Framework Installed Before Microsoft IIS ......................................................134

Installation Error Messages ....................................................................................135

A Pre-Install Worksheet......................................................................137

B Installing the VCS on Multiple Servers.......................................... 139


5/170

Surgient Installation and Configuration Guide iv

PrefaceThe Surgient Installation Guide provides information to assist you with the

process of installing and configuring a Surgient environment. After you

complete an installation, see the Management Console online Help for

information on using the Surgient Management Console to create and

populate necessary objects.

Target Audience

The target audience for this book is the individual responsible for installing

Surgient applications and performing the initial configuration required to

begin using Surgient solutions on a day-to-day basis. Typically, these users

are system administrators.

About This Book

This book provides the information you need to install and configure

Surgient components during the initial deployment of a Surgient

environment. It is not intended to provide a complete description of the

features and capabilities of the Surgient platform or Surgient Management

Console.

The Surgient Installation Guide consists of the following sections:

Chapter 1, Before You Start, on page 1 provides an introduction to the

various Surgient components as well as to the physical and logical

architecture of a Surgient environment. It also describes installation

scenarios that can help you decide how to set up your network.

Chapter 2, Product Installation, on page 23 describes the steps for

installing Surgient components.


6/170

v Surgient Installation and Configuration Guide

Chapter 3, Verifying the Installation, on page 65 provides the Getting

Started steps for configuring your environment, creating a sample

application configuration, and deploying the sample configuration.

Chapter 4, Remote Access, on page 83 addresses issues associated

with enabling communication across a firewall.

Chapter 5, Advanced Installation and Administration, on page 107provides information about advanced options such as using a VMFS

volume on a SAN (storage area network).

Appendix A, Pre-Install Worksheet, on page 137 features a worksheet

designed to expedite the installation process.

Appendix B, Installing the VCS on Multiple Servers, on page 139

provides instructions for distributing the VCS components.

For your convenience, an index is located after the appendixes.

Surgient Documentation

The following documentation is available in support of version 5.4:

Surgient Remote Access Testing Guide provides information to assist in

running the user readiness test (URT) and the classroom readiness test

(CRT). URT enables virtual lab participants to verify, in advance, that

the computer and the location from which it is tested both support a

successful lab experience. CRT measures the connectivity and

performance characteristics of a physical classroom where hands-on

training is scheduled to occur.

Release notes for the Management Console and VQMS, VDMS, and

VTMS. The release notes contain the most current information about the

products and should be used in conjunction with other Surgient

documents. You should read these release notes before you begin

installing the Surgient products.


7/170

Surgient Installation and Configuration Guide vi

Typeface Conventions

The following typeface conventions are used in this book:

Acronyms and Abbreviations

The following acronyms and abbreviations are used in this book:

Component Convention

Window and dialog names Title caps, default font

Emphasis Italic

File or directory names Courier

Examples, including code Courier

UI commands within a procedure when aspecific action is taken

Bold

New terms Bold italic

Typed user input BoldCourier

Variables

Acronym orAbbreviation

Definition

API Application Programming Interface

CD-ROM Compact Disc Read Only Memory

CPU Central Processing Unit

DNS Domain Name System

GB Gigabyte

GUI Graphical User Interface

GUID Globally Unique Identifier

HBA Host Bus Adapter

HTTP Hypertext Transfer Protocol

ICA Independent Computing Architecture


8/170

vii Surgient Installation and Configuration Guide

ICMP Internet Control Message Protocol

IDE Integrated Drive Electronics

IIS Internet Information Service

IP Internet Protocol

LLP Local Listening Proxy

MAC Media Access Control

MDAC Microsoft Data Access Components

MB Megabytes

NAIL Network Abstraction and Isolation Layer

NAT Network Address Translation

NFS Network File System

NIC Network Interface Card

OS Operating System

PSA Path Signature Analysis

RAM Random Access Memory

RDP Remote Desktop Protocol

SCSI Small Computer System Interface

SE Sales Engineer

SMTP Simple Mail Transfer Protocol

SQL Structured Query Language

SSL Secure Socket Layer

SSPI (Microsoft) Security Support Provider Interface

TCP/IP Transmission Control Protocol/Internet Protocol

UI User Interface

UNC Universal Naming Convention

URA Universal Remote Access

URL Uniform Resource Locator


Definition


9/170

Surgient Installation and Configuration Guide viii

Surgient Contact InformationFor further information regarding Surgient offerings, phone

1-888-240-6997, send an e-mail to [email protected], or visit our Web site

at www.surgient.com.

To contact Surgient Support, use the Surgient Online Support Web page

available on our Web site. Send an e-mail message to

[email protected] to request a user account and instructions foraccessing Surgient Online Support.

VCS (Surgient) Virtualization Control Server

VDMS (Surgient) Virtual Demo Management System

VM Virtual Machine

VNC Virtual Network Control

VQMS (Surgient) Virtual QA/Test Management System

VR Virtual Resource

VTMS (Surgient) Virtual Training Management System

WebDAV Web based Distributed Authoring and Versioning


Definition


10/170

ix Surgient Installation and Configuration Guide


11/170

Surgient Installation and Configuration Guide 1

Before You Start

This chapter discusses the system requirements and other objectives and

conditions that must be considered while planning an installation.

The following sections address these issues and provide instructions for

ensuring that you are fully prepared to complete a Surgient installation.

Surgient Components and Solutions on page 2

Determining the Scope of Your Installation on page 4

System Requirements on page 7

Additional Considerations on page 11

Network Communication on page 15

Choosing a Windows Account for the Agent Service on page 18

Pre-installation Checklists on page 19

1


12/170

2 Surgient Installation and Configuration Guide

Surgient Components and Solutions

The following components are essential to the Surgient environment:

Surgient Virtualization Control Server (VCS) Typically installed on

a single virtual machine (VM) or physical server. Depending on the size

of the deployment, however, the VCS can be distributed across multipleVMs or physical servers.

The Surgient VCS consists of the following pieces, which provide the

capabilities required by all Surgient applications:

Core services Provide a platform of services and capabilities that

enable the Surgient applications to create and manage virtual

resources. Key services include the control service and the Surgient

engine.

Component services Host the reservation service, deployment

service, and other Surgient services.

Agent message forwarder Functions as the mailbox for the

Surgient VCS.

Agent message processor Parses agent documents.

Surgient Management Console Functions as the administrators

interface to the Surgient platform. Through this console, the

administrator can perform the tasks that are necessary to define andmaintain the Surgient environment, including the creation and

maintenance of users, organizations, virtual resources, and software

images.

Surgient applications Allow customers to take full advantage of the

Surgient platform and services.

The following applications are available from Surgient:

Surgient Virtual Demo Lab Management System (VDMS) Provides software-demonstration capabilities that result in the faster

and more reliable presentation of a product to potential customers.

These enhancements, in turn, generate additional leads and shorten

sales cycles.


13/170


Surgient Virtual QA/Test Lab Management System (VQMS)

Automates test lab environments for software organizations.

Surgient VQMS orchestrates the allocation, scheduling,

provisioning, configuration, and tearing down of software test

environments for developers and quality assurance (QA) engineers.

By providing self-service capabilities to groups and individuals who

desire access to automated test lab environments, VQMS enables

software organizations to increase repeatability in the test process

while optimizing test lab resources, reducing development and test

cycles, increasing the productivity of developers and QA engineers,

and eliminating errors.

Surgient Virtual Training Lab Management System (VTMS)

Enables training organizations to reduce delivery costs, shorten

cycles, and increase reach by delivering live, hands-on, technical

software training to anyone, anytime, anywhere. When using

VTMS, customers, partners, and employees experience the full

benefits of interacting with real training labs as part of instructor-led

and self-paced courses.

System library Contains a collection of such system resources as base

images, ISO images, and snapshots. The system library also includes the

templates directory and snapshots directory in which the various

files are stored. The file-storage device that you use as the system library

must have enough capacity to store many large files.

Surgient operations database Houses the configuration and state

information for all of the physical and virtual resources. Created on an

existing structured query language (SQL) server, the database also stores

information about users, their roles and privileges, and their

authentication policies.

Surgient reporting database Serves as a repository for historical data.

Logically distinct from the Surgient operations database, the reporting

database can be installed either as an independent database on the same

server as the operations database or on a different server altogether.

Surgient application server The physical server or VM on whichSurgient applications, including VDMS, VQMS, and VTMS, are

installed. End users and application administrators access these

applications through a Web browser.

Surgient file cache Contains copies of images from the system library

and allows multiple VMs to share the same image. When an image


14/170


changes in the system library, the updated image is sent to the file cache

upon the next deployment of the application configuration. Multiple

caches are supported, with each cache consisting of one or more cache

locations.

Surgient agents Facilitate communication with the VCS. Surgient

agents are installed on any system that hosts a system library location,

file cache location, or virtualization resources. They regularly poll theserver on which they are installed for performance and health statistics,

executing any commands needed to manage the physical and virtual

resources.

Virtual machine host server The physical device on which VMs are

created.

Optional:VQMS command-line interface (CLI) server Allows

Surgient VQMS users to issue commands and run scripts by way of a

CLI environment, provided they are also using the appropriatecommand-line client.

Determining the Scope of Your Installation

Because the Surgient platform is highly scalable, the Surgient components

and products can be installed on a single server or distributed across multiple

servers as you see fit. If you are installing a Surgient solution within the

confines of a relatively small environment, for example, you can install thecomplete VCS on the same server that hosts your databases and system

library.

On the other hand, if your installation is slated for a larger environment,

installing some of the VCS components on one server and the remaining

components on a second server can help you maximize the efficiency of your

solution. Databases, applications, and the system library can also be set up

on separate servers as needed.

The following criteria can be useful when determining which approach to

use:

The number ofvirtual labs to be deployed and serviced. A virtual lab is

a live software environment deployed on demand for demonstration,

testing, or training purposes. Users of Surgient VDMS, VQMS, and

VTMS can access virtual labs for software demonstrations and


15/170


evaluations, software testing, and hands-on software training,

respectively.

The diversity of your lab images, including the number of different

images, the size and content of each image, and their hosting

requirements.

Your reporting needs, as determined by the amount and type of data youexpect to save, as well as the number of reports you expect to generate.


16/170


Installation Scenario

In the following installation scenario, the VCS, the Management Console

and the application (VQMS, VDMS, or VTMS), are installed on the VCS

Server.

If you foresee that a large amount of storage space for your Library content

will be required, the system library can be installed on a server different from

the VCS server. Additionally, the database usually resides on a separate

database server than the VCS server.

An example installation is depicted by Figure 1.

Figure 1 Example Installation Scenario

See System Requirements on page 7 for information about the minimum

system requirements for following the example installation scenario.


17/170


System Requirements

The hardware and software requirements are detailed in the following

section.

General ConsiderationsReview the following general information:

Surgient is not compatible with VMwares Virtual Center and Lab

Manager products. Hosts that are managed by Surgient cannot also be

managed by VMware products.

The disk space required by the System Library location depends upon

the number and size of the images (labs, demos, classes) that are stored.

Using NAIL Server (used to support cloning) in advanced mode requirestwo (2) 1 GB Ethernet cards in all VM hosts. For more information about

NAIL Server in advanced mode, see the Management Consoles online

Help.

The Active X controls used by Surgient require 32-bit Internet Explorer

(default browser) when running on Windows 64 platforms. Both 32-bit

Internet Explorer and 64-bit Internet Explorer are shipped in Windows

x64. The combination of Firefox 2.0 and Sun Java J2SE 1.6 also works

on 64-bit Windows.

The VCS server and all VM host servers should reside on the same Local

Area Network (LAN).


18/170


System Requirements

Review the following system requirements for the example installation

scenario. See Figure 1 on page 6 for a description of this configuration.

Note: Installation of the Surgient VCS components requires that both

Microsoft IIS 6.x and .NET Framework 2.0 be installed on the VCShost computer before installing the VCS and Management Console.

Be aware that IIS must be installed before .NET Framework on the

VCS machine. See the troubleshooting topic .NET Framework

Installed Before Microsoft IIS on page 134 if IIS was not installed

first.

Computer

Surgient

Components System Requirements

Surgient

VCS Server

Generalrequirements forVCS, the Surgientapplications, andrelatedcomponents

Physical or virtual server with the followingspecifications:

English version of one of the following operatingsystems:

Microsoft Windows Server 2003 R2 (Standard,Enterprise, Web, x64)

Microsoft Windows Server 2003 SP1 (Standard,Enterprise, Web)

2 GB RAM Free disk space:

10 GB free disk space if images are stored on anetwork attached storage (NAS) device

40 GB free disk space if images are stored on alocal disk

Microsoft .NET Framework 2.0 Microsoft Internet Information Services (IIS) 6.x ASP.NET Application Server installed and enabledNote: IIS must be installed before .NET Framework.

Library Host System Library Microsoft .NET Framework 2.0 400 GB free disk space (The amount of requireddisk space depends on the size of the disk images.) Surgient agent installed.


19/170


Database

host

Surgient database One of the following databases: Microsoft SQL Server 2005 SP1 Microsoft SQL Server 2005 x64 Microsoft SQL Server Express

Microsoft SQL Server Express x64 Mixed Mode Authentication must be enabled Remote connections using TCP/IP must be enabled

Host Server

(host serverfor VMs)

Surgient Agent

This is the server,running a VMwareor Microsoftvirtualizationproduct, on whichthe Surgientapplicationmanages thevirtual resources.A typicalenvironmentconsists ofmultiple hostservers whoseaggregatecapacity is pooledand allocated.

One of the following virtualization products: VMware ESX 3.0.1, 3.0.2 VMware ESX 3.5 (Standard or Enterprise

version) Microsoft Virtual Server 2005 R2 SP1

4 GB RAM (supports approximately 6 virtualmachines with 512 MB RAM each)

10 GB free disk space (library provisioning) or 40 GB(dedicated cache location) Microsoft .NET Framework 2.0 Surgient agent installed

ComputerSurgientComponents

System Requirements


20/170


Guest VM

(If your VMimage doesnot contain a

SurgientGuest Agent,theserequirementsare notapplicable.)

Surgient GuestAgent

These are the

requirements ofthe guest VM inorder for theSurgient GuestAgent to functionproperly.

One of the following 32-bit operating systems: Windows Server 2003, Windows XP, Windows

2000, or Windows Vista Business edition orhigher

Red Hat Linux 9.0 Red Hat ES 3.0 or 4.0 SUSE 9.0 or 9.1 SUSE ES 9.0

OR

One of the following 64-bit operating systems: Windows XP 64 or Windows Server 2003 R2

x64 Red Hat Enterprise Linux Server 4.0 SUSE Enterprise Linux 10.0

Microsoft .NET Framework 2.0 (Windows agentsonly)

Note: VMs created from an image prepped with theSurgient Image Prep process include a Surgient GuestAgent.

Client

computer

(Applicationusers)

none

This is thecomputer used byIT operations andlab management

personnel toadminister theapplication and byend-users torequest andaccess labenvironments

English version of one of the following operatingsystems:

Microsoft Windows Server 2003 Microsoft Windows 2000 Microsoft Windows XP Red Hat Linux 9.0

Novell SUSE Linux 9.0, 9.1

MAC OS X with Firefox browser; remote accessmethods supported are Citrix ICA and MicrosoftRDP (must use Microsoft Remote DesktopConnection Client for Mac 2.0 (Beta 2)).

One of the following web browsers: Microsoft Internet Explorer 6.0 / 7.0 with cookies

enabled (only 32-bit version of IE Mozilla Firefox 1.5 / 2.0 with cookies enabled

Note: Web browser must be configured for either:

Microsoft ActiveX controls Sun Java Plugin JRE 1.4.2_06 - 1.6

(version 1.5 for Mozilla Firefox for Linux)

ComputerSurgientComponents

System Requirements


21/170


Additional Considerations

Depending on the configuration of your network and the needs of your

customers, the following variables can also affect how you set up a Surgient

environment:

Whether you anticipate any remote access requirements

Whether you intend to implement a file-cache system to help maximize

network efficiency

Whether you intend to use a VMFS volume on a SAN (storage area

network) for a Surgient library location.

Whether you have any address translation needs

The following sections examine these variables in more detail and provide

the information necessary for you to address any potential challenges.

Remote Access

To address your potential remote access needs, Surgient provides the

following solutions:

Universal remote access (URA) Enables communication from a

remote computer to a Surgient VM located behind a firewall.

Classroom readiness test (CRT) Measures a networks bandwidth and

latency and compares them with established ranges to determine

whether they are appropriate for your classroom needs.

User readiness test (URT) Used in conjunction with Surgient VDMS,

VTMS, and VQMS to determine if a remote users computer and the

computers current location meet the requirements to successfully

connect to a Surgient VM.

These solutions are described in greater detail in Chapter 4, RemoteAccess, on page 83. To utilize URA, you must install a URA gateway.

Similarly, to take advantage of CRT, you must install a CRT server.

Note: The URA gateway and CRT server must not be installed on the same

machine.


22/170


For more information about the system requirements for the URA gateway

and CRT server along with the requirements for the other servers used in a

Surgient solution, see System Requirements on page 7.

Image Provisioning and File CacheLocations

Images in Microsoft Virtual Server (MSVS) environments are, by default,

provisioned to destination VMs directly from the system library. VMware

ESX hosts can also access images directly from a system library when the

system library server supports both NFS and CIFS access protocols (see

Using NFS Servers on page 121) or the images are stored on a SAN

(storage area network). For more information, see Using a VMFS-based

(SAN) Library Location on page 118.

For image provisioning from a system library to be successful, the following

conditions must be met:

All MSVS host servers and system libraries must reside within the same

Windows domain.

The agent that manages an MSVS host servers or system libraries cannot

run as Local System account. Instead, it must run as a domain user in

the machines Administrators group.

ESX hosts that use a library location on a SAN VMFS volume must be

configured before installing Surgient. See Configuring the ESX Hostand SAN Server on page 120.

When a virtual lab is deployed under these conditions, the VM uses images

that remain in the system library location. Files are not copied to the VM host

server, which reduces the time required to deploy virtual labs.

Situations exist, however, when provisioning from the system library is not

optimal or possible. For instance, a very large number of VMs with heavy

usage can cause excessive load on the library server.

For these situations, Surgient usesfile caches andfile cache locations. A file

cache location describes any physical location on a server to which an image

and its related files are copied. If your environment requires a large number

of simultaneously accessible VMs, file cache locations provide load

balancing across multiple servers.


23/170


Whenever an application configuration is deployed, any file that is part of the

server configuration, including the .vhd, .dsk, .vmdk, and .iso files, is

copied to a file cache location and attached to the appropriate VM or VMs.

Upon termination of the application configuration session, the image and all

of its related files remain in the file cache location, where they can be

attached to other VMs during future deployments.

Surgient supports the following types of file cache locations:

Dedicatedfile cache locations are created on each VM host server.

Dedicated file cache locations are supported by MSVS and VMware

ESX. (Legacy images that were created on an ESX 2.x server are always

copied to a dedicated file cache.)

Sharedfile cache locations are accessible by all the VM host servers in

a specified resource pool. For VMware ESX, the shared cache locations

can either use NFS and CIFS access protocols (see Using NFS Servers

on page 121) or be on a SAN VMFS volume (see the ManagementConsole online Help topic Adding a Shared File Cache Location).

With shared file cache locations, you have the option of setting up cache

locations that are all managed by an existing Surgient agent on another

server. Regardless of whether your shared cache locations are remote or

local, the MSVS host servers and system libraries must reside within the

same Windows domain, and the managing agent must run as a domain

user in the Administrators group.

When planning the optimal solution for your network configuration, it isimportant to remember the following points:

Each VM must have direct read/write access to a file cache location.

A single physical host server can support multiple file cache locations,

provided the locations exist on different volumes.

The size of a shared file cache location is configurable. If you do not

specify a size, the entire disk is used.

File cache locations can be set up on servers that are managed by Surgientagents or on remote servers accessible by a managed server. If you define

more than one shared cache location, the system determines which location

to use during a deployment by identifying the following criteria:

The images and related files that are cached in each location


24/170


The number of VMs that require the image

If the required image exists in a cache location that is not currently at

maximum capacity, then that cache location is used. If the image resides in

a cache location that is attached to more than the Surgient-approved number

of VMs, the next available cache is used.

When a file cache location reaches full capacity, the least recently usedimages and files are purged automatically. Cached files that are connected to

a VM are considered active and cannot be purged.

The online help provides detailed instructions for creating file cache

locations.

Address Translation and Virtual Networking

The repeated cloning of a small number of VMs provides a fast, efficientmethod by which to create a large pool of identical VMs. In a Surgient

environment, many of the VMs that represent or comprise viable application

configurations are clones of one or more original VMs.

Unfortunately, cloned VMs share the following identifiers with the original

VM as well as with each other:

Machine name Duplicate machine names cause conflicts with network

shares. For example, an OS like Windows 2000 or Windows 2003

disables a clones network connection when it detects a duplicatemachine name. Changing the machine name of each VM is a time-

consuming effort that requires a restart of each VM. Additionally,

changing a machine name can break licensing codes, configuration files,

registry entries, and certificates.

Security identifier (SID) Redundant SIDs generate authentication

issues. Although SIDs can be changed, the process is a time-consuming

effort that requires a system restart for each VM. Further, changing a

VMs SID can result in software problems that affect licensing codes,

Windows authentication, Windows Shares, and IIS Services.

Static IP address The duplication of IP addresses, each of which must

be unique to every VM on a network, renders the original VM and all of

its clones incapable of communicating over the same network. Although

an administrator can change the IP address of each VM, this change can

also disrupt Web services, databases, special protocol drivers, firewall


25/170


rules, tuned applications, and other servers that still use the previous IP

address.

The Surgient environment solves the problem of duplicate IP addresses by

utilizing a network abstraction and isolation layer (NAIL). NAIL is installed

automatically when the Surgient agent is installed. The appropriate IP

addresses and MAC addresses are configured by way of the Surgient

Management Console.

As shown in Figure 2, NAIL uses network address translation (NAT) to

provide a unique IP address for each VM on a network.

Figure 2 Cloned VMs with Unique External IP Addresses

Network Communication

Review the following section for information about the various types of

network resources that you will need to create. Additionally, see the matrix

of ports on pagepage 17 for a list of port numbers that Surgient requires for

communication between the VCS and other components.

Network Requirements

You will need to define network resources for the application configurations

that you want to deploy. The appropriate IP addresses, MAC addresses, and

VLAN IDs are defined using the Surgient Management Console.


26/170


Surgient recommends that you verify the accuracy of all IP address, MAC

address, and VLAN ID ranges that you enter. A small error when entering a

range of addresses can result in the creation of thousands of unwanted

address records in the Surgient database.

Resource Description Requirements

MAC

Address

Ranges

This is the most widely used ofthe network resources becauseevery VM NIC (network interfacecard) will consume an ethernetMAC address while the VM isdeployed, regardless of how theinterface is configured within theVM guest operating system, andregardless of whether multipleclones of the VM aresimultaneously deployed.

Values should fall within the VMwareOrganizationally Unique Identifier (OUI)range of 00:50:56:00:00:00-00:50:56:3F:FF:FF. The size and values of this range can bechanged at any time. Plan to use at least one MAC address foreach VM per test configuration, up to themaximum number of concurrent VMs acrossall VM hosts.

IP Address

Ranges

NAIL uses IP address resourcesto prevent conflicts and providea unique IP address for each

VM whose network interfacesare configured with static IPaddresses within the VM guestoperating systems

These IP addresses cannot overlap withaddresses assigned by any DHCP server.Plan to dedicate one additional IP address

per VM host, plus one for each VM per testconfiguration that will be configured for NAILcloning, up to the maximum number ofconcurrent VMs across all VM hosts. Thesize and values of this range can be changedat any time.

Note: Consult your network administrator

to determine a range of IP addresses valid

for your local network that can be

dedicated to your Surgient installation.

VLAN IDRanges

NAIL also uses a virtual LAN(VLAN) for VMs that requiregrouping, as is the case whenmultiple server configurationscomprise a single applicationconfiguration. NAIL Server usesIEEE 802.1q VLANs to isolateapplication configurations fromone another and preventduplicate host name or IPaddress errors while

simultaneously deploying clonesof VMs.

You must use IDs within the range of 2 -4095, inclusive. If you are implementing NAIL Server inthe advanced mode, you should work withyour network administrator to select theappropriate network adapters, switches, andVLAN IDs that are compatible with yourphysical network environment. As a general guideline, plan for 1-2VLAN IDs per concurrent test configuration,depending on the complexity of the testconfiguration. The VLAN ID range selected

should be dedicated for use by the Surgientproduct.


27/170


Ports Used by Surgient

The following table lists the ports or port ranges required by Surgient.

Note: All ports are TCP unless otherwise specified.

Ping is open in some cases to facilitate connectivity testing, not for

VCS communications.This matrix does not account for Windows networking ports.

To

VCS

To

DBs

To App To Lib To

Hosts

To

VMs

To

URA

GW

To

Syslog

To

LDAP

From

VCS

2997-

2999

1433 2997-

2999

1024-

4999>32767ICMP

Ping

4277 4277 4277

ICMPPing

None UDP

514

389

From

DBs

None N/A None None None None None None None

From

App2997-

2999

80/

443

ICMPPing

1433 N/A 4277 4277 None None UDP

514

389

From

Lib

80/443 None 80/443 N/A 1024-

4999

>32767

None None None None

From

Hosts

80/443 None 80/443 1024-

4999

>32767

N/A None None UDP

514

None

From

VMs

80/443 None None None None N/A None None None

From

URA

GW

None None None None 5900

902

3389

5900

1494

N/A None None

From

Syslog

None None None None None None None N/A None


28/170


Choosing a Windows Account for the AgentService

Each physical computer that will be used to host the VMs that run the

labs, or test configurations, must have a Surgient agent installed.

On an agent host that runs Windows as the operating system, the agent

runs as a service, displayed in the Services panel as Surgient Agent.

Warning: If the host on which you install the agent uses Microsoft

Virtual Server, you must configure a user name and

password. Do not run the Agent service as a Local System

service, or deployments of labs might fail.

Considerations

Review the following considerations when determining which account to usefor the Agent service:

If the computer on which you install the agent is a member of a domain,

the user name and password should be for a domain account.

For computers that are not in a domain, the same Windows user account

must exist with the same password on every server/host where you

install the Windows agent

Every Windows agent service must be configured to run under the same

account.

The account must have read/write access to the System Library location.

The account must be a member of the local Administrators group (not

necessarily Domain Administrators). A Domain User that is in the local

Administrators group is preferred.

From

LDAP

None None None None None None None None N/A

To

VCS

To

DBs

To App To Lib To

Hosts

To

VMs

To

URA

GW

To

Syslog

To

LDAP


29/170


The password rules for the account must be configured to never expire.

Pre-installation Checklists

This section contains a checklist that correspond to the example installation

scenario. Before proceeding to the next chapter and installing the Surgientcomponents on your network, it is recommended that you complete the

checklist. Performing the tasks that are listed in the checklist will ensure that

your network is functional and will help you determine the information that

is needed during the installation process.

A complementary pre-install worksheet is provided in Appendix A, Pre-

Install Worksheet, on page 137. To speed up the installation process, record

the specified information in the appropriate worksheet and keep it nearby.

Installation Checklist

Before attempting an intermediate installation, perform the following steps:

____ 1. Identify the four or more servers that will be used in the Surgient

environment, as follows.

___ VCS server

___ Library server

___ Host server

___ SQL Server database server

Make certain the servers meet the specifications listed in System

Requirements on page 7.

____ 2. Add the VCS server to your network.

____ 3. Verify that the VCS server has basic network connectivity by pinging

your network gateway.

____ 4. Record the DNS name and the IP address of the VCS server in lines 1

and 2 of the worksheet onpage 137.

____ 5. Add the library server to your network.


30/170


____ 6. Verify that the library server has basic network connectivity by pinging

the VCS server.

____ 7. Verify that the VCS server can ping the library server.

____ 8. Add the machine that will become the first VM host server to your

network.

____ 9. Verify that the host server has basic network connectivity by pinging

the VCS server.

____ 10. Verify that the VCS server can ping the host server.

____ 11. Repeat steps 8 10 for each host server you add to your network.

____ 12. Add the SQL server to your network.

____ 13. Verify that the SQL server has basic network connectivity by pinging

the VCS server.

____ 14. Verify that the VCS server can ping the SQL server.

____ 15. Record the following database information in the pre-install worksheet:

Line 3 Unique name of the operational database that will be

created automatically during installation.

Line 4 DNS name of the operational database server.

Line 5 Installation account ID used to install the Surgient database.In some organizations, this might be the sa account.

Line 6 Installation account password.

Line 7 Unique name of the reporting database that will be created

automatically during installation.

Line 8 DNS name of the reporting database server, if different

from the one used for the operational database.

Line 9 Installation account ID used to install the Surgient database,

if different from the one used for the operational database. In some

organizations, this might be the sa account.

Line 10 Installation account password, if different from the one

used for the operational database.


31/170


____ 16. In line 11 of the pre-install worksheet, record the password that you

want to assign to the platform administrator account.

____ 17. In line 12, record the DNS name of the SMTP e-mail server through

which the Surgient VCS will send e-mail notifications.

____ 18. In line 13, record the e-mail address that will receive notifications when

an error occurs.

____ 19. If your environment will be employing a universal remote access

(URA) gateway, record the DNS name and IP address in lines 14 and

15, respectively. For more information on the URA gateway, see

Universal Remote Access on page 84.

____ 20. Determine and record in lines 16 and 17 the IP addresses and MAC

addresses, respectively, to be used during address translation. For more

information on how these addresses are used, see Address Translation

and Virtual Networking on page 14.

____ 21. If your environment will be using the Surgient classroom readiness test

(CRT), record the DNS name and IP address in lines 18 and 19,

respectively. For more information on CRT, see Classroom Readiness

Test on page 93.

Directions for completing the installation are listed in Chapter 2, Product

Installation.


32/170



33/170


Product

Installation

This chapter provides instructions for installing the Surgient VQMS product.

Installing the VCS and Management Console on page 25

Installing the Management Console on a Separate Server on page 37

Installing Surgient Applications on page 43

Installing Surgient Agents on page 49

Installing the VQMS CLI Server on page 59

Next Steps and Getting Started on page 63

2


34/170


After using the information and checklists in the previous chapter to define

and set up your network, you can begin installing the following Surgient

products or components:

Virtualization Control Server (VCS) and the Management Console

(page 25)

Virtual Demo Management System (VDMS), Virtual QA/TestManagement Server (VQMS), and Virtual Training Management Server

(VTMS) applications (page 43)

Library and Host agents (page 49)

VQMS CLI server (page 59; optionally installed separately)

Once you have completed the installation, refer to Chapter 3, Verifying the

Installation, on page 65.

By default, the Surgient software is installed in c:\Program Files\

Surgient. You can choose a different destination directory during the

install process. VCS log files are written to the \logs subdirectory in the

destination directory.

Installation Scenario

The following steps provide an overview of setting up your Surgient

environment:

1. Install the Surgient VCS and Management Console on the VCS server.

For more information, see Installing the VCS and Management

Console on page 25.

Note: Depending upon your installation scenario, review the following

topics: Installing the Management Console on a Separate Server

on page 37 and Installing the VCS on Multiple Servers on page

139

2. Install the appropriate Surgient application.

For more information, see Installing Surgient Applications on page

43.

3. Install a Surgient agent on the library server.


35/170


For more information, see Installing Surgient Agents on page 49.

4. Install an agent on the VM host server or servers.

For more information, see Installing Surgient Agents on page 49.

An example installation is depicted by Figure 3.

Figure 3 Example Installation Scenario

Installing the VCS and Management Console

To install the VCS components and the Management Console on a single

machine, perform the following steps:

Note: In some situations, you might want to also install the Management

Console on a separate computer, one that is more accessible to end

users than the VCS Server might be. For more information, see

Installing the Management Console on a Separate Server on page

37. Additionally, if you want to distribute the VCS componentsacross multiple computers, review Installing the VCS on Multiple

Servers on page 139.

1. From the Surgient CD, double-clickSurgientVCS.exe to launch the

Install Surgient VCS Wizard.


36/170


Note: If an Open File Security Warning message appears, click

Run.

2. Click Next to view the License Agreement page.


37/170


3. Read the end user license agreement (EULA).

To print a copy of the agreement, clickPrint.

4. Click I accept the terms of the license agreement.

5. Click Next to view the Installation Type page.


38/170


6. Click Express.

7. Click Next to view the Components To Install page.


39/170


8. Click Next to view the Destination Folder page.

9. Optional: To specify a destination folder other than the default folder of

C:\Program Files\Surgient\VCS, clickBrowse.

10. ClickNext to view the Operational Database page.


40/170


The operational database stores information associated with real-time

processes and functions.

11. Specify the following information for the operational database:

A unique name for the database, which is recorded in line 3 of the

pre-install worksheet.

The DNS name of the server that will act as the database server. This

name is recorded in line 4 of the pre-install worksheet. To select a

server from a list of available servers, clickBrowse.

The authentication method to use while connecting to the database.

To use SQL Server authentication, specify a logon ID and

password. If you choose to use SQL Server authentication, the

account and password information are recorded on lines 5 and 6

of the pre-install worksheet.

To use Windows authentication, checkUse Windows

authentication.

12. ClickNext to view the Reporting Database page, which is

automatically populated with values derived from the information

specified on the Operational Database page.


41/170


The reporting database captures historical information to be used when

generating reports.

13. Specify the following information for the reporting database:

A unique name for the database, which is recorded in line 7 of the

pre-install worksheet.

The DNS name of the server that will act as the database server. This

name is recorded in line 8 of the pre-install worksheet. To select a

server from a list of available servers, clickBrowse.

The authentication method to use while connecting to the database.

To use SQL Server authentication, specify a logon ID and

password. If you choose to use SQL Server authentication, the

account and password information are recorded on lines 9 and

10 of the pre-install worksheet.

To use Windows authentication, checkUse Windows

authentication.

14. ClickNext to view the Platform Administrator Password page.


42/170


15. Type a password for the platform administrator.

This password is recorded in line 11 of the pre-install worksheet.

16. Confirm the password by retyping it.

17. ClickNext to view the Surgient VCS E-Mail Settings page.


43/170


The information specified on this page defines who will receive the

appropriate e-mail message when an error occurs.

18. Specify the following information:

The DNS name of the mail server, such as mail.mycompany.com.

This name is recorded in line 12 of the pre-install worksheet.

The e-mail address to which messages will be sent. This address is

recorded in line 13 of the pre-install worksheet.

19. ClickNext to view the URA Gateway Information page.


44/170


20. Optional: If you are installing the Surgient VCS behind a firewall and

want to enable browser access from outside the firewall, specify the

host name or IP address of the Surgient universal remote access (URA)

gateway.

You might have recorded this information in lines 14 and 15 of the pre-

install worksheet. If you do not know this information at this time,

however, you can specify it later by using the Management Console

advanced configuration settings.

For more information on the URA gateway, see Universal Remote

Access on page 84.

21. ClickNext to view the Verification page.


45/170


22. Verify that the appropriate components will be installed according to

your specifications.

To make a correction, clickBackuntil you return to the appropriate

page.

23. ClickNext to install the Surgient VCS.

When the installation is finished, the Complete page opens.


46/170


24. ClickFinish to quit the Install Surgient VCS Wizard.


47/170


Installing the Management Console on aSeparate Server

The Surgient Management Console serves as the administrators interface to

the Surgient platform. By default, the Management Console is installed

directly on the VCS server, as part of the VCS Server installation. If yourenvironment is such that the Management Console users do not easily have

access to the VCS server, then you should install the Management Console

on a separate server.

To install the Surgient Management Console, perform the following steps:



Note: If an Open File Security Warning message appears, clickRun.



48/170


3. Click Custom.



49/170


The amount of disk space required for the installation and the amount of

space available on the currently selected disk are both shown. To view

the amount of space available on your other disks or to specify a different

disk for the installation, clickDisk Space.

5. Ensure that Management Console is the only selected check box.

6. Optional: To specify a destination folder other than the default folder ofC:\Program Files\Surgient\VCS, clickBrowse.

7. Click Next to view the System Information page.


The name or IP address of the computer on which you have installed

the Surgient VCS. If you have distributed the VCS across multiple

servers, specify the name or IP address of the one on which the core

services have been installed. These values are recorded on lines 1

and 2 of the pre-install worksheet.

If you are installing the Management Console on the same computer

as the Surgient VCS, type the name or IP address of the current

computer.


50/170


The platform administrator password that was specified during the

VCS installation. This password is recorded on line 11 of the pre-

install worksheet.

9. Click Next to view the URA Gateway Information page.

10. Optional: If you are installing the Management Console in an

environment that utilizes a firewall, specify the host name or IP addressof the Surgient universal remote access (URA) gateway.

This information is recorded on lines 14 and 15 of the pre-install

worksheet. For more information on the URA gateway, see the Surgient

Platform Operations Manual.

11. ClickNext to view the Verification page.


51/170


12. Verify that the Management Console will be installed according to your

specifications.


page.

13. ClickNext to install the Management Console.



52/170




53/170


Installing Surgient Applications

Surgient applications (VQMS, VTMS, or VDMS) can be installed directly

on the VCS server, or you can install an application on a separate application

server. Follow the directions below for either case.

To install a Surgient application, perform the following steps:

1. From the Surgient CD, double-click the file that corresponds to the

application you want to install, as follows:

To launch the Install Surgient VDMS Wizard, clickVDMS.EXE.

To launch the Install Surgient VQMS Wizard, clickVQMS.EXE.

To launch the Install Surgient VTMS Wizard, clickVTMS.EXE.


Run.

The Welcome page opens.


54/170


Note: The steps described in this section are applicable to all three

Surgient applications. However, the accompanying figures

represent the pages that are used during a Surgient VQMS

installation.





servers, specify the name or IP address of the one on which the core

services have been installed. These values are recorded on lines 1

and 2 of the pre-install worksheet.

If you are installing the application on the same computer as the

Surgient VCS, type the name or IP address of the current computer.

The password for the platform administrator. This password is

recorded on line 11 of the pre-install worksheet.

4. Click Next to view the Choose Destination Location page.


55/170


5. Optional: To specify a destination folder other than the default folder of

C:\Program Files\Surgient\ (where

is VDMS, VQMS, orVTMS, depending on which

application you are installing), clickBrowse.

If you are installing Surgient VTMS, go to step 6. If you are installing

VDMS or VQMS, go to step 8.

6. Click Next to view the CRT Server Information page.


56/170


7. Optional: If you are installing VTMS in an environment that utilizes the

Surgient classroom readiness test (CRT), specify the host name or IP

address of the CRT server.

These values are recorded on lines 18 and 19 of the pre-install

worksheet. For more information on Surgient CRT, see Classroom

Readiness Test on page 93.

8. Click Next to view the Start Copying Files page.


57/170


9. Verify that the application will be installed according to your

specifications.


page.

10. ClickNext to install the application.



58/170


11. ClickFinish to quit the InstallShield Wizard.


59/170


Installing Surgient Agents

Agents must be installed on the following servers before setting them up for

their intended use:

Surgient-managed host servers (where the VMs are deployed)

Servers that manage the system library (Windows or ESX Server)

Servers that manage any file cache locations (Windows or ESX Server)

Surgient provides an ESX host agent for host servers that utilize VMware

ESX 3.0.1, 3.0.2, or 3.5.

Surgient also provides a Windows agent for the Windows 2000 and

Windows 2003.

When you install an agent, one or more modules are installed along with thecore agent service. Which modules are installed is determined by the OS of

the machine and whether the machine is a physical host. Do not change these

selections without first contacting Surgient support.

The following table lists the available Windows agent modules and the

capabilities they provide:

The following sections describe how to install the Windows and ESX host

agents.

Agent Module Capabilities

Command line Provides the ability to run various systemcommands.

File management Provides the ability to manage files.

User management Provides the ability to manage user accounts.

Performance monitor Collects data from Microsofts WinPerf Monitor.

Microsoft Virtual Server Provides the Windows commands needed tomanage virtual resources.

Session state monitor Allows consultants to instrument a customer'sapplication for progress indication.

Table 1 Windows Agent Module Types and Capabilities


60/170


Installing the Windows Agent

To install the Windows agent, perform the following steps.

Note: Before installing the Agent, review Choosing a Windows Account

for the Agent Service on page 18 for important information about

selecting an account for the agent service to run as.

1. From the directory containing the distribution files, double-click

WindowsAgent.exe to launch the Install Surgient Agent Wizard.

Note: If a File Download message appears, clickOpen.


61/170


2. Click Next to view the Library Configuration page.

The Surgient library requires an Agent to manage the use of the library

images and files, as well as to facilitate communication between the

VCS, the application, and any client computers. The agent(s) thatmanage a library can be on a Windows host or an ESX Server host;

typically a single agent is selected to manage the library location(s) foran environment.

Select No to indicate if this agent will be notbe used to manage a

Surgient library.

Select Yes to indicate if this agent will be used to manage a Surgient

library. If you select Yes, provide the following information:

Location to create the library: enter the path to connect to the server

that will serve as the library location host.

Note: The library location must be on a server to which all host servers that

will use images from the library have access. For information about

placing the library location on an NFS (network file system) server,

see Using NFS Servers on page 121.


62/170


Location of the Images directory: this directory was created

automatically during the VCS installation, and by default is located on

the VCS host in /Images.

3. Click Next to view the Agent Configuration page.

4. For the Agent Message Forwarder, specify the name or IP address ofthe computer on which you have installed the VCS.


63/170


5. Click Next to view the Setup Type page.

6. Select Complete (Recommended).

7. Enter the directory path in which you would like to install the Agent.

To specify a destination folder other than the default folder ofC:\

Program Files\Surgient\Agent, clickBrowse.


64/170


8. Click Next to view the Service Configuration page.

9. Type a user name and password of a domain account under which the

agent will run as a Windows service to communicate with the system

library or file cache locations.

See Choosing a Windows Account for the Agent Service on page 18for important information about selecting an account for the agent

service to run as.

Agents that remotely manage the system library or file cache locations,

such as NFS export volumes, must run as an account with administrator

privileges and have Read/Write access.

If you do not provide a user name and password here, the Agent will run

as the Local System service.

Warning: If the host on which you install the agent uses Microsoft

Virtual Server, you must configure a user name and

password. Do not run the Agent service as the Local

System account because this could result in deployment

failures.


65/170


Note: Agents installed on VM host servers must run as an account with

administrator privileges and have Read/Write access to the remote

file locations.

Agents that remotely manage the system library or file cache

locations, such as NFS export volumes, must run as an account with

administrator privileges and have Read/Write access.

10. ClickNext to begin the installation.

The Setup Status page appears.


66/170


11. When the wizard finishes installing the Surgient agent, the Complete

page opens.

12. ClickFinish to conclude the Install Surgient Agent Wizard.

Note: After installing the Windows Agent, the computer must be rebooted

if either of the following is true:

-- The computer has one or more Intel PRO/1000 adapters.

-- The computer will be used for deployments in "Advanced" server

mode.

The computer must be rebooted because the Windows Agent

installation program adds two registry settings that affect the Intelnetwork adapters.


67/170


Installing the ESX Host Agent

To install, start, and configure the ESX host agent, perform the following

steps:

1. Log on to the target system as root.

2. Copy the file named esx-agent-5.4.0-xxx.i386.rpm from the

Surgient CD or distribution file to a temporary location.

3. Navigate to the directory where the .rpm file is and enter the following

command to install the agent:

rpm -i esx3-agent-5.4.0-xxx.i386.rpm

where xxx is the build number associated with the agent that you want

to install, such as 861.

4. Review the notice about firewall configuration and the port numbers

that were opened for use by the Surgient agent.

5. Enter the following command to start and configure the agent:

/etc/init.d/surgientagent start

6. Review the directory where the log files will be stored. By default, this

is:

/var/log/surgient/agent.log

7. Chose whether or not this ESX Host agent will manage any libraries.

Type Y to indicate that this agent will act as a library agent. TypeNto

indicate that this agent will notact as a library agent.

Note: The Surgient library requires an Agent to manage the use of the

library images and files, as well as to facilitate communication

between the VCS, the application, and any client computers.

The agent(s) that manage a library can be on a Windows host or anESX Server host; typically a single agent is selected to manage the

library location(s) for an environment.


68/170


If you select Yes, provide the following information:

Location to create the library: enter the path to connect to the server

and directory that will serve as the library location. This is where images

for your environment will be stored.

Note: The library location must be on a server to which all host servers that

will use images from the library have access. Options to consider

include placing the library location on a SAN (storage area network)

or placing the library location on an NFS (network file system)

server. See Chapter 1 Before You Start for additional

information.

Location of the Images directory: the Images directory is located on

Surgient media, and contains images and files that are necessary for the

configuration of the Surgient environment. When you enter the location

of the Images directory, the agent installation program copies therequired files into the library location that you defined in the previous

step.

Note: If you enter a path for the Images directory, but then see the promptRequired Surgient images were not found at dir/

subdir, this indicates that the required Surgient-supplied images

are not in the location you entered for the Images directory. If the

Surgient media files are not local, you can use the UNIX mount

command to mount a remote NFS volume or a remote UNC (Samba)

shared directory containing the Surgient-supplied images.

8. Select the volume on the VM host computer where the VMs used in

your environment will be created. Type 1 and press Enter to accept the

default as shown.

9. Enter the URL of the mailbox server, using the IP Address of the

computer where you installed VQMS (i.e. http://10.5.11.40/ingress/

mailbox.aspx).

To uninstall the agent from an ESX host server, enter the followingcommand:

rpm -ev esx3-agent

where xxx is the build number associated with the agent that you want to

uninstall, such as 861.


69/170


Installing the VQMS CLI Server

The Surgient VQMS CLI server is an optional component that allows VQMS

users to issue commands and run scripts by way of a CLI environment,

provided they are also using the appropriate command-line client.

The CLI Server is installed by default with the VQMS server. However,certain environments might necessitate installing the CLI Server on a

separate computer.

To install the Surgient VQMS CLI server, perform the following steps:




Run.



70/170


3. Click Custom.



71/170


The amount of disk space required for the installation and the amount of

space available on the currently selected disk are both shown. To view

the amount of space available on your other disks or to specify a different

disk for the installation, clickDisk Space.

5. Ensure that VQMS CLI Server is the only selected check box.

6. Optional: To specify a destination folder other than the default folder ofC:\Program Files\Surgient\VCS, clickBrowse.





servers, specify the one on which the core services have been

installed. These values are recorded on lines 1 and 2 of the pre-install

worksheet.

If you are installing the VQMS CLI server on the same computer as

the VCS, type the name or IP address of the current computer.

The password for the platform administrator. This value is recorded

in line 11 of the pre-install worksheet.


72/170


9. Click Next to view the Verification page.

10. Verify that the VQMS CLI server will be installed according to your

specifications.


page.

11. ClickNext to install the VQMS CLI server.



73/170



Next Steps and Getting StartedNow that you have successfully installed Surgient, identified the LibraryLocation, installed and started the Host Agent(s), you are ready to log on to

the Management Console and deploy a sample application configuration.See Chapter 3, Verifying the Installation, on page 65 for information

about using a sample image to create and deploy an application configura-tion.

Note: Before proceeding to Chapter 3 Verifying the Installation and

verifying your installation, review both Chapter 4, Remote

Access, on page 83 for information about remote access and

enabling communication from a remote computer to a Surgient VM

behind a firewall, and Chapter 5, Advanced Installation and

Administration, on page 107.


74/170



75/170


Verifying the

Installation

To verify that the installation was successful and to get you started with

Surgient, this chapter addresses the following topics:

Quick Start Using the Surgient Sample Image on page 66

Workflow Summary on page 67

Copy the Sample Image into the Library Location on page 67

Launch the Surgient Management Console on page 68

Add a Library Location on page 69

Create Network Resources and Add to Default Resource Pool on page

70

Assign the Host to the Default Pool on page 74

Creating a Server Configuration on page 76

Creating an Application Configuration on page 78

Deploying a Sample Configuration on page 79

Connecting to the Deployed Configuration on page 80

Launching the Application on page 80

3


76/170


Quick Start Using the Surgient Sample Image

The instructions in this chapter are streamlined for deploying the sample

image included in the installation media, as a way to both test your

installation and to help you become familiar with the basic work flow.

Refer to Workflow Summary on page 67 for an over view of each of thetasks.

More detailed instructions about each of the tasks in this chapter is

documented in the Management Console online Help. After completing the

tasks in this chapter using the Surgient sample image, and when you are

ready to build and deploy your full environment, it is important to refer to the

complete instructions in the Management Console online Help.

To access the online Help, open the Management Console and click Help on

the upper right of the graphical user interface.


77/170


Workflow Summary

The following steps are required to configure the environment in preparation

for deploying the sample application configuration:

Copy Surgient sample image files into the Templates directory in the

library location that was defined during the Agent installation process.(See Installing Surgient Agents on page 49 for more information.)

Launch the Management Console and complete the following tasks:

Add the library location, specifying the same server and location that

you defined during the Agent installation process.

Create and add new network resources (at minimum, an IP address

and a MAC address) to the default pool

Assign the new host (on which you installed the Agent) to the defaultpool

Create a server configuration

Create an application configuration

Deploy the application configuration and access the remote desktop

session

Copy the Sample Image into the LibraryLocation

To add the sample image to your system library location, perform the

following steps:

1. Log on to the computer on which the Surgient Agent that will act as the

library agent is installed.

2. Navigate to the directory that was defined as the library location during

the Agent installation. (See Installing Surgient Agents on page 49 for

more information.)

3. Copy the sample image files (SurgientImageSample.iso, and either

SurgientImageSample.vhd for a MSVS host or


78/170


SurgientImageSample.vmdk for a VMware EX host) from the Surgient

media into the Templates subdirectory of the library location.

Launch the Surgient Management Console

After you install Surgient, begin the setup process by logging on to theSurgient Management Console

Note: Verify the Agent you installed on the VM host server is running. To

do so in a Windows environment, view the Services panel to confirm

that the Surgient Guest Agent is started. In an ESX environment, use

the ps -ef command and locate an entry forsurgientagent. To

start the Agent on ESX, use the command /etc/init.d/

surgientagent start.

To access the Surgient Management Console in Microsoft Internet Exploreror Mozilla Firefox, type the following URL in the web browser address bar:

http:///console

where is the name or IP address of the server on which you

installed the Management Console in Product Installation on page 23.

When the Log On panel opens, enter the user name (by default the user name

is admin) and the platform administrator password that you created during

the installation process.

Note: Before clicking Log On to open the Management Console for the

first time, see the Testing Your Web Browser on page 69.


79/170


Figure 4 Log On Panel

Testing Your Web Browser

Before logging on to the Management Console, Surgient recommends that

you test your web browser. To do so, click the See if your browser is ready

link on the Log On panel.

The Surgient Web Browser and Connectivity Test launches and runs several

tests. As each of the tests are completed, a mes

Documents

Surgient Install 54