Tuesday, March 30, 2010

Installing Citrix Provisioning Server 5.1 sp2 [part 1]

Citrix Provisioning Server is a great way to ease Administrative support of Citrix XenApp Environments. When properly installed and deployed using Physical or Virtual Servers (or a mix) you can easily and quickly spin up new servers to expand an existing farm with little effort. This article will cover getting your Provisioning Server off the ground and ready to stream server images to your platform of choice.

Assumptions for this to work



  • A functioning AD environment already in-place

  • A location for your vDISK store (file server/cluster or iSCSI/SAN attached storage or worst case a really big local Drive)


  • A working Citrix License Server (including purchased or evaluation Provisioning Server Licenses for your company) this should also give you access to the Provisioning Server 5.1 SP2 install media via MyCitrix - you should have this downloaded and ready






Prerequisite work:




  • DHCP

  • A DHCP server should be configured to boot servers. This can be installed on the provisioning server or an existing DHCP server can be used. Create a new DHCP Scope that matches your Citrix Server Subnet(s) (the following Assumes 2008 DHCP)


  1. Open DHCP Admin tool

  2. Under DHCP > (server name) > IPv4 > Scope [(server subnet)] (name) - right click Scope Options and left Click Configure Options


  3. Scroll down to 066 Boot Server Host Name - check this option and put the server name or IP of the new Provisioning server here (if using host name make sure it can be resolved across the environment)

  4. Check 067 Bootfile Name - in the string input ARDBP32.BIN - click OK




Optionally you can configure DHCP Reservations (Static DHCP) for each server's MAC address if you want to further lock-down DHCP on a server segment - this usually is good in environments where the idea of DHCP on a server segment doesn't sit well with the Security team.

  • Active Directory



  1. Service Account and PVS Admin Group


  2. A service account (svc_PVS) should be created, this account is used to run the PVS services as well as access the store. Account can be a standard domain user but needs the following rights on the Provisioning Server: Run as Service, Registry read access, R/W to Program Files\Citrix\Provisioning Server, and R/W access to any vDISK location (Local disk or network share). Account will also need access to SQL (see below). A PVS admin group created (CTX_PVS_Admins) - the account above should be added to this group as well as any domain accounts of users you want to Administer PVS, this account can be added to the local administrators group on the PVS server.
  3. GPO

  4. For Provisioning Server to properly manage newly deployed hosts a GPO setting is required on the OU will host all the servers that are Streamed via Provisioning Server. You can either set this on your existing OU or create a brand new OU for PVS Hosts - The Policy Domain Member: Disable machine account password changes should be set to Enabled (found under: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options)



  • MS SQL

  • Provisioning Server, like XenApp, requires a SQL Database, this can be SQL Express if needed, but should be a SQL Server in the environment for true High Availability. Make sure the service account you created above has DBCreator and security admin rights if you are creating the database during the setup; otherwise if you pre-create a blank database the service account requires db_datareader, db_datawriter, and execute permissions on stored procedures.
  • Store Creation

  • PVS requires a location to store vDisks, local storage to the PVS server will do, but in a HA environment this should be some form of Network Storage (Share on a File Cluster or a iSCSI disk). Make sure the PVS admin group created above have R/W access to this location, and to keep the area clean you should create a folder called vDisks and one called Cache.
  • Citrix Licensing


  • You should also assure you have the proper licenses installed into a Citrix License server this server should be 11.6.1 or higher. Download your Provisioning server licenses from My Citrix and assure they appear in your License Management Console correctly before deploying a single host (a license-less install will shut down the PVS hosts every 180m after boot).





Installing Provisioning Server



  1. Insert the Provisioning Server 5.1 sp2 install media (or run autorun.exe from the extracted media on your HD or Fileshare)


  2. Server Installation > Install Server

  3. Next > on the welcome screen

  4. Accept the license agreement, Next >


  5. Enter your information on the User/Org Screen Next >

  6. Default install location should be fine, Next >

  7. Leave Complete Install selected, Next >


  8. Click Install

  9. After install is complete click Finish





Configuration Wizard


As soon as the install completes the Configuration Wizard begins.

  1. Click Next > on the welcome screen


  2. On the DHCP screen select the option that matches your environment and click Next >


  3. On the PXE Services Screen, select the option that matches your environment - when in doubt select The Service that runs on this computer and Microsoft DHCP (unless DHCP is remote), click Next >



  4. On the Farm Configuration Screen select Create farm and click Next >


  5. On the Database screen enter the information appropriate to your environment (SQL server name, instance, and port) click Next >


  6. On the New Farm screen fill in the information for your environment, the Database name, farm name, site name and initial collection name. Select Use Active Directory Groups for security and select the group created above in Prerequisites as the Farm Administrator group click Next >

  7. Input the License server name and port for your Citrix License server



  8. On the Service Account screen select Specified user account and input the information for the service account created above. Check Configure database for the account and click Next >



  9. On the Stream Services Screen, leave all options default (you can unselect any extra NICs that are unused), click Next >


  10. Check Use the Provisioning Server TFTP service, leave the path to the BIN file alone and click Next >



  11. Highlight the IP in the Stream Server Boot List, as this is the only server at this time, select Edit, uncheck use BOOTP/DHCP for Subnet mask and gateway and they should fill in, click OK, click Next >



  12. Confirm all your settings on the next screen, make sure Automatically Start Services is checked, click Finish

  13. Make sure everything is Green Check Marks and click Done



  14. Create the Store

  15. Launch the Provisioning Services Console
    Right Click Stores, Left Click Create Store...
    Name: Enter the Store name (admins choice - in my example I use Default Store
    Description: Admin Choice here
    Site: This should match the site you created above during the wizard

    Click the Servers tab
    Site should match your site
    Check your server name

    Click the Paths tab
    Default store path: this is the vDISK folder you created on your share or disk above. ex: G:\CTXPVS\Default\vDisks
    Default Write cache paths: this is the Cache folder you created on your share or disk above. ex: G:\CTXPVS\Default\Cache
    Click OK







Install is now complete. Part 2 covers capturing a image for use by PVS Stream Clients

1 comment:

  1. Highlight the IP in the Stream Server Boot List, as this is the only server at this time, select Edit, uncheck use BOOTP/DHCP for Subnet mask and gateway and they should fill in, click OK, click Next

    Is wrong. You must enter ip.

    ReplyDelete