Install

Installation and Configuration Guide

Citrix® Provisioning Services™ 5.6May 2010Revision 1

Provisioning Services: Copyright and Trademark NoticesUse of the product documented herein is subject to your prior acceptance of the End User License Agreement. Aprintable copy of the End User License Agreement is included with your installation media.

Information in this document is subject to change without notice. Companies, names, and data used in examples hereinare fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by anymeans, electronic or mechanical, for any purpose, without the express written permission of Citrix Systems, Inc.

© 2010 Citrix Systems, Inc. All rights reserved.

The following are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in theUnited States Patent and Trademark Office and in other countries:

Branch Repeater™, Citrix®, Citrix Access Essentials™, Citrix Access Gateway™, Citrix DesktopReceiver™, Citrix Desktop Server™, Citrix EasyCall™, Citrix Essentials™, Citrix MerchandisingServer™, Citrix Provisioning Server™, Citrix Receiver™, Citrix Repeater™, Citrix StreamingServer™, Citrix Subscription Advantage™, Citrix Workflow Studio™, Citrix XenApp™, Dazzle™,EdgeSight®,HDX™, ICA®, NetScaler®,Request Switching®, StorageLink™, VPX™, WANScaler™,XenDesktop™, XenServer™, Xen Data Center™, Xen Source™

All other trademarks and registered trademarks are the property of their respective owners.

Document code: May 6 2010 16:20:54

Contents

1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7What’s New in This Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Administration and Manageability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Removed Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Provisioning Services and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Provisioning Services Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Getting Service and Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Getting the Subscription Advantage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11Locating the Citrix Developer Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Participating in Citrix Education and Training. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

2 Installing and Configuring Provisioning Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Installation Wizards and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Citrix Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Provisioning Services Installation Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Provisioning Services Console Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Master Target Device Installation Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Provisioning Services Imaging Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Installation and Configuration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

MS SQL Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Authentication and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Reviewing System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Map out Your Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Getting Product Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Installing the license server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Installing Provisioning Services Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Silent Product Software Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

Configuring the Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Configuration Wizard Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Starting the Configuration Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Network Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Identify the Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Identify the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Create a New Store for a New Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Identify the Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Select the License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Configure User Account Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Select network cards for the Stream Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Configure Bootstrap Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Running the Configuration Wizard Silently. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Prerequisite. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35To Create the ConfigWizard.ans File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36To Copy and Modify the ConfigWizard.ans File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36To Run the ConfigWizard.exe Silently. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Adding Additional Provisioning Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Managing Administrative Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Preparing a Master Target Device for Imaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Preparing the Master Target Device's hard disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38Configuring a Master Target Device's BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39

Configuring network adapter BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .39Installing Master Target Device software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40To install Provisioning Services target device software on a Windows device. . . . . . . .41To install Provisioning Services target device software on a Linux device. . . . . . . . . . . .41

Using the Imaging Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Assigning vDisks to Target Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Uninstalling Product Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

Uninstalling the Provisioning Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Uninstalling Windows Target Device Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Uninstall Linux Target Device Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46

3 Installing and Configuring Embedded Target Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48To install Embedded Target Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48To un-install the Embedded Target Device package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Windows XP Embedded Build Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49To set up your embedded target device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52To create an image of your embedded target device disk on the vDisk. . . . . . . . . . . . . . . . . . . .53

Contents

4 Upgrading from Previous Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55Upgrade Utilities and Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Upgrading from Previous Releases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

Backing up Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Upgrading Provisioning Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Upgrading the vDisk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

Boot VHD formatted vDisks in Private Image mode.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Upgrade target device product software on a Master Target Device. . . . . . . . . . . . .57

Migrating the Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5 Managing Multiple Network Interface Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .61Requirements and Considerations for Manufacturer's NIC Teaming. . . . . . . . . . . . . . . . . . . . . . . 62Requirements and Considerations for Provisioning Services NIC Failover. . . . . . . . . . . . . . . . 62

6 Managing Bootstrap Files and Boot Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Configuring the Bootstrap File From the Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Configuring the Bootstrap File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Using the Manage Boot Devices Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .70

Configuring Boot Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71Configuring the BIOS Embedded Bootstrap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

Configuring the BIOS-Embedded Bootstrap Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73General Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Target Device IP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Server Lookup Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Options Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

A Upgrading vDisks Using Hyper-V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Upgrading vDisks using Hyper-V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

B Upgrading vDisks Using Reverse Imaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Upgrading vDisks Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Manual Upgrade Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Automate the Upgrading of vDisks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82

Automated Inline Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Automated Rolling Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Automated Rolling Upgrade with USB Key. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

Provisioning Services | TOC | v

Image Back to Master Target Devices Hard Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Image Back to the Original Hard Drive from Which the vDisk was Created. . . . . . . . . .87Image back using an unformatted, uninitialized hard-disk drive. . . . . . . . . . . . . . . . . . . . . . .87Uninstall Product Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88Install Master Target Device Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88Imaging the Hard Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88Boot from the vDisk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

Contents

Chapter 1

Introduction

Topics:• What’s New in This Release

• Provisioning Services andResources

The information included in this product introduction includes

w What’s New in This Release on page 8

w Provisioning Services and Resources on page 9

What’s New in This ReleaseThis section identifies new features and enhancements that are associated with thisrelease.

Administration and ManageabilityThe following administration and management features and enhancements have beenimplemented in this release:

Image Management

w vDisk Imaging Wizard; automates vDisk creation procedures from the master targetdevice such as, connecting to the farm, creating the vDisk file and imaging.

Note: For details, refer to the Using the Imaging Wizard section in theAdministrator's Guide.

Store Management

w A default store can now be created when the Configuration Wizard runs.

Note: The wizard only allows a server to create or join an existing store if it is newto the database.

w New store path configuration settings are now validated.

Note: For details, refer to the Store Properties section in the Administrator's Guide.

w By enabling the new Managed Store feature in the Console, a SANs read-only LUNs,which are used for vDisk storage, can now be concurrently accessed by multipleProvisioning Servers without having to deploy solutions such as NAS Gateway, ClusterFile System, and Windows Cluster Services. After enabling the Managed Storefeature, administrators can quickly change a store's availability on a SAN volume tobe either active (Active Mode/read-only) or offline (Maintenance Mode/read/write).

Note: For details, refer to the Working with Managed Stores section in theAdministrator's Guide.

High Availability Management

w MS SQL Database Mirroring is now supported by Provisioning Services.

Note: For details, refer to the Database Mirroring section in the Administrator'sGuide.

w New load balancing algorithms provide for more robust and dynamic load balancingof vDisks between qualified Provisioning Servers.

Target Device Management

Chapter 1 8 | Provisioning Services | Introduction

w Auto-Add Target Device Wizard

• The new Auto-Add wizard automates the configuration of rules for automaticallyadding new target devices to the Provisioning Services database.

• Expanded target device naming capabilities.

Note: Refer to Using the Auto-Add Wizard section in the Administrator's Guide.

Active Directory Management

w Support for Cross Forest Active Directory deployment is now supported.

Product Installation

w Ability to simplify large farm deployment with scripted server configuration.

Other Enhancements

w Support for 10 GigE networking and jumbo packets.

Removed FeaturesThe following product feature was removed in this release:

w Port Blocker

Provisioning Services and ResourcesThe following services and resources are available to support Provisioning Services.

w Provisioning Services Documentation

w Getting Service and Support

w Getting the Subscription Advantage

w Locating the Citrix Developer Network

w Participating in Citrix Education and Training

Provisioning Services DocumentationThe following identifies the documentation that is available to support ProvisioningServices. All supporting documentation assumes that Provisioning Servicesadministrators are knowledgeable about networking components and administration,and that device operators are familiar with networking concepts.

The majority of product documentation is provided as Adobe Portable DocumentFormat (PDF) files. To view, search, and print PDF documentation, you need to haveAdobe Reader 5.0.5 with Search, or a more recent version. You can download theseproducts for free from Adobe System’s Web site at http://www.adobe.com/

Provisioning Services | Installation and Configuration Guide | 9

http://www.adobe.com/

Most PDF product documentation, including knowledge-based topics and white papers,are accessible from the Citrix Knowledge Center, http://support.citrix.com/.

Citrix Product Licensing Documentation

For Citrix product licensing documentation, refer to Licensing Your Product under theTechnologies section.

Release Notes

This document contains important product information and is intended to be read first.Contents include information on new product features, enhancements, and knownproduct issues as well as late additions that were not included in the other productdocumentation.

The release notes are accessible from:

w Citrix Knowledge Center: http://support.citrix.com/

w Product installation CD-ROM, when the installation executable is run.

w Programs directory, after completing the product installation: Start>AllPrograms>Citrix Provisioning Services>Provisioning Services Release Notes

Programmer’s Guides

Administrator’s with the appropriate privileges can use any of the following guides tomanage your implementation from command lines.

w MCLI Programmer’s Guide

w SOAP Server Programmer’s Guide

w PowerShell Programmer’s Guide

These guides are available as a PDF and can be accessed from the Citrix KnowledgeCenter: http://support.citrix.com/

Virtual Disk Status Tray Help

The Virtual Disk (vDisk) Status Tray help is available to aid in the management andtroubleshooting of vDisks on target devices.

This help system is assessable from the Help menu on the Virtual Disk Status Tray.

XenConvert Documentation

The XenConvert Guide is available as a PDF and can be accessed from the CitrixKnowledge Center: http://support.citrix.com/.

Finding Additional Documentation

From the Help menu or product installation directory, the following additionaldocumentation is available for optional Provisioning Services utilities:

w Boot Device Manager (BDM.hlp)


http://support.citrix.com/

http://support.citrix.com/proddocs/index.jsp?lang=en&topic=/infocenter/ic-how-to-use.html




w BOOTPTab Editor (BPEDIT.hlp)

w BOOTP (BNBOOTP.hlp)

Getting Service and SupportCitrix provides technical support primarily through the Citrix Solutions AdvisorsProgram. Contact your supplier for the first-line support or check for your nearestSolutions Advisor. In addition to the Citrix Solutions Advisors Program, Citrix offers avariety of self-service, Web-based technical support tools from its Knowledge Centerat: http://support.citrix.com/

The Knowledge Center feature includes:

w A knowledge base containing thousands of technical solutions to support your Citrixenvironment.

w An online product documentation library.

w Interactive support forums for every Citrix product.

w Blogs and communities.

w Access to the latest hotfixes and service packs.

w Security bulletins.

w Additional resources are available to customers with valid support contracts,including online problem reporting and tracking.

w Citrix Live Remote Assistance. Using Citrix’s remote assistance product, GoToAssist,a member of our support team can view your desktop and share control of yourmouse and keyboard to get you on your way to a solution.

Another source of support, Citrix Preferred Support Services, provides a range ofoptions that allows you to customize the level and type of support for yourorganization’s Citrix products.

Getting the Subscription AdvantageSubscription Advantage gives you an easy way to stay current with the latest server-based software functionality and information. Not only do you get automatic deliveryof feature releases, software upgrades, enhancements, and maintenance releases thatbecome available during the term of your subscription, you also get priority access toimportant Citrix technology information.

