To use a device within a Scheduled Activity, an Event Activity or in a Device Policy, it is essential to configure the correct ThinMan Address on the device.
The ThinMan Address can be either:
Configuring ThinMan Address from ThinMan Console
You can set the ThinMan Address directly from the ThinMan console using Contextual Menu - Special Functions via Set ThinMan Server Address.
Best practices for Configuring ThinMan Address
Use Network Parameters for Automatic Configuration By factory default, thin clients are preconfigured to:
- First test DHCP option 163.
- If DHCP Option 163 is not configured or fails, resolve the PRAIMSERVER hostname via DNS.
Recommendation: Use network parameters to allow thin clients to connect to ThinMan out-of-the-box. This setup ensures that devices are ready to be managed through the ThinMan Profile Manager.
For detailed guidance, see How to Configure a DNS Server with PRAIMSERVER hostname and How to Configure DHCP Option 163.
Using a Non-Standard Port on ThinMan Server
By defaut, ThinMan uses the port 443 (HTTPS) for thin client connections. If this port is changed via the ThinMan Server Menu, you must inform the devices by specifying the port in the format: ThinManServerNameOrIPAddress:port. A ThinOX device manually configured to use port 1443 might look like this:![]()
Important Notes: Automatic ThinMan Address configuration through DNS will not work if a non-standard port is used. The only automatic method to provide this configuration is via DHCP Option 163. The option's value must follow the format: ThinManServerNameOrIPAddress:port
Not using network parameters for configuration will prevent the use of Zero Config with Profile Manager.
Getting Started - Configuring Praim Devices to Contact ThinMan
For step-by-step guidance, refer to the Getting Started Guide or watch the video
Configuring ThinMan Address The client uses the following methods in order to connect to the ThinMan server:
Test Connection
Use the Test Connection button to verify the connection between the device and the ThinMan Server. Once successful, the device will appear on the ThinMan Server, with its status displayed as WSS.
Click OK to save the settings, and then click OK again in the Configuration Settings window to finalize the configuration.
Enter the hostnames or IP Addresses of the Primary and Secondary ThinMan Server separated by a comma (,).
Example: PrimaryThinManServer,PraimSecondaryServer
Restart the thin client to apply the settings.
Tip:
Use hostnames instead of IP addresses for easier maintenance. Hostnames allow all devices to redirect to a new ThinMan Server without requiring manual reconfiguration.
Read the available documentation at Agile: Configuring the ThinMan Settings.