pvs installation

Installation and Configuration Guide

Citrix Provisioning Services 5.6 SP1October 2010Revision 4

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 SourceAll other trademarks and registered trademarks are the property of their respective owners.

Document code: January 4 2012 18:59:18

Contents

1 Provisioning Services Product Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Provisioning Services Streaming Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7Provisioning Services Solution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Provisioning Services Editions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Product Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Software-Streaming Process Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Benefits and Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Benefits for XenApp and other Server Farm Administrators. . . . . . . . . . . . . . . . . . . . . . . . . . .11Benefits for Desktop Administrators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Provisioning Services Product Infrastructure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Provisioning Services Farm Hierarchy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Farms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Device Collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Additional Provisioning Services' Product Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Provisioning Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Provisioning Services Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15vDisks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Target Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Device Collections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Network Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Product Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Provisioning Services Administrator Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Provisioning Services and Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

Provisioning Services Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Getting Service and Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Getting the Subscription Advantage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Locating the Citrix Developer Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Participating in Citrix Education and Training. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

iii

2 Whats New in This Release. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Administration and Manageability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Removed Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

3 Installing and Configuring Provisioning Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Installation Wizards and Utilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Citrix Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Provisioning Services Installation Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Provisioning Services Console Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Master Target Device Installation Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Upgrade Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Installation and Configuration Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Planning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

MS SQL Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Authentication and Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Reviewing System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Map out Your Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

Getting Product Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41Installing the license server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

Installing Provisioning Services Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42Silent Product Software Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Configuring the Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43Configuration Wizard Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Starting the Configuration Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Network Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Identify the Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Identify the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47Create a New Store for a New Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Identify the Site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48Select the License Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Configure User Account Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Select network cards for the Stream Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Configure Bootstrap Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50Running the Configuration Wizard Silently. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

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

Contents

iv

Installing Provisioning Services Server Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Silent Product Software Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

Adding Additional Provisioning Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Managing Administrative Roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Preparing a Master Target Device for Imaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Preparing the Master Target Device's Hard Disk. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57Configuring a Master Target Device's BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58

Configuring Network Adapter BIOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Installing Master Target Device Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Installing Provisioning Services Target Device Software on a Windows Device. . . . . .60

Creating vDisks Automatically. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Using the Imaging Wizard to Create a New vDisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Assigning vDisks to Target Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62Uninstalling Product Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

Uninstalling the Provisioning Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63Uninstalling Windows Target Device Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Uninstall Linux Target Device Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Uninstalling Product Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Uninstalling the Provisioning Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Uninstalling Windows Target Device Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64Uninstall Linux Target Device Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

4 Installing and Configuring Embedded Target Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68Installing Embedded Target Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68Un-installing an Embedded Target Device Package. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Windows XP Embedded Build Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Setting Up Embedded Target Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

5 Upgrading a Provisioning Services Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75Upgrading the Database and Provisioning Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76

Upgrading the Database and the First Provisioning Server. . . . . . . . . . . . . . . . . . . . . . . . . . . 76Upgrading Remaining Provisioning Servers in the Farm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Upgrading vDisks by Re-imaging. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Automated Upgrade of vDisks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77

Automated Inline Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 0Automated Rolling Upgrade. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Upgrading vDisks Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Image Back to Master Target Devices Hard Drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79


v

Upgrading vDisks using Hyper-V. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

6 Managing Multiple Network Interface Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Requirements and Considerations for Manufacturer's NIC Teaming. . . . . . . . . . . . . . . . . . . . . . .85Requirements and Considerations for Provisioning Services NIC Failover. . . . . . . . . . . . . . . .85

7 Managing Bootstrap Files and Boot Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .87Configuring the Bootstrap File From the Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Configuring the Bootstrap File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90Using the Manage Boot Devices Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92

Configuring Boot Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

Contents

vi

Chapter 1

Provisioning Services Product OverviewTopics: Software-Streaming Process

Overview Benefits and Features Provisioning Services

Product Infrastructure Additional Provisioning

Services' ProductComponents

Product Utilities Provisioning Services

Administrator Roles Provisioning Services and

Resources

Most enterprises struggle to keep up with the proliferationand management of computers in their environment. Eachcomputer, whether it is a desktop PC, a server in a datacenter, or a kiosk-type device, must be managed as anindividual entity. The benefits of distributed processing comeat the cost of distributed management. It costs time andmoney to set up, update, support and ultimatelydecommission each computer. The initial cost of the machineis often dwarfed by operational costs.Over the years, various software solutions have been offeredthat are designed to address the operational challenges facedby IT organizations. For example:w Imaging solutions allow backup and duplication of existing

machines.w Distribution tools can automate many of the tasks required

to install and upgrade software across many computers.w Simplifies the management of the end points by removing

most software and processing locally.Each of these approaches has benefits and limitations.Provisioning Services takes a very different approach byfundamentally changing the relationship between hardwareand the software that runs on it. By streaming a single shareddisk image rather than copying images to individual machines,Provisioning Services enables organizations to reduce thenumber of systems that they manage, even as the number ofcomputers continues to grow. This solution simultaneouslyprovides the efficiencies of a centrally managed solution withthe benefits of distributed processing.

Provisioning ServicesStreaming TechnologyProvisioning Services streaming technology allows computersto be provisioned and re-provisioned in real-time from a singleshared-disk image. In doing so, administrators can completelyeliminate the need to manage and patch individual systems.Instead, all image management is done on the master image.The local hard-disk drive of each system may be used for

