- This topic has 8 replies, 3 voices, and was last updated 6 years, 3 months ago by
.
-
Posts
-
Hi,
we are testing the rollout of thin clients (5060). Therefore we installed WMS 1.1 on a management server. According to the admin guide we have set dhcp-option tags. My understanding is, that when a thin client gets a dhcp lease it will pull settings of WMS and then will regiser automatically. But this is not the case. Firewall ports on the mangement server are set to allow inbound on port 443 and 1883. We did not set the cavalidation tag in dhcp, because we dont use certficates for now. Did I miss anything?
1. add Cavlidation to your DHCP option tags, as WMS uses a self-signed certificate by default.
2. make sure to have firmware version 8.4_009 or higher on the client.CG
Hi,
We just just added the missing option tag, but still, the clients don’t register. Is there something I do have to install on the clients? They have Windows 10 running and we have just flashed the latest Image.
Question:
we still use WDM but plan an change to WMS on premise setup.
What’s best practise? DHCP Options or Server record?
Do we need every service record ?
Follow the steps in Quick Start Guide with DHCP. This works great and is easy to set up.
- You must be logged in to reply to this topic.