-
Book Overview & Buying
-
Table Of Contents
Citrix XenDesktop Cookbook-Third Edition
By :
In this book, we decided to give particular importance to both the possible resource deployment ways (MCS and PVS) as we did earlier in the previous XenDesktop cookbooks. In this recipe, we will explain the step-by-step way to install and configure the Provisioning Services 7.6 platform.
Citrix Provisioning Services 7.6 eliminates the need of external PXE and TFTP platforms, thanks to the empowered Boot Device Manager feature.
Thanks to the BDM feature, you can avoid using any IP helper (DHCP relay) within your network, because of the absence of PXE systems that eliminates the boot problems across different networks. Moreover, BDM also introduces the chance of centrally manage PXE and TFTP in a more dynamic way.
The Provisioning Services 7.6 can be implemented on the following platforms:
For a number of vDisks equal or greater than 250, the minimum RAM requirement for the server machine changes from 2 GB to 4 GB of RAM.
In case of Master Images deployed with the latest XenDesktop Virtual Desktop Agent installed, Windows XP is not supported.
In this recipe, we are going to execute all the steps required to install and configure the Citrix Provisioning Services platform, as follows:
In presence of Windows Server 2012 / 2012 R2, you have to install the .NET Framework 3.5 from the Windows installation media, by following this guide: http://blogs.msdn.com/b/sql_shep/archive/2012/08/01/windows-2012-and-net-3-5-feature-install.aspx.
Autorun.exe from the installation media.
C:\Program Files\Citrix\Provisioning Services\) or modify it by clicking on the Change button. After completion, click on the Next button to proceed.
The best choice is to install DHCP server on a machine different from the Provisioning Service server. You should always separate components for better performance and roles isolation.
To better convey the differences between the MCS and PVS architectures, we will always use two different farms to accomplish tasks for both architectures.

You should always consider separating the database server from the PVS machine. Separating roles will assure you separation, isolation, and better load balancing and security.

To check the validity of your License Server with the PVS 7.6 platform, flag the Validate license server version and communication option.


C:\ProgramData\Citrix\Provisioning Services\Tftpboot). Click on the Next button to continue.

The verbose mode is particularly useful when executing a problem analysis. Consider this as a PVS debug mode.
Remember that active Windows Firewall may be a problem for your installation process. You have to open required ports or turn them off. The ports are UDP 6890-6909 (Inter-Server communication), TCP 1433 (SQL Server database), TCP 389 (Active Directory communication), UDP 67 (DHCP), UDP 67 and 4011 (PXE Services), UDP 69 (TFTP), UDP 6910 (Target Device logon), UDP 6910-6930 (vDisk Streaming), and TCP 54321 and 54322 (SOAP Service).

C:\Program Files\Citrix\Provisioning Services Console\), click on the Change button a browse for a valid location.

Be sure that the Citrix PVS Soap Server service is running, otherwise you will not be able to connect to the PVS configured farm.

In the Chapter 3, Master Image Configuration and Tuning, we will discuss about the creation of the Target Device for the Provisioning Services in the Configuring a target device – PVS architecture recipe.
PVS is one of the two deployment technologies for desktop and application deployments. Provisioning Services 7.6 is the latest release of the software used to implement this kind of architecture.
The structure is quite simple. A server component which is managed by a PVS console, delivers operating systems images to the end users' devices by creating instances of the virtual disks of an installed operating system called Master Target Devices and streaming them through the network from the PVS server memory every time users need them. This process permits having high-elevated network performance, dramatically reducing the impact on storage activities.
You have to give attention to the PVS DB size. In fact, even if it starts only with 20 MB of data, its dimension has a growth of 10 MB. This means that in presence of hundreds or thousands of objects, the database size can become higher than your expectations.
Provisioning Services use the Kerberos authentication to let its components communicate with each other, registering the components against the Active Directory through the Service Principal Name (SPN) and permitting the Domain Controller to identify the accounts, which manage the running services. In case of registration problems, your PVS service could fail. To avoid this situation, you have to use the setSpn command in order to give the right permissions to the account that manage the earlier described services (such as the PVS Soap Service) by applying the following syntax:
setSpn –a PVSSoap/PVS_Server_FQDN <username_managing_service>
At the following MSDN link, you can find more information about the SPN: http://msdn.microsoft.com/en-us/library/windows/desktop/ms677949(v=vs.85).aspx.
Change the font size
Change margin width
Change background colour