7

runtime data caching or, in some scenarios, removed from thesystem entirely, which reduces power usage, system failurerates, and security risks.

Provisioning ServicesSolutionThe Provisioning-Services solutions infrastructure is based onsoftware-streaming technology. Using Provisioning Services,administrators prepare a device (master target device) forimaging by installing any required software on that device. AvDisk image is then created from the master target deviceshard drive and saved to the network (on a Provisioning Serveror storage device).Once the vDisk is available from the network, the targetdevice no longer needs its local hard drive to operate; it bootsdirectly across the network. The Provisioning Server streamsthe contents of the vDisk to the target device on demand, inreal time. The target device behaves as if it is running fromits local drive. Unlike thin-client technology, processing takesplace on the target device.

Provisioning ServicesEditionsThe Provisioning Server editions you can choose from include:w Provisioning Services for Datacentersw Provisioning Services for Desktops

Note:The ability to create an embedded target devices issupported in either edition.A single Provisioning Server can stream to both data centerand desktop target devices.

Product LicensesProduct licenses are issued based on the product edition thatyou choose. For Citrix product licensing documentation, open

Chapter 1 Provisioning Services Product Overview

8

the Citrix Knowledge Center, then select Licensing under theKnowledge Resources section.

Note: The following licensing time out conditions exist:w If no licenses are available: 96 hrsw Contact is lost with the license server: 720 hoursw Out of Box Grace Period (OOBGP): 96 hours


9

Software-Streaming Process OverviewProvisioning Services provides all of the tools you need to bring software-streamingtechnology to your computing environment. After installing and configuring ProvisioningServices components, a vDisk is created from a devices hard drive by taking a snapshotof the OS and application image, and then storing that image as a vDisk file on thenetwork. A device that is used during this process is referred to as a Master targetdevice. The devices that use those vDisks are called target devices.vDisks can exist on a Provisioning Server, file share, or in larger deployments, on astorage system that the Provisioning Server can communicate with (iSCSI, SAN, NAS,and CIFS). vDisks can be assigned to a single target device as Private Image Mode, or tomultiple target devices as Standard Image Mode.When a target device is turned on, it is set to boot from the network and tocommunicate with a Provisioning Server (refer to Step 1 in the illustration that follows).

The target device downloads the boot file from a Provisioning Server (refer to Step 2),and then the target device boots. Based on the device boot configuration settings, theappropriate vDisk is located, then mounted on the Streaming Server (refer to step 3).The software on that vDisk is streamed to the target device as needed. To the targetdevice, it appears like a regular hard drive to the system.


10

Instead of immediately pulling all the vDisk contents down to the target device (asdone with traditional or imaging deployment solutions), the data is brought across thenetwork in real-time, as needed. This approach allows a target device to get acompletely new operating system and set of software in the time it takes to reboot,without requiring a visit to a workstation. This approach dramatically decreases theamount of network bandwidth required by traditional disk imaging tools; making itpossible to support a larger number of target devices on your network withoutimpacting overall network performance.

Benefits and FeaturesThere are many benefits associated with using vDisks as opposed to hard drives. One ofthose benefits includes not having to install software on each target device within afarm. Instead, when booting, software is dynamically assigned to the target device bythe Provisioning Server. This allows a target device to completely change theiroperating systems and application stack, in the time it takes to reboot.Using Provisioning Services, any vDisk can be configured in Standard Image mode. AvDisk in Standard Image mode allows many computers to boot from it simultaneously;greatly reducing the number of images that must be maintained and the amount ofstorage that would be required. The vDisk is in read-only format and the image can notbe changed by target devices.

Benefits for XenApp and other Server FarmAdministrators

If you manage pool of servers that work as a farm, such as XenApp servers or webservers, maintaining a uniform patch level on your servers can be difficult and timeconsuming. With traditional imaging solutions you start out with a pristine goldenmaster image, but as soon as a server is build with the master image, you now mustpatch the individual server along with all of the others. Rolling patches out toindividual servers in your farm is not only inefficient, but it can also be unreliable.Patches often fail on an individual server and you may not realize you have a problemuntil users start complaining or the server has an outage. Once that happens, gettingthe server back into sync with the rest of the farm can be challenging and sometimes itcan require a full re-imaging of the machine.With Provisioning Services, patch management for server farms is simple and reliable.You start out managing your golden image and you continue to manage that singlegolden image. All patching is done in one place and then streamed to your serverswhen they boot-up. Server build consistency is assured because all your servers areusing a single shared copy of the disk image. If a server becomes corrupted, simplyreboot it and it's instantly back to the known good state of your master image.Upgrades are extremely fast. Once you have your updated image ready for productionyou simply assign the new image version to the servers and reboot them. In the time ittakes them to reboot you can deploy the new image to any number of servers. Just asimportantly, roll-backs can be done in the same manner so problems with new imageswill not take your servers or your users out of commission for an extended period of time.


11

