Deployment Guide for Project Avalon Excalibur Tech Preview

8/11/2019 Deployment Guide for Project Avalon Excalibur Tech Preview

1/25

Deployment Guide for Project Avalon

Excalibur Technology Preview

Project Avalon Excalibur Technology Preview


2/25

Copyright and Trademarks

Use of the product documented herein is subject to your prior acceptance of the End User License Agreement. A

printable copy of the End User License Agreement is included with your installation media.

Information in this document is subject to change without notice. Companies, names, and data used in examples herein

are fictitious unless otherwise noted. No part of this document may be reproduced or transmitted in any form or by any

means, electronic or mechanical, for any purpose, without the express written permission of Citrix Systems, Inc.

2012 Citrix Systems, Inc. All rights reserved.

The following are trademarks of Citrix Systems, Inc. and/or one or more of its subsidiaries, and may be registered in the

United States Patent and Trademark Office and in other countries:

Citrix, Citrix Receiver, Citrix XenApp, Xen, XenDesktop, XenServer,

All other trademarks and registered trademarks are the property of their respective owners.

Document code: November 8 2012 11:32:28


3/25

Contents

Deployment Guide for Project Avalon Excalibur Technology Preview..............5

Disc la imer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

Important information for XenApp administrators.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .6

Important Excalibur infrastructure concepts for XenApp administrators.. . . . . . . . . . . . . . .6

Key differences between XenApp and Excalibur... .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .7

Components of an Excalibur deployment................................................8

Application publishing in Excalibur. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Overview and scenario requirements.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .9

Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

Scenar io Requirements... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

System Requirements... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Delivery Control ler .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Site database.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Director. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Delivery Agent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Hos t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Other. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Install Server 1 components.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

To install components on Server 1.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..14

Configure a site. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Install Server 2 components and create a server certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

Create a server certificate and add site binding........................................16

Install StoreFront. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Install Server 3 components.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Install the Delivery Agent on the Image.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..18Configure the StoreFront server.............................................................19

Create Machine Catalogs... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Create Delivery Groups... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Add hosted applications.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

To add Notepad to the Delivery Group.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .23

Install and configure Citrix Receiver.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .24

iii


4/25

Appendix: Create a domain certificate authority.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Contents

iv


5/25

Deployment Guide for Project Avalon

Excalibur Technology Preview

The Deployment Guide for Project Avalon Excalibur Technology Preview is a scenario-

based guide. There are ten overall tasks to be done, each of which is broken into

smaller steps. The activities are:

Each of the tasks build toward that outcome. Once you have concluded this series of

tasks, you will have an environment on which you can explore application and desktop

delivery in Excalibur.

The Deployment Guide for Project Avalon Excalibur Technology Preview is designed to

allow you to try this preview release. It guides you through a small deployment to help

you better understand how the core desktop and application technology works. Not

every component, feature, or configuration is addressed here.

Note: See the Project Avalon Excalibur Technology Preview document for a

description of the components, features, and configurations included in this technology

preview release, such as Director, Configuration Logging, and delegated

administration. You can find the document at http://www.citrix.com/techpreview/

projectavalonexcalibur.

For convenience, components are installed on fewer servers than are recommended for

a production environment.

Important: Please follow the instructions in the Deployment Guide for Project Avalon

Excalibur Technology Preview in the order they are presented. Do not skip topics. The

Deployment Guide for Project Avalon Excalibur Technology Preview experience is

designed to build from topic to topic. If steps are skipped or not completed as

described, the expected outcome of the scenario may fail.

5
http://www.citrix.com/techpreview/projectavalonexcaliburhttp://www.citrix.com/techpreview/projectavalonexcalibur


6/25

Also included is a topic from the main Project Avalon Excalibur Technology Preview

documentation titled Important information for XenApp administrators, targeted

toward XenApp administrators working with the new architecture for the first time.

DisclaimerThis document is furnished "AS IS." CITRIX DISCLAIMS ALL WARRANTIES REGARDING THE

CONTENTS OF THIS DOCUMENT, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES

OF MERCHANTABILITY AND FITNESS FOR ANY PARTICULAR PURPOSE. This document may

contain technical or other inaccuracies or typographical errors. Citrix reserves the right

to revise the information in this document at any time without notice. This document

and the software described in this document constitute confidential information of

Citrix and its licensors, and are furnished under a license from Citrix. This document

