WVD is a scalable and cost-effective alternative to individual cloud virtual machines (VMs) for deploying software to many users in Azure. Each WVD host pool consists of multiple session hosts (VMs) that remain always-on, by default.
When users connect to WVD, their Windows user data is not automatically synchronized between session hosts. Some of this data is required by Harmony Enterprise to function correctly. This includes user-created templates and settings that are normally saved to a user’s computer, rather than in a specific Harmony Enterprise database. A solution to this problem is to use a tool called FSLogix, which can persist user-profile data in another location, such as a file share.
Note: To get a good high-level technical understanding of WVD, FSLogix, and how they fit together, see Windows 10 Enterprise multi-session FAQs.
For Microsoft instructions on WVD setup, see the following:
- Create a VM from a managed image
- Software preparation and installation
- Create FSLogix Profile Container
Microsoft is deploying rapid changes to WVD and sometimes the official documentation is out of date compared to the currently available functionality. Third-party tutorials may be valuable to assist you in completing the WVD setup process.
Creating your image
There are certain configuration steps that need to be applied to all WVD session hosts, so we recommend that you do these things at image-creation time, so that each user does not have to do configuration themselves.
- After installing Harmony Enterprise on your master image VM, launch Harmony Enterprise and set the license server to the private IP address of the dedicated license server for the Azure VM you created earlier.
- Set up a system DSN for each Harmony Enterprise database that your Harmony Enterprise users need to connect to. For more information, see connecting using the Data Source Manager.
Note: All WVD users use the license server and system DSNs that you configure in this image, so if you want to change these items, you need to create a new image version with your changes, and deploy it to new session hosts.