Module 1: Understanding the Architecture of a

XenDesktop Solution

XenDesktop Architecture Overview

User Layer
o Citrix Receive
Access Layer
o Citrix NetScaler
o Citrix StoreFront
o Discussion Questions
Control Layer
o Delivery Controller
o Machine Creation Services
o Citrix Provisioning Services
o Hypervisor
o Virtual Delivery Agent
o Discussion Question
Resource Layer
o Applications
o Operating System Image
o Citrix Profile Management
o Policies
o Personal vDisk
Management Layer
o Citrix Studio
o Citrix Director
o Discussion Questions
XenDesktop Site
Ports
Reinforcement Exercise: XenDesktop 7 Components

 XenDesktop Architecture Overview

The User layer represents the end-user devices used to connect to XenDesktop resources
regardless of whether the end user is connecting from an internal or external device. Citrix
Receiver, Receiver for Web Sites, of Citrix HTML 5 Receiver can be used from these devices to
access the resources.
Citrix Receiver :-> Citrix Receiver is installed on end-user devices to provide and users with
quick, secure, self-service access to documents, applications, and desktops from any end-user
device, including smartphones, tablets and PCs. Receiver provides on-demand access to
Windows, Web, and Software as a Service (SaaS) applications.

The access layer contains the components that provide end-user access to the environment: Citrix
NetScaler and StoreFront. NetScaler provides secure access and intelligent load balancing for
StroeFront, Deliver Controller, and related infrastructure. Internal end-user devices connect from the
user layer to the access layer using StoreFront.
NetScaler is an integrated Web application delivery controller that slashes server and bandwidth
requirements, cutting the costs of delivering enterprise applications. NetScaler functions as an
application accelerator through layer-7 load balancing and content switching functions. NetScaler also
includes application security using a Web application firewall. NetScaler offloads applications and Web
servers to ensure application availability, increased security through SSL, and server consolidation. It
reduces the cost of ownership of Web application delivery and optimizes the end-user experience.
Ctirx StoreFront:- StoreFront delivers a powerful, self-service Windows applications store to provide a
single, simple, and consistent aggregation point for all IT user services.

The control layer is home for the various controllers and infrastructure components required for
managing and delivering virtual desktops. Within the control layer, decisions surrounding the
management and maintenance of the overall solution are addressed. The Control layer is comprised of
access controllers, delivery controllers, and infrastructure controllers. Once an end-user connection
moves past the access layer, Citrix StoreFront communicates with the Delivery Controller in the control
layer.
Delivery Controller:- The Delivery Controller is installed on servers in the datacentre and consists of
services that communicate with the hypervisor to distribute applications and desktops, authenticate and
manage end-user access, and broker connections between end user and their virtual desktops and
applications. The Controller manages the state of the desktops, starting and stopping them based on
demand and administrative configuration. Each site has one or more delivery controllers.
Machine Creation Services (MCS) :- It is a collection of services that run on the Delivery Contr9oller to
generate multiple clone-like machines from a single virtual machine serving as the primary image. The
Machine Creation Service communicates with the hypervisor and crates the desired number of
machines using storage-based snapshot technologies, while the Citrix AD Identity Service generates the
computer accounts within Active Directory.
Citrix Provisioning Services (PVS) :- PVS uses network-based streaming technology to deliver the
operating system for both single-user virtual-desktops and multi-user, server-based resources. Citrix
Provisioning Services allows a single vDisk to be used to deliver a consistent virtual desktop across the
environment and to simplify image management and maintenance.