You can find more information on the Citrix Web site (http://www.citrix.com/) byselecting Subscription Advantage from the Support menu.

You can also contact your Citrix sales representative or a member of the CitrixSolutions Advisors Program for more information.



http://www.citrix.com/

Locating the Citrix Developer NetworkThe Citrix Developer Network (CDN) is at: http://www.citrix.com/cdn/

This enrollment membership program provides access to developer toolkits, technicalinformation, and test programs for software and hardware vendors, system integrators,and corporate IT developers who incorporate Citrix computing solutions into theirproducts.

Note: There is no cost associated with enrolling with the Citrix Developer Network.

Participating in Citrix Education and TrainingThe following identifies the documentation that is available to support ProvisioningServices. All supporting documentation assumes that Provisioning Servicesadministrators are knowledgeable about networking components and administration,and that device operators are familiar with networking concepts.

The majority of product documentation is provided as Adobe Portable DocumentFormat (PDF) files. To view, search, and print PDF documentation, you need to haveAdobe Reader 5.0.5 with Search, or a more recent version. You can download theseproducts for free from Adobe System’s Web site at: http://www.adobe.com/


http://www.citrix.com/cdn/

http://www.adobe.com/

Chapter 2

Installing and Configuring ProvisioningServices

Topics:• Installation Wizards and

Utilities

• Installation andConfiguration Tasks

• Planning

• Getting Product Licensing

• Installing ProvisioningServices Software

• Configuring the Farm

• Adding AdditionalProvisioning Servers

• Managing AdministrativeRoles

• Preparing a Master TargetDevice for Imaging

• Using the Imaging Wizard

• Assigning vDisks to TargetDevices

• Uninstalling Product Software

To create a new Provisioning Services implementation,product software and components are installed from theproduct CD-ROM or as a product download. Both the productCD-ROM and download contain the following installationwizards and product utilities:

w Getting Product Licensing on page 24

w Provisioning Services Installation Wizard on page 14

w Provisioning Services Console Wizard on page 14

w Master Target Device Installation Wizard on page 14

w Upgrade Wizard on page 15

Installation Wizards and UtilitiesCitrix Licensing

CTX_Licensing.msi installs the Citrix licensing software on a server that cancommunicate with Provisioning Servers within your implementation.

Provisioning Services Installation WizardRun PVS_Server.exe or PVS_Server_x64.exe to install the following ProvisioningServices’ components within a farm:

w Provisioning Services Stream Service

w Network Boot Services

w Configuration Wizard (runs after the installation wizard to configure installedcomponents and creates the Provisioning Services database)

w Programming Utilities

w Provisioning Services Console (also available as a separate, standalone installer)

w Boot Device Manager (BDM)

Note: Installing from a UNC path is not supported.

Provisioning Services Console WizardRun PVS_Console.exe or PVS_Console_x64.exe to install the Console, which alsoincludes the Boot Device Mangement utility, on machines that do not have theProvisioning Services software installed (Provisioning Services software includes theConsole installation). The Console can be installed on any machine that cancommunicate with the Provisioning Services database.

Master Target Device Installation WizardFor Windows: PVS_Device.exe or PVS_Device_x64.exe

Linux Target Device Software: PVS_LinuxDevice.run or PVS_LinuxDevice_x64.run

Installs the target device software on a Master Target Device. The Master Target Deviceis used to create the ‘golden image,’ which is then saved to a vDisk file using theXenConvert utility for Windows devices, or using image.sh for Linux devices.XenConvert and image.sh install with the respective target device software.

Chapter 2 14 | Provisioning Services | Installing and Configuring Provisioning Services

Provisioning Services Imaging WizardThis wizard, which runs on the target device, automates the process of creating avDisk, including formatting, image copy, and entry of the target device into theProvisioning Services database.

Upgrade WizardThe Upgrade Wizard facilitates the automation of the upgrade process, and includesthe following utilities:

w The UpgradeAgent.exe runs on the target device to upgrade previously installedproduct software.

w The UpgradeManager.exe runs on the Provisioning Server to control the upgradeprocess on the target device.

Installation and Configuration TasksInstalling and configuring Provisioning Services requires completing the following majortasks:

1. Planning on page 15

2. Getting Product Licensing on page 24

3. Installing Provisioning Services Software on page 25

4. Configuring the Farm on page 26 on a server (in a new farm, the wizard can beused to create the new farm, define the default store and site to use, as well asidentify the license server and Provisioning Server database)

5. Adding Additional Provisioning Servers on page 37 to the farm.

6. Managing Administrative Roles on page 37 within the farm.

7. Preparing a Master Target Device for Imaging on page 38

8. Using the Imaging Wizard on page 42 on a master target device, which connectsto the farm to create and format the vDisk file, then images the device to that file.

9. Assigning vDisks to Target Devices on page 45.

PlanningThe following prerequisite steps must be completed prior to installing and configuringyour implementation:

w MS SQL Database on page 16

w Authentication and Configuration on page 16


w Reviewing System Requirements on page 18

w Map out Your Farm on page 24

MS SQL DatabaseSelect which of following MS SQL 2005 or MS SQL 2008 Server editions to use for theProvisioning Services Database:

w SQL Server Express Edition

w SQL Server Workgroup Edition

w SQL Server Standard Edition

w SQL Server Enterprise Edition

Note: In some production environments, your database administrator may prefer tocreate a Provisioning Services database for you. In this case, provide the MS SQLdatabase administrator with the file created using the DbScript.exe utility, which isinstalled with the Provisioning Services software.

Authentication and ConfigurationProvisioning Services uses Windows authentication. All Provisioning Services’components, including the Configuration Wizard and services that access the database,must run in the context of the logged-in user.

Services, such as the Stream Process and SOAP Server, need to have the userspecifically configured with minimal privileges.

Note:Provisioning Services supports Windows authentication as is recommended byMicrosoft.

Microsoft SQL Server authentication is not supported, except when running theConfiguration Wizard.

Configuration Wizard User Permissions

The following MS SQL permissions are required for the user that is running theConfiguration Wizard:

w dbcreator; required for creating the database

w securityadmin; required for creating the SQL logins for the stream and soap services

If the user does not have sufficient SQL privileges, a dialog prompts for a SQL Serveruser that has the appropriate permissions (dbcreator and securityadmin).


If using MS SQL Express in a test environment, you can choose to provide the user thatis running the Configuration Wizard sysadmin privileges (the highest database privilegelevel).

Note: Alternatively, if the database administrator has provided an empty database, theuser running the Configuration Wizard must be the owner of the database and havethe "View any definition permission" (these settings are set by the databaseadministrator when the empty database is created).

Service Account Permissions

The user context for the Stream and Soap services requires the following databasepermissions:

w db_datareader

w db_datawriter

w execute permissions on stored procedures

Note: The Configuration Wizard assigns these permissions provided the user hassecurityadmin permissions.

In addition, the service user must have the following system privileges:

w Run as service

w Registry read access

w Program Files\Citrix\Provisioning Services

w Read/write access to any vDisk location

Determine which of the following supported user accounts the Stream and Soapservices will run under:

w Network service account

Minimum privilege local account that authenicates on the network as computersdomain machine account.

w Specified user account (required when using a Windows Share)

Workgroup or domain user account.

w Local system account (for use with SAN)

Because authentication is not common in workgroup environments, minimal privilegeuser accounts must be created on each server, and each instance must have identicalcredentials (i.e. password).

Caution: Installing SQL Server and Provisioning Services on the same servercan cause poor distribution during load balancing. It is highly recommended that theydo not co-exist on the same server.


Determine the appropriate security option to use in this farm (only one option can beselected per Farm and the selection you choose impacts Role Based Administration andUser Groups).

w Use Active Directory groups for security (default); select this option if on aWindows Domain running Active Directory. This option enables you to leverageActive Directory for Provisioning Services’ roles.

w Use Windows groups for security; select this option if you are on a single server orin a Workgroup. This option enables you to leverage the Local User/Groups on thatparticular server for Provisioning Services’ roles.

Note: Console users do not directly access the database.

Reviewing System RequirementsConfirm that hardware and software requirements are met.

Provisioning Server OS Requirements

Provisioning Server: Recommended System Requirements

Operating Systems

Provisioning Services English onEnglish, Japanese, German, French,Spanish, Simplified Chinese,Traditional Chinese, Korean, andRussian versions of operating systemsare supported

Windows 2003 Server SP2 (32 or 64-bit); alleditions

Windows 2008 Server (32 or 64-bit); alleditions

Windows 2008 R2 (64-bit); all editions

Provisioning Server System Requirements

In most implementations, there is a single vDisk providing the standard image formultiple target devices. The more target devices using the same vDisk image, the lessvDisks need to be created; making vDisk management easier. In order to have a singlevDisk, all target devices must have certain similarities to ensure that the OS has all ofthe drivers it requires to run properly. The three key components that should beconsistent are the motherboard, network card, or video card.

Disk storage management is very important because a Provisioning Server can havemany vDisks stored on it, and each disk can be several gigabytes in size. Your streamingperformance can be improved using a RAID array, SAN, or NAS.

The table that follows includes Provisioning Server recommended system requirements.



Processor Intel or AMD x86 or x64 compatible; 2 GHz minimum; 3GHz preferred; 3.5 GHz Dual Core/HT or similar forloads greater than 250 target devices.

Memory Minimum of 2 GB RAM; 4 GB preferred; 4 GB is requiredfor a larger number of vDisks (greater than 250).

Hard Disk and Storage There must be enough space on the hard disk to storethe vDisks. For example, if you have a 15 GB harddrive, you can only create a 14 GB vDisk

Additional requirements depend on several factors suchas:

Hard disk capacity requirement of the operatingsystem and applications running on a target device. Itis recommended to add 20% on the base size of thefinal installed image.

Private Image Mode - number of target devices using avDisk in Private Image mode (vDisks in Private Imagemode should be backed up daily)

Standard Image Mode - number of target devices usinga vDisk in Standard Image mode.

Note: Best practices include making a copy of everyvDisk created.

Windows 2003 and 2003 x64; minimum of 250 MB on theapplication drive.

Minimum Common Storage Sizes

w 250 MB for the database

w 5 GB on a clean Windows system

w 5 GB per vDisk for Linux Class images

w 15 GB per vDisk for Vista Class images (estimated)

Additional space per vDisk based on additionalsignificant applications loaded.

Network Adapter Static IP

Minimum 100 MB Ethernet, 1 GB Ethernet preferred;Dual 1 GB Ethernet for more than 250 target devices.



Note: Two NICs often perform better than a single dual-ported NIC.

Network Requirements

Provisioning Server: Recommended Network Requirements

UDP and TCP PortRequirements

Provisioning Server to Provisioning ServerCommunication

Each Provisioning Server must be configured to use thesame ports (UDP) in order to communicate with eachother (uses the Messaging Manager). At least five portsmust exist in the port range selected. The port range isconfigured on the Stream Services dialog when theConfiguration Wizard is run.

The default range for the first port in the range is UDP6905 and the last port is 6909.

Provisioning Servers to Target Device Communication

Each Provisioning Server must be configured to use thesame ports (UDP) in order to communicate with targetdevices (uses the StreamProcess). The port range isconfigured using the Console’s Network tab on theServer Properties dialog.

The default ports include:

UDP 6910, 6911, 6912, 6913, 6914, 6915, 6916, 6917,6918, 6919, 6920, 6921, 6922, 6923, 6924, 6925, 6926,6927, 6928, 6929 and 6930.

Login Server Communication

Each Provisioning Server that will be used as a loginserver must be configured on the Stream Servers BootList dialog when the Configuration Wizard is run.

The default port for login servers to use is UDP 6910

Console Communication

The Soap Server is used when accessing the Console.The ports (TCP) are configured on the Stream Servicesdialog when the Configuration Wizard is run.


Provisioning Server: Recommended Network Requirements

The default ports are TCP 54321 and 54322 (ProvisioningServices automatically sets a second port byincrementing the port number entered by 1; 54321 + 1).

If this value is modified, the following command mustbe run.

For Powershell: MCLI-Run SetupConnection

For MCLI: MCLI Run SetupConnection

(refer to the Provisioning Server Programmers Guidesfor details).

TFTP Communication

The TFTP port value is stored in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BNTFTP\Parameters Port

The TFTP port defaults to UDP 69.

TSB Communication

The TSB port value is stored in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PVSTSB\Parameters Port

The TSB port defaults to UDP 6969.

Port Fast Port Fast must be enabled.

Network Card PXE 0.99j or greater.

Network Addressing DHCP

Target Device Requirements

Note: Dual boot vDisk images are not supported.

Target devices are identified by the operating system that runs on that device. Thefollowing table lists the supported operating systems for target devices.

Windows Target Device

(32 or 64 bit)

Windows Server 2003 SP1 (32 or 64-bit); all editions

Windows Server 2008 (32 or 64-bit); all editions


Provisioning ServicesEnglish on English,Japanese, German,French, Spanish,Simplified Chinese,Traditional Chinese,Korean, and Russianversions of operatingsystems are supported.

Windows Server 2008 R2 (64-bit); all editions

Windows XP Professional (32 or 64-bit)

Windows Vista (32 or 64-bit)

w Business

w Enterprise

w Ultimate (retail licensing)

Windows 7 (32 or 64-bit)

w Business

w Enterprise


Notes: The Ultimate editions of Microsoft Vista andWindows 7 are only supported in Private Image mode.

Windows Vista Business and Enterprise and WindowsServer 2008 are deployed with Microsoft MultipleActivation Key (MAK) or Key Management Server (KMS)volume licensing keys. MAK is only supported in PrivateImage mode. KMS is supported in both Private andStandard Image Mode.

Supported File SystemTypes

NTFS

Linux Target Devices Red Hat (x86 and x86_64 architecture)RHEL 4, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6 and 4.7RHEL 5, 5.1, 5.2 and 5.3

Novell (x86 and x86_64 architecture)SuSE Linux Enterprise Server 9 x86 onlySuSE Linux Enterprise Server 9.1 x86 onlySuSE Linux Enterprise Server 9.2 x86 onlySuSE Linux Enterprise Server 9.4 x86 onlySuSE Linux Enterprise Server 10SuSE Linux Enterprise Server 10 SP1SuSE Linux Enterprise Server 10 SP2

SuSE Linux Enterprise Desktop 10SuSE Linux Enterprise Desktop 10 SP1SuSE Linux Enterprise Desktop 10 SP2

Novell Linux Desktop 9.0 x86 onlyNovell Linux Desktop 9.1 x86 only


Novell Linux Desktop 9.3 x86 onlyNovell Linux Desktop 9.4 x86 only

Turbo Linux FUJI 11

Vine Linux

Vine Linux 4.0 x86 onlyVine Linux 4.1 x86 onlyVine Linux 4.2 x86 only

Ubuntu Linux

Support is available for only those kernels that ship withthe Linux distribution releases listed above, and anysubsequent service pack releases.

x86-based Linux; RAM cache size is limited to less than 1GB when using Shared Image vDisk mode. Actual limit ofRAM cache size decides on kernel's virtual address space.Set the value of RAM cache size, then minus the spaceneeded to map the kernel code itself. This limitation ison the Linux architecture.

Provisioning Services Console Requirements

The table that follows lists Console requirements.


Processor Minimum 1 GHz, 2 GHz preferred

Memory Minimum 1 GB, 2 GB preferred

Hard Disk Minimum 500 MB

Operating System Windows Server 2003 (32 or 64-bit); alleditionsWindows Server 2008 (32 or 64-bit); alleditionsWindows 2008 R2 (64-bit); all editionsWindows XP Professional (32 or 64-bit)Windows Vista (32 or 64-bit)

w Business

w Enterprise




Other Required: MMC 3.0

Optional: Adobe Acrobat Reader highlyrecommended.

Map out Your FarmBefore attempting to install and configure Provisioning Services, it is important to firstmap out your farm and note the information that will be requested during theinstallation and configuration process.

Complete the sections that follow to create a map of your farm.

Provisioning Services Database

Only one database is associated with a farm. You can choose to install the ProvisioningServices database software on:

w An existing SQL database; if that machine can communicate with all ProvisioningServers within the farm.

w A new SQL Express database machine, created using the SQL Express software,which is free from Microsoft.

Database server

Host Name:

Instance Name:

License server

Host Name:

Vendor Daemon / license server port:

Getting Product LicensingThe Citrix License Server must be installed on a server within the farm that is able tocommunicate with all Provisioning Servers within the farm.

Consider the following options when deciding which server to use as the license server:

w Single System: Same system as Provisioning Services; for evaluations, test labs, orimplementations with one Citrix product.

w Stand-alone: Separate system that has an existing license server installed; for largerimplementations or implementations using multiple Citrix products.

w Point to an existing license server.


Installing the license serverDownload or run CTX_Licensing.msi from the Product Installation CD-ROM.

Note: If Provisioning Services is installed after the license server or if new licensesare added, the Stream Service must be restarted.

For product licensing documentation, open Citrix eDocs , expand the Technologiessection, and then select Licensing Your Product .

Installing Provisioning Services SoftwareInstall any Windows service packs, drivers, and updates before installing theProvisioning Services software.

Note:

This installation task is for new Provisioning Services’ implementations. For upgradetasks, refer to Upgrading from Previous Releases on page 55.

The software can also be installed silently. Refer to Silent Product Software Installon page 26

Complete the steps that follow to install the services and applications required tocreate a Provisioning Server.

1. Click on the appropriate platform-specific install option. The Provisioning ServicesWelcome window appears.

2. Click Next. The Product License Agreement appears.

3. Scroll to the end to accept the terms in the license agreement, then click Next tocontinue. The Customer Information dialog appears.

4. Type or select your user name and organization name in the appropriate textboxes, then click Next. The Destination Folder dialog appears.

5. Click Change, then enter the folder name or navigate to the appropriate folderwhere the software should be installed, or click Next to install ProvisioningServices to the default folder. The Setup Type dialog appears.

6. Select the radio button that best describes the installation to perform:

• Complete - Installs all components and options on this computer (default).

• Custom - Choose which components to install and where to install thosecomponents.

Note: Installing the Network Boot Services does not activate them. If uncertainabout the need for any of these services, choose the Complete installation option.


http://support.citrix.com/proddocs/index.jsp?lang=en&topic=/infocenter/ic-how-to-use.html

7. Click Next.

8. If you select Complete, the ‘Ready to Install the Program’ dialog appears.If you selected Custom, the ‘Custom Setup’ dialog appears. This dialog provides a‘Feature Description’ text box that provides a description for the selectedcomponent as well as the space required to install that component.

• Expand each component icon and select how that component is to be installed.

• After making component selections, click Next. The ‘Ready to Install theProgram’ dialog appears. Or, click Cancel to close the wizard without makingsystem modifications.

9. On the ‘Ready to Install the Program’ dialog, click Install to continue with theinstallation process (the installation may take several minutes).

10. The ‘Installation Wizard Completed’ message displays in the dialog when thecomponents and options are successfully installed.

Note: The Installation Wizard can be re-run to install additional components at alater time, or re-run on a different computer to install select components on aseparate computer.

11. Click Finish to exit the Installation Wizard. The Provisioning Services ConfigurationWizard automatically opens.

Note: Although Provisioning Services does not require that you restart the server afterinstalling the product software, in some instances, a Microsoft message may appearrequesting a restart. If this message appears, complete Configuring the Farm on page26 using the Configuration Wizard, before restarting the server. If this messageappears and the server is not restarted, the removeable drive may not appear.

Silent Product Software InstallTarget devices, Provisioning Servers, and Consoles can be silently installed to a defaultinstallation directory using the following command:<Installer Name>.exe /s /v"/qn"Or, use the following to set a different destination:

<Installer Name>.exe /s /v"/qn INSTALLDIR=D:\Destination"

Configuring the FarmRun the Configuration Wizard on a Provisioning Server when creating a new farm,adding new Provisioning Servers to an existing farm, or reconfiguring an existingProvisioning Server.

When configuring a Provisioning Server, consider the following:


w All Provisioning Servers within a farm must share the same database to locate vDisksfor target devices on shared storage devices within the farm. If that shared storagedevice is a Windows network share, refer to configuration information described inthe Administrator’s Guide, Managing Network Components section. If that sharedstorage device is a SAN, no additional configuration is necessary.

w To properly configure the network services, be sure that you understand networkservice options and settings.

Note: If all Provisioning Servers in the farm share the same configuration settingssuch as site and store information, consider Running the Configuration Wizard Silentlyon page 35.

Configuration Wizard SettingsBefore running the Configuration Wizard, be prepared to make the following selections:

Note: The Configuration Wizard can also be run silently on servers that share simularconfiguration settings. For details, refer to Running the Configuration Wizard Silentlyon page 35.

w Network Topology on page 28

w Identify the Farm on page 28

w Identify the Database on page 30

w Identify the Site on page 31

w Select the License Server on page 31

w Select network cards for the Stream Service on page 32

w Configure Bootstrap Server on page 33

Note: If errors occur during processing, the log is written to a ConfigWizard.log file,which is located at C:\Documents and Settings\All Users\ProgramData\Citrix\Provisioning Services.

Starting the Configuration WizardThe Configuration Wizard starts automatically after Provisioning Services software isinstalled. The wizard can also be started by selecting:

1. Start>All Programs>Citrix>Provisioning Services>Provisioning ServicesConfiguration Wizard

2. After starting the Configuration Wizard, click Next to begin the configuration tasksthat follow.


Note: When running the Configuration Wizard, the tasks that appear depend onthe network service options that are selected and the purpose for running the wizard.

Network TopologyComplete the network configuration steps that follow.

1. Select the network service to provide IP addresses

Note: Use existing network services if possible. If for any reason existing networkservices can not be used, choose to install the network services that are madeavailable during the installation process.

To provide IP addresses to target devices, select from the following networkservice options:

• If the DHCP service is on this server, select the radio button next to one of thefollowing network services to use, then click Next:

w Microsoft DHCP

w Provisioning Services BOOTP service

w Other BOOTP or DHCP service

• If the DHCP service is not on this server, select the radio button next to Theservice is running on another computer, then click Next.

2. Select the network service to provide PXE boot information

Each target device needs to download a boot file from a TFTP server.

Select the network service to provide target devices with PXE boot information:

• If you choose to use this Provisioning Server to deliver PXE boot information,select The service that runs on this computer, then select from either of thefollowing options, then click Next:

w Microsoft DHCP (options 66 and 67)

w Provisioning Services PXE Service

• If Provisioning Services will not deliver PXE boot information, select Theinformation is provided by a service on another device option, then clickNext.

Identify the FarmSelect from the following farm options:

• Farm is already configured


Select this option to reconfigure an existing farm, then continue on to the“Configure user account settings” procedure. This option only appears if a farmalready exists.

• Create farm

i. On the Farm Configuration dialog, select the Create Farm radio button tocreate a new farm, then click Next.

ii. Use the Browse button to browse for existing SQL databases and instances inthe network, or type the database server name and instance. Optionally, entera TCP port number to use to communicate with this database server.

iii. To enable database mirroring, enable the Specify database mirror failoverpartner option, then type or use the Browse button to identify the failoverdatabase server and instance names. Optionally, enter a TCP port number touse to communicate with this server.

Note: Refer to Database Mirroring for more information.

iv. Click Next to continue on to the “Identify the Database on page 30” procedure.

• Join existing farm

i. On the Farm Configuration dialog, select the Join Existing Farm radio button toadd this Provisioning Server to an existing farm, then click Next.

ii. Use the Browse button to browse for the appropriate SQL database andinstance within the network.

iii. Select the farm name that displays by default, or scroll to select the farm to join.

Note: More than one farm can exist on a single server. This configuration iscommon in test implementations.

iv. To enable database mirroring, enable the Specify database mirror failoverpartner option, then type or use the Browse button to identify the failoverdatabase server and instance names. Optionally, enter a TCP port number touse to communicate with this server.

Note: Refer to Database Mirroring for more information.

v. Click Next.

vi. Select from the following site options, then click Next:

• Existing Site: Select the site from the drop-down menu to join an existing site.

• New Site: Create a site by typing the name of the new site and a collection.

Continue on to Configure User Account Settings on page 32 procedure.


Identify the DatabaseOnly one database exists within a farm. To identify the database, complete the stepsthat follow.

1. Select the database locationIf the database server location and instance have not yet been selected, completethe following procedure.

a. On the Database Server dialog, click Browse to open the SQL Servers dialog.

b. From the list of SQL Servers, select the name of the server where this databaseexists and the the instance to use (to use the default instance, SQLEXPRESS,leave the instance name blank). In a test environment, this may be a stageddatabase.

Note: When re-running the Configuration Wizard to add additionalProvisioning Servers database entries, the Server Name and Instance Nametext boxes are already populated. By default, SQL Server Express installs asan instance named ‘SQLEXPRESS’.

c. Click Next. If this is a new farm, continue on to the “Defining a Farm” procedure.

2. To change the database to a new database

a. On the old database server, perform a backup of the database to a file.

b. On the new database server, restore the database from the backup file.

c. Run the Configuration Wizard on each Provisioning Server.

d. Select Join existing farm on the Farm Configuration dialog.

e. Enter the new database server and instance on the Database Server dialog.

f. Select the restored database on the Existing Farm dialog.

g. Select the site that the Server was previously a member of on the Site dialog.

h. Click Next until the Configuration Wizard finishes.

3. Define a farm.Type in the following information in the appropriate text boxes, then click Next.

• The name of the database that this farm will use.

• The name to assign to this farm.

• The name of the first site to create within this farm.

• The name of the first target device collection to create in this site.

Continue on to the “Selecting the license server” procedure.


Create a New Store for a New FarmA new store can be created and assigned to the Provisioning Server being configured:

Note: The Configuration Wizard only allows a server to create or join an existing storeif it is new to the database. If a server already exists in the database and it rejoins afarm, the Configuration Wizard may prompt the user to join a store or create a newstore, but the selection is ignored.

1. On the New Store page, name the new Store.

2. Browse or enter the default path (for example: C:\PVSStore) to use to accessthis store, then click Next.If an invalid path is selected, an error message appears. Re-enter a valid path,then continue. The default write cache location for the store is located under thestore path for example: C:\PVSStore\WriteCache.

Identify the SiteWhen joining an existing farm, identify the site where this Provisioning Server is to be amember, by either creating a new site or selecting an existing site within the farm.When a site is created, a default target device collection is automatically created forthat site.

• Create a new site

i. On the Site page, enable the New Site radio button.

ii. In the Site Name text box, type the new site name where this ProvisioningServer is to be a member.

iii. In the Collection Name, accept the default collection, Collection, or create anew default collection name to associate with this Provisioning Server, thenclick Next.

• Select an existing site

i. On the Site page, enable the Existing Site radio button. (The default site nameis Site.)

ii. Select the appropriate site from the drop-down list, then click Next.

iii. Create a new store or select an existing store on the Store page, then clickNext.

Select the License ServerNote: When selecting the license server, ensure that all Provisioning Server’s in thefarm are able to communicate with that server in order to get the appropriate productlicenses.


1. Enter the name (or IP address) and port number of the license server (default is27000). The Provisioning Server must be able to communicate with the licenseserver to get the appropriate product licenses.

2. Optionally, select the checkbox Validate license server version andcommunication to verify that the license server is able to communicate with thisserver and that the appropriate version of the license server is being used. If theserver is not able to communicate with the license server, or the wrong version ofthe license server is being used, an error message displays and does not allow youto proceed.

3. The checkbox Use Datacenter licenses for desktops if no Desktop licenses areavailable enables the license tradeup option and is enabled by default. Optionally,disable this trade up option by clicking on the enabled checkbox (uncheck).

4. Click Next to continue on to the “Configure user account settings” procedure.

Configure User Account SettingsThe Stream and Soap services run under a user account.

1. On the User Account dialog, select the user account that the Stream and Soapservices will run under:

• Specified user account (required when using a Windows Share; workgroup ordomain user account)

Type the user name, domain, and password information in the appropriate textboxes.

• Local system account (for use with SAN)

2. Select the checkbox next to the Configure the database for the account option, ifyou selectedSpecified user account, which adds the appropriate database roles(Datareader and Datawriter) for this user.

3. Click Next, then continue on to the “Selecting network cards for the StreamService” procedure.

Select network cards for the Stream ServiceNote: If multiple network adapters are selected, they must be configured with thesame IP subnet address. For example: IP subnet: 100.100.10.x; IP subnet mask255.255.255.0

1. Select the checkbox next to each of the network cards that the Stream Service canuse.

2. Enter the base port number that management services the default port for that theProvisioning Services’ network services communications in the appropriate text box.


Note: A minimum of 20 ports are required within the range. For largerimplementations, consider allocating additional ports.

3. Select the Soap Server port (default is 54321) to use for Console access, then clickNext.

Continue on to the “Selecting the bootstrap server” procedure.

Configure Bootstrap ServerComplete the steps that follow to identify the bootstrap server and configure thebootstrap file location.

Note: Bootstrap configurations can be reconfigured by selecting the ConfigureBootstrap option from the Provisioning Services Action menu in the Console.

1. Select the bootstrap server.To use the TFTP service on this Provisioning Server:

a. Select the Use the TFTP Service option, then enter or browse for the boot file.The default location is:C:\Documents and Settings\All Users\ProgramData\Citrix\Provisioning Services\Tftpboot

If a previous version of Provisioning Services was installed on this server, andthe default location is:

C:\Program Files\Citrix\Provisioning Services\TftpBoot

You must run the Configuration Wizard to change the default location to:

C:\Documents and Settings\All Users\ProgramData or ApplicationData\Citrix\Provisioning Services\Tftpboot

If the default is not changed, the bootstrap file can not be configured from theConsole and target devices will fail to boot; receiving a ‘Missing TFTP’ errormessage.

b. Click Next.

2. Select Provisioning Servers to use for the boot process:

a. Use the Add button to add additional Provisioning Servers to the list, the Editbutton to edit existing information, or Remove to remove the ProvisioningServer from the list. Use the Move up or Move down buttons to change theProvisioning Server boot preference order.The maximum length for the server name is 15 characters. Do not enter FQDNfor the server name.In an HA implementation, at least two Provisioning Servers must be selected asboot servers.


b. Optionally, highlight the IP address of the Provisioning Server that targetdevices will boot from, then click Advanced. The Advanced Stream ServersBoot List appears.

The following table describes advanced settings that you can choose from. Aftermaking your selections, click OK to exit the dialog, then click Next to continue.

Table 2-1: Advanced Stream Servers Boot List

Verbose Mode Select the Verbose Mode option ifyou want to monitor the bootprocess on the target device(optional) or view system messages.

Interrupt Safe Mode Select Interrupt Safe Mode if you arehaving trouble with your targetdevice failing early in the bootprocess. This enables debugging oftarget device drivers that exhibittiming or boot behavior problems

Advanced Memory Support This setting enables the bootstrap towork with newer Windows OSversionsand is enabled by default.Only disable this setting on older XPor WindowsServer OS 32 bit versionsthat do not support PAE, or if yourtarget device ishanging or behavingerratically in early boot phase.

Network Recovery Method Restore Network Connections—Selecting this option results in thetarget device attempting indefinitelyto restore it's connection to theProvisioning Server.

Note: Because the Seconds field doesnot apply, it becomes inactive whenthe Restore Network Connectionsoption is selected.

Reboot to Hard Drive— (a hard drivemust exist on the target device)Selecting this option instructs thetarget device to perform a hardwarereset to force a reboot after failingto re-establish communications for adefined number of seconds. The userdetermines the number of seconds towait before rebooting. Assuming thenetwork connection can not beestablished, PXE will fail and the


system will rebooot to the local harddrive. The default number of secondsis 50, to be compatible with HAconfigurations.

Logon Polling Timeout Enter the time, in milliseconds,between retries when polling forProvisioning Servers. EachProvisioning Server is sent a loginrequest packet in sequence. The firstProvisioning Server that responds isused. In non-HA configurations, thistime-out simply defines how often toretry the single available ProvisioningServer with the initial login request.

This time-out defines how quicklythe round-robin routine will switchfrom one Provisioning Server to thenext in trying to find an activeProvisioning Server. The valid rangeis from 1,000 to 60,000 milliseconds.

Login General Timeout Enter the time-out, in milliseconds,for all login associated packets,except the initial login polling time-out. This time-out is generally longerthan the polling time-out, becausethe Provisioning Server needs time tocontact all associated servers, someof which may be down and willrequire retries and time-outs fromthe Provisioning Server to the otherProvisioning Servers to determine ifthey are indeed online or not. Thevalid range is from 1,000 to 60,000milliseconds.

c. Verify that all configuration settings are correct, then click Finish.

Running the Configuration Wizard SilentlyRun the Configuration Wizard silently to configure multiple Provisioning Servers thatshare several of the same configuration settings such as the farm, site, and storelocations.

PrerequisiteThe Configuration Wizard must first be run on any Provisioning Server in the farm thathas the configuration settings that will be used in order to create the ProvisioningServices database and to configure the farm.


The basic steps involved in the silent configuration of servers within the farm include:

w Create a ConfigWizard.ans file from a configured Provisioning Server in the farm.

w Copy the ConfigWizard.ans file onto the other servers within the farm, and modifythe IP address in the ConfigWizard.ans file to match each server in the farm.

w Run the ConfigWizard.exe with the /a parameter.

To Create the ConfigWizard.ans File1. Run the ConfigWizard.exe with the /s parameter on a configured server.

2. When selecting farm settings on the Farm Configuration page, choose the Joinexisting farm option.

3. Continue selecting configuration settings on the remaining wizard pages, then clickFinish.

4. Copy the resulting ConfigWizard.ans file from the Provisioning Services ApplicationData directory. The location for this directory varies depending on the Windowsversion. For Windows 2003, use \Documents and Settings\All Users\Application Data\Citrix\Provisioning Services. For Windows 2008and Windows 2008 R2, use \ProgramData\Citrix\Provisioning Services.

To Copy and Modify the ConfigWizard.ans File1. For each server that needs to be configured, copy the ConfigWizard.ans file to the

Provisioning Services Application Data directory.

2. Edit the StreamNetworkAdapterIP= so that is matches the IP of the server beingconfigured. If there is more than one IP being used for Provisioning Services on theserver, add a comma between each IP address.

To Run the ConfigWizard.exe SilentlyTo configure servers, run the ConfigWizard.exe with /a parameter on each server thatneeds to be configured.

Note: To get the list of valid ConfigWizard parameters:

1. Run the ConfigWizard.exe with the /? parameter.

2. Open the resulting ConfigWizard.out file from the ConfigWizard.ans file fromthe Provisioning Services Application Data directory.

3. Scroll down to the bottom of the file to view all valid parameters.

Note: To get the list of valid ConfigWizard.ans commands with descriptions:

1. Run the ConfigWizard.exe with the /c parameter.

2. Open the resulting ConfigWizard.out file from the ConfigWizard.ans file fromthe Provisioning Services Application Data directory.


3. Scroll down to the bottom of the file to view all valid parameters.

Adding Additional Provisioning ServersTo add additional Provisioning Servers, install the Provisioning Services software oneach server that is to a member of the farm. Run the Provisioning Services InstallationWizard, then the Configuration Wizard on each server.

Note: The maximum length for the server name is 15 characters. Do not enter FQDNfor the server name

When the Configuration Wizard prompts for the site to add the server to, choose anexisting site or create a new site.

After adding Provisioning Servers to the site, start the Console and connect to thefarm. Verify that all sites and servers display appropriately in the Console window.

Managing Administrative RolesThe ability to view and manage objects within a Provisioning Server implementation isdetermined by the administrative role assigned to a group of users. ProvisioningServices makes use of groups that already exist within the network (Windows or ActiveDirectory Groups). All members within a group will share the same administrativeprivileges within a farm. An administrator may have multiple roles if they belong tomore than one group.

The following administrative roles can be assigned to a group:

w Farm Administrator

w Site Administrator

w Device Administrator

w Device Operator

After a group is assigned an administrator role through the Console, if a member ofthat group attempts to connect to a different farm, a dialog displays requesting that aProvisioning Server within that farm be identified (the name and port number). You arealso required to either use the Windows credentials you are currently logged in with(default setting), or enter your Active Directory credentials. Provisioning Services doesnot support using both domain and workgroups simultaneously.

When the information is sent to and received by the appropriate server farm, the rolethat was associated with the group that you are a member of, determines youradministrative privileges within this farm. Group role assignments can vary from farmto farm.


Preparing a Master Target Device for ImagingA Master Target Device refers to a target device from which a hard disk image is builtand stored on a vDisk. Provisioning Services then streams the contents of the vDiskcreated from the Master Target Device to other target devices.

w Preparing the Master Target Device's hard disk on page 38

w Configuring a Master Target Device's BIOS on page 39

w Configuring network adapter BIOS on page 39

w Installing Master Target Device software on page 40

Preparing the Master Target Device's hard diskThe Master Target Device is typically different from subsequent target devices becauseit initially contains a hard disk. This is the hard disk that will be imaged to the vDisk. Ifnecessary, after imaging, the hard disk can be removed from the Master Target Device.

In order to support a single vDisk, that is shared by multiple target devices, thosedevices must have certain similarities to ensure that the operating system has allrequired drivers. The three key components that must be consistent include the:

w Motherboard

w Network card, which must support PXE

w Video card

However, the Provisioning Services Common Image Utility allows a single vDisk tosimultaneously support different motherboards, network cards, video cards, and otherhardware devices.

If target devices will be sharing a vDisk, the Master Target Device serves as a‘template’ for all subsequent diskless target devices as they are added to the network.It is crucial that the hard disk of Master Target Device be prepared properly and allsoftware is installed on it in the proper order:

Note: Follow the instructions below after installing and configuring the ProvisioningServer and creating target devices.

Software must be installed on the Master Target Device in the order that follows:

1. Operating System (Windows or Linux)

2. Device Drivers

3. Service Packs Updates

4. Target Device Software

Applications can be installed before or after the target device software is installed. Iftarget devices will be members of a domain, and will share a vDisk, additional


configuration steps must be completed (refer to Managing Domain Accounts in theAdministrator’s Guide, before proceeding with the installation).

Note: Dual boot vDisk images are not supported.

Configuring a Master Target Device's BIOSThe following steps describe how to configure the target devices system’s BIOS and theBIOS extension provided by the network adapter, to boot from the network. Differentsystems have different BIOS setup interfaces – if necessary, consult the documentationthat came with your system for further information on configuring these options.

1. If the target device BIOS has not yet been configured, re-boot the target deviceand enter the system’s BIOS setup. (To get to BIOS setup, press the F1, F2, F10 orDelete key during the boot process. The key varies by manufacturer).

2. Set the network adapter to On with PXE.

Note: Depending on the system vendor, this setting may appear differently.

3. Configure the target device to boot from LAN or Network first. Optionally, selectthe Universal Network Driver Interface; UNDI first, if using a NIC with ManagedBoot Agent (MBA) support.

Note: On some older systems, if the BIOS setup program included an option thatpermitted you to enable or disable disk-boot sector write protection, ensure thatthe option is disabled before continuing.

4. Save changes, then exit the BIOS setup program.

5. Boot the target device from it’s hard drive over the network to attach the vDisk tothe target device.

Configuring network adapter BIOSThis procedure is only necessary for older systems.

1. Re-boot the Master Target Device.

2. Configure the network adapter’s BIOS extension through setup.

During the system boot, the network adapter’s BIOS extension will present aninitialization message similar to the following:

Initializing Intel ® Boot Agent Version 3.0.03 PXE 2.0 Build 078 (WfM 2.0) RPL v2.43Enter the network adapter’s BIOS extension. (Consult the network adapter’sdocumentation.) The key combination for entering the network adapter’s BIOSextension varies by manufacturer. For example, to enter the Intel Boot Agent setupscreen, type Ctrl+S.

A screen similar to the following appears:


3. Change the boot order to Network first, then local drives.

4. Save any changes, and exit the setup program. In the Intel Boot Agent, typing F4saves the changes.

Alternatively, a device can be configured to provide IP and boot information (boot file)to target devices using the Manage Boot Devices utility.

Installing Master Target Device softwareNote: It is recommended that you read the Release Notes document before installingtarget-device software. Before installing the product software on a Master TargetDevice, turn off any BIOS-based-virus protection features. To include anti-virussoftware on the vDisk image, be sure to turn the anti-virus software back on prior torunning XenConvert.

Provisioning Services target device software must be installed on a Master TargetDevice prior to building a vDisk image.

Provisioning Services target device software components include:

w Provisioning Services Virtual Disk, which is the virtual media used to store the diskcomponents of the operating system and applications.

w Provisioning Services Network Stack, which is a proprietary filter driver that isloaded over the NIC driver, allowing communications between the target devicesand the Provisioning Server.

w Provisioning Services SCSI Miniport Virtual Adapter, which is the driver that allowsthe vDisk to be mounted to the operating system on the target device.

w Provisioning Services Imaging Wizard, use to create the vDisk file and image theMaster Target Device.

w XenConvert, use to create an vDisk image from the Master Target Device.

w Virtual Disk Status Tray Utility, to provide general vDisk status and statisticalinformation. This utility includes a help system.

w Target Device Optimizer Utility, used to change target device setting to improveperformance.


Provisioning Services target device software is available for 32-bit and 64-bit Windowsand Linux operating systems.

To install Provisioning Services target devicesoftware on a Windows device

1. Boot the Master Target Device from the local hard disk.

2. Verify that all applications on the device are closed.

3. Double-click on the appropriate installer. The product installation window appears.

4. A dialog displays prompting you to install XenConvert. Click Install to begin theinstallation. Wait until XenConvert installs, than continue on to the next step.

5. On the Welcome dialog that displays, click Next, scroll down to the end, thenaccept the terms of the license agreement.

6. Click Next to continue, the Customer Information dialog appears.

7. Type your user name and organization name in the appropriate text boxes.

8. Select the appropriate install user option. The option you select depends on if thisapplication will be shared by users on this computer, or if only the user associatedwith this computer should have access to it.

9. Click Next, the Destination Folder dialog appears.

10. Click Next to install the target device to the default folder (C:\Program Files\Citrix\Provisioning Services). Optionally, click Change, then either enter the folder nameor navigate to the appropriate folder, and then click Next, then click Install. Theinstallation status information displays in the dialog.

Note: The installation process may take several minutes. While the installationprocess is running, you can click Cancel to cancel the installation and roll-backany system modifications. Close any Windows Logo messages that appear.

11. The "Installation Wizard Completed" message displays in the dialog when thecomponents and options have successfully been installed. Close the wizard window.If both .NET 3.0 SP1 or newer is installed and Windows Automount is enabled, the Using the Imaging Wizard on page 42 will start automatically by default.

12. Reboot the device after successfully installing product software and building thevDisk image.

To install Provisioning Services target devicesoftware on a Linux device

1. Log on to the Linux system as root.


Note: The Linux target device requires root privileges and visual desktop, suchas gnome or KDE to install and execute properly.

2. Insert the product CD-ROM into your Linux target device’s CD-ROM drive. YourLinux target device should auto-mount the CD-ROM and a message should displayon your target device. If your Linux target device doesn’t auto-mount the CD-ROM,consult your Linux system documentation on how to mount CD-ROMs or DVDs.

3. Copy the PVS_LinuxDevice.run or PVS_LinuxDevice_x64.run file from the CD-ROMinto your /tmp directory.

4. Open a terminal shell/command shell and execute the appropriate Linux targetdevice software.

32-bit

# cd /tmp# sh PVS_LinuxDevice.run64-bit

# cd /tmp# sh PVS_LinuxDevice_x64.runThe Terms and Conditions associated with this product license agreement appears.

Accept the license agreement, and then the installer prompts for a directorylocation to install the product software. The /root/citrix directory is recommended.

5. After the Linux utilities are installed to the hard disk, the installer prompts you toreboot your system. You can not begin the imaging phase until the target devicehas been rebooted.

The installer adds an entry into the GRUB boot loader. If GRUB is not used, youmust add the Provisioning Services kernel and initrd into your boot loader:

Kernel: vmlinuz-ardence

(This is a symbolic link which points to your distribution’s kernel)

Initrd: initrd-ardence

The boot loader prompts you with the Image target device option. Select thisoption when you are ready to image a target device after booting.

Using the Imaging WizardOn the master target device, run the Provisioning Services Imaging Wizard to create avDisk file in the Provisioning Services database and then image to that file withouthaving to physically go to a Provisioning Server.


Note: If both .NET 3.0 SP1 or newer is installed and Windows Automount is enabled,the Imaging Wizard starts automatically after the target device product installationcompletes.

Note: The maximum capacity of a vDisk is 2040 GB.

Prerequisites

w Enable Windows Automount on Windows Enterprise Server operating systems.

w Disable Windows Autoplay.

w Remove any virtualization software before performing a conversion.

w Verify adequate free space exists on the destination, which is approximately 101% ofused space on the source volumes.

w Select a NIC for imaging that has a binding to Provisioning Services, which is the NICbinding chosen during the installation of the Target Device software.

1. From the master target device's Windows Start menu, select Citrix>ProvisioningServices>Imaging Wizard.The wizard welcome page appears.

2. Click Next.The Connect to Farm page appears.

3. Enter the name or IP address of a Provisioning Server within the farm to connectto, and the port to use to make that connection.

4. Use the Windows credentials (default), or enter different credentials, then clickNext.The Select New or Exisiting vDisk page appears.

5. Select to create a new vDisk (default), or use an existing vDisk by entering thatvDisks name, then click Next.The Add Target Device page appears.

6. Enter the target device name, then click Next.The machine name cannot be used as the name for the target device beingimaged. If the target device is a domain member, use the same name as in theWindows domain, unless that name is the same as the machine name beingimaged. When the target device boots from the vDisk, the name entered herebecomes the target device machine name.

7. Select the NIC (which contatins the MAC address) and the collection to add thisdevice to, then click Next.If the target device is already a member of the farm, the Existing Target Devicespage appears.

8. Click Next.The Summary of Farm Changes appears.

9. Verify all changes, then click Next.


A confirmation message displays.

10. Click Yes on the confirmation message to start the imaging process.The Configure Image Volumes page appears.

11. Select the source volumes for imaging in the Source table. The vDisk partitions willbe an exact replica of the master target device's hard disk drive unless thepartitions are deselected.

• Used – The amount of space used by existing files on the selected volume,which is required on the virtual disk volume being created (displays in MB andas a percentage of volume capacity).

• Free – The amount of file space that is available for use on the selected volume(displays in MB and as a percentage of volume capacity)

• Capacity – Maximum space of the original volume selected (Used Space + FreeSpace).

• Type – File system format. Must be NTFS.

12. Select the destination volumes and size them as needed in the Destination table.

• Used – The amount of space used by existing files on the selected volume,which is required on the virtual disk volume being created (displays in MB andas a percentage of volume capacity).

• Free – The amount of space available to new files. To resize the volume, changeits free space. To change the free space to a specific value, type the number ofmegabytes. To increment the free space by one megabyte, click the up arrowbutton. To decrement the free space by one megabyte, click the down arrowbutton.To change the free space to match the source volume, click the resetbutton.

• Capacity – The maximum space on the original volume (Used Space + FreeSpace). This amount automatically changes when the free space changes.

• Type – Type of file system associated with the selected volume. Must be NTFS.

13. In Total allocated text box, verify the amount of space to allocate to used and freespace for all selected volumes.

14. In Total capacity, verify the amount of space not allocated to used or free space ofany volume. To reserve space on the virtual disk for creating or extending volumeslater, change the unallocated space. To change the unallocated space to a specificvalue, type the number of megabytes. To increment the unallocated space by onemegabyte, click the up arrow button. To decrement the unallocated space by onemegabyte, click the down arrow button. To change the unallocated space to zeromegabytes, click the reset button.

15. In Total unallocated, use the up and down arrows to select the amount of space toleave unallocated.

16. Click Next to create the vDisk image.

17. On the master target device's BIOS, PXE boot from the NIC that was selected instep 6.


Assigning vDisks to Target DevicesWhen a target device boots, the software on the vDisk that is assigned to that devicebecomes available.

If one vDisk is assigned to a target device and the Any Server option is set for thatvDisk, the Provisioning Server will choose the least busy server to service the device. Ifa specific server is selected, then that specific server will service the target device.

If multiple vDisks are assigned to a target device, the user is presented with a menu atBIOS time to select which vdisk to boot from. After this selection, the ProvisioningServer will use the Any Server or specific server option of the chosen vDisk to selectthe Provisioning Server used to service the device.

If the custom bootstrap and/or local HD is selected in the target device properties, theuser will be presented with a menu at BIOS time. The menu prompts to select to bootfrom the vDisk, custom bootstrap, or HD as appropriate.

Note: The quickest method for replacing or assigning a vDisk for a target devicewithin a collection is to select the vDisk in the Console, then drag-and-drop the vDiskonto a target device collection in the tree of a second Console window (open a newConsole window by selecting the New window from here right-click menu option foreither the device collection or the store that contains the vDisk you want to assign.)

To assign a vDisk to a target device:

1. In the Console tree, expand the Device Collections folder, then click on thecollection folder where this target device is a member. The target-device displaysin the details pane.

2. Right-click on the desired target device, then select Properties. The Target DeviceProperties dialog appears.

3. On the General tab, select from the Boot from options.

4. Click on the vDisks tab, then select the Add button within the vDisk for thisDevice section. The Assign vDisks dialog appears.

5. To locate vDisks to assign to this target device, select a specific store or serverunder the Filter options, or accept the default settings, which includes All Storesand All Servers.

6. In the Select the desired vDisks list, highlight the vDisks to assign, then click OK,then OK again to close the Target Device Properties dialog.

Uninstalling Product SoftwareRemoving the software from your system requires that you uninstall both theProvisioning Server and target device components.


Uninstalling the Provisioning Services1. On the Provisioning Server, open the system’s Control Panel. From the Windows

Start menu, select Settings, and then click Control Panel.

2. Double click on the Add/Remove Programs icon.

3. Use Add/Remove Programs from the control panel to uninstall the product software.

Uninstalling Windows Target Device Software1. Disconnect the SDOM from the IDE interface on your target device’s motherboard.

Re-connect the original target device hard drive to the IDE interface.

2. Set the system BIOS to boot from the original hard drive.

3. Re-boot the target device directly from the hard drive.

4. On the target device, open the system’s Control Panel.

5. Double-click on the Add>Remove Programs icon.

6. Use Add>Remove Programs from the control panel to uninstall the product software.

Uninstall Linux Target Device Software1. Disconnect the SDOM from the IDE interface on your target device’s motherboard.

Re-connect the original target device hard drive to the IDE interface.

2. Open a terminal shell/command shell window and change directories to where theproduct software is installed. By default, the software is installed in /root/citrix.


Chapter 3

Installing and Configuring EmbeddedTarget Devices

Topics:• System Requirements

• To install Embedded TargetDevices

• To un-install the EmbeddedTarget Device package

• Windows XP EmbeddedBuild Overview

• To set up your embeddedtarget device

• To create an image of yourembedded target device diskon the vDisk

Using the Provisioning Services components described in thischapter, it is possible to create Windows XP Embeddedoperating system images that can boot from a vDisk.

Note:This feature is for Windows XP Embedded developers. Thisdocument assumes that you are familiar with the MicrosoftWindows Embedded Studio tools including Target Designerand the Component Database Manager.

For more information on the Microsoft Windows Embeddedtools, please refer to the documentation provided with theMicrosoft Windows Embedded Studio.

Embedded Target Device consists of the following components:

w ProvisioningservicesTargetDeviceSupport.sld - The ServerLevel Definition (SLD) file defines the components that willbe incorporated into the Windows XP Embedded databasefor use in the XP Embedded operating systems.

w ProvisioningservicesRepository - Contains all of the filesused in the ProvisioningservicesTargetDeviceSupport.sld,including Provisioning Services’ drivers and installationutilities. These files are included in an XP Embedded buildcontaining Provisioning Services components.

System Requirementsw Windows XP Embedded with the latest service pack.

w In order to build Windows XP Embedded operating systems, Microsoft WindowsEmbedded Studio must first be installed.

w The target device must meet the Windows XP Embedded system requirements. It isrecommended that a Windows XP Embedded operating system be built first on thedesired embedded target device to ensure OS compatibility and to resolve any OSspecific issues (such as driver requirements).

w Each embedded target device must also meet the target device requirementsoutlined in the Provisioning Services Installation Guide.

w A local drive must exist on a target system during the initial XP Embedded operatingsystem build process. This is necessary to allow Microsoft’s First Boot Agent to runand finish your XP Embedded image setup. Once the image is complete and the XPEmbedded disk image has been copied to the vDisk on the Provision Server or onshared network storage, the local disk can be removed (if desired).

w The maximum size of the vDisk is 2 terabytes.

To install Embedded Target DevicesInstallation of Embedded Target Device components is done through the ProvisioningServices Installation Wizard.

1. Close all Windows and Embedded Studio tools that may be open (Target Designerand/or Component Designer).

2. When the Provisioning Services Installation Wizard is run, components used to buildProvisioning Services into an XP Embedded operating system are installed bydefault. Run the Component Database Manager from the Microsoft Start menu.

3. Select Programs>Microsoft Windows Embedded Studio.

4. Select the Database tab, and then click the Import button.

5. On the Import SLD screen, point the SLD file field to theProvisioningservicesTargetDeviceSupport.sld in the destination directory createdby the Provisioning Services installation. Select the desired root destination(typically there is only one choice), and then click the Import button to start theimporting process.

6. Exit the Component Database Manager.

The Embedded Target Device support components will now be available in TargetDesigner under the Software: System: Network & Communication component group.The Embedded Target Device support macro component causes all necessaryProvisioning Services’ components to be included during dependency checking.

Chapter 3 48 | Provisioning Services | Installing and Configuring Embedded Target Devices

To un-install the Embedded Target Devicepackage

1. Select Start>Programs>Microsoft Windows Embedded Studio.

2. Select the Package tab.

3. Under Available Packages, select the Provisioning Services Embedded TargetDevice package, then click the Delete Package button.

4. A Confirmation Delete Package dialog appears, displaying all Provisioning Servicescomponents. Check the Delete all Provisioning Services Database files option,and click Yes.

5. Select the Group tab.

6. Under Available Dependency Groups, select Provisioning Services ComponentGroup, then click the Delete Dependency Group button.

7. Go to Control Panel>Add/Remove Programs, select Provisioning Services, andclick Change/Remove to uninstall the program.

Windows XP Embedded Build OverviewTo fully understand how Provisioning Services gets incorporated into a Windows XPEmbedded operating system, it is first necessary to understand how a Windows XPEmbedded operating system is built. The illustration below outlines the major phasesof a Windows XP Embedded operating system build process.

Note: For more information on building an XP Embedded operating systems, refer tothe Windows XP Embedded Platform documentation provided with the WindowsEmbedded Studio tools.



Provisioning Services installation occurs in two phases. Phase one occurs when theoperating system is built with Target Designer. All necessary files and non-device-specific components are installed in the target operating system.

Phase two occurs the first time the Windows XP Embedded operating system boots. Atthis time, all device-specific installation steps are performed. This second phasecannot occur until after the First Boot Agent has completed and the full operatingsystem is up and running.

Note: If automatic installation was turned off to remove the dependence on theExplorer shell component, it will be necessary to manually run the second phase of theinstallation process.

Once the XP Embedded Image with Provisioning Services support is fully up andrunning, it can be imaged onto the embedded target device’s vDisk, after which theembedded target device can be booted virtually.

Note: Provisioning Services require that at least one of the target systems have aphysical disk for the creation of the initial XP Embedded operating system. After theoperating system is built and transferred to a vDisk, the target system’s physical diskcan be removed (if desired).


To set up your embedded target device1. Transfer the built XP Embedded Image to the XP Embedded partition on the

embedded target device.


Note: The embedded target device must be configured to be bootable by XPEmbedded. To do this, run the BootPrep utility provided by Microsoft. For moreinformation on preparing target media to boot Windows XP Embedded, refer to“Building a Run-Time Image” in the Microsoft Windows XP Embedded Help.

2. Change your embedded target device’s BIOS setting to boot Network first, thenboot the embedded target device.

3. The XP Embedded Image will run through the Microsoft’s First Boot Agent (FBA),and complete the setup of the XP Embedded Operating system.

Note: By including the "Network Command Shell" component, the embeddedtarget device can be configured to use a static IP address from the command line(using netsh.exe). For more information on the Network Command Shell, refer tothe following web page: http://www.microsoft.com/technet/prodtechnol/winxppro/proddocs/netsh.asp

If the XP Embedded Image was created with Automatic installation turned off, orwith a shell other than the Explorer Shell, Provisioning Services installation willhave to be completed manually. This can be done by running bnSetup.bat locatedin the C:\Program Files\Citrix\Provisioning Services directory. If the commandprompt component (CMD - Windows Command Processor) was not included in thebuild, you may have to run the commands in the batch file manually.

Note: The batch file BNSetup.bat will reboot your system.

4. Prepare your embedded target device. Once the XP Embedded Operating system iscompletely up and running an additional local disk appears on the device. This diskis the vDisk associated with the embedded target device and is actually located ona Provisioning Server.

To create an image of your embedded targetdevice disk on the vDisk

The completed XP Embedded Image must be transferred to the vDisk located on theProvisioning Server to allow for the embedded target device to boot virtually.

1. On the XP Embedded target device go to C:\Program Files\Citrix\ProvisioningServices, then run BNImage.exe.

2. In XenConvert, enter the Destination Path; this will be the root directory of yourvDisk as it shows up on the embedded target device. The vDisk appears as a localhard drive on your embedded target device.

Note: The operating system and all files on the Source Image partition are copiedon a file-by-file basis. Active files (such as registry hives) are programmaticallyunloaded and recreated on the target system. The file system of the destination


http://www.microsoft.com/technet/prodtechnol/winxppro/proddocs/netsh.asp

http://www.microsoft.com/technet/prodtechnol/winxppro/proddocs/netsh.asp

drive does not need to be formatted with the same file system as the source, soan NTFS target can be built from a Fat32 source Image.

3. The vDisk is now configured to boot Windows XP Embedded.

4. From the Provisioning Server, start the Console.

5. Right click on the embedded target device, then select Properties.

6. Select the vDisk tab, and set your disk boot order to boot Virtual Disk First.Optionally, remove the local hard drive from the target device.

7. Reboot the embedded target device.

The embedded target device will now boot from the vDisk.


Chapter 4

Upgrading from Previous Releases

Topics:• Upgrade Utilities and

Features

• Upgrading from PreviousReleases

• Migrating the Database

This chapter describes how to upgrade to the most currentversion of Provisioning Services.

Note: Upgrading from Ardence 3.x, 4.0, and 4.1 is notsupported. Upgrading from Provisioning Server 4.5 is nolonger supported.

Note: The following alternative upgrade methods are alsoavailable: Upgrading vDisks using Hyper-V on page 78 and Upgrading vDisks Using Reverse Imaging on page 81.

Upgrade Utilities and FeaturesNote: Citrix recommends using the“Upgrading vDisks Using Hyper-V on page 77”because neither physical media nor imaging and reimaging is required. This methodgreatly simplifies the upgrade process. Hyper-V can be downloaded from Microsoft.

Caution: Be sure to backup vDisks and the database prior to upgrading.

The Upgrade Wizard facilitates the automation of the upgrade process, and includesthe following utilities:

w The UpgradeAgent.exe runs on the target device to upgrade previously installedproduct software.

w The UpgradeManager.exe runs on the Provisioning Server to control the upgradeprocess on the target device.

The upgrade method differs based on the version that is being upgraded.

Upgrading from Previous ReleasesImportant: When upgrading a 5.0 or 5.1 Provisioning Services implementation, allservers in that farm must be upgraded before connecting to the upgraded database.

Important: Provisioning Services 5.1 are not compatible with a 5.0.x database. Tomigrate the database, refer to Migrating the Database on page 58.

Complete the following steps to upgrade Provisioning Services implementation:

1. Backing up Data on page 56

2. Upgrading Provisioning Services on page 56

3. Upgrading the vDisk on page 57

4. Boot VHD formatted vDisks in Private Image mode. on page 57

5. Upgrade target device product software on a Master Target Device on page 57

Backing up DataBe sure to back up all data prior to upgrading.

Upgrading Provisioning ServicesComplete the procedure that follows on each server.

Chapter 4 56 | Provisioning Services | Upgrading from Previous Releases

1. Uninstall the previous version of the product software on the server, then rebootthe server (for details, refer to “Uninstalling Product Software on page 45”).

2. Run the new version of the Provisioning Server installer to install the ProvisioningServices software.

3. Run the Configuration Wizard. Select Farm already configured. Running the wizardwill start the services (for details, refer to Configuring the Farm on page 26).

Upgrading the vDiskThe Upgrade Manager automates the steps described in “Upgrading vDisks Manually onpage 82”.

Complete the procedures that follow to upgrade VHD formatted vDisks.

Note: Only one vDisk should be assigned to the target device being used for theupgrade.

Boot VHD formatted vDisks in Private Image mode.1. Assign the VHD formatted vDisk to the target device that will be used to upgrade.

This target device may be placed in a separate Console view to avoid confusing itwith another target device.

2. Change the target device vDisk to Private Image mode.

3. PXE boot the target device from the vDisk.

Upgrade target device product software on a Master TargetDevice1. From the product CD, on the target device, depending on the device platform, run

either:

• PVS_UpgradeWizard.exe

• PVS_UpgradeWizard_x64.exe

Note:If the target device hard drive has Vista installed, use disk management toformat the OS partition on the hard drive before proceeding.

Target devices can not be uninstalled while running from a vDisk.

2. Copy the Upgrade Manager executable that is specific to your current productversion, from the target device installation directory, to the Provisioning Servicesinstallation directory on the Provisioning Server.

3. Run the Upgrade Manager on the Provisioning Server.


4. On the target device, run UpgradeConfig.exe from the shortcut in the WindowsStart menu.

5. Specify a local account with Administrator privileges. This local account cannothave an empty password.

6. Specify the destination drive to which the vDisk will be cloned. It is recommendedthat you use the original machine (master target device) from which the vDisk wascreated.

Note: If this is a new hard drive, use the process described in “Image Back toMaster Target Devices Hard Drive on page 87” to initialize the hard drive.

7. Specify the Provisioning Server IP address and a user account and password toconnect to UpgradeManager. This account cannot have an empty password.

8. Click OK and the UpgradeConfig performs a sanity check.

9. The machine will reboot several times, and Upgrade Manager displays a message toindicate that the upgrade process has completed successfully.

Migrating the DatabaseThe Microsoft JET database has been replaced by the Microsoft SQL database. If youhave not yet migrated to the Microsoft SQL database, complete this step.

Note: Migrating from the JET database to Provisioning Services 64 bit productsoftware is not supported.

1. Navigate to the product installation directory.

2. Run the following MCLI command:cli run importDatabase /p filename=database.mdb collectionname=collection sitename=siteWhere database.mdb is the fully qualified name of the database, filename is thedated sub-directory of the installation directory (the default sub-directory differsdepending on the which product version you are upgrading from), collection is thename of the collection where you want the imported target devices to be, andsitename is the site where the collection exists. (For details on using MCLI, refer tothe Provisioning Services MCLI Programmer’s Guide).

Note:If necessary the upgrade process can be stopped after migrating the database.However, until the vDisks are actually upgraded, you can not benefit from the latestvDisk fixes or enhancements.


After successfully converting vDisks to VHD format and migrating the database toMicrosoft SQL, you may choose to complete the installation of Provisioning Servers.



Chapter 5

Managing Multiple Network InterfaceCards

Topics:• Requirements and

Considerations forManufacturer's NIC Teaming

• Requirements andConsiderations forProvisioning Services NICFailover

Provisioning Services provides the ability to run redundantnetworks between the servers and the target devices. Thisrequires that both the servers and the target devices beequipped with either multi-port NICs or multiple NICs.

Multiple NICs on the target device may be configured into avirtual team by using Manufacturer’s NIC teaming drivers, orinto a failover group using the Provisioning Services NICfailover feature.

Requirements and Considerations forManufacturer's NIC Teaming

Provisioning Services supports Broadcom and Intel NIC teaming drivers. A vDisk that isbuilt after configuring NIC teaming can run Standard or Private Image Mode.

Note: Broadcom NIC Teaming Drivers v9.52 and 10.24b are not compatible withProvisioning Services target device drivers.

1. The server’s operating system must be Microsoft Windows 2003 or 2008.

2. The new virtual team NIC MAC address has to match the physical NIC that performsthe PXE boot.

3. The new virtual team NIC MAC address has to match to the physical NIC thatperforms the PXE boot.

4. OEM NIC Teaming software should be installed and configured prior to the TargetDevice software.

5. Configure NIC teaming and verify that the selected teaming mode is expected bythe application and the network topology. It should expose at least one virtualteam NIC to the operating system.

6. During the Master Target Device installation process, Provisioning Services targetdevice client drivers need to bind to the new virtual team NIC MAC address. If allphysical NICs have been teamed up to a single virtual NIC, then the ProvisioningServices installer will automatically choose the virtual NIC silently, withoutprompting.

7. If changes are required, Provisioning Services Target Device software must beuninstalled before making changes to the teaming configuration, and thenreinstalled after those changes are complete.

8. Changes to teaming configurations on a Master Target Device that has target devicesoftware installed, may result in unpredictable behavior.

Requirements and Considerations forProvisioning Services NIC Failover

A Provisioning Services target device or Provisioning Server may be configured tosupport failover between multiple NICs. This feature will work with any brand or amixture of different brands of NICs and is available in both Standard and Private ImageMode.

1. The PXE boot NIC is considered the primary target device MAC address, which isstored in the Provisioning Services database.

Chapter 5 62 | Provisioning Services | Managing Multiple Network Interface Cards

2. The failover group of NICs is defined when running the Provisioning Services targetdevice installer on the Master Target Device. If the machine has more than oneNIC, the user is prompted to select the NICs that the Provisioning Services driversbind to. Select all the NICs that participate in NIC failover. Alternatively, inProvisioning Services 5.1 or later, run bindcfg.exe, which is located in theinstallation directory, to selectively bind NICs post installation.

3. A Target Device will only failover to NICs that are in the same subnet as the PXEboot NIC.

4. In the event that the physical layer fails, such as when a network cable isdisconnected, the Target Device fails over to the next available NIC. The failovertiming is essentially instantaneous.

5. The NIC failover feature and Provisioning Services HA feature compliment eachother, and provide network layer failover support. If the failure occurs in thehigher network layer, then the target device fails over to the next ProvisioningServer, subject to HA rules.

6. If a NIC fails and the target device is rebooted, the next available NIC from thefailover group will be used. Therefore, these NICs must be PXE capable and PXEenabled.

7. If a virtual NIC (teamed NICs) is inserted into the failover group, the vDisk becomeslimited to Private Image Mode. This is a limitation imposed by the NIC teamingdrivers.

8. Load balancing is not supported in the NIC failover implementation.


Chapter 5 64 | Provisioning Services | Managing Multiple Network Interface Cards

Chapter 6

Managing Bootstrap Files and BootDevices

Topics:• Configuring the Bootstrap

File From the Console

• Using the Manage BootDevices Utility

• Configuring the BIOSEmbedded Bootstrap

The following information is detailed in this chapter:

w Configuring the Bootstrap File From the Console on page66

w Using the Manage Boot Devices Utility on page 70

w Configuring the BIOS Embedded Bootstrap on page 73

Configuring the Bootstrap File From the ConsoleFor the Provisioning Server to start a target device, a boot file is downloaded by theProvisioning Services’s MBA or PXE-compliant boot ROM, when the device is turned on.This file must be configured so that it contains the information needed to communicatewith the Provisioning Servers. The Configure Bootstrap dialog is used to define the IPaddresses for up to four Provisioning Servers in the boot file.

The Configure Bootstrap dialog field descriptions are as follows:

General Tab: Configure Bootstrap

Field Description

Bootstrap File The currently selected boot file displays. If you wantto select a different boot file to configure, click theAdd button or Read Servers from Database button.

IP Settings The IP Address, Subnet Mask, Gateway, and Port for upto four Provisioning Servers, which will perform loginprocessing.

Add button Click the Add button to add a new Provisioning Serverto the file. Up to four Provisioning Servers may bespecified for Provisioning Servers.

Edit button Highlight an existing Provisioning Server from the list,then click the Edit button to edit this server’s IP settings.

Remove button Select an existing Provisioning Server from the list,then click the Remove button to remove this serverfrom the list of available Provisioning Servers.

Move Up and Move Downbuttons

Select an existing Provisioning Server, and click tomove up or down in the list of Provisioning Servers.The order in which the Provisioning Servers appear inthe list determines the order in which the ProvisioningServers are accessed should a server fail.

Read Servers fromDatabase button

To populate the boot file with the Stream Service IPsettings already configured in the database, click theRead Servers from Database button. This removes anyexisting settings before populating the list from thedatabase.

Target Device IP: Configure Bootstrap

Use DHCP to retrievetarget device IP

Select this option to retrieve target device IP; defaultmethod.

Chapter 6 66 | Provisioning Services | Managing Bootstrap Files and Boot Devices

Use static target device IP Selecting this method requires that a primary andsecondary DNS and Domain be identified.

Server Lookup: Configure Bootstrap

Use DNS Select this option to use DNS to find the server. Thehost name displays in the Host name textbox. If thisoption is selected and the Use DHCP to retrieve DeviceIP option is selected (under Device IP Configurationsettings), your DHCP server needs to provide option 6(DNS Server).

Note: If using HA, specify up to four ProvisioningServers for the same Host name on your DNS server.

Use Static IP Use the static IP address of the Provisioning Serverfrom which to boot from. If you select this option,click Add to enter the following Provisioning Serverinformation, then click OK to exit the dialog:

IP AddressSubnet MaskGatewayPort (default is 6910)

Note: If using HA, enter up to four ProvisioningServers. If you are not using HA, only enter one. Usethe Move Up and Move Down buttons to sort theProvisioning Servers boot order. The first ProvisioningServer listed will be the server that the target deviceattempts to boot from.

Options Tab: Configure Bootstrap

Verbose Mode Select the Verbose Mode option if you want to monitorthe boot process on the target device (optional) orview system messages.

Interrupt Safe Mode Select Interrupt Safe Mode if you are having troublewith your target device failing early in the boot process.

Advanced MemorySupport

This setting enables the bootstrap to work with newerWindows OS versions and is enabled by default. Onlydisable this setting on older XP or Windows Server OS32 bit versions that do not support PAE, or if yourtarget device is hanging or behaving erratically in earlyboot phase.


Network Recovery Method Restore Network Connections — Selecting this optionresults in the target device attempting indefinitely torestore it's connection to the Provisioning Server.

Reboot to Hard Drive — (a hard drive must exist onthe target device) Selecting this option instructs thetarget device to perform a hardware reset to force areboot after failing to re-establish communications fora defined number of seconds. The user determines thenumber of seconds to wait before rebooting. Assumingthe network connection can not be established, PXEwill fail and the system will rebooot to the local harddrive. The default number of seconds is 50, to becompatible with HA configurations.

Login Polling Timeout Enter the time, in milliseconds, between retries whenpolling for Provisioning Servers. Each ProvisioningServer is sent a login request packet in sequence. Thefirst Provisioning Server that responds is used. In non-HA systems, this time-out simply defines how often toretry the single available Provisioning Server with theinitial login request.

This time-out defines how quickly the round-robinroutine will switch from one Provisioning Server to thenext in trying to find an active Provisioning Server. Thevalid range is from 1,000 to 60,000 milliseconds.

Login General Timeout Enter the time-out, in milliseconds, for all loginassociated packets, except the initial login polling time-out. This time-out is generally longer than the pollingtime-out, because the Provisioning Server needs timeto contact all associated servers, some of which maybe down and will require retries and time-outs fromthe Provisioning Server to the other ProvisioningServers to determine if they are indeed online or not.The valid range is from 1,000 to 60,000 milliseconds.

Configuring the Bootstrap File1. In the Console, highlight the Servers folder in the tree, or highlight a Provisioning

Server, then select Configure bootstrap from the Action menu. The ConfigureBootstrap dialog appears.

Select the boot file that was copied to the directory you selected during theProvisioning Server setup.

Important:


If a previous version of Provisioning services was installed on this server, youmust change the default location from:

C:\Program Files\<CitrixorOEMname>\Provisioning Server\Tftpboot

to:

C:\Documents and Settings\All Users\Application Data\<CitrixorOEMname>\Provisioning services\Tftpboot

If the default is not changed, the bootstrap file can not be configured from theConsole and target devices will fail to boot; receiving a ‘Missing TFTP’ errormessage.

Note: If you installed the Console on a separate machine, select the path of theremote Provisioning Server (which has boot services installed).

2. Click Read DB. When the Stream Service starts, it creates a record in the databasewith its own IP address. There is only one Stream Service option record perdatabase. If the service is bound to multiple IP addresses, multiple records appearin the database. The Read DB function chooses only one IP address from eachProvisioning Server. This function can also be used to populate the boot file withthe Stream Service IP settings already configured in the database.

3. Choose from the following options:

• Select the Verbose Mode option if you want to monitor the boot process on thetarget device (optional). This enables system messaging on the target device.

• Select Interrupt Safe Mode if the target device hangs early in the boot process.

• Select Advanced Memory Support option to enable the bootstrap to work withnewer Windows OS versions (enabled by default). Only disable this setting onolder XP or Windows Server OS 32 bit versions that do not support PAE, or ifyour target device is hanging or behaving erratically in early boot phase.

4. Select from the following Network Recovery Methods:

• Restore Network Connections - Selecting this option results in the targetdevice attempting indefinitely to restore it's connection to the Provisioning Server.

• Reboot to Hard Drive - Selecting this option instructs the target device toperform a hardware reset to force a reboot after failing to re-establishcommunications for a defined number of seconds. The user determines thenumber of seconds to wait before rebooting. Assuming the network connectioncan not be established, PXE will fail and the system will reboot to the localhard drive. The default number of seconds is 50. Click the Browse button tosearch for and select the folder created in Step 1, or enter a full path or UNCname.

Note: If the partition containing the vDisks is formatted as a FAT file system, amessage displays a warning that this could result in sub-optimal performance. It is


recommended that NTFS be used to format the partition containing the vDisks. Donot change the address in the Port field.

Caution: All boot services (PXE, TFTP) must be on the same NIC (IP). Butthe Stream Service can be on a different NIC. The Stream Service allows you tobind to multiple IPs (NICs).

5. Configure the following:

Login Polling Timeout

Enter the time, in milliseconds, between retries when polling for servers. Eachserver is sent a login request packet in sequence. The first server that responds isused. This time-out simply defines how often to retry the single available serverwith the initial login request. If you are using the High Availability feature, this time-out defines how quickly the round-robin routine will switch from one server to thenext, in trying to find an active server. The valid range is from 1,000 to 60,000milliseconds.

Login General Timeout

Enter the time-out, in milliseconds, for all login associated packets, except theinitial login polling time-out. The valid range is from 1,000 to 60,000 milliseconds.

6. Click OK to save your changes.

Using the Manage Boot Devices UtilityThe Manage Boot Devices Utility provides an optional method for providing IP and bootinformation (boot device) to target devices; as an alternative to using the traditionalDHCP, PXE, and TFTP methods. Using this method, when the target device starts, itobtains the boot information directly from the boot device. With this information, thetarget device is able to locate, communicate, and boot from the appropriateProvisioning Server. After the user is authenticated, the Provisioning Server providesthe target device with its vDisk image.

Supported Boot Devices

The following boot devices are supported in this release:

Note: The Boot Device Management utility is not supported on operating systemsolder than, and including, Windows 2000. Wireless NICs are not supported.

w USB

w CD-ROM (ISO)

w Hard Disk Partition (currently, only physical hard disk partitions are supported)

Caution:


When an entire hard drive is selected as boot device, all existing disk partitions areerased and re-created with a single active partition. The targeted partition isreserved as a boot device and cannot be used by the operating system or data.

When a hard disk partition is selected as boot device, the selected disk partitiondata is deleted and set as an active partition. This active partition becomes the bootdevice.

Boot devices are configured using the Boot Device Management utility. The ManageBoot Devices utility is structured as a wizard-like application, which enables the user toquickly program boot devices.

After installing the boot device, complete the procedures that follow.

Configuring Boot Devices1. From C:\Program Files\Citrix\Provisioning Services product installation directory,

run BDM.exe. The Boot Device Management window opens.

2. Under Server Lookup, select the radio button that describes the method to use toretrieve Provisioning Server boot information:

• Use DNS to find the Provisioning Server from which to boot from. If this optionis selected and the Use DHCP to retrieve Device IP option is selected (underDevice IP Configuration settings), your DHCP server needs to provide option 6(DNS Server)

Note: The boot device uses Host name plus DHCP option 15 (Domain Name,which is optional) as the fully qualified domain name (FQDN) to contact theDNS server to resolve the IP address.

If using HA, specify up to four Provisioning Servers for the same Host name onyour DNS server.

• Use the static IP address of the Provisioning Server from which to boot from. Ifyou select this option, click Add to enter the following Provisioning Serverinformation, then click OK to exit the dialog:

w IP Address

w Subnet Mask

w Gateway

w Port (default is 6910)

If using HA, enter up to four Provisioning Servers. If you are not using HA, onlyenter one. Use the Move Up and Move Down buttons to sort the ProvisioningServers boot order. The first Provisioning Server listed will be the server thatthe target device attempts to boot from.

3. Click Next. The Set Options dialog appears


4. Configure the following local boot options, then click Next:

• Verbose Mode; enable/disables the displaying of extensive boot and diagnosticinformation that is helpful when debugging issues.

• Interrupt Safe Mode; enable/disable for debugging issues, which is sometimesrequired for drivers that exhibit timing or boot behavior problems.

• Advanced Memory Support; enables/disables the address extensions, to matchyour operating system settings. Select this option to enable the bootstrap towork with newer Windows OS versions (enabled by default). Only disable thissetting on older XP or Windows Server OS 32 bit versions that do not supportPAE, or if your target device is hanging or behaving erratically in early boot phase.

• Network Recovery Method; select to attempt to restore the networkconnection or to reboot from a hard drive if the target device loses connectionto the Provisioning Server, and how long (in seconds) to wait to make thisconnection.

• Login Polling Timeout; in general, it is recommended that you start values ofone second for each of the polling and general timeouts. You should extendthese when using 3DES encryption. You should further extend the timers basedupon workload. A reasonable setting for 100 target devices running triple DES inthe network would be three seconds.

• Login General Timeout; a reasonable setting for 100 target devices runningtriple DES in the network would be ten Seconds for the General Timeout.

5. On the Burn the Boot Device dialog, configure the target device IP. If the Use DNSto find the Server option is selected and your DHCP service does not provide option6 (DNS Server), then enter the following required information (note that the servername must be less than 16 characters length and the domain name less than 48characters in length):

• Primary DNS Server Address

• Secondary DNS Server Address

• Domain Name

6. Configure boot device and media properties, then click Burn. A message appearsto acknowledge that the boot device was successfully created.

7. Click Exit to close the utility.

8. If selecting ISO format, use your CD burning software to burn the ISO image.

9. Boot the target device and enter the BIOS Setup. Under the Boot Sequence, movethe boot device to the top of the list of bootable devices. Save the change andboot the target device.

After the boot device is programmed, a target device boot sequence can be configuredusing the Console’s Target Device Disk Properties dialog. These boot behaviors are usedafter a target device connects to a Provisioning Server. The Console allows multiplevDisk images to be assigned to a target device. The way in which these vDisks bootdepends upon the selected boot behavior.

When configuring the BIOS to work with the boot device (either USB or ISO image), it isimperative that the NIC PXE option is enabled. The PXE boot option is required in order


for the NIC Option ROM to stay resident in memory during the pre-boot process. Thisway, UNDI will be available to the boot device to properly initialize the NIC. Otherwise,the "API not found" message would be displayed by the boot device.

Configuring the BIOS Embedded BootstrapThis feature is OEM specific and provides end users with systems preconfigured withProvisioning Services, allowing customers to deploy an Provisioning Services-enabledenvironment with minimal effort. This feature becomes an alternative to the standardPXE boot method.

As part of this solution, the OEM embeds the bootstrap within the target device’s BIOSat the factory. The OEM also pre-configures the device with product license keys.

For the BIOS-Embedded Bootstrap feature to work automatically from the factory, thetarget network must support the following:

w A DHCP server that is capable of providing the target device’s IP, Subnet & Gatewayaddress. Additionally, the DHCP service must provide the default DNS server for theclient to use.

w A DNS server must be active on the network

w A DNS entry must be defined which points the name <IMAGESERVER1> to eachProvisioning Server's active IP address. This DNS entry is used by the target device tofind an active server.

If the target device boots using the BIOS-Embedded Bootstrap, the configurationsettings are obtained from the device’s BIOS. These BIOS settings may indicate usingDHCP with DNS to lookup the IP and server information (dynamic), or it may list up tofour server IP addresses in the BIOS (static).

The first time a target device boots, it reads the product license key and configurationinformation from the BIOS, locates the Stream Service, and then sends a deviceregistration message to the server. This message contains the information, in additionto the information inherited from the device collection template, necessary to add thedevice to the Provisioning Services database.

Configuring the BIOS-Embedded Bootstrap SettingsThe OEM configures the BIOS-embedded bootstrap settings so that the bootstrap works‘out-of-the-box’. If the Provisioning Services administrator needs to change settings,use the Configure BIOS Bootstrap feature in the Console. Configuration changes areupdated automatically the next time the target device boots. However, only those BIOSsettings that differ from the new settings are updated.

Note: The target device must have enough information stored in the BIOS to makeinitial contact with the Provisioning Server.


General Tab1. Right-click on a Provisioning Server in the Console window, then select the

Configure Bootstrap menu option. The Configure Bootstrap dialog appears.

2. To allow target device BIOS settings to be automatically updated if connected tothis server, on the General tab, check the Automatically update the BIOS on thetarget device with these settings check box. The next time the target deviceboots, these settings are automatically applied.

Target Device IP1. Select the Target Device IP tab on the Configure BIOS Bootstrap dialog.

2. Select from the following methods to use to retrieve target device IP addresses:

• Use DHCP to retrieve target device IP; default method.

• Use static target device IP; selecting this method requires that a primary andsecondary DNS and Domain be identified.

Server Lookup TabOn the Server Lookup tab, select the method that the target device will use to find theProvisioning Server it will boot from:

• Use DNS to find server

Select this option to find the server using DNS. The host name displays in the Hostname textbox.

Note: When using DNS, the DNS server must be able to resolve the name with theIP address of the server.

• Use specific servers

Select this option to manually enter Provisioning Server data. If this information wasnot previously entered, no data appears. To quickly list all servers in the database,click Read Servers from Database button.

To change or enter new information, click Edit, then manually enter the informationin the Server Address dialog.

Note: Selecting the Reset to Default button will display a confirmation message toindicating that automatic BIOS updates on the target devices will be disabled and touse DNS to find the server.


Options Tab1. On the Options tab, select from the network options that follow:

• Select the Verbose mode option if you want to monitor the boot process on thetarget device (optional). This enables system messaging on the target device.

• Select Interrupt safe mode if the target device hangs early in the boot process.

• Select the Advanced Memory Support option to enable the bootstrap to workwith newer Windows OS versions (enabled by default). Only disable this settingon older XP or Windows Server OS 32 bit versions that do not support PAE, or ifyour target device is hanging or behaving erratically in the early boot phase.

2. Select from the following Network Recovery Methods:

• Restore network connections

Selecting this option results in the target device attempting indefinitely torestore it's connection to the Provisioning Server.

• Reboot to Hard Drive

Selecting this option instructs the target device to perform a hardware reset toforce a reboot after failing to re-establish communications for a definednumber of seconds. The user determines the number of seconds to wait beforerebooting. Assuming the network connection can not be established, the targetdevice will fail to contact the server and the system will reboot to the localhard drive. The default number of seconds is 50.

Note: If the partition containing the vDisks is formatted as a FAT file system, amessage displays a warning that this could result in sub-optimal performance. It isrecommended that NTFS be used to format the partition containing the vDisks. Donot change the address in the Port field.

Caution: All boot services must be on the same NIC (IP). But the StreamService can be on a different NIC. The Stream Service allows you to bind tomultiple IPs (NICs).

3. Configure the following:

Login Polling Timeout

Enter the time, in milliseconds, between retries when polling for servers. Eachserver is sent a login request packet in sequence. The first server that responds isused. This time-out simply defines how often to retry the single available serverwith the initial login request. If you are using the High Availability feature, this time-out defines how quickly the round-robin routine will switch from one server to thenext, in trying to find an active server. The valid range is from 1,000 to 60,000milliseconds.

Login General Timeout


Enter the time-out, in milliseconds, for all login associated packets, except theinitial login polling time-out. The valid range is from 1,000 to 60,000 milliseconds.

4. Click OK to save your changes.


Appendix A

Upgrading vDisks Using Hyper-V

Topics:• Upgrading vDisks using

Hyper-V

This chapter describes how to upgrade Provisioning ServervDisks using Microsoft Hyper-V as the mechanism to installnew versions of the Provisioning Service drivers and othertarget device components. Using this method, neither physicalmedia nor imaging and reimaging is required. This methodgreatly simplifies the upgrade process and reduces thenumber of tasks you must complete.

RequirementsBefore upgrading using Hyper-v, review the followingrequirements:

w Hyper-V must be installed (Hyper-V does not need to beinstalled on the Provisioning Server).

w General Hyper-V knowledge.

Upgrading vDisks using Hyper-V1. Un-install previously installed Provisioning Services server software.

2. Install newer version of Provisioning Services server software.

3. Copy the newly created or existing VHD file to the Hyper-V server.

4. Create a new virtual machine in the Hyper-V Manager.

5. During the creation steps, attach the existing newvDisk.vhd instead of using a newVHD.

6. Go into the properties of the newly created Hyper-V virtual machine (Action panel> Settings) and remove the Network adapter. Go to Add Hardware and add theLegacy NIC.

7. Go to the Legacy NIC and attach it to the physical system's NIC.

8. Boot the virtual machine.

9. Let the system install the new drivers, then reboot if prompted.

10. Un-install Provisioning Services target device software, then reboot.

11. Optional: Install Hyper-V's Integration Services. This is only necessary when theresulting VHD must be bootable in both physical and virtual systems. While thevirtual machine is on, go to Action, then choose Insert Integration Services set updisk and install.

12. Install Provisioning Services target device software.

13. Go to Provisioning Services installation directory (default is: C:\Program Files\Citrix\Provisioning Services).

14. Start bindcfg.exe.

15. Choose to bind Provisioning Services to the inactive NIC (the physical NIC from theoriginal target device).

16. Shutdown the virtual machine.

17. Go to the virtual machine’s properties (Action panel>Settings), then set it to bootto the legacy NIC first.

18. Transfer the VHD (newvDisk.vhd) back to the Provisioning Server.

19. From the Provisioning Service’s Console:

a. Add the VHD to the Provisioning Services database using the Add existing vDiskmenu option.

b. Add the Hyper-V virtual machine to the list of the target devices.

c. Associate the vDisk with the appropriate target devices.

d. Set the vDisk to Standard Image Mode

Appendix A 78 | Provisioning Services | Upgrading vDisks Using Hyper-V

20. Boot the physical target device (assuming this is set to PXE first), then the Hyper-Vvirtual machine.

The original vDisk is now upgraded and a common image between the physical andvirtual machines has also been created.


Appendix A 80 | Provisioning Services | Upgrading vDisks Using Hyper-V

Appendix B

Upgrading vDisks Using Reverse Imaging

Topics:• Upgrading vDisks Manually

• Automate the Upgrading ofvDisks

• Image Back to Master TargetDevices Hard Drive

Unlike traditional software packages, target devices can notbe uninstalled while running from a vDisk. vDisks can only beuninstalled while the operating system is running on a physicalhard disk so that the vDisk storage and network driver stackcan be properly shut down. The upgrade method that youchoose will depend on your existing Provisioning Servicesimplementation and network requirements.

Upgrade vDisks methods include:

w Upgrading vDisks Manually on page 82

w Automate the Upgrading of vDisks on page 82

While the manual upgrade method is the most reliableapproach for all types of Provisioning Services deployments, itis also the most labor intensive and time consuming of themethods.

A set of upgrade script utilities are included to streamline andautomate the process. UpgradeAgent.exe andUpgradeManager.exe are the proxies to run on target devicesand Provisioning Servers that were installed from previousproduct releases. This agent facilitates the upgradeautomation.

Upgrading vDisks ManuallyThis section describes how to upgrade Provisioning Server vDisks manually. This manualmethod is recommended if vDisks have been upgraded using the Upgrade Wizard priorto version 4.5, to ensure that the previous version has been uninstalled completely.

Use the manual upgrade as a universal approach to upgrading vDisks, or if any of thefollowing are true:

w The vDisk has gone through a number of modifications in Private Image mode

w The original hard drive is no longer available

Manual Upgrade TasksThe tasks performed during a manual upgrade can be performed automatically usingthe The manual upgrade method includes completing the following tasks:

1. Image Back to Master Target Devices Hard Drive on page 87

2. Uninstall Product Software on page 88

3. Install Master Target Device Software on page 88

4. Imaging the Hard Drive on page 88

5. Boot from the vDisk on page 89

Automate the Upgrading of vDisksThe automated methods to choose from when upgrading vDisks include:

w Automated Inline Upgrade on page 82

w Automated Rolling Upgrade on page 84

w Automated Rolling Upgrade with USB Key on page 85

Automated Inline UpgradeThe automated inline upgrade method takes an existing vDisk and converts it to thecurrent product version. Inline upgrades require downtime from the Provisioning Serverdeployment.

Prerequisites:

w The previous Provisioning Server is currently running and has not been upgraded.

w The vDisk was imaged from a previous version and has not been upgraded.

Appendix B 82 | Provisioning Services | Upgrading vDisks Using Reverse Imaging

w The vDisk can boot from a previous Provisioning Server.

Upgrading the server with the new Provisioning Server product software

1. On the Provisioning Server, uninstall previous product software.

2. Run the new version of the Provisioning Server installer to install the ProvisioningServer software.

3. Prepare the Citrix License Server by adding the product license file to it, thenverify the license status from Provisioning Server Console.

4. Run the Configuration Wizard to select the original database. This will upgrade thedatabase.

5. Change the target device vDisk to Private Image Mode.

6. PXE boot the target device from the vDisk.

7. The Upgrade Manager requires RPC communication over the network. If there is afirewall on this server, set the firewall to allow TCP port 6901.

Upgrading target device product software on a Master Target Device

1. Depending on the target device platform, run either: PVS_UpgradeWizard.exe orPVS_UpgradeWizard_x64.exe.

2. Copy UpgradeManager56.exe to the Provisioning Server 5.6 installation directory.

3. Run the UpgradeManager56.exe on the Provisioning Server.

4. Run UpgradeConfig.exe from the shortcut in the Windows start menu or from theinstallation directory.

5. Specify a local account with Administrator privilege to AutoLogon. This localaccount cannot have an empty password.

6. Specify a local partiton to which reverse imaging will clone data. The original harddrive that the vDisk was cloned from is recommended.

Note: If this is a new hard drive, please use the manual upgrade method toinitialize the hard drive.

7. Specify the Provisioning Server IP address and a user account and password toconnect to UpgradeManager. This account cannot have an empty password.

8. Click OK and the UpgradeConfig preforms a sanity check on various parameters. Ifeverything passes, the UpgradeConfig exits, reboot the machine to start theupgrade process.

The upgrade script should automate the manual steps that are captured in the ManualUpgrade procedure. The machine will reboot several times, and then display a messageto indicate that the script has successfully completed.

The AutoLogon clears when the upgrade completes. If AutoLogon is wanted for vDiskdeployment, setup AutoLogon as necessary.


Automated Rolling UpgradeThe automated rolling upgrade method converts vDisks to the current ProvisioningServer vDisk format. This upgrade method does not require Provisioning Serverdeployment downtime, but it does require that a new dedicated Provisioning Server co-exist, side-by-side with a pervious version of the server.

Prerequisites:

w Both the previous version of the server and the new server are dedicated machines.

w The vDisk is from a previous version and has not been upgraded.

w The vDisk can boot from a previous version of the server.

w If both the previous and new versions of the servers are on the same networksubnet, there should be only one PXE/TFTP service on the network.

Upgrading using the automated rolling upgrade process

On existing Provisioning Servers:

1. Change the target device’s vDisk to Private Image Mode, then PXE boot the targetdevice from that vDisk.

2. The Upgrade Manager requires RPC communication over the network. If there is afirewall on this server, set firewall to allow TCP port 6901.

On the new Provisioning Server:

1. Create a new vDisk with the same name, but of equal or larger size than theoriginal vDisk. Preformat the new vDisk by mounting it from the Provisioning ServerConsole, formatting it, and then unmounting it.

2. The Upgrade Manager requires RPC communication over the network. If there is afirewall on this server, set firewall to allow TCP port 6901. Do not turn on DHCP/PXE services if this server is on the same network subnet as previous servers.

On the Master Target Device:


2. Copy the matching version of the UpgradeManager.exe to the product installationdirectory.

3. Run Upgrade Manager on the Provisioning Server to be upgraded.

4. Copy UpgradeManager.exe to the new Provisioning Server installation directory.

5. Run UpgradeManager.exe on the new Provisioning Server.

6. Specify a local account with Administrator privileges to AutoLogon. This localaccount can not have empty password.

7. Specify a partition to which reverse imaging clones data. The original hard drive,which the vDisk was cloned from, is recommended. If this is a new hard drive,


follow the Upgrading vDisks Manually on page 82 procedure to initialize the harddrive.

8. Specify the previous Provisioning Server IP address, and a user account andpassword to connect to UpgradeManager. This account cannot have an emptypassword.

9. Specify the newer Provisioning Server IP address, and a user account and passwordto connect to UpgradeManager. This account cannot have an empty password.

10. Click OK and the UpgradeConfig performs a sanity check on various parameters. Ifeverything passes, you are prompted to reboot to start the upgrade process.

11. The upgrade script automates the steps performed during the Manual Upgradeprocedure. The machine reboots several times during the process, and thendisplays a message when the upgrade has completed successfully. The script pausesand prompts you after the reverse imaging and uninstallation steps. This is thetime to switch the target device to the new Provisioning Server network.

12. If both the previous and new Provisioning Servers are on the same network, turnoff PXE and TFTP services on the previous Provisioning Server, then turn on PXE andTFTP services on the new Provisioning Server. Alternatively, use DHCP Reservationto create a exception for this target device and change DHCP option 66 Boot ServerHost Name to point to the new Provisioning Server.

13. If the servers are on different networks, now is the time to swap the network cableto connect the target device to the new network.

14. After all vDisks have been upgraded, setup the PXE and TFTP services on the newProvisioning Server permanently, to serve new target devices.

Automated Rolling Upgrade with USB KeyThis upgrade method is a superset procedure for the Automated Rolling Upgrade. Itutilizes the USB boot device to switch a target device from a previous ProvisioningServer to the current version of the Provisioning Server.

Prerequisite:

w Both the previous version of the Provisioning Server and the new Provisioning Serverare dedicated machines.

w The vDisk is from a previous version and has not yet been upgraded.

w The vDisk can boot from a previous version of the Provisioning Server.

w If both the previous and new versions of the Provisioning Servers are on the samenetwork subnet, verify that there is only one PXE/TFTP service on the network.

w The target device is capable of USB boot and initialize UNDI to connect to theProvisioning Server.

w Verify that the entire USB disk content can be erased (it will only be used by theProvisioning Server to boot).

Upgrading Previous Versions of vDisks using the Automated Rolling Upgrade withUSB Key Method


On existing Provisioning Servers, complete the same procedure previously described inthe Automated Rolling Upgrade.

On the new Provisioning Servers, complete the same procedure previously described inthe Automated Rolling Upgrade.

On the Master Target Device:

1. Run BDM.exe to program a USB disk as boot device. This erases all data on theexisting USB disk.

2. On the login server, specify a static IP address for the Provisioning Server. Precedeto the last dialog to choose the USB device, then click Burn.

3. Reboot the machine and go into the BIOS setup screen, to verify that the USB diskis the first boot device and the local hard drive is the very next boot device in theBIOS boot sequence settings.

4. Reboot the machine and verify that the vDisk boots through USB as expected.


6. Run UpgradeConfig.exe from the Upgrade Wizard installation directory.

7. In the UpgradeConfig, select to use the USB boot disk to automate the transferringof previous target devices to the upgraded Provisioning Servers.

8. Specify a local account with Administrator privileges to AutoLogon. This localaccount can not have empty password.

9. Specify a partition to which reverse imaging clones data. The original hard drive,which the vDisk was cloned from, is recommended. If this is a new hard drive,follow the manual upgrade procedure to initialize the hard drive.

10. Specify the previous Provisioning Server IP address, and a user account andpassword to connect to UpgradeManager. This account cannot have an emptypassword.

11. Specify the Provisioning Server IP address, then a user account and password toconnect to the Upgrade Manager. This account cannot have an empty password.

12. Click OK and the UpgradeConfig performs a sanity check on various parameters. Ifeverything passes, you are prompted to reboot to start the upgrade process.

13. The upgrade script automates the steps performed during the Manual Upgradeprocedure. The machine reboots several times during the process, and thendisplays a message when the upgrade has completed successfully.

14. This upgrade method does not pause. It automatically re-programs the USB key toswitch the target device to the new server at the appropriate time.

15. After all vDisks have been upgraded, setup PXE and TFTP services on the newProvisioning Servers to permanently serve new target devices. USB key can now beremoved.

16. Set the target device’s BIOS back to PXE as the first boot device.


Image Back to Master Target Devices Hard DriveThere are two procedures that allow you to image a vDisk back to a hard drive. Theprocedure you select depends on the state of the disk drive you are imaging to. Selectone of the following procedures:

w Image Back to Master Target Devices Hard Drive on page 87

Use the original hard drive from which the vDisk was created (recommended method).

w Image back using an unformatted, uninitialized hard-disk drive on page 87

Use an unformatted, uninitialized hard-disk drive.

Image Back to the Original Hard Drive from Whichthe vDisk was Created

1. Boot from the vDisk in Private or Shared Image Mode.

2. From Windows Administrative Tools, select the Computer Management menuoption. The Computer Management window appears.

3. In the tree, under Storage, select Disk Management.

4. Note the partition letter of the active partition of the original hard disk. If new,format the disk before continuing.

5. Run the Image Builder utility on the target device. This utility is located at\Program Files\Citrix\Provisioning Services\BNImage.exe

6. Specify the drive letter of the newly created partition (or the original boot HDDpartition) as the Destination Drive. The destination drive should point to the vDiskfirst partition by default.

7. Proceed cloning the hard drive image to the vDisk Destination Drive.

8. To connect the vDisk to the Provisioning Server, from the Console, set the targetdevice to boot from the hard drive, then PXE boot the target device. If this step isnot completely properly, the Provisioning Server will not be able to connect withthe vDisk

9. Continue onto Uninstalling Product Software on page 45 .

Image back using an unformatted, uninitialized hard-disk drive

1. Boot from the vDisk in Private Image Mode.

2. From Windows Administrative Tools, select the Computer Management menuoption. The Computer Management window appears.


3. In the tree, under Storage, select Disk Management.

4. Create a new primary partition, as the first partition, assign a drive letter to it,and then format the partition.

5. Right-click on the newly created partition, then choose Mark Partition as Active.

6. Delete the boot.ini.hdisk file from the root of the vDisk.

7. Run the Image Builder utility on the target device. This utility is located at\Program Files\Citrix\Provisioning Services\BNImage.exe.



10. To connect the vDisk to the Provisioning Server, from the Console, set the targetdevice to boot from the hard drive, then PXE boot the target device. If this step isnot completely properly, the Provisioning Server will not be able to connect withthe vDisk.

11. Uninstalling Product Software on page 45

Uninstall Product SoftwareRefer to Uninstalling Product Software on page 45 to uninstall existing product softwarefrom the target device and Provisioning Server.

Install Master Target Device SoftwareComplete the following steps to install the latest product software on the MasterTarget Device.

1. Run the new Provisioning Server Target Device installer on the target device.

2. PXE boot the target device.

Imaging the Hard DriveComplete the following steps to image the target device’s hard drive on to the vDisk file:

1. Run the Image Builder utility on the target device. This utility is located at\Program Files\Citrix\Provisioning Services\BNImage.exe.



4.


Boot from the vDiskUsing the Console, set the target device on the Provisioning Server to boot from vDiskfirst, then reboot the target device. The new target device should now be running thenew vDisk image.
