When setting up new Zero clients, it has been noticed that when you change the primary display in the zero client user settings under display topology, it changes the primary display for the menus before you login to View but the primary monitor reverts back to the Zero client after logging in (start bar will always be on the Zero client screen).
The only workaround at this point is to use the zero client as the primary monitor.
According to the following this is a known issue: http://techsupport.teradici.com/ics/support/KBAnswer.asp?questionID=1090&hitOffset=1285+1247+1018&docID=952
"The OSD Display Topology's Primary Port setting is ignored while in session with a VM."
We are seeing this issue on all of our Samsung Zero clients (Tera1 & Tera2).
OS: Windows 7 x64
View 5.1.2
Zero Clients: Samsung NC241-T (4.0.3 Firmware), Samsung NC190-T (4.0.2 Firmware), and Samsung NC240 (4.0.2 Firmware)
I opened up ticket #15134-12615 with Teradici and they said this:
"We've been investigating this issue and are working on determining if this will be included in an upcoming View release. It may be possible to address this in a workaround in zero client firmware. However, if we can confirm a fix is coming in a future release of View, this is a preferable approach as there is a possibility a firmware workaround may cause other issues in the future.
The issue is in the View release, not firmware. However, if we reach a point where we are not confident in VMware including this fix in an upcoming release, we will consider the less-than-ideal firmware workaround. We agree this is an issue that needs to be resolved."
I opened up ticket #13317255004 with VMware and they don't seem to be aware of this issue nor do they think it's an issue with View. I am going to upload some logs, but posting this here to see if anyone else is running into this.