Unlike Windows 7/10/11, where there is no need of any additional configuration in terms of licensing, Windows Servers in AVD requires RDS Licensing Server in the environment. (Note: Timing, text and the duration of the message may vary depending on the Server OS edition). However, if you try connecting using RDP client with a local administrator user, a warning message below will appear in the system tray. Host Pool deployment wizard will install AVD Agent and perform Active Directory Join of the VMs in the pool.Īssigned Users/Groups will be able to connect fine. Below two screen-capture demonstrates the only difference being use of Windows Server (in this case 2012 R2 version) customized "gold image".
All existing methods such as Azure Portal, ARM Templates, other automation will work fine. Implementing Windows Server based AVD Hosts is no different than deploying it with Windows 10/11 multi-session. IT Pro, System Administrators, Cloud Administrators, VDI/EUC Administrators, Cloud Architects, IT Architects.įamiliarity with Azure and AVD VDI Technology Solution, Deployment. Note : AVD Host pool can run Windows Server 2012 R2 and above editions however not all design choices would work.įor example, Azure AD Join is only supported Windows 10 single-session or multi-session, version 2004 or later. While Azure and on-premises technologies AVD leverages such as Identity, Networking will need the similar approach but there is a difference worth considering mainly around Remote Desktop licensing. (App compatibility, licensing, cloud transformation to name a few). Goal of this blogpost is to provide some guidance around deploying Windows Server OS editions as Azure Virtual Desktop (AVD) Host Pool VMs.Ĭommon use case of AVD is to run Windows 10/11 multi-session (Pooled Scenarios) or Windows 10/11 Enterprise (Personal Scenarios) OS versions however some scenarios may require running Windows Server edition as Host OS.
0 kommentar(er)
