The best way is that every thin clients know (when they start) the ThinMan Server address. In this case you achieve the full potential for the device management by ThinMan Server. The device does not have to be discovered by the ThinMan Server but when started it notifies himself to the ThinMan Server.
This configuration could be achieved in two different modes: manual or provided by the network.
In the manual case you have to power on the device and insert the ThinMan Server address in the specified configuration panel. Obviously this operation is really time consuming and it is not suggested when you have lot of thin clients to manage.
The suggested way is to give such information using the network where the thin client is attached; this can be done using two different methods. The first one is to define the DHCP Option 163 on the DHCP Server; the option will define (using the FQDN or the IP Address) the address of the ThinMan Server. The second one is to let the DNS to resolve the “PRAIM_THINMAN” hostname with the ThinMan Server address.
If you configure your environment using the network parameters every Praim thin clients or devices know which is the ThinMan Server in the network and can notify himself. This is also true for brand out-of-the-box devices that can be attached to the network and could connect to the ThinMan Server without any configuration from the IT Manager.
For more information read these links: