![]() A restart of the desktop will not change the Video card settings and since this was a manual desktop pool with the Remote Machine Power Policy set to Ensure machines are always powered on, the desktop was never really powered off after being added to the pool. ![]() The cause of my issue because I failed to remember that changing the resolution settings for the desktop pool does not get applied to the virtual desktops unless the desktop is completed Powered Off. … which is still higher than the original virtual machine settings. ![]() When set to the lowest resolution indicated above, the Video card for the virtual machine settings are configured as: Max resolution of any one monitor: 1680x1050 These settings were lower than the minimum required for the lowest monitor resolution that VMware Horizon View provides: I had a feeling it was the video memory but never bothered to check the actual virtual machine’s settings because I assumed they were adjusted and when I finally did, it was set to: This issue threw me off for a bit of time because I’ve come across this issue before as mentioned in one of my previous posts:Ĭonnecting to VMware View 5.1.2 desktop via PCoIP displays a black screen when in full screen You’ve confirmed that you’ve set the monitor resolution for the desktop pool to a high resolution: The session does not cut off and navigating to the VMware Horizon 6 View Administrator shows that the session is in a Connected state: With the newly added desktop listed as Available in the Status column, you attempt to connect to the desktop via PCoIP with your VMware Horizon View client but all you see is a black screen: You’ve deployed a new Windows desktop, created a manual desktop pool and then added the desktop to the pool.
0 Comments
Leave a Reply. |