Highlighted
fabnik1s
1 Nickel

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. 

Knipsel.JPG

0 Kudos
5 Replies

Re: Cant get Wyse 5070 Windows 10 IOT working with WMS 1.3

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

 

fabnik1s
1 Nickel

Re: Cant get Wyse 5070 Windows 10 IOT working with WMS 1.3

thanks for the fast reply but i can resolve the NETBIOS name on both sides. and i disabled the firewall on both ends. but still no luck. tried multiple Thincients is there any Log file where i can check ?
0 Kudos

Re: Cant get Wyse 5070 Windows 10 IOT working with WMS 1.3

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
1 Nickel

Re: Cant get Wyse 5070 Windows 10 IOT working with WMS 1.3

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  

 

0 Kudos
fabnik1s
1 Nickel

Re: Cant get Wyse 5070 Windows 10 IOT working with WMS 1.3

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.

0 Kudos