Q: Can multiple PvDs be associated to a device/user?
A: There can only be one PvD per Virtual Machine. The PvD is assigned to a Virtual Machine when building the catalog of desktops. The pool type for a PvD catalog is a pooled static, which the desktop is assigned to the user on first use.
Q: Is the PvD a 1-1 mapping per user?
A: Actually, it is a 1:1 mapping to a Virtual Machine in a catalog, which is then assigned to the user on first use. A PvD is attached to a Virtual Machine assigned to the user. The administrator can move a PvD to a new virtual machine in a recovery situation.
Q: If you create a catalog for pooled with PvD, it does not mean that the user is always required to be assigned to that Virtual Machine defeating one of the benefits of a pooled?
A: The base image is still shared and updated across the pool. However, once the user makes an initial connection to a Virtual Machine, the Virtual Machine is kept assigned to the user.
Note: You must connect early in the starting stage long before you know who the user is in order to maximize the application compatibility for services, devices etc.
Q: How does the pooled with personal vDisk catalog affect idle pool?
A: After the user connects, this user is kept assigned to the Virtual Machine.
You must connect early in the starting stage long before you know who the user is in order to maximize the application compatibility for services, devices etc. So for hypervisor resource management, instead of idle pool management, you would use power management to handle Virtual Machine idle workloads.
Q: What Operating Systems are supported for PvD?
A: Windows 7 x86, Windows 7 x64, and Windows 10 up to v1703.
Q: Is PvD only for Desktop Operating Systems or will it also work with Server Operating Systems?
A: It is only supported on Desktop Operating Systems.
Q: What kinds of risks are there for BSODs with PvDs?
A: PvD is architected to be compatible with a wide range of Windows software, including software that loads the drivers. However, drivers that load in phase 0 or software that alters the networking stack of the machine (through the installation of additional miniports or intermediate or protocol drivers) might cause PvD to not operate as expected. You must install these types of software in the base Virtual Machine image.