- This topic has 8 replies, 4 voices, and was last updated 3 years, 8 months ago by
.
-
Posts
-
Hello,
I am currently testing WMS Standard Edition.
At the moment the Wyse thin clients and their display Settings (Dual Monitor in Span Mode, Main Display and Swap Screen) are configured manually.
Our issue is that these manual settings are overwritten when thin clients are registered to WMS or when a policy is applied to the client (usually after every boot).
We tried to tackle this by using a policy for the display configuration instead.
However because some users like their main display on the right monitor and the connection/wires is not the same on every thin-client, the monitor arrangement is wrong on some clients.
Also sometimes just changing the displayport wires between the ports is not possible and the “swap dual screens” options has to be used.
How can this be configured correctly, that either..
.. the manual settings will not be overwritten by policies
.. a display policy for different settings can be deployed?
We have a little amount of C10 EOL devices. We register the devices through DHCP option tags. Is there a way (for example a group) to seperate those EOL devices from other WYSE thin-clients, to stop WMS trying to apply policies to those EOL clients?
The latest ThinOS version for those supports WMS, but not all the current settings, which causes problems with their configuration.
If you know a way to deploy host names (like WYSE-### with an increasing number) instead of configuring them manually locally or in WMS for each device, that would be great too. I haven’t figured out yet, if it is possible.
Add
ManualOverride=yes Components=”Display”
to the Advanced section and the user can overwrite the WMS settings for Displays.CG
Thank you very much, I’m definitely going to try this.
Is there a way to find parameters like this, are they part of the Configuration generator? I couldn’t find those in the WMS Administrator Guide.
Nearly all parameters are part of my ConfGen. Just working on an update to support all parameter again.
Other option is always the INI guide on the Dell Support site.CG
Hi
I tried to add ManualOverride=yes Components=”Display” in line 1 but it doesn’t work on every boot.
sometimes it shows invalid parameter and I have no idea what the issue is.
I am using WMS 1.4 with thin os 8.6_013(3010,3020,3040)
Thanks.
What do you mean by “doesn’t work on every boot” and “sometimes”?
CG
Hi,
I am having the same issue, did the above settings worked?
I am doing a WDM to WMS upgrade and many users reporting they lost Display settings which were set manually after upgrading to WMS.
I tried to add ManualOverride=yes Components=”Display” in advanced settings line 3 but it doesn’t seem to work. It shows as invalid parameter in eventlog and all the manual display settings being lost.
I am using WMS 1.4 with thin OS 8.6_303(5010,3040)
Devices in WDM are on 8.4 & 8.5 image and moving them to 8.6 while upgrading to WMS.
Thanks.
Hi,
I also tested on devices which are on WMS already with 8.6_303 and the behavior is still the same. I applied span mode manually on couple of devices which are on WMS with 8.6_303 and tried moving them to different group with advanced settings applied but not retaining display setting(Span Mode) policies.
Thanks,
Sunil
- You must be logged in to reply to this topic.