How to create machines using MCS with AWS Cloud

book

Article ID: CTX241160

calendar_today

Updated On:

Description

This article lists the steps for Machine Catalog creation process for Citrix VM’s running in AWS.

Instructions

Select the AWS zone where VM needs to be hosted.

Select the Golden image AMI created to use as Master image for MCS on which VDA agent is installed.

Select the AWS VPC where VM needs to be connected
NOTE:- Selected VPC should allow communication between VDA and other Citrix Core components and Active Directory

When selecting dedicated hardware, MCS machines and volume worker will be launched with dedicated tenancy.

Note: For 7.15 LTSR, dedicated host is not supported. Tenancytype PowerShell string that is used to specify a dedicated host which is not recognized in 7.15 LTSR.
The support for dedicated host started from 1811. Refer to https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/1811/whats-new.html
Select the instance type running on AWS required for MCS catalog VM’s.

Note: Refer article for more information about updating AWS instance types with XenDesktop https://support.citrix.com/article/CTX139707 (applicable only to non-citrix cloud DDC’s)

Select the network used for MCS machine.

Select the active directory OU where MCS machines will be placed.
Provide the machine name and catalog name and click Finish.

Once the above configuration is finished below process will start on the AWS side.

Preparation VM will be started and stopped in the selected VPC at the time of MCS setup.

DDC will upload the RPM package present in “path” to the S3 bucket in that region

A XenDesktop Temp VM instance will be launched in default VPC using standard Linux AMI for that region.

XenDesktopTemp runs a user data script, which instructs the VM to downloads the RPM package from S3 which installs and configures the volume worker service.

After this XenDesktopTemp VM OS will shut down and an AMI will be created from the XenDekstopTemp VM.

A snapshot will be created from the XenDesktop temp VM.

Volume Worker AMI creation.

Once the above AMI status changes from pending to available, newly created AMI will be used to launch the Citrix Volume Worker instance and at the same time XenDesktop temp instance will be terminated.