Select Choose a public IP address, Create new, enter a name, and select Ok. Enter a Name, select Public as the Type of load balancer, and select the appropriate Subscription, Resource Group, and Location.In the Azure portal click Browse > Load balancers, and then click Add.Accept the defaults for location and host caching, and then click OK.Ĭreate an external load balancer to access the deployment externally:.You can approximate 5 GB per user you plan to have Enter a size (in GB) that is large enough to hold network shares for the tenant's environment, including user profile disks and certificates.In the Azure portal click Browse > Resource groups, click the resource group for the deployment, and then click the VM created for the RD Connection Broker (for example, Contoso-Cb1).RD Connection Broker, License Server, and File Server:Ĭreate and attach an Azure data disk for the user profile disk (UPD) share: Then return here to attach Azure data disks for the file share and enter an external URL for your deployment.Ĭreate Windows virtual machines to host the RD Connection Broker, RD License Server, and File server.įor our purpose, we used the following naming conventions: If you need to create virtual machines from a custom image, which requires PowerShell, check out Create a Windows VM with Resource Manager and PowerShell. This section outlines the steps necessary to deploy virtual machines for each role based on Windows Server images in the Microsoft Azure Marketplace. For larger deployments, you can install the various role services on individual virtual machines to allow better scaling. For very small deployments, you can reduce VM costs by using AAD App Proxy to eliminate all public endpoints from the deployment and combining all the role services onto a single VM. A third virtual machine host the RD Session Host role service. A second virtual machine will host the RD Gateway and Web Access role services. One virtual machine will host the Remote Desktop (RD) Connection Broker and License Server role services and a file share for the deployment. Use the following steps to create the virtual machines in the tenant's environment that will be used to run the Windows Server 2016 roles, services, and features required for a desktop hosting deployment.įor this example of a basic deployment, the minimum of 3 virtual machines will be created. Applies to: Windows Server 2022, Windows Server 2019, Windows Server 2016
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |