Deploy Xenapp and Xendesktop 7 5 With Amazon VPC
Deploy Xenapp and Xendesktop 7 5 With Amazon VPC
Version: 5.0
Known issues
Amazon Web Services depreciated the ECU terminology and no longer lists this value for new instance
types. However, Studio lists some new instance types for Memory Optimized and General purpose that
display 2.5 in the ECU column. The 2.5 actually refers to the clock speed in GHZ for these instance types
and not ECU. Refer to the Amazon Web Services website https://aws.amazon.com/ for details on each
instance type and its technical specification. [#496972]
Requirements
To deploy a XenApp or XenDesktop 7.5 or 7.6 Site in an Amazon VPC, ensure that you complete the
prerequisites and link AWS Marketplace AMIs to your account as follows.
Prerequisites
Make sure you perform the following before you begin:
Plan to take one day for the first-time implementation of the deployment.
Have an AWS environment set up and running, with an active AWS account and preferably an AWS
Identity and Access Management user account that can be used for this specific deployment.
For this proof of concept (POC) deployment, the IAM user must have administrative rights to your
AWS environment. For information about the rights you need, see the XenApp and XenDesktop
topic Prepare to Install.
Subscribe with your AWS account to the NetScaler VPX AMI located in AWS Marketplace.
1. From the AWS console, select Find software on AWS MarketPlace under the additional information
section on the right side of the console.
2. Search for NetScaler VPX Platinum Edition – 10 Mbps, and select version 10.1-123.9.
1. On the CloudFormation Stack console tab, use the drop-down box in the upper-right-hand
corner to select the region in which you want to build the environment.
6. After specifying the required parameters, select I acknowledge that this template may create
IAM resources check box, and click Continue.
Note: It is important to ensure that the availability zone, your access credentials and keypair are correct. If
not, go back and correct the error; otherwise, the template creation will fail. Once correct, click Continue
to start the stack build process.
It displays two CloudFormation stacks: one for the EC2 Infrastructure and one for the NetScaler VPX.
EIP
Corporate
Office
(80,443,1494,2598,3389,53,5986,8080,27000)
Workers
(80, 443, 3389)
AD DC
Public SG
Eth 0/1
EIP
Private SG
XenApp /
Eth 0/0 XenDesktop
NetScaler NSVPX-1 Delivery Controller Workers
Eth 0/0 (.175) SQL Server
Eth 0/1 (.100) StoreFront
XD7DDC
EIP
NAT SG
(22)
Remote
& Mobile
Users NAT iNet VDAMaster
Gateway
1. From the EC2 instances management console, select Download Desktop File to connect to the
Bastion host using RDP.
2. Log in with the domain administrator credentials you provided during the CloudFormation Stack
creation.
3. From the Bastion host, RDP to the Delivery Controller (the controller is xd7ddc.xencloud.net
when using the default domain name), and log in as the domain administrator using again the
DomainAdminUser and DomainAdminPassword provided as parameters during the stack
creation event.
Note: The credentials file for the root AWS account, retrieved from
https://console.aws.amazon.com/iam/home?#security_credential is not in the same format for
credentials files downloaded for standard AWS users. Because of this, Studio cannot use the file to
populate the API and secret key fields when creating a connection. Ensure that you are using IAM
credentials files when administering Studio.
5. Install XenApp or XenDesktop as required for your environment.
a. Select the Delivery Controller.
b. Select All Core Components.
c. Follow the wizard instructions to complete the Delivery Controller Installation.
6. Start Citrix Studio, and follow the wizard to create the site. Note that the CloudFormation
template has preinstalled SQL Server 2012 on the Delivery Controller.
10. Select the AWS region, your VPC, and the desired availability zone for this connection.
12. Skip the configuration for the App-V Publishing option to complete the Site setup. You can add
this feature later.
Once you have configured the Delivery Controller, you must configure a master image by configuring a
master VDA machine.
1. From the Bastion host, RDP to the VDA Master (you can find the IP address from the EC2
console), and log in as the domain administrator, using again the DomainAdminUser and
DomainAdminPassword provided as parameters during the stack creation event.
2. The XenApp and XenDesktop 7.5 and 7.6 product media is already mounted. Run
AutoSelect.exe to start the installation.
11. Supply the FQDN of the Delivery Controller you configured earlier in this process.
14. After the machine reboots, log in to the Master VDA. The XenApp and XenDesktop product media is
no longer mounted (it searches for the media), and the installation does not continue.
16. When the media is mounted, select the Virtual Delivery Agent for Windows installation, which
automatically continues from where it left off.
17. Restart the machine.
Page 25 © 2014 Citrix Systems, Inc. All rights reserved.
18. After the VDA installation completes, install applications that will be published or available on the
users' desktops on the master VDA.
Important: By default, Delete on Termination is selected. Do not change this setting. The product works
on the assumption that root disk volumes are deleted automatically by Amazon. Unchecking this box can
cause the deployment to leak volumes in EBS storage.
Depending on the size of the instance volume, image creation can take a long time. You must wait until
the image is fully created before you can see it in Studio.
When the AMI creation process completes, set up machines in Studio using Master VDA AMI.
2. Select Server OS. If your configuration has Server VDI available on a Desktop OS, you can
alternatively choose the Desktop OS option.
5. Select the required security groups. In this example, you must select the DomainMemberSG
Security as well as the private security group PrivateSecurityGroup.
You can also indicate that dedicated hardware is required to host your instances. Use Shared
Hardware is the default.
9. Enter a name, and click Finish. Note that the process of copying the master image can take a long
time to complete. It may take 30 to 40 minutes, or more if there are a lot of machines in the catalog.
1. In Studio, select the Delivery group node and click Create Delivery Group.
2. Click Add Machines, select a machine catalog for this Delivery Group, and then enter the number
of machines the group consumes from the machine catalog.
3. On the Users page, click Add users to add the users or user groups that can access the desktops
or applications. You can select user groups by browsing or entering a list of Active Directory users
and groups each separated by a semicolon. For Desktop OS Delivery Groups, you can import user
data from a file after you create the group.
4. On the Delivery Type page, select what the desktops deliver to users:
Applications only
Desktops only
Applications and desktops
5. On the StoreFront page, select StoreFront URLs to be pushed to Citrix Receiver so that Receiver
can connect to a StoreFront without user intervention. Note that this setting is for Receiver
running on VDAs.
6. On the Scopes page, define which administrators can access the Delivery Group.
7. On the Summary page, check all details and then enter a display name that users and
administrators see and a descriptive Delivery Group name that only administrators see.
Set up StoreFront
1. Run the StoreFront administration console on the Delivery Controller and enable remote access.
3. Add the Secure Ticket Authority (STA), which is the Delivery Controller.
The following example shows a desktop launched using an AWS g2.2xlarge instance (template), which
allows for HDX 3D Pro support:
Exporting your existing Windows images or template from your on-premises virtualization
environment using the environment’s virtualization tools.
Importing the image or template to Amazon EC2 using the Amazon EC2 command line or API
tools.
See the Importing EC2 Instances in the AWS EC2 User guide for detailed instructions on importing
existing VMs.
Once you import your template, and create an instance from it as described in Importing EC2 Instances,
you can turn it in to an AMI as with any other instance.
EIP
Corporate
Office
(80,443,1494,2598,3389,53,5986,8080,27000)
Workers
(80, 443, 3389)
AD DC
Public SG
Eth 0/1
EIP
Private SG
XenApp /
Eth 0/0 XenDesktop
NetScaler NSVPX-1 Delivery Controller Workers
Eth 0/0 (.175) SQL Server
Eth 0/1 (.100) StoreFront
XD7DDC
EIP
NAT SG
(22)
Remote
& Mobile
Users NAT iNet VDAMaster
Gateway
This section lists network specifics used in this manual set up example.
Inbound Outbound
Inbound Outbound
80 (HTTP) 0.0.0.0/0
Inbound Outbound
80 (HTTP) publicSG
135 publicSG
389 publicSG
49152 -
65535 publicSG
Delivery Microsoft Windows Server 2012 with SQL ami-e743478e private 10.0.1.15
Controller ami-a1b9bcc8
Microsoft Windows Server 2008 R2 with
SQL
VIP 10.0.0.176
Private
NSIP 10.0.1.100
SNIP 10.0.1.102
Creating a Site involves creating the Virtual Private Cloud (VPC) network infrastructure in your Amazon
Web Services account.
1. Log in to your AWS account, and navigate to the VPC tab. Click Get Started Creating your VPC.
The security groups in Amazon VPC provide communication between the Internet and public network,
and the public and private network. The security groups contain ACLs and are the basis of the firewalls
shown in the network diagram.
1. On the VPC tab, select Security Groups > Create Security Group.
2. Add ACL rules for inbound and outbound traffic. Select:
a. Create a new rule
b. Port number
c. Source IP address
Note: A source IP address of 0.0.0.0/0 indicates that you want to allow all inbound or outbound traffic.
Inbound Outbound
NAT instance
Go to the EC2/Instances page, and locate the instance. Right-click the instance, and change the security
group to NATSG.
1. On the VPC tab, select Security Groups > Create Security Group.
Note: Entering a Source IP address of 0.0.0.0/0 allows all inbound or outbound traffic.
80 (HTTP) 0.0.0.0/0
1. On the VPC tab, select Security Groups > Create Security Group.
Note: Entering a Source IP address of 0.0.0.0/0 allows all inbound or outbound traffic. Create ACL rules to
match the table.
Inbound Outbound
80 (HTTP) publicSG
135 publicSG
389 publicSG
49152 -
65535 publicSG
DHCP options
Create a DHCP options set
There is a domain controller running DNS in the private network. The controller enables Citrix servers to
authenticate and communicate with each other. To implement this communication:
Create a new DHCP options set that contains your DNS server IP address.
Add an open-source DNS server on the Internet in case a server needs to access the Internet.
1. Navigate to the VPC tab, and select DHCP Options Set > Create DHCP Options Set.
4. Assign a friendly name to the AMI to make it easily identifiable in the Amazon console.
Launch the remaining XenApp or XenDesktop AMIs using the parameters in the following table. Ensure
that you launch them into the correct network (private or public as applicable), and assign an IP address
and the elastic IP addresses.
Note: The Amazon VPC wizard automatically creates the NAT server, so you should not need this AMI.
NetScaler VPX
NetScaler VPX Platinum Edition -
10 Mbps ami-c995aaa0 public/private 10.0.1.100
7. Assign an elastic IP address to the NetScaler public ENI – associated to the VIP (10.0.0.176).