Benefits for Desktop AdministratorsAs part of XenDesktop, desktop administrators have the ability to use ProvisioningServices' streaming technology to simplify, consolidate, and reduce the costs of bothphysical and virtual desktop delivery. Many organizations are beginning to exploredesktop virtualization. While virtualization addresses many of the consolidation andsimplified management needs of IT, deploying it also requires deployment of supportinginfrastructure. Without Provisioning Services, storage costs can put desktopvirtualization out of the budget. With Provisioning Services, IT can reduce the amountof storage required for VDI by as much as 90%. At the same time the ability to managea single image rather than hundreds or thousands of desktops significantly reduces thecost, effort, and complexity for desktop administration.Not all desktops applications or user groups can be supported by virtual desktops. Forthese scenarios, Provisioning Services IT can still reap the benefits of consolidation andsingle image management. Desktop images are stored and managed centrally in thedatacenter and streamed out to physical desktops on demand. This model worksparticularly well for standardized desktops such as those in lab and trainingenvironments, call centers, and "thin client" devices used to access virtual desktops.

Provisioning Services Product InfrastructureThe infrastructure design includes a hierarchy that directly relates to administrativeroles within a Provisioning Services farm.The graphic that follows provides a high-level view of the Provisioning Servicesinfrastructure and illustrates how Provisioning Services components might appearwithin that implementation.


12

Provisioning Services Farm HierarchyThe farm hierarchy consists of the following major levels:w Farms on page 13w Sites on page 13w Device Collections on page 14For each major component level, administrative roles exists.

FarmsA farm represents the top level of a Provisioning Services infrastructure. Farms providea Farm administrator with a method of representing, defining, and managing logicalgroups of Provisioning Services components into sites.All sites within a farm share that farms Microsoft SQL database. A farm also includes aCitrix License Server, local or network shared storage, and collections of target devices.In the Console window, administrators select the farm that they want to manage orview. Sample tasks that are specific to a farm can include managing:w Farm configurationsw Product licensingw High Availability configurationsw Active Directory configurationsw User Groupsw Administrative roles

Note: The Console does not need to be directly associated with the farm becauseremote administration is now supported on any Console that can communicate withthat farms network.

SitesA site provides both a site administrator and farm administrator, with a method ofrepresenting and managing logical groupings of Provisioning Servers, Device Collections,and local shared storage.A site administrator can perform any task that a device administrator or deviceoperator can perform. A site administrator can also perform additional tasks such asmanaging:w Print serversw Device administrator and device operator role configurations


13

w Provisioning Serversw Shared storagew User GroupsProvisioning Servers within a site, communicate with farm components to obtain theinformation necessary to boot target devices and to provide target devices with theappropriate vDisk. Provisioning Server(s) must be able to communicate with the storewhere those vDisks exist.

Device CollectionsDevice collections provide the ability to create and manage logical groups of targetdevices, which are typically created and managed by a device administrator (a farmand site administrator can also perform a device administrators tasks).A device collection could represent a physical location, a subnet range, or a logicalgrouping of target devices. Creating device collections simplifies device managementby performing actions at the collection level rather than at the target-device level.A target device can only be a member of one device collection. For device collectiondetails, refer to Managing Device Collections.

Additional Provisioning Services' ProductComponents

The Provisioning Services infrastructure also consists of the following additionalcomponents:Provisioning Servers on page 14Provisioning Services Database on page 15Console on page 15vDisks on page 16Target Devices on page 17Store on page 18Device Collections on page 19Network Services on page 19

Provisioning ServersA Provisioning Server is any server that has Stream Services installed. It is used tostream software from vDisks, as needed, to target devices. In some implementations,vDisks reside directly on the Provisioning Server. In larger implementations, ProvisioningServers get the vDisk from a shared-storage location on the network.


14

Provisioning Servers also retrieve and provide configuration information to and from theProvisioning Server Database. Provisioning Server configuration options are available toensure high availability and load-balancing of target device connections.For Provisioning Server details, refer to Managing Provisioning Servers.

Provisioning Services DatabaseThe database stores all system configuration settings that exist within a farm. Only onedatabase can exist within a farm and all Provisioning Servers in that farm must be ableto communicate with that database. You may choose to leverage an existing SQL Serverdatabase or install SQL Server Express, which is free and available from Microsoft.

ConsoleThe Console is a utility that is used to manage your Provisioning Servicesimplementation. After logging on to the Console, you select the farm that you want toconnect to. Your administrative role determines what you can view in the Console andmanage in the farm.The following illustration displays the farm hierarchy in the tree pane and the keyscomponents in the Console window.

Action MenuThe Action menu displays Provisioning Services tasks that can be performed on anobject that is highlighted in the Console. The same tasks are available when you right-click on the object in the Console.


15

Tasks are object specific and can only be performed if the user has the appropriate roleassigned (role-based administration). Your role determines what displays in theConsole. For example, if you are a farm administrator, you can perform all tasks andsee all objects in the farm. Device administrators can only perform device-collectionmanagement tasks on collections to which they have privileges. Administrator roles aredescribed later in this chapter.

Note:MMC (Microsoft Management Console) specific console features are not described inthis document. Refer to Microsofts MMC documentation for detailed information.

Console Tree and Details PaneTo view information about an object in the Details pane, click on the object or folder inthe Tree pane. The Details pane provides information such as the objects name and adescription of that object.Properties MenusTo view or change an objects properties, right-click on the object, then select theProperties menu option. You can also highlight the object in the Console window, thenselect Properties from the Action menu options. The Properties dialog displaysproperty settings in tabular format.

