XenApp and XenDesktop 7.15 Reviewer's Guide

Faster, simpler publishing of apps & desktops

Who should use this guide?

This reviewer’s guide is designed to help you quickly install and configure XenApp and XenDesktop version 7.15 LTSR or later for a trial evaluation. It guides you through a XenApp and XenDesktop deployment scenario to help you better understand how the application delivery capabilities work with the FlexCast® Management Architecture (FMA).

This guide will walkthrough setting up the three most common use cases:

  1. Publishing applications from XenApp (Server OS)
  2. Publishing a Hosted Shared Desktop from XenApp (Server OS)
  3. Deploying virtual desktop infrastructure (VDI) desktops with XenApp and XenDesktop (client OS)

Starting with release 7.0, XenApp and XenDesktop use identical code-base and are delivered using the same software download. The difference is in how it is licensed and purchased, offering flexibility of picking the feature-set and price point to suit different budgets and needs. Throughout this guide, the terms XenApp and XenDesktop may be used interchangeably. 

The target reviewer will:

  1. Have prior knowledge of managing virtual machines and Windows servers
  2. Possess experience in a system administration or technical reviewer role
  3. Be familiar, at least on a conceptual level, with previous versions of XenApp and XenDesktop

In the process of following this guide, the reviewer will use XenApp and XenDesktop for the core datacenter infrastructure, Citrix StoreFront for access to the enterprise app store, and Workspace appTM as the end user client software. An active directory infrastructure with DHCP and DNS services must be available. Setting up prerequisites is outside the scope of this guide.

For an in-depth evaluation and more details on the release, please see the Product Documentation.

Components of XenApp and XenDesktop
Licensing

XenApp and XenDesktop Enterprise and Platinum editions include both application and desktop publishing capabilities. Unlike previous deployments requiring separate infrastructure for XenApp and XenDesktop, unification of the architecture with FMA provides a single delivery infrastructure, and the same consoles are used for delivering server-based applications and desktops.

Organizations looking only for app publishing capabilities at this time may license the standalone Citrix Virtual Apps product. Since the code base is the same, subsequently upgrading from XenApp to XenDesktop is as easy as replacing the license key. There is no requirement for deploying additional infrastructure or management consoles.

Important information for customers upgrading from XenApp 6.5

Until XenApp 6.5, the product used a different architecture known as Independent Management Architecture (IMA). All current releases of XenApp and XenDesktop use the FMA. If you are upgrading from XenApp 6.5, please review this documentation.

A significant enhancement in this release, compared to XenApp 6.5, is the concept of separating XenApp management from the Windows Server machines that host virtual apps or server-based desktops. XenApp enables you to publish apps and server-based desktops from multiple platforms such as Windows Server 2008 R2, 2012, 2012 R2, and 2016 – all from one instance of the product. Future upgrades are also simpler as a result, because it is not directly associated with a specific version of Windows Server.

Back to top

Getting Started

Prerequisites
Network design
Activity scenario
Prerequisites

Please download the free evaluation software. For this evaluation, it is assumed that the reviewer will perform the necessary steps to put the downloaded ISO on a DVD or mount it as virtual disk.

For convenience in this guide, components are installed on fewer servers than are recommended for a production environment. An Active Directory infrastructure with DNS and DHCP services is required before you begin (during the evaluation, we strongly recommend a non-production Active Directory and DHCP service for the test environment).


Tip: While not recommended for production deployment, all virtual machines VMs for this evaluation may be run on a single physical server. The topology in this guide uses server hardware with 8 CPU cores and 64GB RAM for the test load.

Before we begin, please complete these prerequisite tasks:

  1. Ensure an Active Directory infrastructure is available. Create a group CitrixEval in Active Directory. Add users (user1, user2, etc.) to the CitrixEval group. To keep this evaluation simple, these accounts must have local administrator privileges and be domain administrators in Active Directory. In production, being a domain administrator is not required because relevant permissions will be assigned to administrator accounts according to their role.
  2. Create the virtual environment using your hypervisor of choice. XenApp and XenDesktop is supported on popular hypervisors such as Citrix Hypervisor, and Microsoft Hyper-V Server, as well as public clouds, such as Azure, AWS, and SoftLayer.

    Note: Please set up the preferred hypervisor (not in scope of this guide) before starting the lab.

    Download Citrix Hypervisor
    Microsoft System Center Virtual Machine Manager is required if Hyper-V is used.
    Require VMware vCenter, with the correct certificates installed, if vSphere is used.
  3. You need a VM templates for Windows 10 and Windows Server 2016. Create these templates as follows: Define the VM specifications (2 vCPU, 4GB RAM, 30GB vDisk) for the VMs. Assign a single network interface to all VMs. Install the operating system and activate. Convert to the template. Refer to your hypervisor vendor’s documentation for details.
Network design

The installation and configuration (excluding the prerequisites) are expected to take about 3 hours. Following is a list of VMs required for the setup shown in Figure 1.

