(RDS) Tip of the Day: Azure Resource Manager Templates for RDS Deployment


Today’s Tip…

Create Remote Desktop Session Collection deployment – (Creates AD)

  • The template will deploy DC, join all virtual machines (VMs) to the domain and configure RDS roles in the deployment.
  • This template deploys the following resources:
    • storage account;
    • vnet, public IP, load balancer;
    • domain controller VM;
    • RD Gateway/RD Web Access VM;
    • RD Connection Broker/RD Licensing Server VM;
    • a number of RD Session hosts (number defined by ‘numberOfRdshInstances’ parameter)

Create Remote Desktop Session Collection deployment (uses existing AD)

  • The template will use existing DC, join all VMs to the domain and configure RDS roles in the deployment.
  • This template deploys the following resources:
    • storage account;
    • RD Gateway/RD Web Access VM;
    • RD Connection Broker/RD Licensing Server VM;
    • a number of RD Session hosts (number defined by ‘numberOfRdshInstances’ parameter)

Create Remote Desktop deployment using custom image for RDSH machines

  • The template will use existing DC, join all VMs to the domain and configure RDS roles in the deployment.
  • This template deploys the following resources:
    • storage account;
    • RD Gateway/RD Web Access VM;
    • RD Connection Broker/RD Licensing Server VM;
    • a number of RD Session hosts using custom image (number defined by ‘numberOfRdshInstances’ parameter)

Provide High Availability to RDG and RDWA Server on top of Remote Desktop Session Collection deployment

  • This template deploys the following resources:
    • a number of RD Gateway/RD Web Access VM (number defined by ‘numberOfWebGwInstances’ parameter)
  • The template will
    • join all new VM’s to the domain.
    • Deploy RDS roles in the deployment.
    • Join new VM’s to the existing web and Gateway farm of basic RDS deployment.
    • Post configurations for web/Gateway VM’s such as defining the Machine keys for IIS modules.
  • Prerequisites: RDS-deployment-HA is an extension to the Basic-RDS-Deployment and it is mandatory to deploy any one of the template as prerequisite
  • This template expects the same names of resources from RDS deployment, if resource names are changed in your deployment then please edit the parameters and resources accordingly, example of such resources are below:
    • StorageAccountName: Resource must be exact same to existing RDS deployment.
    • publicIpRef : Resource must be exact same to existing RDS deployment.
    • availabilitySets : Resource must be exact same to existing RDS deployment.
    • Load-balancer : Load balancer name, Backend pool, LB-rules, Nat-Rule and NIC.
    • VM’s – VM name classification which is using copy index function.
    • NIC – NIC naming convention.

References:

Comments (0)

Skip to main content