vDisksvDisks exist as disk image files on a Provisioning Server or on a shared storage device.vDisk images are configured to be in Private or Standard Image disk mode. (For moreinformation, refer to the Configuring vDisk Modes section in the Administrator's Guide).vDisks are associated with a sites vDisk pool. To view vDisks within a pool, expand thevDisk Pool folder in the Console tree.vDisk PoolsvDisk pools are the collection of all vDisks available to a site. There is only one vDiskpool per site. The method used to locate a vDisk on a server share is illustrated in thegraphic that follows.


16

1. The target device begins the boot process by communicating with a ProvisioningServer and acquiring a license.

2. The Provisioning Server checks the vDisk pool for vDisk information, which includesidentifying the Provisioning Server(s) that can provide the vDisk to the targetdevice and the path information that server should use to get to the vDisk. In thisexample, the vDisk shows that only one Provisioning Server in this site can providethe target device with the vDisk and that the vDisk physically resides on theFinance Server (shared storage at the farm level).

3. The Provisioning Server locates the vDisk on Finance Server, then streams thatvDisk, on demand, to the target device.

On the Consoles Create a New vDisk dialog, you can add a new vDisk file to a store andselect the Provisioning Server that will create the vDisk file on a Provisioning Server oron shared storage.

Target DevicesA device, such as a desktop computer or server, that boots and gets software from avDisk on the network, is considered a target device.

Note: In the product documentation, the term target device is used generically whenreferring to any device within the a Provisioning Services Farm, which boots and getssoftware from a vDisk on the network.

Target devices deliver a higher level of security than traditional technologies, by fullyutilizing your existing management infrastructure. Each target device continues to haveits own unique identity on the network and within your existing network operatingsystem (i.e. Active Directory, Novell E-Directory and other LDAP directories). Target


17

devices can continue to be managed by group policies and existing security policiespushed out by these directory management tools.In addition to using existing policy management tools, greater security is inherit by thefact that there is no longer a hard drive in the target device. If the target device isstolen, data is not lost. Instead, it is easily ported to another target device.A target device can only be a member of one device collection. Expanding a DeviceCollection folder in the Consoles tree allows you to view members of a devicecollection and information such as the target device name, IP address, vDisk, and theProvisioning Server currently providing the vDisk.Target device settings are made in the Consoles Device Properties dialog, whichincludes settings such as printer assignments.

StoreA store is a logical name that is given to a physical vDisk storage location. The storename is the common name used by all Provisioning Servers within the farm.Example OneThe physical vDisk for Windows XP (WINXP1) resides on a Provisioning Server (PVS1)local to a site. The vDisk path is:C:\vDisks\WINXP1.vhd

The logical name that is given to this physical location is the store.Store name (logical name): bostonwinxpExample TwoThe physical vDisk for Windows XP (WINXP1) resides on a network share (FinanceShare)at the farm level. The vDisk path for Provisioning Server (PVS1) to WINXP1 is:\\FinanceShare\vDisks\WINXP1.vhd

Access or visibility to a store depends on the users administrative privileges:w Farm administrators have full access to all stores within the farm.w Site administrators have access to only those stores owned by the site. They can

delete stores owned by the site but they can not modify store properties or addvDisks to the store.

w Device administrators and device operators have read-only access and can not viewstore information. Site Administrators may also have read-only access if that storeexists at the farm level, or if that store belongs to another site.

Stores that exist in a farm can be viewed by expanding the Store parent directory inthe Consoles tree. The Stores property settings can be modified from the PropertiesDialog.


18

Device CollectionsDevice collections provide the ability to create and manage logical groups of targetdevices. A device collection could represent a physical location, a subnet range, or alogical grouping of target devices. Creating device collections simplifies devicemanagement by performing actions at the collection level rather than at the target-device level.

Note: A target device can only be a member of one device collection.

Device collections are created and managed by farm administrators, site administratorsthat have security privileges to that site, or device administrators that have securityprivileges to that collection. Device administrators can not modify the collection itself;only the devices within it. Device operators can only perform tasks on devicecollections that they are assigned to.

Network ServicesNetwork services include a BOOTP service, Preboot Execution Environment (PXE)service, and a TFTP service. These service options can be used during the boot processto retrieve IP addresses, and locate then download the boot program from theProvisioning Server to the target device. Alternative boot options are also available,refer to Booting From an Optional Boot Device.

Note: For network service details, refer to Managing Bootstrap Files and BootDevices on page 87 in this document.

Product UtilitiesIn addition, Provisioning Services includes several tools for use when configuring andmanaging a Provisioning Services deployment. After installing Provisioning Servicessoftware, the following tools become available:w Installation Wizard Use this wizard to install Provisioning Services components to

create a Provisioning Servers and Master target devices.w Configuration Wizard Use this wizard to configure Provisioning-Server components,

including network services, and database permissions. This wizard is installed duringthe Provisioning Services installation process.

w Imaging Wizard On the master target device, run the Provisioning Services ImagingWizard to create a vDisk file in the Provisioning Services database and then image tothat file without having to physically go to a Provisioning Server. This utility isinstalled during the target device installation process.


19

w Virtual Disk Status Tray Use this target device utility to get target-deviceconnection status and streaming statistical information. This utility is installedduring the Provisioning Services target device installation process.

w Boot Device Manager Use this utility to configure a boot device, such as a USB or CD-ROM, which then receives the boot program from the Provisioning Services.

w Upgrade Utilities There are several upgrade methods available. The method youselect depends on your network requirements.

w Programming Utilities Provisioning Services provides programmers with amanagement application programming utility and a command line utility. Theseutilities can be accessed by all users. However, users can only use those commandsassociated with their administrator privileges. For example, a Device Operator isable to use this utility to get a list of all target devices that they have access to.

Provisioning Services Administrator RolesThe ability to view and manage objects within a Provisioning Services implementationis determined 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 share the same administrative privileges within a farm. Anadministrator may have multiple roles if they belong to more than one group.Groups are managed at the farm level through the Consoles Farm Properties dialog.The following roles exist within a Provisioning Services farm:w Farm Administrator Farm administrators can view and manage all objects within a

farm. Farm administrators can also create new sites and manage role membershipsthroughout the entire farm.

w Site Administrator Site administrators have full management access to the allobjects within a site. For example, a site administrator can manage ProvisioningServers, site properties, target devices, device collections, vDisks, vDisk pools, andlocal vDisk stores. A site administrator can also manage device administrator anddevice operator memberships.

w Device Administrator Device administrators can perform all device-collectionmanagement tasks on collections to which they have privileges, including; viewvDisk properties (read-only), assign or remove vDisks from a device, boot or shutdown target devices, edit device properties, and send messages to target deviceswithin a device collection to which they have privileges.

w Device Operator Device operators can view target device properties (read-only),boot or shut down target devices, and send messages to target devices within adevice collection to which they have privileges.

For details on administrator roles, refer to 'Managing Administrators' in theAdministrator's Guide.


20

Provisioning Services and ResourcesThe following services and resources are available to support Provisioning Services.w Provisioning Services Documentationw Getting Service and Supportw Getting the Subscription Advantagew Locating the Citrix Developer Networkw 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 Systems Web site at 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/ or fromCitrix eDocs at http://support.citrix.com/proddocs/index.jsp.Citrix Product Licensing DocumentationFor Citrix product licensing documentation, refer to Licensing Your Product under theTechnologies section on Citrix eDocs (http://support.citrix.com/proddocs/index.jsp).Release NotesThis 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.Programmers GuidesAdministrators with the appropriate privileges can use any of the following guides tomanage your implementation from command lines.w MCLI Programmers Guide


21

w SOAP Server Programmers Guidew PowerShell Programmers GuideThese guides are available as a PDF and can be accessed from the Citrix KnowledgeCenter: http://support.citrix.com/Virtual Disk Status Tray HelpThe 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.Finding Additional DocumentationFrom the Help menu or product installation directory, the following additionaldocumentation is available for optional Provisioning Services utilities:w Boot Device Manager (BDM.chm)w BOOTPTab Editor (bootptab-editor-help.chm)w PXE (pxemap.chm)

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 Citrix

environment.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 Citrixs 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 yourorganizations Citrix products.


22

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.

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 Systems Web site at: http://www.adobe.com/


23


24

Chapter 2

Whats New in This ReleaseThis section identifies new features and enhancements thatare associated with this release.

Administration andManageabilityThe following administration and management features andenhancements have been implemented in this release:Image Managementw vDisk Imaging Wizard; automates vDisk creation procedures

from the master target device such as, connecting to thefarm, creating the vDisk file and imaging.

Note: For details, refer to the Using the Imaging Wizardsection in the Administrator's Guide.

Store Managementw A default store can now be created when the Configuration

Wizard runs.

Note: The wizard only allows a server to create or joinan existing store if it is new to the database.

w New store path configuration settings are now validated.

Note: For details, refer to the Store Properties section inthe 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 multiple ProvisioningServers without having to deploy solutions such as NASGateway, Cluster File System, and Windows ClusterServices. After enabling the Managed Store feature,administrators can quickly change a store's availability on aSAN volume to be either active (Active Mode/read-only) oroffline (Maintenance Mode/read/write).

25

Note: For details, refer to the Working with ManagedStores section in the Administrator's Guide.

High Availability Managementw MS SQL Database Mirroring is now supported by Provisioning

Services.

Note: For details, refer to the Database Mirroring sectionin the Administrator's Guide.

w New load balancing algorithms provide for more robust anddynamic load balancing of vDisks between qualifiedProvisioning Servers.

Target Device Managementw The Microsoft KMS and MAK volume licensing process has

been almost entirely automated and can be configuredwhen the Imaging Wizard is run to create the vDisk. It canalso be configured using the Console user interface, MCLIor PowerShell command-line interface. This enhancementwas introduced in 5.6 SP1.

w Auto-Add Target Device Wizard The new Auto-Add wizard automates the configuration

of rules for automatically adding new target devices tothe Provisioning Services database.

Expanded target device naming capabilities.

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

Active Directory Managementw Support for Cross Forest Active Directory deployment is

now supported.Product Installationw Ability to simplify large farm deployment with scripted

server configuration.Other Enhancementsw Support for 10 GigE networking and jumbo packets.

Removed FeaturesThe following product feature was removed in this release:

Chapter 2 Whats New in This Release

26

w Port Blocker


27

Chapter 2 Whats New in This Release

28

Chapter 3

Installing and Configuring ProvisioningServicesTopics: Installation Wizards and

Utilities Installation and

Configuration Tasks Planning Getting Product Licensing Installing Provisioning

Services Software Configuring the Farm Installing Provisioning

Services Server Software Adding Additional

Provisioning Servers Managing Administrative

Roles Preparing a Master Target

Device for Imaging Creating vDisks

Automatically Assigning vDisks to Target

Devices Uninstalling Product Software Uninstalling Product Software

This chapter describes the Provisioning Services installationwizards that are included in the product software, and theinstallation and configuration procedures required to create anew Provisioning Services implementation.

Note: Provisioning Services product software andcomponents are installed from the product CD-ROM or fromthe product download site.

29

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 Servicew Network Boot Services (optional)w Configuration Wizard (runs after the installation wizard to configure installed

components and creates the Provisioning Services database)w Programming Utilitiesw 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 Management utility. The Console can be installed on anymachine that can communicate with the Provisioning Services database.

Master Target Device Installation WizardFor Windows: PVS_Device.exe or PVS_Device_x64.exeInstalls 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 theImaging Wizard.

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 installed

product software.

Chapter 3 Installing and Configuring Provisioning Services

30

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 312. Getting Product Licensing on page 413. Installing Provisioning Services Software on page 424. Configuring the Farm on page 435. Adding Additional Provisioning Servers on page 566. Managing Administrative Roles on page 567. Creating a Store8. Creating and Formatting a New vDisk File9. Adding a Target Device to the Database

10. Assigning vDisks to Target Devices on page 6211. Preparing a Master Target Device for Imaging on page 5712. Creating vDisks Automatically on page 60

PlanningThe following prerequisite steps must be completed prior to installing and configuringyour implementation:w MS SQL Database on page 31w Authentication and Configuration on page 32w Reviewing System Requirements on page 34w Map out Your Farm on page 40

MS SQL DatabaseSelect which of following MS SQL 2005, MS SQL 2008, MS SQL 2008R2 Server editions touse for the Provisioning Services Database:w SQL Server Express Editionw SQL Server Workgroup Editionw SQL Server Standard Edition


31

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.

Database MirroringTo use the MS SQL Server's database mirroring feature within your farm:

Note: For Provisioning Services to support MS SQL database mirroring, the databaseneeds to be properly configured with High-safety mode with a witness(synchronous).

1. Run the Configuration Wizard, then select the Create farm option.2. Configure the mirroring database by following Microsoft's instructions.3. Re-run the Configuration Wizard, then select the Join existing farm option.4. On the Existing Farm dialog, select the checkbox next to Specify database mirror

failover partner. Enter the database server and instance name of the databasemirror failover partner and, if necessary, an optional TCP port.

Note: Refer to Configuring the Farm on page 43 for details.

Authentication and ConfigurationProvisioning Services uses Windows authentication. All Provisioning Servicescomponents, 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 PermissionsThe following MS SQL permissions are required for the user that is running theConfiguration Wizard:w dbcreator; required for creating the database


32

w securityadmin; required for creating the SQL logins for the stream and soap servicesIf 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 PermissionsThe user context for the Stream and Soap services requires the following databasepermissions:w db_datareaderw db_datawriterw 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 servicew Registry read accessw Program Files\Citrix\Provisioning Servicesw Read/write access to any vDisk locationDetermine which of the following supported user accounts the Stream and Soapservices will run under:w Network service account

Minimum privilege local account that authenticates 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).