Using these templates, create VMs 1 through 7 as per Table 1. Apply all the latest Windows patches, and turn Windows Update setting to “Never” afterwards. Take a snapshot of the “clean state” for each VM before installing any software other than the operating system (helpful if you ever wish to go back and start over). Join all VMs to the Active Directory domain. Using these VMs to create the master image is explained later in Step 1.1: Creating the master image.

Table 1: VM Assignment

Activity scenario

Once you have concluded the series of exercises in this guide, you will have an environment in which you can explore the full feature set and performance of XenApp and XenDesktop. Please read the product documentation for detailed instructions. The instructions in this guide are meant to provide you with an evaluation method. Not every component, feature or configuration is addressed.

The example scenario is to deliver applications and a desktop published from Windows Server 2016, and one pooled desktop based on Windows 10 operating system.

After you download and install the software, publishing desktops and apps is a three-step process, driven through a user friendlyuser-friendly wizard in Citrix Studio. One task needs to be performed outside of the wizard-based Studio console: creation of the master images. This involves setting up Windows machines with the required OS and other applications, then installing Citrix Virtual Delivery Agent on them to enable communication with the delivery controller.

At the end, apps will be launched using the Citrix Workspace app client from any device, such as a Windows laptop, MacBook, thin client, mobile device, or tablet. Citrix Workspace app is available as a free download from Citrix.com and the respective app stores. 

During this evaluation, the server-side activity flowchart will look something like this. 

Step 1: Installation and Initial Configuration

Ensure that the prerequisites (previous section) are in place and the software has been downloaded to a DVD (or mounted on a virtual DVD). Also, ensure VM1 has Windows Server 2016 (as per Table 1) installed, patched, and added to the Active Directory domain. This section describes the process for installing various components of XenApp and XenDesktop and configuring Studio.

The default option will be selected for most of the configuration settings. When a different option is recommended or explanation is required, those tasks are marked with a sign.

Step 1.1: XenApp and XenDesktop Installation

Install the Controller and other core components on VM1.

Slide: elulm

Insert the XenDesktop 7.15 LTSR DVD into VM1 and launch the Autorun Wizard. XenApp and XenDesktop are available in the same installation media.

Click Start for the relevant product to enter the Installation Wizard.

1 of 10
Slide: f8xvj

Select the Delivery Controller under Get Started.

The Installation Wizard automatically detects the Operating System and displays only compatible installation options.

2 of 10
Slide: c8sjb

Read through the license agreement and click “I have read, understand, and accept the terms of the license agreement”, then click Next.

3 of 10
Slide: zee5h

For the purpose of this evaluation, we will install all the core components on a single server. Accept the default values and click Next.

In a production environment, it is best practice to install the core components on separate servers for high availability and resource scaling. See the XenApp and XenDesktop Product Documentation for more details.

4 of 10
Slide: c019y

For this evaluation, we will use the built-in SQL Server Express to store app and desktop settings. Accept the default value and click Next.

5 of 10
Slide: ueltn

Allow the Installer to automatically configure Windows Firewall. Accept the default value and click Next.

If you are using a non- Windows Firewall, the Installer may be unable to configure it automatically. For this non-production exercise, manually disable any non-Windows Firewall or security apps.

6 of 10
Slide: 8g4x8

That’s all the information the Wizard needs to install the core components. Verify the information for accuracy, and click Install.

7 of 10
Slide: 8kv0t

All the components are installed automatically, including any missing prerequisites. The process takes about 15-20 minutes. The server may prompt to be restarted, in which case the installation will automatically continue when you log back in.

8 of 10
Slide: n2f9q

For the purposes of this exercise, select I do not want to connect to Citrix Smart Tools or Call Home and click Next.

 For production environments, we recommend taking advantage of Citrix Smart Tools and Call Home to diagnose issues and find recommended fixes.

9 of 10
Slide: tdcqm
10 of 10

Step 1.2: Set up the site in Citrix Studio

When you launch Citrix Studio for the first time, the first run wizard helps you quickly build a new site, create a pool of application servers and desktops (called “machine catalog”) and assign users to those applications and desktops (called “delivery groups”). More advanced users may add this Controller to an existing site or access physical machines using Remote PC Access (not in scope of this guide).

Slide: j16w1

Select Deliver applications and desktops to your users to initiate the site creation.

This wizard walks you through the initial configuration, database tables, and site environment.

The first steps is to create a site, which is the container for everything else we do today.

1 of 11
Slide: kv3kz

For this evaluation, select A fully configured, production-ready Site (default option) and give your site a name.

2 of 11
Slide: c8i35

As we are using the bundled SQL Express, allow it to create the database from Studio and accept the default database names.

The database location is “Localhost\SQLEXPRESS”. Configuration user should be a domain administrator.

Click Next.

3 of 11
Slide: 3ag5z

Accept the default licensing selection for a 30-day free trial.

Click Next.

4 of 11
Slide: d54ng

Provide connection details to the platform that will host virtual machines created by Machine Creation Services (MCS).

Studio supports connections to all popular hypervisors and cloud platforms, in addition to Citrix Hypervisor.

