With all this information in focus, how does a system administrator create the image for Windows 10 that will run in this VDI configuration? ProjectVRC (http://www.projectvrc.com/) was a good source of information for a number of years. They published whitepaper studies of performance metrics of VDI in a variety of workloads and found web-based ads in browsers were a major cause of CPU consumption in VDI implementations and some other great nuggets of information. They seem to be silent lately but it's probably worth bookmarking them just in case.
Brian Madden (http://www.brianmadden.com/) is a good source of knowledge as well, with an excellent repository. Brain himself has left IT but the site still seems to be going strong. You can find a great variety of articles on VDI here.
Generally in Windows 7 and 8.x, administrators used vendor-provided scripts to configure the Windows image to make it ready to be a virtual machine. With Windows 10, that can still be the case but Microsoft is starting to (some would say finally) understand that VDI and remote desktop usage is a thing. Microsoft has partnered with Citrix to provide desktops for Windows 10 in Azure, and AWS has a similar offering as well. With these types of configurations becoming more common, we can expect a streamlined guidance or profile from Microsoft on VDI configuration to be sure. It may even be that a new version of Windows 10 comes out that is cloud ready. It wouldn't surprise me.
Perhaps one of the often overlooked considerations for a VDI deployment is the ability to collect diagnostic data from the virtual guests. How are you going to collect a full memory dump if needed? Are you doing error reporting of user-mode applications? What about the performance impact of applications and monitoring software such as data loss prevention suites? These are things that ideally are thought through prior to a call with a Microsoft or other support engineer in an emergency.
In conclusion, the key point for a VDI solution is to spend the money to do it right. There are few magical registry tweaks that can fix a slow backend storage solution for your VDI users.