The resource layer contains the end users virtual desktop and applications and is subdivided in to three
components: applications, operating system image, and personalization.
OS (Operating System): Virtual desktop delivery with XenDesktop involves delivering an image of an
Operating System (such as Windows 7) to the end user.
Apps: (Applications can be installed on Server OS or Desktop OS machines in your XenDesktop
environment. These applications are delivered to end users.
Profile: Profile management provides an easy, reliable, and high-performance way to manage end-user
personalization settings in virtualized or physical Windows environments. Profile management allows
end users to customize their virtual and physical desktops, applications, and server settings. Managed
through Citrix policies or GPOs, Profile management can provide a central point of configuration and
control to give a consistent experience regardless of hich machine hosts the end-user session.

Policy: Citrix Policies are the most efficient method of controlling connection, security, and bandwidth
settings. Policies can be created for specific groups of end users, devices, or connection types. Each
policy can contain multiple settings and different settings from policies can be mearged. Any confilicts
between settings are resolved using a system of priorities.
PvD : With the personal vDisk feature, you can manage pooled and streamed desktops from a single
image while offering end users the flexibility to install applications and change personal settings.

The management layer contains all of the consoles and utilities used to configure and manage the
XenDesktop components.
Ctirx Studio :- It is a management console that enables you to configure and manage your deployment,
eliminating the need for separate management consoles for managing delivery of applications and
desktops. Studio provides various wizards to guide you through the process of setting up your
environment, creating you workloads to host applications and desktops, and assigning applications and
desktops to end users.
Cirtix Director: It is a web-based tool that enables IT support and Help Desk teams to monitor a
XenDesktop environment, troubleshoot issues before they become system critical, and perform support
tasks for end users.

Introduction to Studio:
Studiois the primary management console for XenDesktop. It enables you to configure and manage your
deployment, eliminating the need for separate management consoles to manages the delivery of
applications and desktops.
If you transition from XenApp to XenDesktop, Studio replaces the Delivery Services Console.

Module 2: Managing Licenses and Delegating

Administration

Managing Licences in Studio

o Discussion Question
o Types of Licenses
o Downloading, Allocating, and Importing a License File
To Download ,Allocate, and Import a License File
o Discussion Question
o Adding a License Administrator
To Add a License Administrator

Managing Delegated Administration

o Administrators
o Roles
o Scopes
To Add an Administrator
To Create a Custom Scope Using Studio
To Edit a Custom Scope
To Create a Custom Role
To Edit a Custom Role
To Edit an Administrators Permissions
o Running a Delegated Administration Report
To Display Configuration Log Content
To Generate Configuration Log reports

To Change the Configuration log Settings

o Discussion Question
Troubleshooting: Managing Licences and Delegated Administration
Reinforcement Exercise: Configuring Roles and Scopes

Managing Licences in Studio:

XenDesktop Offers four license editions:
1234-

Platinum
Enterprise
Apps
VDI

The License Administration Console enables you to manage and monitor Citrix licenses through
a Web browser. Studio can also be used for license administration and these consoles can be
used interchangeably. However, the License Administration Console manages licenses during
the deployment of XenDesktop, prior to the installation of Studio.

To Download ,Allocate, and Import a License File

Open www.citrix.com

To Download, Allocate, and Import a License File Exercise Steps

1. Click My Account (Log In).
2. Click Create Account.
3. Click Create Customer Account.

4. Enter your information to create an account.

5. Click Continue on page 1 of the registration.
6. Create a new Login ID and Password. Type Admin1 for Login ID and Password1 for
the password.
7. Click Continue on page 2 of the registration.
8. Click Activate and Allocate Licenses.
9. Click Single Allocation.
10. Type the license code. TypeCTXLF-12345-67890-12345-67890.
11. Click Continue on the license code page.
12. Click Continue on the Host Name Warning page.
13. Type the Host ID. Type LS-1.
14. Type the license quantity. Type5.
15. Click Continue on the configure page.
16. Verify the information is correct and click Confirm.
17. Click OK within the dialog box.
18. Click Save on the download dialog box.
19. Select a location to save the license file. Leave as the default Downloads folder.
20. Click Save on the Save As window.
21. Click Close on the Download Complete window.
22. Click Log Out.
23. Close the browser window.
24. Click Start on the Windows desktop and then click in theSearch field.
25. Type Citrix License Administration and pressEnter.
26. Click Citrix License Administration.
27. Click Administration within the License Administration Console.
28. Log on as an administrator. Typecch\admin1 for User Name andPassword1 for
password and press Submit.
29. Click Vendor Daemon Configuration.
30. Click Import License.
31. Click Browse and locate the recently downloaded license file. Select FID_309f.lic.
32. Click Open.
33. Click Import License.
34. Click OK upon completion

Adding a License Administrator

To Add a License Administrator Steps

1. Click Start on the bottom left hand corner of Windows.
2. Type Citrix License Administration at the Windows Start screen and
press Enter.
3. Click Citrix License Administration to open the license console.
4. Click Administration to log on.
5. Type CCH\Admin1 into the User Name field and Password1 into the password field
and click Submit.
6. Click User Configuration and then click New User.
7. Select Domain Administrator from the Role field.
8. Type CCH\Admin2 and then clickSave.
9. Click Log Out.

Managing Delegated Administration

The delegated administration model offers the flexibility to match how your
organization wants to delegate administration activities, using role and object-based
control. Delegated administration accommodates deployments of all sizes and allows
you to configure more permission details as your deployment grows in complexity.
Citrix recommends that delegated administration be implemented for all high-security
environments to ensure that administrative privileges are restricted based on role. This
will help to improve security and reduce incorrect configurations within the
environment.
Note: No Specific Active Directory permissions are required for delegated
administration. Standard domain users will surface

Administrators : An administrator represents an individual person or group identified by

their Active Directory account. Each administrator is associated with one or more role and scope
pairs, which allows organizations to delegate responsibility based on the administrators role
and functions.

Roles: Roles represent a job function with defined permissions. Click on

each role to learn more about the built-in XenDesktop role.

Scopes:
Scopes represent a collection of objects. An object can exist in more than one scope.
Scopes group objects in a way that is relevant to your organization. The built-in All
scope contains all objects and is always paired with the Full Administrator role.
You can now apply roles and scopes to groups in Active Directory instead of applying
roles and scopes to individuals only

Delegated Administration and Organization Size

Directions: The number of administrators and the granularity of their permissions
depends on the size and complexity of the deployment

Small Deployments: In small deployments, or proof-of-concept deployments, one or more

administrators perform all tasks; there is no delegation. In this case, create cach administrator
with the built-in Full Administrator role, which has the All scope.
Medium-Sized Deployments: In larger deployments with more machines, applications and
desktops, administrators require more delegation. Several administrators might have specific
functional responsibilities (roles). For example, a medium-sized deployment might contain two
Full Administrators along with several other Help Desk Administrators. Additionally, an
administrator might manage only certain groups of objects (scopes), such as machine catalogs.
In this case, create new scopes and add administrators with one of the built- in roles and the
appropriate scopes.

Large Deployments: Even larger deployments might require more (or more specific) scopes in
addition to different administrators with unconventional roles. In this case, edit or create additional
scopes, create custom roles, and create each administrator with a built-in or custom role along with
existing and new scopes.

Running a Delegated Administration Report:

Run a delegated administration report through Citrix Studio to list the permissions for an individual
administrator.
The HTML report describes the Resultant Set of Policy (RSOP), which shows the role\scope pairs
associated with an administrator and lists the individual permissions for each type of object.

Module 3: Managing and Monitoring the

Hypervisor

Architecture Overview
Creating a Virtual Machine from an ISO
o Creating a Virtual Machine
To Create a Virtual Machine Using XenCenter
To Install a Windows OS onto a Virtual Machine
o Installing XenServer Tools
To Install XenServer Tools on a Virtual Machine
o Generalizing the Virtual Machine

To Generalize the Virtual Machine

o Creating a Template
To Create a Template from a Virtual Machine
Managing Virtual Machines within a Hypervisor
o Creating a Virtual Machine
To Create a Virtual Machine Using XenCenter
o Taking a Snapshot
To Take a Snapshot in XenCenter
o Discussion Question
o Restoring a Virtual Machine From Sysprep
To Restore a Virtual Machine from Sysprep
o Copying a Virtual Machine Using XenCenter
To Copy a Virtual Machine Using XenCenter
o Discussion Question
o Reverting to a Snapshot

To Revert to a Snapshot in Xen

Managing and Monitoring the Hypervisor

Directions: The following components are combined to virtualize server and desktop hardware so
that multiple operating systems can share devices such as hard drives and network cards.

Control Domain: The Control Domain manages the network I/O and storage I/O of all virtual machines.
VIF: A virtualized representation of a computer network interface. A virtual machine connects to a
virtual interface to provide network connectivity to other virtual machines and the physical network.
PIF: A physical interface that corresponds to an actual connection to network prots.
Physical NIC: A physical network card that is installed on the host hardware.
Virtual Machine: Virtual Machine appear to end users as separate computers, each with its own
network identity, user authorization, authentication capabilities, operating system version,
configuration, applications, and data. The abstraction from physical hardware allows the virtual machine
to be protable.
Virtual NIC: Software that allows a computer to connect to a virtual network.
Guest OS: The operating System that is installed on a virtual machine.

Supported Hypervisors:
The hypervisor works by virtualizing the hardware. Hardware virtualization abstracts system components, such as
hard drives, resources, and ports, and allocates them to the virtualized machines running on the system. The
virtual machines run operating systems and applications that are known as guest software. The hypervisors
supported by XenDesktop 7 are:
1- XenServer
2- Hyper-V and System Center Virtual Machine Manager (SCVMM)
3- VMware vSphere

Hypervisor Tools
When using a hypervisor to host your XenDesktop virtual machines, ensure that the proper tools are installed. For
example, XenServer Tools must be installed in order to properly manage virtual machines within XenServer Tools,
you cannot:

Restart a virtual machine.

Suspend a virtual machine.
Migrate a running virtual machine using XenMotion.
Use the checkpoint and roll back feature.
Dynamically adjust the number of virtual CPUs assigned to a running Linux Virtual Machine; Windows
virtual machine require a restart for this to take effect.
Dynamically adjust the memory of the virtual machines to compensate for overload situations.
View virtual machine performance data in XenCenter.
Create quiesced snapshots or snapshots with memory.
Revert to snapshots.

Virtual machines are deployed to end users or used as server machines. New virtual machines are created
for many reasons, including proper allocation of resources, replacing physical boxes with virtual machines,
hosting different operating systems, and end-of-life replacement. Virtual machines never leave the
datacentre, which offers a much higher level of security and simplifies administration and management.

XenServer Tools provide high performance Windows drivers and a management agent, enhancing disk
and network performance for XenServer virtual machines. Install XenServer Tools on each virtual machine
in order to use the xe command-line interface (CLI) or XenCenter.
Note: Running a virtual machine without installing the XenServer Tools is not a supported configuration.

Citrix recommends that you generalize a virtual machine before using it to create a template. This
eliminates the possibility of conflicts between virtual machines created from the same template. On a
Windows operating system, use the Sysprep tool (bundled with all versions of Windows from Vista
forward).
Note: This process is only required if you create a template from a virtual machine.

With the virtual machine properly prepared and generalized, create the template in XenServer.
Note: This process is only required if you create a template from a virtual machine.

Managing Virtual Machine

The virtualized environment and virtual machines are managed within the hypervisor. Create virtual
machines by building an image or by using a t3emplate that contains all the pre-configured settings
necessary to create an instance of specific virtual machine.

A snapshot is an image of a virtual machine that preserves the current settings and data at the point in
time in which the snapshot is taken. Taking a snapshot allows a virtual machine to be restored if it fails.

Use the Revert To option to discard changes made to the virtual machine and reset it back to the original
state when the snapshot was taken.

A benefit of creating virtual machines is that they can be easily copied. You should create a copy of a
virtual machine when you want to.
o Complete a virtual machine backup
o Troubleshoot
o Test applications for fault tolerance.
o Provide the ability to roll back in the event of problems.
Prior to installation on a live machine.
o Repurpose the machine for other needs within the environment.

Managing Resources for a Virtual Machine or Template

When managing a virtualized environment, it is important to use and allocate resources wisely to maximize
efficiency. When creating virtual machines and templates within a hypervisor you must consider storage
capacity, available memory, network resources, and processing power.

Adjusting storage: Before purchasing additional storage hardware, verify that the existing storage is
allocated appropriately. Make adjustments as needed to support end-user requirements and use
existing storage resources more efficiently if possible.
Adding storage: With the appropriate resources, storage can easily be added to a virtual machine or a
template.

Memory: The hypervisor manages, memory allocation and allows additional memory assignment to a virtual
machine when it is running low on resources or if the end users require more memory to use resource-intensive
applications.
Processing Power :
Adjusting vCPUs: The processing power available to virtual machines can be a limiting factor within an
environment. Although each vCPU must be allocated strategically, XenCenter is used to set the priority of vCPUs
and gives more options when distributing processors across the environment.

Network Resources:
Adding a Virtual Network Interface Controller: You may need to add NICs in your virtual environment to associate
virtual machines with the appropriate network. When you install an interface into the virtual machine, link it to the
relevant network, allocate it a MAC address, and select the option of completing Quality of Service (QoS).

Configuring Alerts
Hypervisors allow for the configuration of events and alerts to simplify monitoring the
environment. Alerts raise awareness when resources reach a pre-determined level and respond

to selected system events, or when CPU, memory usage, network, storage throughput, or VM
disk activity go over a specified threshold on a managed host, VM, or storage repository.

Module 4: Managing Desktops and Application

Architecture overview
Managing Machine Catalogs
o Creating New Resource Setting
Machine Creation Services
Creating Machine Catalog
o Creating a Machine Catalog for Windows Server
Installing VDA
o Creating a Server OS Machine Catalog
o Creating a Machine Catalog for Windows Desktop
Installing the VDA
o Creating A Desktop OS Machine Catalog
o Creating a Remote PC Access Machine catalog
Managing Delivery Groups
o Creating a Delivery Group for User Desktops
o Creating a Delivery Group for Application Delivery
Managing Resources
o Adding Machines to a Machine Catalog
o Updating Desktops in a Machine Catalog
o Managing Computers Accounts
o Managing Power for Machines in a Desktop OS Delivery Group
o Reallocating Machines in a Delivery Group
o Discussion Question
o Shutting Down and Restarting Desktops
o Discussion Question
Deleting Resources
o Enabling and Disabling Maintenance Mode
o Removing Desktops from Delivery Groups
o Deleting a Delivery Group
o Deleting a Delivery from a Machine Catalog
o Deleting a Machine Catalog
Troubleshooting : Managing Desktops and Applications
Reinforcement Exercise: Delivering Server Desktops

Architectural Overview
The Delivery Controller (Controller) is responsible for managing end-user access, load balancing
connections, and optimizing connections.

Step by Step Delivery Controller communication process.

1. The Controller receives authentication requests from end users through
Citrix Receiver and queries Active Directory.
2. The Controller then interacts with the SQL database to retrieve the list of
resources for the end user.

3. Next, the Controller communicates with StoreFront to make the resources

available for selection.
4. The Controller then receives requests from the end user to access a
resource.
5. Next, the Controller load balances the request for a resource.
6. The Controller prepares the resource to be delivered to the end user
through the hypervisor.
7. Next, the Controller sends load balancing information to StoreFront where
a connection file is created.
8. The Controller then prepares the VM for connection.
9. The Controller retrieves the client license and issues it to the started
resource.
10. After the connection has been established, the Controller monitors the
connection state throughout the duration of the session.

Delivery Controller Requirements

Lesson 2: Machine Creation Services

Machine Creation Services (MCS) is a collection of services that work together to create
virtual desktops from a master desktop image on demand. MCS optimizes storage
utilization and provides a pristine virtual desktop to end users every time they log on.

Lesson 3: Creating Machine Catalogs

A machine catalog is a collection of VMs or physical computers managed as a single
entity., Machine catalogs specify the VMs or computers available to host applications or
desktops, the Active Directory computer accounts assigned to those VMs or computer,
and in some cases, the master image that is copied to create the VMs. VMs within
machine catalogs are organized into Delivery Groups that deliver the same set of
desktops and applications to groups of end users.

Creating Machine Catalog

If you are not provisioning through Machine Creation Services or Provisioning Services,
Citrix recommends that you use Microsoft System Center Configuration Manager or
another third-party application to ensure that the machines in the catalog are
consistent.
Create a new machine catalog whenever the desktop needs or your end users deviate
from those used in the environment. For example, all of the end users are currently
provided with a Windows 8 desktop, but some of your end users require a Windows 7
desktop.

Machine Catalog Types

The machines within a machine catalog are configured to run either a Windows Desktop OS or a Windows
Server OS. For end users who need to remotely access their office machine, select Remote PC Access for
those machine catalogs.

Learn more about Windows Desktop OS and Windows Server OS machines.

Desktop OS machine catalogs use a Windows desktop environment to

provide desktops and applications that are assigned to individual users.

Typically, end users who need a Desktop OS machine:

Are task or knowledge workers who require personalized desktops of
which they can take ownership.
Are obile workers who want to access the same desktop from a variety of
devices over different networks.
Need to install their own applications on their desktops.

With these types of end users, you want to:

Standardize certain aspects of end users desktops through the use of a
common template.
Deliver end users desktops to any device regardless of hardware
capability.
Reduce desktop management costs while still providing your end users
with a personalized desktop experience.

Three types of machines can be configured for Desktop OS machines:

Random machines (formerly known as pooled) which provide

desktops to end-users on a per session, first-come, first-serve basis.
They are arbitrarily assigned to end users at each log on and returned
to the pool when the end users log off.
Static machines (formerly known as assigned) which provide desktops
that are assigned to individual end users that usually need to install
their own applications on their desktops.
Streamed machines that use Personal vDisk to support end users that
need to personalize their desktops and store their changes to a
separate vDisks so the changes are available at the next log on.

Server OS machine catalogs use a Windows Server desktop environment to

provide standard desktops and applications that are shared by a large number of end users.
These machine catalogs provide desktops and applications that are:

Allocated to end users on a per-session, first-come, first-served basis.

Deployed on standardized machines.

Typically, end users who need a Server OS machine:

Are task workers who require standardized virtual desktops and applications, such
as call center operators and retail workers.

Do not need to or are not permitted to install applications on their desktops.

With these types of end users, you want to:

Optimize hardware use by providing only the number of desktops required at any
one time rather than assigning each user a specific desktop.
Maintain control over desktops and increase security by preventing end users from
making permanent changes.,
Minimize desktop management costs by providing a locked-down standardized
environment for your end users.

Lesson 4: Managing Delivery Groups

A Delivery Group is grouping of end users who require access to a common set of applications or desktop
resources, and require the same end-user experience across those resources. Delivery Groups are created for
specific teams, departments, or types of end users. With Delivery Groups, You can:

Specify groups of end users who access desktops, applications, or desktops and applications.
Add end users and groups of users.

Defining the end-user experience in the Delivery Group means that settings do not need to be duplicated or
maintained across multiple pools of resources, and the backend resources can be changed without affecting
the end-user experience.

Accessing Resources from a Machine Catalog

In order for end users to access resources from a machine catalog, a Delivery Group is required. When creating a
Delivery Group, specify the end users, groups applications and desktop settings to match the end-user needs.
You cannot create a Delivery Group that contains machine catalogs with different machine types. Machine catalog
characteristics must match to put the machines into a single group.
For example, you cannot mix machines from Server OS machine catalogs with Desktop OS machine catalogs.

Lesson 5: Managing Resources

To efficiently manage machine resources, you may need to update both machine catalogs and Delivery Groups.

Task to Mange Resources

1-

2-

3-

4-

5-

6-

Lesson 6: Deleting Resources

Put a machine in maintenance mode in order to perform administrative tasks on the associated
image, such as applying updates and upgrading using image management tools.
When the machine is in maintenance mode, end-user activity is affected in the following ways:

With Server OS machines, end users can connect to existing sessions but cannot start
new sessions.
With Desktop OS and Remote PC Access machines, end users cannot connect or
reconnect. If the end user is already connected, they will stay connected until they
either disconnect or log off.

Machines are available for end-user connections when you take them out of maintenance
mode.

Removing a machine deletes it from a Delivery Group but does not delete the associated VM
from the machine catalog on which the group is based. Therefore, the machines are available
for assignment to other Delivery Groups. You can use this process when you want to delete the
machine but retain the virtual machine it was created from and its associated Active Directory
accounts.
Machines can only be removed while in maintenance mode. Putting the machine in
maintenance mode temporarily prevents end users from connecting to the machine during
removal.
Machines may contain personal data. Manage this activity appropriately, especially if the
machine is allocated to another end user.

There are Delivery Groups for desktops and for applications. Machines may need to be moved
to another Delivery Group and the leftover Delivery Group needs to be deleted, which requires
putting Delivery Group into maintenance mode.

When a machine is deleted end users can no longer access it and the machine is deleted form
the machine catalog. Before deleting the machine, make sure all user data is backed up. No end
users can be logged on the machine that is being deleted. Put the machine in maintenance
mode to stop end users from connecting to the machine.

Contents
Managing StoreFront ............................................................................... Error! Bookmark not defined.
1.0

StoreFront Architectureal Overview ........................................ Error! Bookmark not defined.

2.0

StoreFront Management Console ............................................ Error! Bookmark not defined.

3.0

Creating a New Store ............................................................... Error! Bookmark not defined.

3.1 To Create and Add a New Store .............................................................................................. 42

4.0 Hiding a Store ................................................................................. Error! Bookmark not defined.
4.1 To Hide a Store ........................................................................................................................ 43
4.2

Discussion Question ............................................................. Error! Bookmark not defined.

5.0 Manging Authentication ............................................................................................................. 43

Manage StoreFront
Lesson 1: Architectural Overview
StoreFront is a front-end Web server responsible for aggregating resources from different
locations and presenting end users with a list of resources, including desktops and applications.
When an end user subscribes to a resources, they can customize the presentation and home
page display of that resource.

StoreFront Components

The StoreFron server records the details of end-user application subscriptions locally along with
associated shortcut names and locations. When an end user accesses a store, the application
synchronization feature automatically updates the subscribed applications on the end-user
device to match the configuration stored on the StoreFront server. The credentials are later
retrieved by the Store Service to authenticate to XenDesktop, ensuring that end users have a
consistent experience across all devices.
Note: StoreFront requires a minimum of 2 GB of storage space on the StoreFront server.

The StoreFront authentication service authenticates end users to XenDesktop sites. When an
end users credentials have been validated, the authentication service handles all subsequent
interactions to ensure that the end user only needs to log on once. The credentials are stored
using built-in Windows security features.

The store retrieves end-user credentials from the authentication service to authenticate end
users to the components providing the resources. The store also enumerates and aggregates
the resources currently available from XenDesktop sites and the Delivery Controller (SaaS
applications). End users access the stroe through Citrix Receiver or a Receiver for Web site.

This site enables end users to access stores through a Web page. Furthermore; this site can
verify the version of Receiver installed locally on the end-user device and guide the end user
through an upgrade or installation procedure if required. In scenarios where Receiver cannot be
locally installed, an HTML 5-based Receiver will be used.

1- An end user accesses their resources through Receiver. If Citrix Receiver is not installed
on the endpoint, end users can download Citrix Receiver using the Receiver for Web
site.

2- The authentication service of StoreFront retrieves the end-user credentials and validates them
with a domain controller. The StoreFront servermust be a member of the same Active Directory
forest as the end-user account and the accessed resources.

3- StoreFront retrieves the end users application subscriptions locally and loads them into
memory.

4- StoreFront forwards the end-user credentials as part of an XML query to the XenDesktop
Delivery Controller.

5- The Delivery Controller validates the end-user credentials with a domain controller

6- After a successful validation, the Delivery Controller checks which resuorces have been
published for this end user within its SQL Server database.

7- The Delivery controller sends an XML response to StoreFront, which contains all resources
available for theend user from XenDesktop. Site.

8- StoreFrontsends the list of available resources including the existing subscriptions to Citrix
Receiver or displays them in the Receiver for Web site.

Lesson 2: Managing Stores

Creating New Stores: StoreFront can create as many stores as needed for a particular group of
end users or can group together a specific set of resources. To create a store, identify and
configure communications with the servers providing the resources that you want to make
available.
3.1 To Create and Add a New Store
o Log on to the StoreFrontServer-1 virtual machine using the CCH\Admin1
and Password1 credentials.

o Open Citrix StoreFront.

If snap-in message appears for an extended period of time, click the red X to close
it. Do not click Cancel.
o
o
o
o
o

Select the Stores node.

Click Create Store.
Type Store as the Store name.
Click Next.
Click Add on the Delivery Controllers page.

o Type Delivery Controller as the Display name.

o Select XenDesktop as the type of Delivery Controller.
o Click Add.
o Type C-1.cch.local as the name of the Delivery Controller.
o Click OK.
o Click Add.
o Type C-2.cch.local as the name of the Delivery Controller.
o Click OK.
o Select HTTP.
o Verify that 80 is specified in the Port field.
o Click OK.
o Click Next.
o Select None.
If it is not already enabled, the pass-through from NetScaler authentication method
is automatically enabled when you configure remote access to the store through
NetScaler. End users authenticate to NetScaler and are automatically logged on
when they access their stores.
o Click Create.
o Click Finish.

Hiding a Store: Hiding a store prevents end users from adding stores to their accounts when
they configure citrix Receiver through email-based account discovery. By default, when a store

is created it is presented as an option for end users to add within Citrix Receiver when they
discover the StoreFront server hosting the store. Hiding the store does not make it inaccessible;
instead, end users must configure Citrix Receiver with connection details for the store, either
manually using a setup URL or with a provisioning file.
4.1 To Hide a Store
o Select the Stores node.

o Select the CCH store.

o Click Hide Store in the Actions pane.
o Click Hide .

Manging Authentication
The management of authentication within StoreFront is necessary to allow end users access to
XenDesktop applications and desktops. StoreFront will then handle all interactions to ensure that end
users only need to log on once.
Select an authentication method within the StoreFront management console to enable or disable enduser authentication method set up. If end users experience difficulty accessing the store or Receiver for
Web site, you may need to review their authentication settings.

To Configure Authentication Methods

Select the Authentication node.

Click Add/Remove Methods within the Actions pane.
Specify the access methods that you want to enable or disable for
your end users. Select the following methods:

The authentication methods available for use are:

User name and password: Enables explicit authentication. End users enter their credentials
when they access their stores.
Domain pass-through: Enables pass-through of domain credentials from user devices. End users
authenticate to their domain-joined Windows computers and are automatically logged on when
they access their stores. In order to take advantage of this option, pass-through authentication
must be enabled when Receiver for Windows is installed on user devices.

Smart card: Enables an authentication method in which a physical card is inserted into a reader
along with an end user entering a pin or a password. This adds an extra level of security since a
card is required.
Pass-through from NetScaler Gateway: Enables pass-through authentication from NetScaler.
End users authenticate to NetScaler and are automatically logged on when they access their
stores.

Perform this task to enable end users accessing stores with explicit domain credentials to reset
their expired passwords when logging on. When this setting is enabled, end users who cannot
log on because their passwords have expired are redirected to the Change Password dialog box.
StoreFront then contacts the domain controller to reset the end-user password.
If this feature is enabled, ensure that the policies for the domains containing your Citrix-based
servers do not prevent end users from resetting their passwords and ensure that there is
sufficient disk space on your StoreFront server to store profiles for all your end users. By
default, StoreFront warns end users if their passwords are due to expire. To perform the
password expiry check, StoreFront creates local user profiles on the StoreFront server.
Enabling end users to reset expired passwords exposes sensitive security functions to anyone
who can access any of the stores that use this authentication service. If your organization has a
security policy that restricts end-user password reset functions for internal use this
authentication service are accessible from outside your internal network. End-user resetting of
expired passwords is disabled.

Managing Delivery Controllers:

After creating a store within StoreFront, you may need to add other controllers to avoid a single
point of failure. Additionally, existing controllers that are available to a particular store may
need to be modified or removed at times.

Managing Delivery Controllers

StoreFront has the capability to aggregate several independent infrastructures, such as XenApp
farms or additional XenDesktop sites, to seamlessly present all available resources from each
available infrastructure to users in a single location.

o Adding Delivery Controllers

After creating a store within StoreFront, you may need to add other controllers. Adding
controllers alleviates the issue of having a single point of failure. There may also be
times in which you want to modify or remove existing Delivery Controllers that are
available to particular store.

To Add Delivery Controllers

Select the Stores node in the StoreFront console.

Select Store.

Click Manage Delivery Controllers in the Actions pane.

Click Add to include desktops and applications from another

site, farm, or virtual appliance in the store.

Type XenApp 6.5 Farm in the Display name field.

Select XenApp.

Click Add.

Type xenapp-1.cch.local as the name of the XenApp Server

running the Citrix XML Service and then click OK.

Select HTTP.
If you are using certificates to secure connections between StoreFront and Delivery
Controllers, ensure that the server names you specify in the Servers list match
exactly (including the case) the names on the certificates for the servers.

Click OK twice.

To Remove Delivery controllers

Select the Stores node.

Select Store as the store to delete.

Click Manage Delivery Controllers in the Actions pane.

Select XenApp 6.5 Farm and then click Remove.

Click OK.

Managing Receiver Updates

In order for end users to have the latest version of Receiver, it is important to specify the
mechanism of delivery for any updates. This procedure will offer options tomanage updates and
allow end users to have full functionality of stores.

To Manage Receiver Updates

Select the Stores node.

Select Store.
Click Manage Citrix Receiver Updates in the Actions pane.
Select Citrix (citrix.com).
Click OK.

Removing a Store
If an existing store is being replaced or is no longer usable for a particular group or user, it may
be necessary to remove the store. When a store is removed, any associated Receiver for Web
sites are also deleted.
o To Remove a Store

Select the Stores node.

Select CCH.
Click Remove Store.
Click Remove.

Module 6 : Managing Policies and Profile

Creating Policies Using Studio

Creating a Policy Using Studio
o
o
o
o
o

Unfiltered Policy
Using a Policy Template in Studio
Creating a Policy Using Studio
Applying a Policy Using studio
Editing a Policy Using studio

o Prioritizing Policy Using Studio

o Discussion Question
o Creating a Computer Template in Studio
o Exporting a policy Template Using Studio
o Importing a Policy Template Using Studio
o Obtaining the resultant set of policy using studio
Creating Policy Using Group Policy
o Discussion Question
o Creating and applying a group policy object
o Editing a group policy object
o Using a using template with group policy
o Discussion Question
o Importing a policy template with group policy
o Exporting a policy template with a group policy
o Prioritizing a policy using group policy
o Discussion Question
Policy Precedence (Studio vs. Group Policy Objects)
o Obtaining the Resultant set of policy using group policy object
Troubleshooting: Managing policy
Managing using profiles
Configuring folder redirection
o Managing policy setting using Citrix policy
o Resolving conflicting policies
o Streaming using profiles
o Discussion Question
Troubleshooting : Profiles Management
Reinforcement Exercise1: Working with policy
Reinforcement Exercise 2: Working with profiles

Lesson 1: Recommendations for Configuring Policy Settings

Citrix recommends the following when configuring policy settings:

Assign polices to groups rather than individual end users. If you assign policies to
groups, assignments are updated automatically when you add or remove end users
from the group.

Do not enable conflicting or overlapping settings in Remote Desktop Session Host

Configuration. In some cases, Remote Desktop Session Host Configuration provides
functionality similar to Citrix based policy settings. When possible, keep all settings
consistent (enabled or disabled) for ease of troubleshooting.
Delete unused policies, Policies with no settings create unnecessary processing.

Policy Precedence
Prior to creating policies, It is important evaluate whether policies will be managed and stored
in Studio or using GPOs. Citrix recommends managing and storing policies using GPOs if you
have the appropriate permissions in Active Directory. In situations where policies exist that
have been created using both studio and GPOs, Group Policy-based settings take precedence
over policies stored within the site database.

Lesson 2: Managing Policies in Studio

If you do not have the necessary permissions to manage Group Policy, or if filtering
mechanisms such as SmartAccess are required, use Studio to crate policeis for your site Poicies
created using Studio are stored in the site database and updates are pushed to the end-user

session either when the machine registers with the broker or when an end user connects to the
relevant resource.
Before creating a policy, decide which group of end users or devices you want it to affect. You
may want to create a policy based on end-user job function, connectiontype, end-user device,
or geographic location. Citrix recommends that you define a baseline policy set which outlines
all of the common configuration options for an organization within a single policy set, and then
configure policy exceptions as required to override decisions for specific needs. The key is to
keep the policy configuration simple and well-structured in order to avoid confusion.

Unfiltered Polices
Policy settins that will be applied to all objects and sessions in a site can be applied using an
unfiltered policy. When a XenDesktop site is created, some policy. When a XenDesktop site is
created, some policy settings are applied by default using the unfiltered policy. If you want
polices to impact specific groups, end users or objects, use policy filters to apply these settings.
The pre-created unfiltered policies cannot be deleted. If there are end users you do not want
affected by these policies, create a policy containing exceptions for these end users and then
set the priority higher than the priority of the unfiltered policy.

Applying and Editing a Policy Using Studio

When a policy is assigned to certain end users and machine objects, that policy is applied to
connections according to specific criteria or rules. If no assignments are added, the policy is
applied to all connections. You can add as many assignments as you want to a policy, based on
a combination of criteria. You must add at least one assignment to a policy for that policy to be
applied correctly. If you do not add any assignments, policy settings are applied to all user
sessions, unless those policy settings are overridden by settings in a policy with a higher
priority.
If you want to apply another policy setting, consider editing the existing policy and configuring
the appropriate options instead of creating an additional policy. Avoid creating a new policy
solely to enable a specific setting or to exclude the policy from applying to certain end users.

Prioritizing Policies Using Studio

If you encounter a situation in which specific end users require exceptions to the current policy,
create a new policy and assign it a higher priority.
Prioritizing policies allows you to define the precedence of policies when they contain
conflicting settings conflict, a policy with a higher priority overrides a policy with a lower
priority. A policy with a priority of 1 is the highest priority.

Obtaining the Resultant Set of Polices Using Studio

Sometimes a connection does not respond as expected because several policies may apply. If a
higher priority policy also applies to a connection, it will override the settins you configured in
the original policy. Determine how final policy settings are merged for a connection by
calculating the resultant set of policy (RSOP).
Running policy modeling from Studio as a domain user allows you to see Citrix polices that have
been configured within Active Directory as well as within the Studio console.

Lesson 3: Policy Templates in Studio

Templates saves time when administering a large environment and help establish standards
that multiple administrators can use. Templates are created from either an esisting template or
an existing policy.
Built-in templates include High Definition User Experience, High Server Scalability, Optimized
for WAN, and Security and Control. These templates are models for creating new policies or
templates. Built-in templates are created and updated by Citrix. You cannot modify or delete
these templates; however, you can modify or delete templates that you create.

Exporting and Importing a Policy Template

Exporting a Template: Exporting a policy template creates backups of template files to aid in
the recovery of policy configurations. It also supplies policy configurations from a site to aid
Citrix Support in troubleshooting issues. Policies created in Studio can be exported into Gropu
Policy Objects.
Importing a Template: Policy templates are local to the computer running the console to
manage a site. Policy configurations can be transferred between environments, including other
sites , managed on the computer running the console. Templates are transferred by importing
or exporting them. Importing a policy template allows you to implement policy configurations
from servers in other sites, or policy configurations created by Cirtix Support to resolve issues in
your site.

Lesson 4: Managing Policies with Group Policy Object

If your network environment includes Active Directory and you have the appropriate
permissions to manage Group Policy, use the Group Policy Management Console (GPMC) to
create policies for your site. Using Active Directory group policy allows you to manage both
Windows policies and Citrix policies in the same location and minimizes the administrative tools
required for policy management. The settings you configure affect the GPOs that you specify
through the GPMC. Polices created using Group Policy are stroed on the domain controller and
updates are pushed to the virtual desktop at regular intervals as part of the GPO refresh policy.

Policy Flow
Directions: Click the arrow to view the next step in the policy flow process.

Creating Applying, and Editing a Group Policy Object

The Group Policy Management Console and other Windows Server administrative tools are
installed on Windows 8 by installing Remote Server Administration Tools and then turning on
the appropriate Windows features.
By default, only domain administrators, enterprise administrators, and members of the Group
Policy creator owners group can edit GPOs. Citrix recommends not editing the Default Domain
Controllers Policy GPO or the Default Domain Policy GPO.

Prioritizing a Policy Using Group Policy

With the tree-based structure of Active Directory, policies can be created and enforced at any
level in the tree structure. It is important of understand how the aggregation of policies, known
as policy precedence, flows in order to understand how a resultant set of policies is created.
Any policy setting that is disabled takes precedence over a lower-ranked setting that is enabled.
Policy settings that are not configured are ignored.
If you are using Active Directory, policy settings are updated when Active Directory re-evaluates
policies at regular 90-minute intervals and when an end user logs on.

Obtaining the Resultant Set of Policy Using Group Policy

Objects
If you run the Citrix Group Policy Modeling Wizard or Group Policy Results tools from the Group
Policy Management Console, site policy settings created using Studio are not included in the
RSOP. To ensure that you obtain the most comprehensive RSOP, Citrix recommends launching
the Citrix Group Policy Modeling wizard from Studio, unless you create policies using only the
Group Policy Management Console.

Lesson 5: Policy Templates in GPO

Policy templates are displayed on the Templates tab in Group Policy Editor. Computer
templates are displayed when you are working with computer policies and user templates are
displayed when you are working with user polices.

Importing and Exporting a Policy Template with Group

Policy
Importing a Template: Built-in templates are created and updated by Citrix. You cannot modify
or delete these templates. However, you can modify templates that you import through Studio
or the Group Policy Editor.
Exporting a Template: Exporting a policy template allows you to create backups of your
template files to aid in the recovery of policy configurations. It also allows you to supply policy
configurations form your site to aid Citrix Support in troubleshooting issues.

Lesson 6: Managing End-User Profiles

Profile

Lesson 6: Managing End-User Profiles

Profile management is packaged with Studio and provides an easy and reliable way to manage
end-user personalization settings in both virtualized or physical Windows environments. Each
time an end user logs on, no matter their location or the device they use, they will have access

to all their own personal settings, shortcuts, toolbars, templates desktop wallpapers, and
favorites.
Profile management addresses end-user profile deficiencies in environments where
simultaneous domain logons introduce complexity and consistency issues to the profile. It
optimizes profiles by saving registry changes and file and folder changes to the user store for
each end user at various intervals as well as when the end user logs off.
Profile management is installed by default on master images when you install the VDA.

Lesson 7: Configuring Folder Redirection

Client folder redirection changes the way files and folders within an end-users profile are
accessed from their current logon destination. Folders that are frequently used, such as My
Documents and Desktop can be redirected to a network share outside of the ruaming profile
share to avoid being copied over the network at every logon and logoff. This will improve logon
times because the smaller profile size requires a smaller volume of network resources.

Lesson 8: Managing End-User Profiles with Polices

With polices, you customize and configure policy settings at a detailed level. There are
additional settings within policies that are used to customize end user profiles:

Active Write Back: Periodically writes user settings back to a users profile.
Active Directory Actions: When configured, applies log settings.
Directories to Synchronize: Allows you to choose particular directory paths to include
within Profile Management.

Resolving Confliction Profiles

Profile management has a feature that detects conflicting profiles between end users
Windows profile and Citrix profiles. When an end user experiences difficulties with the
desktop or applications, yet all policies and profiles appear to be correct, verify that there
are no confliction policies.

Streaming End-User Profiles

To improve logon performance and enhance an end-users experience, profiles can be
streamed. With profile streaming, end-users profiles are synchronized on the local
computer only when they are needed. Registry entries are cached immediately, but files
and folders are only cached when accessed by end users.

CC

Reinforcement Exercise: Working with Policies

This exercise is designed to take your newly acquired knowledge and find out if you can apply
that knowledge to tasks youve performed previously. In most instances, the default value or
choice will be the best choice. We encourage you to explore and try things out on you own.

Scenario: The CCH Engineering teams IDE and programming tools will eventually be hosted
on a desktop provided by XenDesktop 7. Since they have access to the source code,
management wants you to put some policies in place that may make it more difficult for the
source code to be taken outside company systems. Your objective is to put a group policy
object in place to put some safeguards in place to limit how the Engineering team can transfer
this kind of data.

Module 7 : Managing Sessions, Sites, and Users with

Director

Director Overview
o Accessing Director
Monitoring within the Director Sashboard
o Monitoring Infrastructure
o Monitoring Connected Sessions
o Monitoring Logon Duration Averages
o Monitoring Machine and User Connection Failures
Monitoring AND Managing User Sessions
o Viewing User Sessions
o Searching for a User
o Monitoring User Application
o Monitoring User Machine Processes
o Managing a Users Machine Power Status
o Enabling or Disabling Maintenance Mode
o Resetting a Users Profile
o Discussion Question
o Monitoring HDX Channels
o Sending a Message to a User
o Shadowing a User Session
o Disconnecting a User Session

o Logging Users Off Sessions

o Monitoring Historical Trends
Troubleshooting: Managing Sites, Sessions, and Users
Reinforcement Exercise: Using Director

Lesson 1: Monitoring within the Director Dashboard

The Director Dashboard is the opening page of Director and shows basic information
regarding your environment including:

Infrastructure
Sessions Connected
Average Logon Duration

The Dashboard gives a general overview of the current status of the environment and
allows you to quickly view unusual and irregular activity.

Information to Monitor within the Director ashboard

Directions: Click on each tab to learn more about the Director Dashboard.

Lesson 2: Monitoring End-User Sessions

Director is used to monitor end-user sessions applications, and machine processes.

Tasks to Monitor an End-User Session

Directions: Click on each tab to learn more about monitoring end user sessions.

Lesson 3: Managing End-User Sessions

Director is used to accomplish many of the tasks require to manage end-user sessions.

Tasks to Manage an End-User Session

Directions: Click on each tab to learn about the tasks to manage an end-user session.

Module 8 : Managing Printing

Printing in a XenDesktop 7 Solution

Managing Printing
Default Printing Behavior
Configuring Client Printing
o Modifying Client Printer Auto-Creation
o Adding Session Printers

Managing Printers Drivers

o Automatic Installation of In-Box Printer Drivers
o Configuring Printer Driver Mapping and Compatibility
o Universal Printer Driver (UPD)
o Controlling Universal Printing Behavior
Optimizing Printing Performance
o Configuring Printing Optimization
o Setting Up and Managing the Universal Print Server
Troubleshooting : Managing Printing
Reinforcement Exercise: Managing Printing

Lesson 1: Configuring Client Printing

XenDesktop policies specify the client printer that are made available for end-user sessions.
Policies control the number and type of available printers, as well as customize printer settings
and options.
Client-based printing policies configure client printer auto-creation, client printer redirection,
printer property retention, print mapping, and other settings.

Modifying Client Printer Auto-Creation

Client printer auto-creation settings specify client-printing behavior from the autocreation of local not-network client printers only.
During printer auto-creation, if a new local printer connected to an end-user device is
detected, the server hosting the published application is checked for the required
printer driver. By default, if a Windows-native driver is not available, the Universal
printer driver is used. This setting overrides default client printer auto-creation settings
and will only take effect if the Client printer redirection setting is present and set to
Allowed.

Adding Session Printers

By default, network printers on the end-user device are created automatically at the
beginning of sessions. XenDesktop reduces the number of network printers that are
enumerated and mapped by specifying the network printers to be created within each
session.
Network printers created within the session printers setting vary accourding to where
the session was initiated by filtering on objects such as subnets. This feature controls
the assignment of network printers and ensures that the most appropriate printer is
presented to the end-user, based on the location of the end-user device (also known as
Proximity Printing).

Lesson 2: Managing Printer Drivers

There are three options for managing printer driver usage within XenDesktop policies.
These features control the way end-user sessions use specific printer drivers as well as
configure the Citrix Universal Printer driver settings.
Directions: Click on each of the icons to learn more about the three options for
managing printer driver usage:

You can control the automatic installation of Windows-native printer drivers. If it is

necessary to ensure consistency across Server OS machines and virtual desktops. You
can disable the policy setting through Citrix or Microsoft policies.
By default, in-box printer drivers are automatically installed, even if the end user does
not have installation permissions, because this task is completed within the systems
context. It is important to never install untested printer drivers in a production
environment. Additionally, Citrix recommends to minimize the number of printer drivers
installed and to uninstall unused printer drivers.

Specifies the order in which XenDesktop attempts to use Universal printer drivers,
beginning with the first entry in the list. Drivers can be added, edited, or removed and
the order of the drivers in the list can be changed.

This option specifies when to use Universal Printing.

Configuring Printer Driver Mapping and

Compatibility
Each client provides information about client-side printers during logon, including the
printer driver name. During client printer auto-creation, Windows server printer driver
names are selected; these names correspond to the printer model names provided by
the client. The auto-creation process then uses identified available printer drivers to
construct redirected client print queues. When you define these rules, you can allow or
prevent printers to be created printers to use only the Universal Printer Driver.
You can add a driver mapping, edit an existing mapping, or override custom settings.

Universal Printer Driver

To simplify printing in XenDesktop environments, Citrix recommends the use of the

Citrix Universal Printer Driver (UPD). The UPD is a device-independent driver that
supports any print device and thus simplifies administration by reducing the number of
drivers required. The UPD supports advanced printer functionality, such as stampling
and sorting, and does not limit color depth.
The UPD consists of two components:

Server component: On a Xendesktop-based virtual desktop, the Citrix UPD is

installed as part of the XenDesktop VDA installation. When a print job is initiated,
this driver records the output of the application and sends it, without any
modification, to the end-user device with the ICA/HDX connections.
Client component: The client component of the Citrix UPD is installed as part of
the citrix Receiver installation. It receives the incoming print stream for the
virtual desktop and forwards it to the local printing subsystem where the print
job is rendered using the device-specific printer dirver.

The diagram show the UPD components and a typical work flow for a printer locally
attached to a device.

Lesson 3: The Universal Print Server

The Universal Print Server provides universal printing support for network printers.
The Universal Print Server uses the Universal Printer Driver, which is installed with XenDesktop.
Citrix recommends the Citrix Universal Print Server for remote print server scenarios.

Lesson 4: Optimizing Printing Performance

To optimize printing performance, use the Universal Print Server and Universal
Printer Driver. The following policies control printing optimization and compression:

Universal printing optimization defaults specify default settings for the

Universal Printer when it is created for a session:

Desired image quality specifies the default image compression limit

applied to universal printing. By default, Standard Quality is enabled,
meaning that users can only print images using standard or reduced
quality compression.
Enable heavyweight compression enables or disables reducing
bandwidth beyond the compression level set by Desired image
quality, without losing image quality. By default, heavyweight
compression is disabled.
Image and font caching settings specify whether to cache images and
fonts that appear multiple times in the print stream, ensuring each
unique image or font is sent to the printer only once. By default,
embedded images and fonts are cached.

Allow not-administrators to modify these settings specifies whether

users can change the default print optimization settings within a
session. By default, users are not allowed to change the default print
optimization settings.

Universal printing image compression limit defines the maximum quality and the
minimum compression level available for images printed with the Universal print driver.
By default, the image compression limit is set to Best Quality (lossless compression).
Universal printing print quality limit specifies the maximum dots per inch (dpi) available
for generating printed output in the session. BY default, no limit is specified.

To improve session performance by limiting printing bandwidth:

The Printer redirection bandwidth limit setting specifies the bandwidth available for
printing in kilobits per second (Kbps).
The Printer redirection bandwidth limit setting limits the bandwidth available for
printing to a percentage of the overall bandwidth available.

Module 9: Managing Provisioning Service and

Personal vDisk

Citrix Provisioning Service

Navigating the Provisioning Services Console

o Creating the vDisk File
o Discussion Question
Migrating from Machine Creation Service to Provisioning Service
o Installing the VDA
o Preparing the Master Image for Provisioning Services
o Creating the Master vDISK Image Using the Imaging Wizard
o Creating the Provisioning Services Target Devices
Creating a New Machine Catalog
o Assigning a Machine Catalog to a Delivery Group
Updating vDISK
o Updating a vDISK

Why Choose Machine Creation Service or Provisioning Service?

Provisioning Service Overview and Architecture
o Discussion Question

o Promoting Updating Versions

o Discussion Question
o VHD Chain of Differencing Disks
o Merging VHD Differencing Disks
Troubleshooting : Personal vDISK and Provisioning Services
Reinforcement Exercise: Provisioning Services

Upgrading Provisioning Services

The Provisioning Services Console is used for viewing and managing sites, servers, connections,
performing tasks such as assigning vDisk to target devices, managing stroes, and createing
device collections. It is also used to upgrade your Provisioning Services environment.

Updating vDisks
A vDisk update delivers new versions of a vDisk to all target devices without creating and
imaging an entirely new vDisk. Another4 advantage of performing a vDisk update, rather than
creating a new vDisk, is that target devices do not need to be reconfigured to use a new vDisk.
A vDisk update can be used to add or remove third-party software applications or files to or
form a vDisk Enabling vDisk updates requires configuring settings in the properties of both the
server and the vDisk.

Promoting Updated vDisks

An updated version of the vDisk is not available to production devices until it is promoted to
production. The updated promotion stages include maintenance, test, and production. Each
time a new version is created, the Access setting is automatically set to maintenance to allow
maintenance devices to make updates. After updates are complete, this version can be
promoted form maintenance to test to allow for testing by test devices, or directly to
production, for use by all target devices.
If issues exist, the net version can be reverted back form test to maintenance (if no active
sessions, exist), or from the production to either test or maintenance (any started device must
be shut down prior to reverting).

VDH Chain of Differencing Disks

A vDisk consists of a VHD base image file, any associated files, and if applicable, a chain of
referenced VHD differencing disks. Differencing disks are created to capture the changes made
to the base disk image, leaving the original base disk unchanged. Each differencing disk that is
associated with a base disk represents a different version.

Merging VHD Differencing Disks

Mearging VHD differencing disk files can save disk space and increase performance, depending
on the merge method selected. Merge methods include merging to a new base image or
merging to a consolidated differencing disk.
A merge can only occur when no Maintenance version exists for the vDisk or when the vDisk is
in Private Image mode. A merge starts from the top of the chain down to a base disk. A starting
disk cannot be specified for the merge.