Hello all,
I was hoping someone might be able to offer some guidance regarding a particular limitation we've been facing. As most of you know, the default options within the View Client are: All Monitors, Fullscreen, Window-Large, Window-Small, or Custom (which is limited to the max resolution of one monitor on the client system). Our issue is that we wish to use only two of the monitors on the client system when there are three or four monitors connected in total. Our VDI infrastructure is being used for development within our segregated "test" domains, and they need at least one monitor to be usable for production work (email, IM, RDP to prod servers, etc.). Below are the options we've already tried, which all leave a lot to be desired still. All tests below are done using a Windows 7 client desktop with three 23" monitors. Connected to a Windows 7 VDI running View Agent 7.0.2 and using View Client version 4.2.0.
1. Setting View Client to open virtual session using "Window-Large" display setting, and then manually stretching the window across two of the three/four monitors on the client system. At best, this is the only solution that actually allows us to use a subset of monitors and the rest still be available for other processes. However, the VDI still sees this as one giant display, meaning all the snap-features and window-resizing within Windows is virtually unusable. Also have to do this every time the session is closed and reopened.
2. Same as above, but using something like DisplayFusion or Dell Display Manager to artificially split the display. Same problem occurs here, as every time you disconnect the display is reset back to the default "Window-Large" size and wipes all settings for DF or DDM.
3. Limiting display settings within View Admin to allow a max of two monitors, and using the "All Monitors" display option within the View Client. Even with the pool set to a max of two monitors, selecting the "All Monitors" option within the display options of the View Client causes any monitors past the two monitor limit on the pool to just go completely black. For our usage case, this isn't any better than all monitors being consumed by the VDI.
If anyone has any other solutions they would be greatly appreciated, as this has been a large contingency point for our 600+ developers.
