WDM -> WMS migration path (DHCP options & DNS records)

Tagged: , , ,

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #53027
    • Total Post: 81
    • Back Stage Pass
    • ★★★★

    Hi guys and Thomas,

    I am currently investigating the best way to migrate my Wyse clients from WDM to cloud-based WMS and would like to ensure I have not missed anything.

    Currently, I manage Wyse clients using per-vlan DHCP scope options only (no DNS records) so every client type (workstation, dashboard) have different “root path” number. 162 root path has a default config in it so if I remotely reset a TC to defaults settings, it comes back with required (VNC) config so I can remote to it and then point it to the required root path.

    Now, with WMS I would like to achieve the same, i.e.:
    1. Clients managed from WMS (both ThinOS 8 & 9) after remote reset to default settings (wipe) automatically check back into WMS.
    2. Existing clients manged by WDM and DHCP scope options are not affected and don’t accidentally check in to WMS.
    3. Ideally, I would like to point clients to WMS using DNS service records (so I don’t have to play with DHCP any more), making sure that existing clients managed by WDM don’t use DNS for their config.

    Any suggestions on the above, please?

    Also, the thing I don’t get is that if I use DNS SRV records for WMS server URL and Group Registration Token, how to set them up on their first boot and then ensure they keep another/custom Group Registration Token after a reboot, is it possible? In other words, if a client is checking in to WMS using certain Group Registration Token while in WMS it is assigned to another (e.g. non-default) GRT, which policy is then applied?

    Thank you

    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    1. I would add something like CloudClientManager=no to your wnos.ini. This way you prevent that clients will look for a WMS server. After a factory reset the clients will look for the WMS server automatically via DNS first.
    So the migration should work straight away.

    2. Once a client has checked in to WMS once it will no longer use DNS to find the WMS server/group token


Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.