5 of 11
Slide: 76lqv

In this example, we are using Citrix Hypervisor with Machin Creation Services (MCS) to provision virtual machines.

Provide the connection information and credentials with permissions to create VMs on the hypervisor. Click Next.

6 of 11
Slide: 6yjfr

Select the storage resource type for your hypervisor. In this example, we are using the local storage on the hypervisor. Click Next.

7 of 11
Slide: r2nhe

Select to data location from your storage device. In this example, the only local storage location is select by default. Click Next.

8 of 11
Slide: svlsr

Select the server and network interface that all the virtual machines should use.

 For the evaluation use one NIC and the same network interface for all VMs.

Click Next.

9 of 11
Slide: 0zkme

XenDesktop 7.15 LTSR supports streamed apps with App-V.

For this evaluation, accept default (skip) and click Next.

 See product documentation to evaluate AppDNA and App-V.

10 of 11
Slide: 00dop

Verify the settings on the Summary page. Click Finish to create the site.

 Before moving to Step 2 of the first run Wizard, you must create a master image.

You will do this outside the Studio workflow in Step 2.1, and return to the Studio in Step 2.2.

11 of 11

Back to top 

Step 2: Create Master Image, Machine Catalog and Delivery Group

In this Step, you will create the Master Image, Machine Catalog, and Delivery Group. You have the option of delivering the 3 use cases, mentioned at the beginning of the guide: (1) deliver published applications from Server OS; (2) deliver a hosted shared desktop from Server OS; and (3) deliver VDI desktops from client OS.

Option A walks through the steps to deploy the first two use cases, to deliver published applications and a hosted shared desktop from Windows Server 2016.

Option B walks through the steps to deploy VDI desktop with Windows 10.

You can choose to deploy Option A, Option B, or both.

Option A: Publish Application and/or Hosted Shared Desktop from XenApp

Follow this section to deliver secure hosted application or a shared hosted desktop from Windows Server 2016.

Step 2.A.1: Install Delivery Agent on the master image

In the Getting Started section, we asked to create virtual machine templates. This is done by defining VM properties (how many vCPU, RAM, disk space), installation of OS, installation of common apps, and other configurations you want to be part of your users’ environment.

Your account must have local administrator privileges and be a domain administrator in the Active Directory, for the purpose of the evaluation.

Before you publish XenApp and XenDesktop, you must install the Citrix Virtual Delivery Agent on this server to create a master image.

The VDA is installed on this VM. For this evaluation, we choose to install it in the Master Image mode, so the virtual image will be managed and replicated using MCS. You may install the Delivery Agent in standalone mode, e.g. to deliver applications from the server itself, without replication. That is useful when the VDA is on a physical server, for instance.

Slide: i86dy

On the Windows Server VM to be used as the Master Image (VM2 per Table 1), insert the XenApp and XenDesktop 7.15 LTSR DVD or ISO and launch the installer. Click either Start button.

1 of 11
Slide: s3g48

Click Virtual Delivery Agent for Windows Server OS.

2 of 11
Slide: 6lp64

Accept the default selection and click Next. The first option (default value) will create MCS-cloned VMs using this master image.

3 of 11
Slide: 8ztbw

Accept the default values and click Next.

4 of 11
Slide: ydvsw

Uncheck both components and click Next.

5 of 11
Slide: f28oa

Select Let Machine Creation Services do it automatically

 If you add it manually, notice how the intelligent configuration validation feature throws an alert if you make an error.

6 of 11
Slide: 6v4mt

Accept the default selections and click Next.

 Advanced users may choose to select additional features.

7 of 11
Slide: h8gvg

Accept the default selection and click Next.

Windows Firewall is configured automatically. For simplicity during the evaluation, ensure other firewalls are not present, or disabled.

8 of 11
Slide: x676o

Click Install to start the installation.

The machine may reboot after some of the components have been installed. After reboot, log back in and installation.

9 of 11
Slide: 1mc0a

Select I do not want to participate in Call Home and click Next.

 For Production deployments, we encourage enabling Call Home to receiver proactive notifications of potential issues.

10 of 11
Slide: yuvka

Click Finish. After the machine restarts install the apps you want to publish with XenApp and shutdown the machine.

11 of 11

Step 2.A.2: Creating the machine catalog

A machine catalog is a collection of desktops or physical computers that are managed as a single entity. To deliver applications and desktops to users, the machine administrator creates a catalog of machines and the assignment administrator allocates machines from the machine catalog to users by creating delivery groups.

For this isolated evaluation, we simply use a domain administrator in the Active Directory with local administrator privileges.

Slide: byk53

Now that the master image is ready, you can return to Citrix Studio to create your Machine Catalog

Next to the number 2, click Set up machines for desktop and applications, then click Next.

1 of 9
Slide: h96qs

If First Run wizard is no longer available, click Machine Catalogs on the left, and then click Create Machine Catalog to launch the workflow, then click Next.

2 of 9
Slide: hfcup

To deliver server-hosted apps and desktops, select Server OS.

Click Next.