33

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 a

Windows Domain running Active Directory. This option enables you to leverageActive Directory for Provisioning Services roles.

Note: Windows 2000 Domains are no longer supported.

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.Operating Systems

Provisioning Services English on English, Japanese, German, French, Spanish,Simplified Chinese, Traditional Chinese, Korean, and Russian versions of operatingsystems are supportedWindows Server 2003 SP2 (32 or 64-bit); all editionsWindows Server 2008 (32 or 64-bit); all editionsWindows Server 2008 R2 and Windows Server 2008 R2 SP1; Standard, DataCenter, andEnterprise editions

Provisioning Server System RequirementsIn 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.


34

ProcessorIntel or AMD x86 or x64 compatible; 2 GHz minimum; 3 GHz preferred; 3.5 GHz DualCore/HT or similar for loads greater than 250 target devices.

MemoryMinimum of 2 GB RAM; 4 GB preferred; 4 GB is required for a larger number of vDisks(greater than 250).

Hard Disk and StorageThere must be enough space on the hard disk to store the vDisks. For example, if youhave a 15 GB hard drive, you can only create a 14 GB vDiskAdditional requirements depend on several factors such as:Hard disk capacity requirement of the operating system and applications running ona target device. It is recommended to add 20% on the base size of the final installedimage.Private Image Mode - number of target devices using a vDisk in Private Image mode(vDisks in Private Image mode should be backed up daily)Standard Image Mode - number of target devices using a vDisk in Standard Image mode.Note: Best practices include making a copy of every vDisk created.Windows 2003 and 2003 x64; minimum of 250 MB on the application drive.Minimum Common Storage Sizesw 250 MB for the databasew 5 GB on a clean Windows systemw 5 GB per vDisk for Linux Class imagesw 15 GB per vDisk for Vista Class images (estimated)Additional space per vDisk based on additional significant applications loaded.

