- This topic has 6 replies, 2 voices, and was last updated 3 years, 4 months ago by
.
-
Posts
-
Is there a way to move wyse thinclients from WMS A to WMS B, without reseting to factory defaults and connect to the new one via dhcp options?
That’s the only way I got some test devices to move to our WMS. Perhaps someone has similar experiances and found a way? Perhaps I missed something.
I have tried:
– change DHCP Options – Not working
– Tried via WMS Settings, additional group with new WMS and groupkey information – Not workingKind regards
LukasIf you are using ThinOS 8, then you can simply use INI parameters to tell the client which WMS server to use.
With ThinOS 9 you can use the WMS policy under Services. Make sure to just use this part of the policy only when you really want to move a client!CG
We have tried an additional MAC.ini with following config:
ccmenable=yes ccmserver=SERVER.LOCAL.COM:443 groupprefix=defa groupkey=GROUPKEY mqttserver=SERVER.LOCAL.COM:1883 cavalidation=no
wdmservice=nowith no effect.
We get following output in the system information event:
Ignoriere WMS Gruppenschlüssel in INI, da er im lokalen UI manuell konfiguriert oder von der WMS Gruppe geändert ist.
Any idea?
You are missing some sub-parameters.
CCMEnable=Yes CCMServer=SERVER.LOCAL.COM:443 GroupPrefix=defa GroupKey=GROUPKEY MQTTServer=SERVER.LOCAL.COM:1883 AdvancedConfig=yes Override=yes CAValidation=no
CG
This two parameters helped.
Some devices we want to migrate have an old firmwa 8.4 / 8.5 and the WMS is now on Version 3.
Are there any known issues that this devices can’t connect to a newer WMS? It’s the same system, only that the devices weren’t used over 100 days and more and the customer updated the WMS from 1.X to 3 so we can migrate on the same base.
- You must be logged in to reply to this topic.