3 of 9
Slide: kc1s8

Accept default selections: Power Managed (Virtual Machines) and Machine Creation Services (MCS).

Click Next.

4 of 9
Slide: qztkl

Select the Master Image from the list that your previously created and click Next.

5 of 9
Slide: m86u7

Select how many cloned VMs are needed in the pool. For testing, one or two is sufficient. You can add additional machines later.

Leave everything else at default and click Next.

6 of 9
Slide: 48kp9

Select the Computer Organizational Unit (OU) to place the newly created VMs.

Provide an account naming schemed, such as Eval-XA-## (Placeholders ## will be replaced by a VM sequence number).

Leave everything else default and click Next.

7 of 9
Slide: uutut

Provide a name for the catalog, and optionally, a description to identify the type of machines in this catalog.

Click Finish to start the machine creation process

8 of 9
Slide: bsvrv

Machine Catalog creation takes about 15-25 minutes depending on the number of machines and type of underlying hardware.

Wait to complete before creating Delivery Groups.

The Dashboard Actions pane shows task status.

9 of 9

Step 2.A.3: Publish desktops and applications

Using Studio, you will first have to configure a site, create and specify machine catalogs, and then create delivery groups using those machine catalogs. Users are then entitled to one or more Delivery Groups and use the desktops/applications published.

This step guides you through creating a Delivery Group to publish applications and a server-based hosted shared desktop to a group of users, using your Windows Server 2016 XenApp machine catalog created in the previous step.

For more details on how application publishing has evolved since XenApp 6.5, please see Important Information for Citrix Virtual Apps and Desktops Administrators in the product documentation.

Slide: cz24c

Select option 3 in the First Run Wizard to set up Delivery Group and click Next.

 If the First Run wizard is no longer available, navigate to Studio > Delivery Groups > Actions (on right pane) > Create Delivery Groups to launch the workflow.

Slide: s4tgz

Select the XenApp and XenDesktop Eval machine catalog.

Click to add the number of machines you want in that group. In this example, we chose 2 machines.

Click Next.

Slide: 8cf9m

Select Restrict use of this Delivery Group… and add the CitrixEval AD created in the Prerequisites section.

Click Next.

Slide: h5fme

Click the Add dropdown and select From the start menu.

This will populate the installed applications. Select the applications you wish to publish. In this example, we selected Wordpad, Paint, and Calculator.

Click OK and then click Next.

Slide: 39us5

To publish a Hosted Shared Desktop from the XenApp servers, clik Add.

 This step is optional.

Enter a display name and add the CitrixEval user group.

Click OK and Next.

Slide: be3nq

Enter a Delivery Group name, such as XenApp and XenDesktop Eval Delivery Group, and optionally add a description. Click Finish.

Option B: Delivering VDI desktops with XenApp and XenDesktop

Follow this section to deploy a VDI desktop with Windows 10.

Step 2.B.1: Install Delivery Agent on the Windows 10 master image

Follow this section to deliver Windows 10 desktops with XenApp and XenDesktop.

In the Getting Started section, we asked to create virtual machine templates. This is done by defining VM properties (how many vCPU, RAM, Disk space), installation of operating system (OS), installation of common apps, and other configurations you want to be part of your users’ environment.

Your account must have local administrator privileges and be a domain administrator in the Active Directory, for the purpose of the evaluation.

Before you publish virtual desktop infrastructure, you must install the Citrix Virtual Delivery Agent on this desktop to create a master image.

Slide: fk3f6

On the Windows 10 VM to be used as the Master Image (VM3 per Table 1), insert the XenApp and XenDesktop 7.15 LTSR DVD or ISO and launch the installer.

Click the Start button next to XenApp and XenDesktop.

1 of 12
Slide: ninzq

Click Virtual Delivery Agent for Windows Desktop OS.

2 of 12
Slide: y5agb

Accept the default selection and click Next.

The first option (default value) will create MCS-cloned VMs using this master image.

3 of 12
Slide: 0op4c

Accept the default values and click Next.

4 of 12
Slide: k0z5f

Accept the default values and click Next.

5 of 12
Slide: pkg40

Uncheck the first two components and click Next.

Advanced users may evaluate the additional options.

6 of 12
Slide: ucxaj

Select Let Machine Creation Services do it automatically and click Next.

7 of 12
Slide: pi4tz

Accept the default selections and click Next.

 Advanced users may choose to select additional features.

8 of 12
Slide: 1qzun

Accept the default selection and click Next.

Windows Firewall is configured automatically. For simplicity during the evaluation, ensure other firewalls are not present or disabled.

9 of 12
Slide: jm4gv

Click Install to start the installation.

The machine may reboot after some of the components have been installed. After reboot, log back in and the installation continues.

10 of 12
Slide: 6jksx

Select I do not want to participate in Call Home and click Next.

For Production deployments, we encourage Call Home to receive proactive notifications of potential issues.

11 of 12
Slide: aihej

Click Finish.

After the machine restarts install the apps you want on your VDI desktops and shutdown the machine.

12 of 12