Network AdapterStatic IPMinimum 100 MB Ethernet, 1 GB Ethernet preferred; Dual 1 GB Ethernet for morethan 250 target devices.Note: Two NICs often perform better than a single dual-ported NIC.

Required SoftwareThe Provisioning Server install program requires the installation of WindowsPowerShell 2.0 on each server.

Network RequirementsUDP and TCP Port Requirements

Provisioning Server to Provisioning Server Communication


35

Each Provisioning Server must be configured to use the same ports (UDP) in order tocommunicate with each other (uses the Messaging Manager). At least five ports mustexist in the port range selected. The port range is configured on the Stream Servicesdialog when the Configuration Wizard is run.

Note: If configuring for a high availability (HA), all Provisioning Servers selected asfailover servers must reside within the same site. HA is not intended to crossbetween sites.

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

Provisioning Servers to Target Device CommunicationEach Provisioning Server must be configured to use the same ports (UDP) in order tocommunicate with target devices (uses the StreamProcess). The port range isconfigured using the Consoles Network tab on the Server 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 CommunicationEach Provisioning Server that will be used as a login server must be configured on theStream Servers Boot List dialog when the Configuration Wizard is run.The default port for login servers to use is UDP 6910

Console CommunicationThe Soap Server is used when accessing the Console. The ports (TCP) are configuredon the Stream Services dialog when the Configuration Wizard is run.The default ports are TCP 54321 and 54322 (Provisioning Services automatically setsa second port by incrementing the port number entered by 1; 54321 + 1).If this value is modified, the following command must be run.For Powershell: MCLI-Run SetupConnectionFor MCLI: MCLI Run SetupConnection(refer to the Provisioning Server Programmers Guides for details).

