File Name: WVD-Deployment-Recommendations-and-Best-Practices-Webinar-09Oct20.pdf
File Size: 2.69 MB
File Type: Application/pdf
Last Modified: 2 years
Last checked: 7 days ago!
This Document Has Been Certified by a Professional
We recommend downloading this file onto your computer
Azure webinar seriesWindows Virtual DesktopDeploymentRecommendations and BestPractices WelcomeHow do I ask a question?If you have a technical or content-related question, please use the Q&A windowWe will address the questions as they come inCan I view this presentation after the webinar?Yes, this presentation is being recordedA link to the recorded presentation will be sent to the email address you used to register Meet our speaker Christiaan Brinkhoff Principal Program Manager, at Microsoft Brinkhoff_C ln/christiaanbrinkhoff Agenda Architecture Windows Virtual Desktop Architecture Clients Windows Virtual Desktop Azure VMs & Services Customer/Partner-managed Microsoft-managed Customer/Partner-managed VMs Web Access Diagnostics Desktops Apps FIREWALL FIREWALL Gateway Broker Azure & legacy Active Directory Azure SQL DB FSLogix User Profile File Server Windows Virtual Desktop Enterprise Architecture Clients Windows Virtual Desktop Azure VMs & Services Customer/Partner-managed Microsoft-managed Azure subscription 1 Desktops Apps VMs Web Access Diagnostics Azure & legacy Active Directory FIREWALL FIREWALL FSLogix User Profile File Server Gateway Broker Azure subscription 2 Desktops Apps VMs Azure SQL DB FSLogix User Profile File Server Windows Virtual Desktop Service Limits 1. 400 host pools per workspace 2. 10.000 VMs per host pool 3. You can't create more than 50 application groups per singleGeneral Azure AD tenant
4. We recommend that youservice limits don't publish more than 50 applications per application group
5. Azure VMs – session host names prefix cannot exceed 11 characters
1. We recommend to deploy not more than 5,000 VMs per Azure subscription per region
2. To manage enterprise environments with more than 5,000 VMs per AzureAzure ARM limits subscription in the same region, you can create multiple Azure subscriptions in a hub-spoke architecture
3. By default, you can deploy up to 800 instances of most resource types in a resource group. Azure Compute doesn't have this limit
1. Limitations are active on the virtual machines per Azure subscription. You could increase the resources of your individual VMs in your Azure subscription to accommodate more user session without hitting the maximum limit of virtual machines per Azure subscription as described above
Azure ARM limits 2. Availability set 200 session hosts limit work around per deployment 1. Availability set is not connected to the same amount of host pools 3. We suggest you deploy your session hosts in a separate resource group (RG). This leaves you in a better position to remove all your virtual machines at once in case of an update Azure Solutions Center – WVD for the Enterprisedocumentation aka.ms/wvdbestpractices aka.ms/fslogixbestpractices
Assign user identities to your host pool: • After the deployment process is complete, assign individual users or user groups to the default application group. • The default app group …
Here's how to deploy Azure Virtual Desktop and a new Azure AD DS domain using the getting started feature: Sign in to the Azure portal. In the search bar, type Azure Virtual Desktop and select the matching service entry. Select Getting started to open the landing page for the getting started feature, then select Start.
Azure Virtual Desktop host pools support running Windows Server 2012 R2 and later. Running Windows Server-based host VMs on Azure Virtual Desktop requires a Remote Desktop Services (RDS) Licensing Server. This server should be a separate server or remote VM in your environment that you've assigned the Remote Desktop Licensing Server role to.
Running Windows Server-based host VMs on Azure Virtual Desktop requires a Remote Desktop Services (RDS) Licensing Server. This server should be a separate server or remote VM in your environment that you've assigned the Remote Desktop Licensing Server role to. For more information about licensing, see the following articles:
If you're using Azure Virtual Desktop (classic) without Azure Resource Manager objects, see this article. The process for deploying Windows Server-based virtual machines (VMs) on Azure Virtual Desktop is slightly different than the one for VMs running other versions of Windows, such as Windows 10 or Windows 11.