>> I selected 4 monitors with the highest resolution available and set the Video Card to "Auto-Detect settings" instead of using a custom setting
This is an indication that you set the vRAM and monitor config using vSphere and editing the video card properties. This is not how you should configure your displays for View usage.
The View broker has a VRAM / Monitor / Resolution setting in the pool settings. You should set it from there. It will properly set the vmx though vSphere. In the past the vSphere approah has not calculated the VRAM correctly.
When you set it though vSphere the View connection server will clobber that setting. If you look at your logs you should see View reconfiguring the VM again. If the VM never gets powered off you end up in a possible state where...
- VM was configured with miscalculated VRAM
- View changed it but did not power it off for the settings to take affect
First thing to do is....
- Set it correctly though the View pool settings
- Let the changes propogate
- Power off all your VMs
- Power them all back on
This should get you back to a known good state. It might not be the fix but it will be one big step in ensuring its all correct and calculated right.
One thing to note. The View pool setting might be your desired setting. If you did change it via vSphere. You might need to change it in View twice now. Once to get at change to kick off and again to set it back to the desired setting. In this case you do not need to power off and on between the changes. You just need to trigger the change to happen. Only power off once the second one has taken effect on all VMs
WP