TFTP CommunicationThe TFTP port value is stored in the registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BNTFTP\Parameters Port


36

The TFTP port defaults to UDP 69.

TSB CommunicationThe TSB port value is stored in the registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PVSTSB\Parameters PortThe TSB port defaults to UDP 6969.

Port FastPort Fast must be enabled.

Network CardPXE 0.99j or greater.

Network AddressingDHCP

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)Provisioning Services English on English, Japanese, German, French, Spanish,Simplified Chinese, Traditional Chinese, Korean, and Russian versions of operatingsystems are supported.

Windows Server 2003 SP1 (32 or 64-bit); all editionsWindows Server 2008 (32 or 64-bit); all editionsWindows Server 2008 R2 and Windows Server 2008 R2 SP1:w Standardw DataCenterw EnterpriseWindows XP Professional (32 or 64-bit)Windows Vista (32 or 64-bit):w Businessw Enterprisew Ultimate (retail licensing)


37

Note: The Ultimate edition of Windows Visa is only supported in Private Imagemode.

Windows 7 and Windows 7 SP1 (32 or 64-bit):w Enterprisew Professionalw Ultimate

Note: The Ultimate edition of Windows 7 is only supported in Private Image mode.

Licensing Key ConsiderationsWindows Vista Business, Windows Enterprise, Windows 7, and Windows Server 2008and Server 2008 R2 are deployed with either Key Management Server (KMS) or withMicrosoft Multiple Activation Key (MAK) volume licensing keys. Windows Office 2010is deployed with KMS.

Note: In order for MAK licensing to work, the Volume Activation Management Tool(VAMT) must be installed on all login servers within a farm. This tool is availablefrom http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en.

Both Private and Standard Image Modes support MAK and KMS.Volume licensing is configured within the vDisk image when the Imaging Wizard is runon the Master target device. Volume licensing is configured for the vDisk file on theMicrosoft Volume Licensing tab, which is available from the Consoles' vDisk FileProperties dialog.

Supported File System TypesNTFS

Required SoftwareThe target device product installation program requires Windows PowerShell 2.0 beinstalled on each device.

