- This topic has 3 replies, 4 voices, and was last updated 4 years, 7 months ago by
.
-
Posts
-
Hey !
We recently started using the Wyse 3040 and we deployed a WMS server to configure and update them (from 8.4 to 8.6 at the moment).
Fact is that our WMS is accessible through its FQDN which is “thinmanager.lan.domain.net”
So when I start a Wyse, I’ll generally set up the WMS by disabling DNS SRV record, Enabling advanced options and putting the FQDN of our server, which works but once it reboots, it’ll become the hostname only : “thinmanager:443” for the WMS server and “thinmanager:1883” for the MQTT.
We tried using DNS SRV records to give the FQDN but it’ll be shorted to the hostname only anyway.
Is there any way to keep the FQDN there instead of just the hostname ? What I have in mind are DHCP options but we would like to avoid that if possible.
Thanks in advance and have a great day.
I use DHCP option tags that point to a DNS alius of the FQDN.
Works perfectly, and was a dream to use when moving from WDM to WMS, as soon as I put the Option tags on the terminals just flipped over perfectly next re-boot with no hassle and perfect ever since 🙂
Hi!
This might be more WMS related, but…
I think I’ve figured out why it changes after a reboot.
ThinOS keeps correcting the “wms server” to its ‘own’ wms-server hostname.
Based on shortyman’s topic, the ‘wms’-machine has not joined a domain.
Although he created a record which resolves, the ‘wms’-machine is still not aware it is member of the forest (example.com)So….
I’ve created a AD-forest with the exact same name as the FQDN i’ve specified earlier and joined the ‘wms’-machine
The ‘wms’-machine now recognizes itself as <hostname>.<example>.<com>Even if I enter the IP of my wms-server, ThinOS changes this to the hostname, which is now; <hostname>.<example>.<com>
Hope this helps!
edit, shortyman’s topic;
- You must be logged in to reply to this topic.