Step 2.B.2: Creating the machine catalog

A machine catalog is a collection of desktops or physical computers that are managed as a single entity. To deliver applications and desktops to users, the machine administrator creates a catalog of machines and the assignment administrator allocates machines from the machine catalog to users by creating delivery groups.

For this isolated evaluation, we simply use a domain administrator in the Active Directory with local administrator privileges.

Slide: zcasu

Now that the master image is ready, you can return to Citrix Studio to create your Machine Catalog.

Next to the number 2, click Set up machines for desktop and applications, then click Next.

1 of 10
Slide: dyla1

If First Run wizard is no longer available, click Machine Catalogs on the left, and then click Create Machine Catalog to launch the workflow.

Click Next.

2 of 10
Slide: ly9o2

Select Desktop OS to deliver VDI desktops.

Click Next.

3 of 10
Slide: yun57

Accept default selections: Power Managed (Virtual Machines) and Machine Creation Services (MCS).

Click Next.

4 of 10
Slide: ccq5a

Select I want users to connect to a new (random) desktop each time they log on.

This scenario is creating a pooled VDI environment where users will get a fresh desktop from the master image each time they log in. Select the second option to give users a dedicated desktop.

Click Next.

5 of 10
Slide: cwcxe

Select VM3 in the list as your Master Image and click Next.

6 of 10
Slide: 1dvx3

Select how many cloned VMs are needed in the pool. For testing, one or two is sufficient. You can add additional machines later.

Leave everything else at default and click Next.

7 of 10
Slide: 4vjtj

Select the Computer OU to place the newly created VMs.

Provide an account naming schemed, such as Eval-XD-## (Placeholders ## will be replaced by a VM sequence number).

Leave everything else default and click Next.

8 of 10
Slide: zmp93

Provide a name for the catalog, and optionally, a description to identify the type of machines in this catalog.

Click Finish to start the machine creation process.

9 of 10
Slide: lds7e

Machine Catalog creation takes about 15-25 minutes depending on the number of machines and type of underlying hardware.

Wait to complete before creating Delivery Groups.

The Dashboard Actions pane shows task status.

10 of 10

Step 2.B.3: Create delivery group to publish VDI desktops

Using Studio, you will first have to configure a site, create and specify machine catalogs, and then create delivery groups using those machine catalogs. Users are then entitled to one or more Delivery Groups and use the desktops/applications published to them.

This step guides you through creating a Delivery Group to publish VDI desktops to a group of users, using your Windows 10 XenApp and XenDesktop machine catalog created in the previous step.

Slide: 9tomk

Select option 3 in the First Run Wizard set up Delivery Group and click Next. 

 If the First Run Wizard is no longer available, navigate to Studio > Delivery Groups > Actions (on right pane) > Create Delivery Groups to launch the workflow.

Slide: al1hi

Select the XenApp and XenDesktop Eval machine catalog.

Click to add the number of machines you want in that group. In this example, we chose 2 machines.

Click Next.
 

Slide: w5lmy

Select Restrict use of this Delivery Group… and add the CitrixEval AD created in the Prerequisites section. Click Next.

Slide: z9i2a

Click Next.

 Advanced users may publish applications from a client OS on this step.

Slide: l8ekj

Click Add and enter a Display name, such as VDI Windows 10 XenApp and XenDesktop. Click OK and then Next.

Slide: kxeo8

Enter a Delivery Group name, such as XenApp and XenDesktop Eval Delivery Group, and optionally add a description. Click Finish.

Back to top 

Step 3: Configuring the StoreFront Server

Citrix StoreFront is the next generation of Web Interface, and enables self-service provisioning of desktops and applications, among a host of new functionality. StoreFront authenticates users and manages the store of applications and desktops. In this evaluation, StoreFront runs on the same server as the Controller (VM1).

Slide: 2tvem

Click View or Change stores to view the default store.

Citrix StoreFront management console is integrated with Citrix Studio.

A default store is automatically created when the first delivery group is created.

 StoreFront console is also available as a standalone console.

Slide: fd8js

Store URL is in the form: http(s)://<servername>/Citrix/Store

Browser URL for store is: http(s)://<servername>/Citrix/StoreWeb

Slide: 15lm1

For evaluations, the auto-created store quickly allows access to the environment. No further configuration needed after the Delivery Groups are set up.

 Please refer to the admin guide if you wish to create a custom StoreFront site.

Slide: aejr4

Advanced users can fine tune the Store Service settings in the action pane on the right.

 As a best practice, StoreFront services are installed in a redundant topology, separate from the Delivery Controller. All components are on a single server for purpose of this guide.

Slide: ry1wy

Advanced users: Some new features have been added to the console that were previously available from the PowerCLI alone.

Click Configure Store settings to manage mandatory user subscriptions, for example.

Slide: cq6pr

Advanced users: StoreFront supports multiple authentication methods, including Smart Cards, anonymous login, and VPN tunneling.

See the admin guide for more details.

Back to top 

Step 4: End user session launch (Citrix Workspace app)