and the software may be used and copied only as agreed upon by the Technology

Preview Agreement.

Important information for XenApp administratorsOne of the major changes you will find in this release is Excalibur, the unification of

hosted applications and desktops (XenApp) with personalized desktops (XenDesktop)

within a single architecture and management experience. The capabilities previously

available within XenApp are now delivered within the XenDesktop infrastructure and

components. If you have prior experience managing XenApp farms, this topic helps you

understand the following:

w Key concepts of the Excalibur infrastructure

w Differences in terminology

w Excalibur components, what they do, and where to find installation instructions

w Publishing applications in the Excalibur infrastructure and where to find more

information about the various ways in which you can make applications available to

your users

Important Excalibur infrastructure concepts for

XenApp administratorsThe following terms and concepts are important for you to understand so that you can

effectively publish applications and publish desktops from the Excalibur infrastructure.

When you publish applications, you are creatingor adding applications. It is important

to be familiar with the following components necessary to deliver applications:

A machine catalogis a collection of virtual machines (VMs) and physical machines

managed as a single entity. Machine catalogs specify the following:

w VMs or physical computers available to host applications or desktops

w The Active Directory computer accounts assigned to those VMs or computers

Deployment Guide for Project Avalon Excalibur Technology Preview

6
http://-/?-


7/25

w In some cases, the master image that is copied to create the VMs

A delivery groupis a collection of servers that specify who can use a set of

applications. A single delivery group can contain applications from a number of

machine catalogs rather than a single hypervisor pool. Also, a single delivery group can

be published to users so that a single user may access multiple applications in the group.

Key differences between XenApp and ExcaliburIn moving from a traditional XenApp environment to Excalibur, you find the following

key differences:

w Citrix Studio instead of Delivery Services Console.In Excalibur, you use Studio toconfigure your environments and provide users with access to applications and

desktops.

wNo IMA data store.Excalibur does not use the IMA data store as the centraldatabase in which to store configuration information. Instead, it uses a MicrosoftSQL Server database as the data store for both configuration and session

information. This means:

Database requirements are different: Microsoft Access and Oracle are no longer

supported databases.

Terminal Services (Remote Desktop Services) is no longer required on servers

running the controller.

There is no dedicated zone master. In XenApp, there is a zone master or data

collector responsible for user connection requests and communication with

hypervisors. In this release, this function is distributed evenly across all

controllers in the site.

If you require high availability or disaster recovery for Microsoft SQL Server you

can configure clustering or mirroring, or deploy the database as a virtual

machine and use your hypervisor's high availability features instead. For more

information about planning for high availability, see the topic "High availability

planning" in the document Project Avalon Excalibur Technology Preview.

w Delegated Administration.In XenApp, you can create custom administrators andassign them permissions based on folders and objects. In this release, you can

create custom administrators whose permissions are based on role and scopepairs.

A role represents a job function and has defined permissions associated with it. A

scope represents a collection of objects. You use scope to group objects in a way

that is relevant to your organization (for example, the set of desktop groups used by

the Sales team). This release also offers several built-in administrator roles (otherthan the full administrator role), such as help desk, applications, hosting, and

catalog. Each of these built-in roles includes specific management permissions. For

more information, see the topic "Delegated administration" in the document Project

Avalon Excalibur Technology Preview.

w No Shadow Taskbar.To view and interact with other users' sessions remotely, youuse the shadow feature launched from Director console. For more information on


7


8/25

Director and how it enables IT support, see the topic "About Director" in the

document Project Avalon Excalibur Technology Preview.

w Sites instead of Farms.In this release, the XenApp "farms" are known as "sites."

Components of an Excalibur deploymentIf you already have experience with a XenApp environment, it will be helpful to you to

identify the components introduced in Excalibur and learn how they work and

communicate with each other.

Excalibur components

Under the Excalibur architecture, management and delivery components are sharedbetween XenDesktop and XenApp to give administrators a unified management

experience.

w Receiver.Receiver provides users with self-service access to resources published onXenApp or XenDesktop servers. Receiver combines ease of deployment and use, and

offers quick, secure access to hosted applications, desktops, and data. Receiver also

provides on-demand access to Windows, Web, and Software as a Service (SaaS)

applications.


8


9/25

w StoreFront.StoreFront authenticates users to XenDesktop sites and manages storesof desktops and applications that users access.

