Unsolved
5 Posts
0
4717
Cant get Wyse 5070 Windows 10 IOT working with WMS 1.3
i have a Local WMS server But when i register a Client the policy is not applied and i cant reboot or query the device.
GR Fabian.
Unsolved
5 Posts
0
4717
i have a Local WMS server But when i register a Client the policy is not applied and i cant reboot or query the device.
GR Fabian.
Top
buffalobound
3 Apprentice
3 Apprentice
•
712 Posts
1
February 15th, 2019 04:00
If a device registers, but cannot be rebooted nor policies can be applied it is most likely a communications issue.
WMS requires 2 ports to communicate properly. The data flow is from the thin client to the management console and it is port 443, and port 1883.
Normally when a device cannot be rebooted it is due to the port 1883 not communicating. Sometimes this occurs because there is a firewall between the device and WMS, or a local firewall on the device blocking it, or it is a name resolution problem from the device to the WMS server.
Confirm that you can resolve the netbios name of the WMS server from the endpoint
Confirm that you can resolve the FQDN, name.domain.com of the WMS server from the endpoint
buffalobound
3 Apprentice
3 Apprentice
•
712 Posts
1
February 15th, 2019 05:00
Make sure you can resolve the FQDN of the WMS server as well, from the client.
Login as admin to the thin client, go to the WDA (Wyse Device Agent) in the system tray, support. There is a section that you can enable logging. Restart the Wyse Device Agent service, wait 15-20 minutes then take a look at the log.
fabnik1s
5 Posts
0
February 15th, 2019 05:00
i found 1 problem the Write Filter was turned off.
nou the policy is applyed but after a manual restart.
stil cant reboot from WMS
fabnik1s
5 Posts
0
February 15th, 2019 05:00
fabnik1s
5 Posts
0
February 18th, 2019 00:00
i have now tested with another Thin Client But still no luck. i still can't Manage the device.
and have this entry in the log file
18/02/2019 09:42:06.252 I 7988 4 WebException returned ProtocolError - The remote server returned an error: (400) Bad Request.
FrankEGD69
9 Posts
0
January 8th, 2020 11:00
Try this, it will clear the known info on the TC pertaining to the WMS server:
Edit the following file on the TC that does not check in with WMS:
C:\Program Files\Wyse\WDA\Config\CCMProtocolConfig.xml
At the bottom of that file, under , delete only the values within the following tags ( i.e.: Value
Make them look exactly like shown, the original values will be repopulated.
Also, under
xx:xx:xx:xx:xx insert the devices MAC address in the same format.
Save the file and reboot the Thin Client. Check WMS and within about one minute the TC will be registered.
I hope that helps.
If it doesn't please, post the content of the .xml file. There might be other sections like that you need to change or add info into, i.e.: defa-WhatEverName for the default device groug that TC is supposed to be registering with.
Thank you.