Create a Citrix MCS Catalog from AWS EC2 Machine
Published: 2023-11-27 15:46:49

In this blog, we will discuss about the steps involved in creating a Citrix MCS catalog from an AWS EC2 machine.
The main difference in creating an AWS MCS catalog is that we need to create an AMI and point the AMI as the master image during the creation process. In the other technologies, we are pointing either directly to the VM(whereas Citrix will create a snapshot) or to the snapshot of the master image.

To begin the process, create an EC2 VM and deploy the VDA agent to support as a master image. I am skipping that section as it is generic steps to be followed for any master image creation process. Once the VDA agent is deployed, stop the EC2 VM and create an AMI.
To create an AMI, right click on the master image-->Actions-->Image and templates-->Create image

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/gap4xkx4ddgllljmhbfg.png)
In the create image wizard, provide the name, description, tags and click on "create image".

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/79zb1ld0n8aryqimux4g.png)

Once the AMI is created and showing in the available state, navigate to Citrix and initiate the machine catalog wizard.
In the wizard, under machine management, select the radio button next to "machines that are power managed". In the deploy machines using option, select Citrix machine creation services and select the resources from the drop down menu.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ohjz8a9gof7mc1numgnd.png)

Select the desktop experience as per your requirement and click next.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/egbbq03oqxdocgslae9x.png)
In the machine template tab, select the AMI from the list and click Done.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/dbwumdfub8pmpoecmqwd.png)

Select the AWS master image EC2 VM as the machine profile for inheriting the tags. Select the functional level of VDA and click Next.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/khf4hahxmu11vl786bq4.png)
In the virtual machines tab, select the number of machines to be created and the VM size.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/y4smdu5u59k100yrgifx.png)
In the security tab, provide the security groups created in the AWS. You can select a maximum of 5 security groups for one catalog.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/v0znrkka608kini89cbm.png)
If the customer is using dedicated host/instances for complying to Microsoft license terms, then this is the place where they can select the hosting type.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/bf7t6h519r6cp7ewdd13.png)
In the networking tab, select the right VPC and click next.
In the machine identities tab, select the Identity type(whether the machines need to be AD joined/AAd joined) and provide the OU details and machine naming standard and click Next

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8eibdnjmzvzk7jgpndal.png)
Provide the domain credentials, if opted for AD joined machines. Select the Scope if any and click Next.
Review the settings, provide a catalog name and click finish.
During the machine catalog creation process, AWS will create a preparatory VM, apply tags and then create the actual XenApp machine. The Cloud trial logs clearly shows if there is a failure in the creation process.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/1y3seqg4tisxa1jznaoe.png)

You can see that the preparatory VM is terminated.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/u2nd734bvp8vff3uy10p.png)
Finally the XenApp machine is created in the Citrix console.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/6z4jyjhji74nbcj60euz.png)