Forum Replies Created
-
AuthorPosts
-
Alrighty, so after a long-winded process I was able to get WYSE to actually look into the issue and provide a Hotfix.
I have been told that the hotfix will be released this coming Monday but I have been given an early tester of it and it seems to work.
The version I have & tested with is HF 2.0_021.
I’ve only tested on a Xenith Pro as it was the only fw I was given, though there seem to be no more issues regarding dual monitors.
ConfGen’s method is probably easiest, but you could separate the client on the network level.
The way I do all my testing is to have different VLANs which allows me to have different DHCP servers, and hence I have a testing environment ‘LAN’ and a production environment ‘LAN’. However, if your router+switches aren’t VLAN/Multi DHCP server capable, this option won’t work for you.
I’ve opened up a support case with Wyse, I will post my findings here if there is any positive conclusion.
Okay, the issue doesn’t seem to be manifesting itself in firmware versions < 2.0 now, but still definitely on v2.0_015 and v2.0_017.
Yep, I have a test device sitting right in front of me *with a test wdm server*, and yes I have attempted the latest hotfix version (see initial post or quote below).
@jellydonuts wrote:
I have tried upgrading the firmware all the way up to the latest version v2.0_015 (and even with the hotfix v2.0_017), the same issue continues manifesting when I use 2 monitors.
I have a test-bed set up so I was able to create a stripped down xen.ini that is simply 3 options:
xen.ini
autoload=2
SessionConfig=ICA OnDesktop=allPS: Thanks for the quick replies.
Hellooo,
Yes, I have tried that multiple times, I usually do it after a fw upgrade.
Of course it will work the first time I do it, because the factory default is mirror mode (hence only 1 monitor). But when it is switched to span mode after the factory reset, the same error occurs.
If the settings are placed in the xen.ini file, span mode is turned on when the ini is read – before getting a logon screen, which causes a reboot – and still, the same error occurs.
-
AuthorPosts