Linux Target DevicesRed 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.3Novell (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


38

SuSE Linux Enterprise Desktop 10SuSE Linux Enterprise Desktop 10 SP1SuSE Linux Enterprise Desktop 10 SP2Novell Linux Desktop 9.0 x86 onlyNovell Linux Desktop 9.1 x86 onlyNovell Linux Desktop 9.3 x86 onlyNovell Linux Desktop 9.4 x86 onlyTurbo Linux FUJI 11Vine LinuxVine Linux 4.0 x86 onlyVine Linux 4.1 x86 onlyVine Linux 4.2 x86 only

Ubuntu LinuxSupport is available for only those kernels that ship with the Linux distributionreleases listed above, and any subsequent service pack releases.x86-based Linux; RAM cache size is limited to less than 1 GB when using SharedImage vDisk mode. Actual limit of RAM cache size decides on kernel's virtual addressspace. Set the value of RAM cache size, then minus the space needed to map thekernel code itself. This limitation is on the Linux architecture.

Provisioning Services Console RequirementsProcessor

Minimum 1 GHz, 2 GHz preferredMemory

Minimum 1 GB, 2 GB preferredHard Disk

Minimum 500 MBOperating System

Windows Server 2003 (32 or 64-bit); all editionsWindows Server 2008 (32 or 64-bit); all editionsWindows Server 2008 R2; Standard, DataCenterand Enterprise EditionsWindows XP Professional (32 or 64-bit)Windows Vista (32 or 64-bit)w Businessw Enterprisew Ultimate (retail licensing)


39

XenDesktop Setup Wizard and Streamed VM Setup Wizard Requirementsw Supported System Center Virtual Machine Management (SCVMM) Servers include

SCVMM 2007, 2008 R2, 2008 R2 SP1w Supported Hypervisors 5.6 SP1

XenServer 5.5 Update 2, XenServer 5.6 ESX 4.1 HyperV 2008, HyperV 2008 R2 SP1

w Supported Hypervisors 5.6 XenServer 5.5 Update 2 ESX 3.0 Update 4 HyperV 2008

OtherRequired: MMC 3.0Optional: Adobe Acrobat Reader highly recommended.

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 DatabaseOnly 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 Provisioning

Servers within the farm.w A new SQL Express database machine, created using the SQL Express software,

which is free from Microsoft.Database serverHost Name:Instance Name:License serverHost Name:Vendor Daemon / license server port:


40

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, or

implementations with one Citrix product.w Stand-alone: Separate system that has an existing license server installed; for larger

implementations or implementations using multiple Citrix products.w Point to an existing license server.Licensing Grace PeriodsThere are three types of grace periods provided by Citrix Licensing. ProvisioningServices implements these grace periods as follows:w Out of Box Grace Period (OOBGP) is 96 hours: If Provisioning Services is installed

prior to either installation of a Citrix License Server or the allocation of validproduct edition licenses for XenApp, XenDesktop, XenServer, Essentials for Hyper-Vor Provisioning Services for Datacenters, it will provision unlimited systems for aperiod of four days (96 hours; this is standard across most Citrix products). If thisgrace period lapses, provisioning sessions that are already running will continue torun, but any new or restarted provisioning sessions will be subject to the 'No ValidLicense Grace Period'.

w License Server Connectivity Outage Grace Period is 30 days (720 hours): Ifconnectivity to the Citrix License Server is lost, Provisioning Services will continueto provision systems for a period of thirty days (720 hours; this is standard acrossmost Citrix products). If this grace period lapses, any existing or new provisioningsessions is subject to the 'No Valid License Grace Period'.

w No Valid License Grace Period is 5.6 = 3 hours, 5.6 SP1 = 96 hours: If ProvisioningServices cannot obtain a valid license for a provisioning session, a warning dialogdisplays on the provisioned system, but the session is allowed to continue runningfor the period of time shown in the table below. When this grace period lapses, eachaffected session is be shut down. This grace period may apply in the followingscenarios: No valid edition licenses for XenApp, XenDesktop, XenServer, Essentials for Hyper-

V or Provisioning Services are available. Licenses are available, but have expired (applies to Evaluation, NFR, and Internal

Use license). The SA Expiration date of the licenses precedes the release date of the version of

Provisioning Services that is being used.


41

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: When installing Provisioning Services software on a server that has previousversions of .Net installed, Citrix recommends rebooting if prompted to do so duringthe .Net installation.

Note: This installation task is for new Provisioning Services implementations. Forupgrade tasks, refer to Upgrading a Provisioning Services Farm on page 75. Thesoftware can also be installed silently. Refer to Silent Product Software Install on page43

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 Services

Welcome 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 to

continue. The Customer Information dialog appears.4. Type or select your user name and organization name in the appropriate text

boxes, then click Next. The Destination Folder dialog appears.5. Click Change, then enter the folder name or navigate to the appropriate folder

where 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 those

components.


42

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

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 aFeature 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 the

Program 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 page43 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:.exe /s /v"/qn"Or, use the following to set a different destination:.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.


43

When configuring a Provisioning Server, consider the following:w All Provisioning Servers within a farm must share the same database to locate vDisks

for target devices on shared storage devices within the farm. If that shared storagedevice is a Windows network share, refer to configuration information described inthe Administrators 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 53.

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 similarconfiguration settings. For details, refer to Running the Configuration Wizard Silentlyon page 53.

w Network Topology on page 45w Identify the Farm on page 45w Identify the Database on page 47w Identify the Site on page 48w Select the License Server on page 49w Select network cards for the Stream Service on page 50w Configure Bootstrap Server on page 50

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 Services

Configuration Wizard2. After starting the Configuration Wizard, click Next to begin the configuration tasks

that follow.


44

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 the

following network services to use, then click Next:w Microsoft DHCPw Provisioning Services BOOTP servicew 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 informationEach 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


45

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

Create farmi. On the Farm Configuration dialog, select the Create Farm radio button to

create a new farm, then click Next.ii. Use the Browse button to browse for existing SQL databases and instances in

the 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 in the Provisioning Services Administrator'sGuide for more information.

iv. Click Next to continue on to the Identify the Database on page 47 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 in the Provisioning Services Administrator'sGuide 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 49 procedure.


46

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

If 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 database

exists and the instance to use (to use the default instance, SQLEXPRESS, leavethe 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 Farmprocedure.

2. To change the database to a new databasea. 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.Select the security group to use: Use Active Directory groups for security

Note: When selecting the Active Directory group to act as the FarmAdministrator from the drop-down list, choices include any group the currentuser belongs to. This list includes Builtin groups, which are local to the currentmachine. Avoid using these groups as administrators, except for testenvironments. Also, be aware that some group names may be misleading and


47

appear to be Domain groups, which are actually Local Domain groups. Forexample: ForestA.local/Builtin/Administrators.

Use Windows groups for security4. Click Next.

Continue on to theSelecting 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 access

this 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 loca

pvs installation

Documents

citrix provisioning

provisioning services

provisioning services

provisioning services

citrix essentials

citrix repeater

citrix xenapp

citrix streamingserver