Add an existing RDS deployment to the MyCloudIT platform to utilize its features.
This guide will provide an overview of 'mapping' a Microsoft Remote Desktop Services (RDS) deployment via the MyCloudIT (MCIT) system. Mapping is the process of 'importing' the settings of an Azure based RDS instance into the MCIT system. This mapping process alone (does not include MCIT RDS Agent) will not change your RDS deployment in any way.
This guide covers the following scenarios:
- You want to 'map' (add) an existing Azure based RDS environment that was not created by the MyCloudIT deployment wizard to be able to take advantage of MCIT RDS autoscale.
- For some reason an MCIT RDS deployment has been 'unmapped' and needs to be 'mapped' again.
This guide currently does not cover the following scenarios:
- Mapping a non-MCIT RDS environment to use all MCIT RDS features
- Mapping an RDS environment that is not hosted in Microsoft Azure
- Migrating a classic (v2) MCIT deployment
Acronyms used in this document:
- AD - Active Directory (An instance of an Microsoft Active Directory Domain Services install on a physical server, VM in azure, etc)
- RDS - Remote Desktop Services (Microsoft's suite of services for delivering thin clients with a full desktop or 'remote apps' via the Windows server operating system)
What you will need:
- A Microsoft Azure tenant and subscription where your current RDS deployment is hosted
- A login to the above Azure tenant with owner or contributor access to the subscription
- AD credentials
- About 15 minutes free time
To map an RDS deployment log in to the MyCloudIT portal and if applicable to the correct customer:
- Log in to the MyCloudIT portal and if applicable to the correct customer.
- Navigate to Manage > Deployments and then click on the Map Deployment button.
- Follow the wizard to completion.
Step 1- Basic
- Select "RDS" as the Deployment Type.
- Choose the Resource Group that your existing " RDS virtual network is located in. If not sure, select the resource group your domain controller is located in.
- For the setting Diagnostics Storage Account, select a storage account where virtual machine boot diagnostics will be stored. This storage account must be in the same resource group as selected above. If none show in the list you likely do not have one and need to create one. See Appendix A for an overview on how to do this. Once created quit and reload the mapping wizard.
- Select your Session Host Availability Set. This is the Azure availability set your session hosts virtual machines are attached to. If you have multiple for different collections, select any of them. If you do not have one you will need to create one. See Appendix B for an overview on how to do this. Once created quit and reload the mapping wizard.
- Choose any Name for this particular RDS Deployment mapping. Often the resource group name is used here.
- Type a small description of a Provider for this particular RDS Deployment. If unsure, type "Custom RDS Deployment."
- For the Select Workload options choose how many vCPU each user will consume on average. Do not be concerned if this is not accurate as this can be tuned later. If unsure, select "Normal".
Step 2 - Network Mapping
- For the option Active Directory VNET, choose the virtual network that contains the domain controller virtual machines.
- For the option Deployment VNET, choose the virtual network that contains your RDS server roles (connection broker, session hosts etc).
- For the option Management Subnet, choose the subnet that contains the RDS connection broker virtual machine.
- For the option External Subnet, choose the subnet that contains the RDS web access and RDS gateway virtual machine.
- For the option Workload Subnet, choose the subnet that contains the RDS Session hosts.
Step 3 - Virtual Machine Mapping
- Tick the various server roles that already exist in your RDS deployment that particular virtual machines hold. Possible roles are:
- DC: Domain Controller
- RDCB: Remote Desktop Connection Broker
- RDL: Remote Desktop Licensing
- RDG: Remote Desktop Gateway
- RDWA: Remote Desktop Web Access
- SH: Session Host
- Virtual machines that are mapped in another deployment (except DC's) already are not available for selection.
- Tick the 'View All Resource Groups' if some of your virtual machines are in other resource groups to display them.
- Note when scrolling to the bottom of this page you can select to display more machines by clicking the "Items per page" drop-down and changing to 100.
Step 4 - Authentication
- Input your existing AD domain name in the Domain Name field. An example is office.local. This domain name does not always match your publicly resolvable RD-Gateway DNS name (however some customers these are the same). You can check the domain name via "Active Directory users and computers".
- The Domain Admin Username should be specified as a username only, example: 'myusername'. It should not be specified as email@example.com or office\myusername.
Step 5 - Confirmation
- Review your RDS deployment mapping settings and click on Create to add your deployment to the MyCloudIT platform.
MyCloudIT RDS session host management and autoscaling requires the agent to be installed on the domain controller virtual machine.
- Install the RDS Agent. Most MyCloudIT RDS features require the agent installed on the MSDC virtual machine. For instructions: RDS Agent Installation
A few examples of features that use the agent to perform tasks are:
- Delete Session Host
- RDS session host autoscaling
- Send message to RDS users
Appendix A: Create an Azure Storage Account
- Log in to the Azure portal and go to create new storage account. Another way to do this is via the following link: https://portal.azure.com/#create/Microsoft.StorageAccount
- Select the domain controller resource group and fill out the settings. For the Name create a unique name such as companyname123. Select standard for 'performance'. Select LRS for 'Redundancy'.
- All other settings should be fine as default. Create the storage account.
Appendix B: Create an Azure Availability Set
- Log in to the Azure portal and go to create new availability set. Another way to do this is via the following link: https://portal.azure.com/#create/Microsoft.AvailabilitySet
- Select the domain controller resource group and fill out the settings. For the Name create a name such as RDSH-SET. Make sure the 'Region' is the same location as your session hosts.
- All other settings should be fine as default. Create the availability set.