You will now use VM #4 from Table 1 to launch apps and desktops on an endpoint and experience as end-user.

Launch published desktops and applications using Workspace app.

Citrix Workspace app is the lightweight access client that enables access to applications and desktops from StoreFront. Once a user is authenticated, you will have access those applications and desktops hosted on XenApp and XenDesktop.

Slide: vprhj

On a client machine, Windows 7 in this case, open a browser and go to the default StoreFront URL

http://<servername>/Citrix/StoreWeb

1 of 12
Slide: 9kapc

If Citrix Workspace app is not already installed on the client, you are prompted to install it. Accept the EULA if you agree, Click Install and follow the installation process.

Return to the login page once it is installed.

2 of 12
Slide: ll93o

Login as a domain user.

If user subscription is enabled, the first screen will be “Favorites”. You can add apps and desktops here, click on the respective icon on the top panel.

3 of 12
Slide: 4tc6z

Click on Apps to see all the apps made available to you by the administrator.

Click Details next to the app you want to add in Favorites, or click the icon to launch the app.

You can search for an app or desktop by name, using the search bar on top-right.

4 of 12
Slide: 4g0az

Click Details next to the app you want to add in Favorites, or click the icon to launch the app.

Click Add to favorites.

5 of 12
Slide: lqhui

The app will be visible in first- screen (Favorites) when you log-in the next time

6 of 12
Slide: swubx

Click Desktop on top to see any Server Hosted Shared Desktops made available to you by the administrator.

Click Details next to the desktop to add it to your favorites screen, or launch the desktop. You can even restart the desktop as a quick fix for any non-responsive sessions.

7 of 12
Slide: mazv7

Click open to launch the desktop

8 of 12
Slide: 9u07r

Congratulations! You have published your first virtual desktop.

A drop-down tool on the top of Desktop Viewer provides access to custom settings, if needed.

9 of 12
Slide: daqht

Custom alternative 1:

If you disable user subscriptions for the store, users see all the apps entitled to them without adding them to a favorites screen.

10 of 12
Slide: 5ao80

There is no Favorites tab, if Mandatory Store is in effect and user subscription is turned off.

11 of 12
Slide: z0ejr

Custom alternative 2:

In the previous section, we saw how to configure the popular feature in StoreFront to bundle apps into related categories known as “Featured App Groups”

Here’s a view from a production deployment.

12 of 12

Citrix Workspace app is a very flexible and user-friendly client for desktop and app access, downloaded by over 200,000 users every month. Feel free to experiment and create the look-and-feel that is most appealing to your users and meets all your business needs.

Step 5: Operations helpdesk and monitoring with Director

Citrix Director is the only operations dashboard designed from the ground up to resolve the unique challenges created by app and desktop virtualization. Unlike most industry monitoring solutions that take an infrastructure view of the environment, Director is designed for the “end user” view. It greatly increases efficiency of support helpdesk and Citrix specialists by providing great detail about all aspects of the user sessions – whether related to application, networking, storage, compute, or even the end user device. Use the Director to quickly identify and resolve issues before they negatively impact end-user performance.

Slide: jbmgg

Access the Director console with this easy URL:

http://<servername>/Director

Director console can also be accessed from the Start Menu of the server. In production, it is deployed on a separate server from delivery controller

1 of 13
Slide: tghi6

This is a snapshot of the Dashboard. It clearly shows relevant information, such as the connected sessions, failed sessions, average logon time, and so on.

2 of 13
Slide: 348ff

Click through on the dashboard to drill down into details of the parameters such as connection or session details, type of delivery group, etc.

On this page, you can filter the view by user, by machine, or by connection state. See the Workspace app version and endpoint name/ IP. Drill down for more.

3 of 13
Slide: qua6p

In case of failed sessions, see the Failure Reason, client version, server group, end-user IP, etc. to get a quick idea for any obvious fixes. Drill down for more.

4 of 13
Slide: c37h3

If a particular user calls into the helpdesk, staff can quickly bring up their details on screen using the search facility.

Search by user name, machine name, or endpoint name

5 of 13
Slide: hajzk

Whether using search or using click-through from connection dashboard, brings up Activity Manager.

Click Details on top-right to see extensive data on that user’s sessions.

6 of 13
Slide: e0n6r

Detailed user information on the IP addresses, software versions, and hardware – endpoint as well as datacenter VM.

State and name of processes and apps running. Ability to end a rogue process on behalf of user.

Troubleshooting tasks such as power or session control can be performed on this console.

7 of 13
Slide: lt40j

Session shadowing is available for walking user through a solution.

Once the user accepts the remote assistance prompt, IT can shadow the user session to help troubleshoot any endpoint issues.

8 of 13
Slide: y61z7

The drop-down on the user details page shows the various delivery groups entitled for the user, and connection status.

Filter capabilities allow IT to focus on the relevant information.

9 of 13
Slide: u2vnp

Understanding when the peak usage is occurring and what those peak levels are allow you to predict the capacity needs based upon past history usage. It’s also important to be able to drill down to the specific application to determine who used that application

