- #Virtual desktop manager registration
- #Virtual desktop manager windows 10
- #Virtual desktop manager windows 8.1
Older operating systems (pre-Windows 10 and pre-Server 2016) using credential roaming, user profile roaming, or mandatory profiles are NOT supported.
#Virtual desktop manager windows 10
Latest release of Windows 10 is recommended.
#Virtual desktop manager windows 8.1
Client devices as old as Windows 8.1 are supported. Single forest syncing of identity data to multiple Azure AD tenants is NOT supported. NOTE: A single forest should sync identities to only one Azure tenant. #Virtual desktop manager registration
Server Core does NOT support any type of device registration. Server 2016 or Server 2019 are recommended. Domain Controller should be at least Windows Server 2008 R2. Credentials of a global administrator for the Azure AD tenant and an Enterprise Administrator account for the on-prem forest are required. When you configure your devices to Hybrid join Azure AD, these devices will be visible and manageable in both your on-premises AD as well in Azure AD. One of the requirements for managing your Windows 10 WVD environment with Endpoint Manager is the use of Hybrid Azure AD join. Microsoft recommends Endpoint Configuration Manager (Current Branch, 1906/newer releases) when managing deployed multi-session WVDs. Only support hybrid Azure AD joined configurations. Will not activate against on-premises Key Management Services (KMS). Cannot run in on-premises production environments. Multi-session varieties of Windows 10 also: Windows 10 Enterprise multi-session is a new Remote Desktop Session Host that allows multiple concurrent interactive sessions. NOTE: RemoteApp, RADC or the Remote Desktop Connection (MSTSC) client are NOT supported NOTE: Intune treats WVD personal VMs the same as physical Win10 Enterprise desktops. Enrolled in Intune using either AD group policy to auto-enroll hybrid-AAD joined devices, ECM co-management or user self-enrollment via Azure AD join. Configured as personal remote desktops in Azure. 
NOTE: WVDs do not support Azure AD guest user accounts UPN to subscript to WVD must exist in the AD domain the VM is joined.Users must be sourced from same AD connected to AAD.
Parented to same AAD tenant and connected to the Windows Server AD or Azure AD DS instance
Window 10 Enterprise (including multi-session). The following requirements are needed to setup and connect WVDs and apps. Technologies such as Intuneand Endpoint Configuration Manager (used manage enterprise devices) are becoming more robust, and these tools can also now be used for virtual devices such as those used by Microsoft’s Windows Virtual Desktop service in Azure.Īs a desktop and app virtualization service in Azure, Windows Virtual Desktop allows administrators to set up a scalable, multi-session Windows 10 deployments using virtualized desktops as well as virtualized Microsoft 365 and other apps in multi-user virtual scenarios.ĭeploying and managing WVDs in Azure can also be accomplished with multiple options for management of host pools, app groups, user assignment and resource publishing.
0 kommentar(er)
