One of the issues that we have found is that due to the changes that have been made in both vsphere and windows that volumes appear as hotplug devices in Computer Manager, also this can affect how disks are brought online by windows.
To resolve this add the following setting to the vmx file
devices.hotplug = "false"
Also within windows make sure your diskpart san policy is set to always on.
(This will then show your policy)
(and your done)
Interesting one today, installing horizon composer on a windows 2016 virtual machine. All the usual checks done for the ODBC settings etc, however constantly getting a rollback error message. After digging around in the logs i spotted error 1603., which after a quick check though the VMware knowledge base i found the following article https://kb.vmware.com/s/article/58887?lang=en_US Seems its a well know issue with thankfully a quick fix.
Power Down the virtual machine in question
Edit the virtual machine and disable Secure boot
Once installed shut down the virtual machine again
Re-enable secure boot.
So far its working for me.
Had an interesting one the other day, deploying windows 2016 servers for a customer, setting one up as a jump server for support staff i naturally wanted to check that we could access the vSphere web console correctly using both flash and html variants.
By reading this post you can imagine that it didn’t work due to our old friend flash. However there is an easy fix
dism /online /add-package /packagepath:"C:\Windows\servicing\Packages\Adobe-Flash-For-Windows-Package~31bf3856ad364e35~amd64~~10.0.14393.0.mum"
Running this will get the respective flash component installed to enable you to use the web client again. More details are available at Technet Article