Click Trends on the top panel, then select Capacity Management. Usage trends available for applications, desktops, and servers.

10 of 13
Slide: z8rbm

XenApp and XenDesktop Platinum activates EdgeSight features for Director, such as historical analysis, modeling and trending.

Citrix ADC Platinum activates HDX Insight to diagnose and improve ICA network performance.

11 of 13
Slide: egig1

This discussion explores only a fraction of visibility offered by the new Director.

Feel free to explore different pages full of helpful tools such as integrated HDX Monitor, personalization statistics, alerts, and so on.

12 of 13
Slide: dz7th

Director provides proactive notifications, based on policy triggers. Click Alerts in the top menu to access this.

Perform a one-time email server setup to send automatic emails.

Create policies to trigger email alerts if a threshold is crossed, say connection failure rate of 25% and greater.

13 of 13

Back to top 

Conclusion

This concludes your evaluation of XenApp and XenDesktop release. This simplified guide is intended for a quick evaluation of the product features, using a narrow scope of work. It does not replace the product documentation and detailed deployment guides .

Through this process, you learned how to install a basic deployment of XenApp and XenDesktop, configure a Studio site and create machine catalogs. Using delivery groups, you provisioned both apps and desktops from a single unified console. You saw the flexible end user delivery options, whether custom branding or true support for any device. Finally, you experienced the powerful monitoring, troubleshooting, and analytical features of Director, seeing the value of an intuitive purpose-built tool for day-to-day operations of a large-scale virtualized environment.

Over the past 25 years, our leading design philosophy believes there is no one-size-fits-all architecture. Our customers have uniquely varied requirements, from small organizations enabling workspace mobility to the largest Fortune 500 corporations deploying tens of thousands of Citrix Virtual Apps servers. The basic building blocks of machine catalogs, delivery groups, and apps can be put together to meet sophisticated and complex business needs. This guide is targeted at administrators that may be new to Citrix, and as such, it follows the simplest workflow to get an evaluation running. Now that you have completed these tasks and seen how a basic deployment functions, use the XenApp and XenDesktop documentation to experience all the components and features available with this release.

Appendix

A few additional features and use-cases are covered in this section. These features require slightly more advanced knowledge of the product, so they were moved outside the main document instructions.

Workspace app for HTML5 for client-less access

One of the most powerful enhancements to XenApp and XenDesktop is the ability to run applications and desktops in a browser, without installing any client software on the endpoint. The HTML5 Workspace app for XenApp and XenDesktop delivers a rich graphical user-experience using the Deep Compression technology from the native Workspace app. For mobile work styles, the HTML5 Workspace app is a very important and useful tool.

Three easy steps get you ready to use Workspace app for HTML5 in XenApp and XenDesktop environment

  1. Enable Workspace app for HTML5 in Citrix StoreFront
  2. Enable ICA WebSockets in Citrix Group Policy
  3. Test Desktop launch from a compatible browser and client

Detailed instructions are provided in Product Documentation

Step 1: Enable Workspace app for HTML5 in Citrix StoreFront
If not already installed, please deploy Citrix StoreFront either on the same server as the Delivery Controller or a standalone console. Create a store for the site.

Slide: z5z1t

In the StoreFront console, click Manage Workspace app for Web Sites in the action pane on the right.

Select the appropriate store, and click Configure...

Slide: f00el

Select Deploy Citrix Workspace app

  • To enable Workspace app for HTML5, there are 3 options:
  • Always use Workspace app for HTML5
  • Use Workspace app for HTML5 if local Workspace app is unavailable
  • Install locally

For this eval, you may choose to always use Workspace app for HTML5

Step 2: Enable Ports using Group Policy
Once the Workspace app settings are configured in StoreFront, we need to enable the ICA Websockets using Group Policies from Citrix Studio console.

Slide: t1gso

Under Citrix Studio, go to Policy

1 of 12
Slide: 4bqob

In the middle pane, under Policies, either modify an existing policy or create a new policy.

For simplicity, we will create a new policy

2 of 12
Slide: nshv8

To create a new policy, go to Citrix Studio Policy, under Actions Policy, Click Create Policy

3 of 12
Slide: w5rqx

Type websoc in the search field of the Edit Unfiltered window that opens. This shows only the three WebSockets related policy settings.

One by one, click Select and edit each of them.

4 of 12
Slide: ihrds

In the first policy, allow WebSockets connections (prohibited by default)

Select Allowed and click OK

5 of 12
Slide: 7wpxv

In the second policy, leave default ports, click OK

Note: In production, a non-default port will be selected as security best practice

6 of 12
Slide: ae302

In the third policy for trusted origin servers, leave default server, click OK

Note: In production, specific trusted servers will be listed as security best practice

7 of 12
Slide: h8s9a

Once all three policies are defined, Click Next

8 of 12
Slide: vsfji

Assign policy to users and machines based on delivery group, OU, or Tags.

Select Delivery group. Click Assign.

9 of 12
Slide: kwwa8

Once you click on Assign, a window – Assign Policy opens. Select the appropriate Delivery Group from the drop-down.

