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.
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
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.
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
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.