90 likes | 121 Views
Microsoft has rebranded its Windows Virtual Desktop as Azure Virtual Desktop, expanding its vision to become a cloud-based virtual desktop infrastructure (VDI) for nearly any use case. Microsoft has added new features to its core Azure Virtual Desktop platform with this rebranding, such as a new application-streaming pricing option and enhanced support for Azure Active Directory (AD)
E N D
Introduction to Azure Virtual Desktop vs Windows Virtual Desktop
What Is Windows Virtual Desktop? windows virtual desktop is Microsoft's desktop as a service (daas) offering. virtual machines (vms) for multiple users and desktops get hosted on the azure platform in a windows virtual desktop environment. organizations can use windows virtual desktop service to deliver virtual applications and desktops to their employees via azure’s cloud infrastructure. this means that endpoints that access the applications and desktops do not directly run the os, applications, desktops, and user settings. currently, users can access the windows virtual desktop resources via multiple Oss, including windows, macOS, android, iOS, and any platform with an html5-compatible browser.
Windows Virtual Desktop has various components • host pools. a host pool is a set of one or more identical hosts or vms within the azure environment. it administrators use host pools to assign virtual applications and desktops to users. • application groups. these are collections of applications available in a particular session host. it administrators can use application groups to provide end-user access to specific applications. • tenants. a Windows Virtual Desktop tenant is a collection of one or more host pools. it administrators can use a tenant to create host pools, build application groups, assign users to their host pools and make connections via an interface. • tenant groups. tenant groups allow it administrators to organize users, host pools, and application groups. an enterprise can use tenant groups if multiple tenants require deployment, such as hosting partners or cloud service providers (csps). • end users. these are consumers to whom the organization wishes to deliver virtual applications and desktops. every user is assigned to a particular host pool with a defined azure ad in a windows virtual desktop environment.
What Are Some New Features in Azure Virtual Desktop? • improved support for azure ad. the newly unveiled azure virtual desktop allows users to join vms directly to azure ad and connect to the virtual machines from any endpoint with basic credentials. this eliminates the need for a domain controller. azure ad now integrates many features, including single sign-on (sso) and new credential types such as fast identity online (fido 2). • management of windows 10 enterprise multi-session vms with endpoint manager. it administrators can now enroll windows 10 enterprise multi-session vms in endpoint manager. this simplifies the management of vms via a centralized console for both physical and Virtual Cloud Desktops. • streamlined onboard experience. it administrators can now deploy applications and desktops with only a few clicks because of a streamlined onboard experience in the azure portal. the new portal validates requirements and jumpstarts automated deployment in minutes.
Components of an Azure Virtual Desktop Environment • the components that make up the azure virtual desktop environment are interconnected to form the setup: • there can only be one or more tenant groups for each azure tenant. • tenant groups are made up of host pools, which are Azure Virtual Machine collections. wvd agents are used to registering the azure vms as hosts for windows vms. • a host pool can be made up of separate virtual machines allocated to specific users or pooled to give access to users who have authorized an app group within the host pool.
App groupings are logical divisions of desktop apps (full desktop virtualizations) and remote apps (selective application deployments). For improved app and desktop accessibility, these application groupings are logically categorized and coupled with workspaces. • Users can join several app groups, which can be desktop app groups, RemoteApp groups, or mixes of the two, but they can only start one form of app group at a time. • Two load-balancing strategies exist at the host pool level to guarantee that user sessions are allocated appropriately among virtual machines. User sessions are fairly allocated in a host pool while using the breadth-first load balancing strategy. Before diverting a connection to any new session, depth-first load balancing tired out the session limit.