Click OK

10 of 12
Slide: 7bpkw

Alternatively, if you select Organizational Unit (OU), then you have the option to select specific OU from your AD environment.

11 of 12
Slide: tixdt

Alternatively, if you Selected Delivery Group Type, in the Assign Policy screen you
can select from the following delivery group types:

  • Private Desktop
  • Shared Desktop
  • Private Application
  • SharedApplication
12 of 12

Step 3: Verify HTML5 access to your Desktops and Applications
From the client machine, access the StoreFront URL using a compatible browser

Login via StoreFront URL using domain credentials based on permission (users/groups) in delivery group. Default URL would be http://<DDC-IPaddress-or-FQDN>/Citrix/StoreWeb

If you selected the Always Use Workspace app for HTML5, you will not see the prompt to install Workspace app. Instead, it will directly ask you to authenticate.

Slide: xlerv

If you selected the option to Use Workspace app for HTML5 if local Workspace app is unavailable during Step 1, and Workspace app is not already installed in the system, it will prompt you to install the Workspace app on the Citrix portal page. Do not install the Citrix Workspace app at the prompt. Instead, click Log On at the bottom.

Slide: c4ep0

Enter the appropriate Username and Password

Slide: ytwkc

Step 2: Enable Ports using Group Policy
Once the Workspace app settings are configured in StoreFront, we need to enable the ICA Websockets using Group Policies from Citrix Studio console.

The page will enumerate all the Apps and Desktops entitled to you. Click the icon to launch.

Slide: 8rib4

The resource opens in a new tab using Workspace app for HTML5. The resources are labeled for easy tab-switching, and can be dragged to their own window instead of tab. A retractable toolbar allows file upload, download, and clipboard copy between local endpoint and virtual app.

Citrix Workspace app for Chrome App is used when users running Google’s Chrome OS log on to a Workspace app for Web site. It is also based on HTML5 but has more features due to Google’s API support.

Workspace app for HTML5 is a great tool when local installation of the plug-in is not possible or recommended, say in kiosk mode. The native client is recommended where possible, for best performance and user-experience.

Citrix Workspace app for HTML5 contains many enhancements for great user experience:

  1. A floating toolbar enables clipboard copy-paste between client and virtual desktop.
  2. Toolbar also lets you send CTRL+ALT+DEL for Windows tasks such as logging off, locking the screen,
    and so on
  3. When not in use, toolbar is inconspicuously docked at any edge of the screen
  4. “Host to client URL redirection” redirects websites opened in session to the client browser, for the best
    multimedia experience.

Back to top

Further reading

Lightbox Content [Component of Citrix Virtual Apps] Use edit bar to hide/show content
Slide: 4ouri

Delivery Controller

The delivery controller is responsible for distributing applications and desktops, managing user access and optimizing connections to applications. The delivery controller runs the broker services, which establishes the HDX connection between end user devices and the resource. One or more delivery controllers make up a site.

1 of 9
Slide: 7pztk

Citrix Studio

Studio is the primary console to configure and manage XenApp and XenDesktop deployments. Studio provides various wizards to guide you through the process of setting up your environment, creating desktops and assigning desktops to users.

2 of 9
Slide: 49zwm

Citrix Director

This web-based console enables IT support and helpdesk teams to monitor XenApp and XenDesktop environments, troubleshoot issues before they become system critical and perform support tasks for end users.

3 of 9
Slide: wspxi

Citrix StoreFront

StoreFront enables you to create enterprise app stores that aggregate resources from XenDesktop 7.x, XenApp 7.x, XenApp 6.x, Citrix Endpoint Management, and cloud services.

4 of 9
Slide: uvucc

Virtual Delivery Agent

The agent, which is installed on the virtual or physical machines hosting applications to be delivered to users, enables these machines to register with the delivery controllers. It also manages the HDX connection between the hosted applications and Citrix Workspace app.

5 of 9
Slide: 36f0f

Server-based resources

These virtual or physical machines based on Windows server operating systems are used for delivering Citrix Virtual Apps-based applications and Citrix Virtual Apps-based desktops to users.

6 of 9
Slide: 7hst4

Desktop-based resources

These virtual or physical machines based on Windows desktop operating systems are used for delivering the full XenApp and XenDesktop VDI to users.

7 of 9
Slide: h0ofd

Citrix Workspace app

This endpoint component provides users with self-service access to resources published on XenApp and XenDesktop servers. Citrix Workspace app is easy to deploy and use, and offers quick, secure access to hosted applications, desktops and data. Users can run it on a wide variety of devices, including low-cost thin-clients, tablets and mobiles, kiosks, and devices based on Linux, Mac, Windows, and Chrome OS.

8 of 9
Slide: ejt9h

Citrix Gateway

Citrix Gateway terminates a virtual private network (VPN) for remote users coming over the Internet and communicates with StoreFront to deliver apps and desktops to authorized users. The optional security component does not fall under the scope of this paper, which considers only local users who access StoreFront directly.

9 of 9