More info on creating an optimized windows image can be found in this techzone link.  

https://techzone.vmware.com/creating-optimized-windows-image-vmware-horizon-virtual-desktop

The VMware OS Optimization Tool fling helps optimize Windows 7/8/10 and Windows Server 2008 R2/2012/2016 systems for use with Horizon 7. The optimization tool includes customizable templates to enable or disable Windows system services and features, according to VMware recommendations and best practices, across multiple systems. Because most Windows system services are enabled by default, the optimization tool can be used to easily disable unnecessary services and features to improve performance. This is the link to the VMware OS Optimization tool. This is beyond the scope of this lab. Go to the VMware OS Optimization Tool page to download and start it for your environment.

https://labs.vmware.com/flings/vmware-os-optimization-tool

Optimizing the master image is well worth the time and effort involved. Savings are returned on a variety of fronts.

• initial deployment Time Savings
• User Logon Time Savings
• Host Memory Savings
• Host CPU Savings
• Storage and IOPS Savings

Considerations you must take into account when creating a Windows system image are much different if you plan to deploy virtual desktops rather than physical desktops:

• Physical desktops - Resource usage on a physical machine impacts only the user who is using that machine. The operating system on a physical machine determines whether or not resources are available. One-time actions impact the user only the first time they are performed because the machine is never refreshed. For example, a user typically gets a new user profile the first time they log on, and they continue to use that same profile with all subsequent logons.
• Virtual desktops - In contrast, in a virtual environment, the guest operating system behaves as if it has exclusive access to the CPU cores, but in reality the cores are shared between 2 to 8 virtual machines. When using non-persistent VMs or user profiles, the actions that are intended to run only once could run every time a user logs on.

Therefore, with virtual desktops, one-time system actions must be configured in the base image, and one-time user actions must be configured in the default (or mandatory) user profile. In addition, to reach a higher consolidation ratio, increasing the number of VMs hosted on a single VMware vSphere host, VMware recommends turning off features that are not needed.