The table below illustrates which provisioning scenarios are supported. Supported scenariosīefore configuring device identities in Azure AD for your VDI environment, familiarize yourself with the supported scenarios. For more information about device identity, see the article What is a device identity. This article will cover Microsoft's guidance to administrators on support for device identity and VDI. This can be achieved by proper management of stale devices, or you can guarantee device name uniqueness by using some pattern in device naming.
You should follow the guidance documented below when deploying non persistent VDI environments to avoid this situation.įor successful execution of some scenarios, it is important to have unique device names in the directory. It's important to ensure organizations manage stale devices that are created because frequent device registration without having a proper strategy for device lifecycle management.įailure to manage stale devices can lead to pressure increase on your tenant quota usage consumption and potential risk of service interruption, if you run out of tenant quota. These non-persistent desktops are reverted to their original state, in Windows current 1 this change happens when a virtual machine goes through a shutdown/restart/OS reset process and in Windows down-level 2 this change happens when a user signs out. Non-persistent versions use a collection of desktops that users can access on an as needed basis.
These unique desktops can be customized and saved for future use.
Persistent versions use a unique desktop image for each user or a pool of users. There are two primary types of virtual desktops: Deliver end-users mobility and the freedom to access virtual desktops anytime, from anywhere, on any device.Reduce costs through consolidation and centralization of resources.Administrators commonly deploy virtual desktop infrastructure (VDI) platforms hosting Windows operating systems in their organizations.
0 kommentar(er)