w Studio.Studio enables you to configure and manage your XenDesktop deployment.Studio provides various wizards to guide you through the process of setting up your

environment, creating your desktops, and assigning desktops to users.

w Delivery Controller.The Delivery Controller is responsible for distributingapplications and desktops, managing user access, and optimizing connections to

applications. Each site has one or more delivery controllers.

w Server OS Machines.VMs or physical machines based on Windows Server operatingsystem used for delivering applications or hosted shared desktops to users.

w Desktop OS Machines.VMs or physical machines based on Windows Desktopoperating system used for delivering personalized desktops to users, or applications

from desktop operating systems.

For more information about installing components and guidance on the order in whichyou install them, see the topic "Install and configure" in the document Project Avalon

Excalibur Technology Preview.

Application publishing in ExcaliburTo publish applications in Excalibur, you create and add applications in Studio to make

them available to delivery group users. Using Studio, you will first have to configure a

site, create and specify machine catalogs, and then create delivery groups within those

machine catalogs. Delivery groups are then used to determine which users will have

access to the applications you decide to publish.

Once you have created delivery groups, you can then create an application to specifywhich delivery groups will provide access to that specific application (see the topic "To

create an application" in the document Project Avalon Excalibur Technology Preview).

You can view which applications are added to a selected delivery group, as well as

enable, disable or modify the applications in Studio (see the topic "To modify

applications" in the document Project Avalon Excalibur Technology Preview).

There are several different methods for delivering applications, and you choose the

method that is most appropriate for your specific environment. One such method is

through use of the Hosted Applications feature, which integrates XenApp functionality

into a XenDesktop environment to virtually deliver applications to remote user devices

in high definition. For more information on this feature and a detailed explanation of

how you configure delivery groups to make applications available to users, see the

topic "Application and desktop groups" in the document Project Avalon ExcaliburTechnology Preview.

Overview and scenario requirementsThe Deployment Guide for Project Avalon Excalibur Technology Preview leads you

through a detailed scenario to a planned outcome. Each of the tasks contained here

build toward that outcome. Once you have concluded this series of exercises, you will


9


10/25

have an environment on which you can explore Excalibur's full features for delivering

applications (XenApp) and desktops (XenDesktop) from the unified architecture.

ScenarioYou are asked to install Project Avalon Excalibur Technology Preview and configure it so

three of five available Windows Server 2008 R2 virtual desktops are accessible through

Citrix Receiver by users with devices running Windows 7. The users should also be able

to access Microsoft Notepad through Receiver.

Scenario RequirementsIn order to complete this scenario, you must meet the following requirements:

Hosting Hypervisor

You will need one of the following hypervisors to serve as host for the master image

and the virtual machines you will generate from it:

w XenServer 6.0.2. Check the Project Avalon Excalibur Technology Preview download

page for the latest information about compatibility with XenServer 6.1, including

details of any XenServer hotfixes.

w VMware vSphere 5.0 (ESXi 5.0 and vCenter 5.0) and VMware vSphere 4.1 Update 1.

No support is provided for vSphere vCenter Linked Mode operation. For vSphere

system requirements, see the VMware documentation.

w System Center Virtual Machine Manager 2012 Rollup 1. For System Center Virtual

Machine Manager system requirements, see the Microsoft documentation.

On the host, you must have a virtual machine running Windows Server 2008 R2. This

virtual machine will be used to create the master image. The virtual machine must be

joined to the same domain as the servers and user device.

Active Directory Domain Controller and three additional servers

You must have permission to create accounts on the Active Directory Domain

Controller. The following servers must be part of the same Active Directory forest:

Note: The names Server 1, Server 2, and Server 3 are provided only for ease of

discussion and have no bearing on the configuration.

All servers should be running Windows Server 2008 R2 Service Pack 1.

w Server 1, containing:

Delivery Controller

Studio

License Server

Microsoft SQL Server Express


10


11/25

w Server 2, containing StoreFront

w Server 3, containing Director

In the Active Directory, create a new user, Evaluate1. This account will be available toyou as a user to test your connection during these tasks. If you already have test users

available, you can substitute those.

User device

The user device should be running Windows 7. Join the user device to the same domain

as the servers and virtual machine on the host. Joining the domain is not a

requirement, but a preference for this scenario.

Domain certificate for StoreFront

Use the Internet Information Services (IIS) Manager console on the Server 2 to create a

server certificate signed by your domain certificate authority.

Note: For details on setting up a domain certificate authority, see http://

technet.microsoft.com/en-us/library/cc731183.aspx.

System RequirementsEnsure that the machines used in the Deployment Guide for Project Avalon Excalibur

Technology Preview tasks are running the supported operating systems.

Note: These system requirements apply to the scenario in Deployment Guide for

Project Avalon Excalibur Technology Preview only. See the separate Project Avalon

Excalibur Technology Preview documentation for the complete requirements for the

technology preview release.

Delivery ControllerSupported operating systems:

w Windows Server 2008 R2, Standard or Enterprise Edition.

Requirements:

w Disk space: 100 MB.

w Microsoft .NET Framework 3.5 SP1.

w Microsoft .NET 4.0.

w Windows PowerShell 2.0 (included with Windows Server 2008 R2).

w Visual C++ 2008 SP1 Redistributable Package. The installer deploys this

automatically. It is also available on the Technology Preview installation media in

the Support\vcredist\2008\2008_SP1 folder.


11
http://technet.microsoft.com/en-us/library/cc731183.aspxhttp://technet.microsoft.com/en-us/library/cc731183.aspx


12/25

Site database

Supported Microsoft SQL Server version:

w SQL Server 2008 R2 SP1 Express Edition. The installer deploys this automatically. It is

also available on the Technology Preview installation media in the Support

\SQLExpress2008R2 folder.

Note: Supported in standalone mode only.

StudioSupported operating system:

w Windows Server 2008 R2

Requirements:


w Microsoft .NET Framework 3.5 SP1.

w Microsoft Management Console 3.0 (included with Windows Server 2008 R2).

w Windows PowerShell 2.0 (included with Windows Server 2008 R2).

Director

Supported operating system:

w Windows Server 2008 R2 SP1, Standard or Enterprise Edition.

Requirements:


w Microsoft .NET Framework 4.0. The installer deploys this automatically. It is also

available on the Technology Preview installation media in the Support\DotNet4 folder.

w Microsoft Internet Information Services (IIS) and ASP.NET 2.0. If these are not

already installed, you are prompted for the Windows Server installation media, then

they are installed for you.

Supported browsers for viewing Director:w Internet Explorer 8 and 9.

w Firefox 14 and 15.

Delivery AgentSupported operating systems for the Delivery Agent for Windows Server Machines (the

installer automatically enables the Remote Desktop Services role):


12


13/25


14/25

w Server 2

StoreFront

w Server 3

Director

In this task, you will install the Server 1 components.

To install components on Server 1

1. Log on to Server 1. Your account must have local administrator privileges and be a

Domain Administrator in the Active Directory.

2. On Server 1, in the installation media, navigate to and start AutoSelect.exe.

The installation wizard starts.

3. On the Welcomepage, click Start.

4. On the Installation Optionspage, click Delivery Controller.

5. Accept the licensing agreement and click Next.The Core Components page appears. All components are selected.

6. Select only the following components and click Next.

Delivery Controller

Studio

License Server

7. On the Databasepage, select Install Microsoft SQL Server Expressand click Next.The Firewall page appears, showing the ports used.

8. Select Automatically open these ports in Windows Firewalland click Next.The Summary page appears, providing a list of components and prerequisites to be

installed.

9. Click Install.The selected components are installed.

10. Click Finish.Studio starts, displaying the Welcome page.

Configure a siteWith the components installed on Server 1, next configure the site. Here, you will:

w License the site.

w Set up the site database.

w Provide information about the host and connection credentials.

You will perform a full deployment, which is the typical deployment.


14


15/25


Domain Administrator in Active Directory.

2. Start Studio.

The Welcome page appears.

3. In the Full Deployarea, click Start.The Full Deployment wizard starts.

4. Click Next.

5. On the Sitepage, do the following:

Field/Label Action

Name Type EvalSite.

Configuration Select Use default database.

Click Next.

6. When asked if you want to create a database because one could not be found,

click OK.

7. On the Licensingpage, select the Select an existing licenseoption and click Addlicense file.

8. In the installation media, browse to the license file, Avalon-Excalibur-TechPreview-

Expires-20130630.lic, select it, click Openand then click Next.

9. On the Host Connectionpage, prepare your virtualization tool by doing thefollowing:

Field/Label Action

Select your host type Select the host type you are using for

these exercises.

Address Type the address of the host server.

Username Type your user name for the host server.

Password Type your password for the host server.

Connection name Type a connection name, such as the

server name, assigned to the host.

Create virtual machines using Accept Studio tools (MachineCreation Services), selected bydefault.

Click Next.

10. On the Networkpage, type Evaluation, select a network, and click Next.


15


16/25

11. On the Storagepage, select your storage device(s), accept Use same storage forvirtual machines and personal vDisks, which is selected by default, and then clickNext.

The Summary page appears.

12. Click Finish.The Full Deployment checklist appears with the second phase, Machine Catalog

highlighted.

Install Server 2 components and create a servercertificate

In this task, use the Internet Information Services (IIS) Manager console on Server 2 to

create a server certificate signed by your domain certificate authority and install

StoreFront on Server 2.

If the Microsoft Internet Information Services (IIS) Manager is not already installed on

Server 2, install it now.

If you do not have a domain certificate authority available, see Appendix: Create a

domain certificate authorityon page 25, to create one for exclusive use with the

Deployment Guide for Project Avalon Excalibur Technology Preview.

Create a server certificate and add site binding

1. From the Startmenu, select Administrative Tools>Internet Information Services(IIS) Manager.The Internet Information Services (IIS) Manager appears.

2. In the Connectionspane, select Server 2.

3. In the Server 2 Homepage in the center pane, in the IISarea, double-click ServerCertificates.

4. Click Create Domain Certificate.The Create Certificate wizard appears.

5. On the Distinguished Name Propertiespage, in Common name, type the fullyqualified domain name for Server 2 as the common name of the certificate,

6. Complete the rest of the form and click Next.7. On the Online Certificate Authoritypage, type your certificate authority name in

the following format: \.

8. In Friendly name, type the same name used as the common name and click Finish.The certificate appears on the Server Certificates page in the center pane.

9. Select the certificate created in Create a server certificate.


16


17/25

10. In the Connectionspane, select Default Web Serverand, from the Actionspane,click Bindings.

11. In the Site Bindingsdialog box, click Add.

12. In the Add Site Binding, do the following:

Field/Label Action

Type Select https

SSL certificate Select the certificate you created.

Click OK.

13. In the Site Bindingsdialog box, click Close.

Install StoreFront






5. Select only StoreFront and click Next.The Summarypage appears, providing a list of components and prerequisites to be

installed.

6. Click Install.StoreFront is installed.

7. Click Finish.The installation wizard closes.

Install Server 3 componentsAfter you have configured the site on Server 1, you are able to install Director on

Server 3.







17


18/25

5. With only Director selected, click Next.The Controller Location page appears.

6. Type the fully qualified domain name of Server 1, where the Delivery Controller is

located.

7. Click Test connectionto ensure a successful connection before proceeding andthen click Next.The Firewall page appears, showing the port used.

8. Select Automatically open these ports on Windows Firewalland click Next.The Summary page appears, providing a list of components and prerequisites to be

installed.

9. Click Install.Director is installed.

10. Click Finish.

The installation wizard closes.

Install the Delivery Agent on the ImageBefore beginning this task, if your host offers management tools, such as XenServer

Tools for XenServer, be sure the latest version is installed on the virtual machine you

will use as a master image.

This process installs the Delivery Agent and Citrix Receiver on the virtual machine you

will use as the master image.

In this topic, use a virtual machine running Microsoft Server 2008 R2 Service Pack 1 on

the host.

Important: Depending on its configuration, you may need to restart the virtual

machine more times than stated in this task. If directed to restart the virtual machine,

do so. Log on and the installation process resumes.

1. From the host, on the virtual machine you will use as the master image, in the

installation media, navigate to and start AutoSelect.exe.



3. On the Installation Optionspage, click Delivery Agent for Windows Server

Machines.4. On the Select Installation Environmentpage, accept the default value, Build a

master image that Excalibur will use to create other machines, and click Next.The Core Components page appears, listing the required Delivery Agent for

Windows Server Machines and the selected Citrix Receiver.

5. Click Next.

6. On the Controller Locationpage, do the following:


18


19/25

Field/Label Action

How do you want to enter Controller

locations?

Accept Manually, the default value.

Delivery Controller address Type the fully qualified domain name

of Server 1.

Delivery Controller address Click Test connectionto ensure asuccessful connection.

Delivery Controller address Click Add.

Click Next.

7. On the Select Configurationpage, accept the default values and click Next.

The Firewall page appears, showing the ports used.8. Select Automatically open these ports in Windows Firewallsand click Next.

The Summary page appears, providing a list of components and prerequisites to be

installed.

9. Click Install.The prerequisites and components are installed.

10. Ensuring Restart the machineis selected, click Finish.The wizard closes and the virtual machine restarts.

11. In preparation for creating the machine catalog, shut down the virtual machine.

Configure the StoreFront serverConfigure StoreFront to enable it to communicate with the Delivery Controller and

database.

1. Log on to Server 2.

2. If the Citrix StoreFront management console is not already open, click Start > AllPrograms > Citrix > Citrix StoreFront.

3. Click Create a new deployment.

4. On the Create New Deploymentpage, accept the default URL and click Create.

5. On the Create Storepage, type EvalStoreand click Next.

6. On the Delivery Controllerspage, click Add.The Add Delivery Controller dialog box appears.

7. In the Add Delivery Controllerdialog box, do the following:

Field/Label Action

Display name Type EvalController.


19


20/25

Field/Label Action

Type Select XenDesktop.

Servers Click Add.

Add Server Type the name or IP address of Server

1 and click OK.

Transport type Select HTTP.

Click OK.

8. Click Next.

9. On the Remote Accesspage, accept the default value, None, and click Create.The store is created.

10. Click Finish.The addresses for users to access the store through Citrix Receiver and through the

Receiver for Web site are available in Citrix StoreFront by clicking Receiver forWeb.

Create Machine CatalogsCollections of desktops or physical computers are managed as a single entity called a

machine catalog. To deliver desktops and applications 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 evaluation:

w Your machines are based on Windows Server Operating System.

w Applications and desktops are delivered from virtual machines.

w Use the account naming scheme of Evaluate###. The ### are placeholders for the

sequential numbering of your virtual machines. Using this format, your virtual

machines will be named Evaluate001, Evaluate002, Evaluate003, and so on.

During this task, you will identify an image from the host to serve as the master image.

Prepare that image with any settings or applications you would like to use in your

evaluation deployment before beginning these steps.

Note: This scenario uses the default Machine Creation Services. If you prefer to use

Citrix Provisioning Services for machine catalog creation, refer to the Project Avalon

Excalibur Technology Preview document at http://www.citrix.com/techpreview/

Projectavalonexcalibur.

When this evaluation is complete, you will have five new desktops generated from the

master image available on the host.


20
http://www.citrix.com/techpreview/projectavalonexcaliburhttp://www.citrix.com/techpreview/projectavalonexcalibur


21/25

Important: Do not begin this task until you have completed Install the Delivery Agent

on the Imageon page 18. The master image should be prepared before it is replicated.

1. Ensure the virtual machine that will be the master image is shut down.


Domain Administrator in the Active Directory.

3. Start Studio.

The Full Deployment checklist appears with the second phase, Machine Catalog,

highlighted.

4. In the Machine Catalogarea, click Start.

5. Click Next.

6. On the Operating system and machine typepage, select Windows ServerOperating Systemand Virtual machines, and then click Next.

7. On the Machine Managementpage, accept Machine Creation Services (MCS),which is selected by default, and then clickNext.

8. On the Master image page, from the list of virtual machines and snapshotsavailable on the host, select the one to serve as the master image and click Next.

9. On the Add and configure machinespage, in the Number of virtual machinesneededfield, type 5and click Next.

10. On the Active Directory Computer Accountspage, do the following:

Field/Label Action

Select an Active Directory account

option

Accept the default Create new ActiveDirectory accountsselection.

Domain Ensure the correct domain is selected.

Locations list Select Default OU.

Account naming scheme Type Evaluate###.

Click Next.

11. On the Summary page, in Machine Catalog name, type EvalCatalogand click

Finish.The Full Deployment checklist appears with the third phase, Delivery Groups,

highlighted. The five virtual machines generated from the master image are created.

12. Check the host to ensure these virtual machines have started. If they have not

started automatically, start them manually before proceeding.


21


22/25

Create Delivery GroupsYou must configure the StoreFront server and create a machine catalog before you

create delivery groups.

Here you will create Delivery Groups for the desktops you created and assign them to a

user group.

When preparing for this evaluation, in Overview and scenario requirementson page 9,

you added a user to the Active Directory. In this task, you assign that user to a Delivery

Group.

Note: If you already have a test group available in Active Directory, you may

substitute that.


2. Start Studio.

The Full Deployment checklist appears with the third phase, Delivery Groups,

highlighted.

3. In the Delivery Groupsarea, click Start.

4. Click Next.

5. On the Create Delivery Grouppage, select the catalog with the following values:

Catalog: EvalCatalog

Description: RDS MCS Random

No. of Available Machines: 5

Note: These values appear on the Create Delivery Group page because you

provided this information while completing the Machine Catalog phase.

6. In Add Machines, type 3and click Next.

Note: The Add machinesvalue is the number of machines the Delivery Group

consumes. This value should be less than or equal to the number of available

machines. Here you are using three of the five machines you created in Create

Machine Catalogson page 20.

7. On the Assign userspage, click Add users.The Select Users or Groups dialog box appears.

8. Add Evaluate1 to the Directory Group and click Next.

9. On the User profile selectionpage, accept the default I will manage this on myownand click Next.

10. Click Next.


22


23/25

The Summary page appears.

11. On the Summarypage, do the following:

Field/Label Action

Display name Type EvalDesktop. This is visible to

users and administrators.

Delivery Group name Type Evaluate Desktop. This is

visible to administrators.

Click Finish.

Add hosted applicationsIn Create Delivery Groupson page 22, you created a delivery group to deliver desktops

to users. In this task, you create a delivery group that provides a hosted application,

Microsoft Notepad, for your users.

To add Notepad to the Delivery Group


2. Start Studio.

3. Click Applicationsand, in the Actionspane, click Create Application.The Create Application wizard appears.

4. On the Delivery Groupspage, click Create new.The Create Delivery Group wizard appears.

5. Click Next.The Create Delivery Group page appears, showing only two available machines.

This is because you used three machines earlier when creating the desktop delivery

group.

6. Select the catalog with the following values:

Catalog: EvalCatalog

Description: RDS MCS Random

No. of Available Machines: 27. In Add Machines, type 1and click Next.

8. On the User profile selectionpage, accept the default I will manage this on myownand click Next.The Summary page appears.

9. In Delivery Group name, type Evaluate Appsand click Finish.

The Create Delivery Group wizard closes and the Create Applications wizard

reappears.


23


24/25

10. On the Delivery Groupspage, click Next.

11. On the Locationpage, for Program executable, click Browse.The Browse for File dialog box appears.

12. Select Local computerand click Browse.

13. Browse for notepad.exe (typically in \Windows\System32\) and click Open.

14. Click Next.

15. On the Userspage, click Add, add Evaluate1, and click Next.

16. On the Shortcutpage, accept the default values and click Next.

17. On the Advancedpage, accept the default values and click Next.

18. On the Namepage, accept the default values and click Next.

19. On the Summarypage, click Finish.

The Create Applications wizard closes and Notepad appears in the Applications list.

Install and configure Citrix ReceiverThis task installs Citrix Receiver onto a user device running Windows 7. Once installed,

configure Receiver to access applications and desktops from StoreFront. With a user

account, you will access those applications and desktops.

1. Log on to a client device using an account with administrator privileges.

2. In the installation media, navigate to \Citrix Receiver and Plug-ins\Windows

\Receiver and start CitrixReceiver.exe.

3. On the Welcome to Citrix Receiver Setuppage, click Install.

4. When asked if you would like to install the USB Redirection Driver, click Install.

5. On the Citrix Receiver Setuppage, type the URL for StoreFront on Server 2 andclick Next.

6. Provide the user credentials for user Evaluate1 and click Connect.

7. Click Add Appsand then All Applications.

8. Click EvalDesktopand Notepadto make them available on the Receiver workspace.

9. Click the EvalDesktop and Notepad icons to start them.

Now that you have completed these tasks and seen how a basic deployment works, use

the Project Avalon Excalibur Technology Preview document to experience all the

components and features available with this technology preview release, such as

Director, Configuration Logging, and delegated administration. You can find the

document at http://www.citrix.com/techpreview/projectavalonexcalibur.


24
http://www.citrix.com/techpreview/projectavalonexcalibur


25/25

Documents

Deployment Guide for Project Avalon Excalibur Tech Preview