With this configuration, the administrator can specify the ThinMan Server address.
It is very important to specify the referenced ThinMan in order the device be able to send to the ThinMan server more information about itself (Serial, Subnet, etc.).
Mandatory Configuration for using specific ThinMan Features
This configuration is necessary in order to use the following ThinMan features: Scheduled Activities, Event Activities, ThinMan Profile Manager, ThinMan Login).
More information
Read How to Setup ThinMan Address on a device to find more information about how the ThinMan is contacted.
¶ Connection tab
The options shown on this tab are used to identify the ThinMan server to which the device will notify.
-
Enable Communication with ThinMan: allows the device to communicate with ThinMan.
-
ThinMan Address Configuration (ordered by priority): on this section, the device will first look into the DHCP option (by default: 163) containing the ThinMan server address. whether the DHCP Option is not configured, the device will use the Explicit address when the DHCP option is not available (by default: PRAIMSERVER). Click Test to verify the device and ThinMan can communicate.
-
ThinMan Connection Options
- Timeout (5-60 sec.): timeout used to communicate with ThinMan(expressed in seconds). The default value is 15 seconds but you can change it according to the speed of your DHCP server.
- Device Listening port: It is the port used by the device to receive communication from ThinMan, by default 443.
- Max. number of connection attempts (0= unlimited): maximum number of connection attempts from the device to the ThinMan Server, by default 3.
- Only WSS with certificate (Safe): allows the device to establish a WSS Safe connection with ThinMan.
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.
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.
Setting up Primary and Secondary ThinMan Address on ThinOX
Enter the hostnames or IP Addresses of the Primary and Secondary ThinMan Server separated by a comma (,).
Use hostnames instead of IP addresses for easier maintenance. Hostnames allow all devices to redirect to a new ThinMan Server without requiring manual reconfiguration.
¶ Authentication tab
¶ ThinMan Authentication Options
It allows defining the options for the ThinMan Login.
- 802.1x credentials passthrough: when enabled, the ThinMan Login will use the credentials given for the network login.
- Imprivata Onesign credentials passthrough: when enabled, the ThinMan Login will use the credentials given for the Imprivata connection.
- VPN agent credentials passthrough: when enabled, the ThinMan Login will use the credentials given for the VPN connection.
- Show last logged user: when enabled, it will precompile the ThinMan Login window with the last username logged in the device.
- Allow to remember the last domain used: when enabled, the ThinMan Login window will show the Save last domain used option (see image below). This option is useful when you have configured more than one domain and you would like to give the end user the possibility to choose the domain and save this as the last domain used.
¶ Behaviour if ThinMan not available
Force Retry is strictly connected to the timeout parameter in the previous tab. When the device tries to contact the ThinMan Server at the device's startup, the device waits and eventually retries the connection during the timeout seconds before accepting that the ThinMan Server does not respond to the request. Be aware there is a ThinMan Server on the network; otherwise, this flag will increase the boot-time of the device. This parameters is useful when a device has been configured with static IP Address.