Menu path: UMS Administration > Global Configuration > Thin Client Network Settings
Configuration of the System Information Update
Update system information on selection of a thin client
The system information of the thin client will be read in again as soon as the thin client is selected (default).
The system Information from the last update will be shown.
Advanced Thin Client Status Updates
Thin clients send status updates
advanced status (default)The thin clients report changes in their
The only thing that is displayed is whether a thin client is online or offline.
Enable automatic registration (without mac address import): This option is provided for the following scenario: The MAC addresses were already imported before the thin clients were added to the UMS database. As a result, preparations such as creating profiles can be made before the thin clients are delivered. If the option is enabled, each thin client will automatically receive the intended settings after it has logged on for the first time.
Further information regarding the importing of thin clients can be found under Import Thin Clients.
Each thin client that contacts the UMS will automatically be registered in the UMS database.
A thin client that contacts the UMS will not be automatically registered (default)
Thin Client Requests
Maximum number of concurrent thin client requests: Defines the number of concurrent thin client requests that are accepted by the UMS.
If you require higher performance and high availability, you can use IGEL UMS High Availability (HA).
No limit: Additional request will have to wait until a thread is available.
Queue size: Defines the queue size. Additional threads that exceed the queue size will be rejected. (Default: Activated, default value: 0)
Adjust Names of Thin Clients
Adjust UMS-internal names if network name has been changed
If the network name of the thin client is changed, the UMS-internal name will be set to the new network name.
The UMS-internal name will not be set to the network name of the thin client (default).
Adjust network name if UMS-internal name has been changed
If the UMS-internal name of the thin client is changed, the network name of the thin client will be set to the new UMS-internal name.
The network name of the thin client will not be set to the UMS-internal name (default).
Enable naming convention
The UMS-internal names of the thin clients will be formed from the prefix and a consecutive number.
The names of the thin clients will not be allocated in accordance with the naming convention (default).
Prefix: Prefix for automatically allocating names. In the neighboring field, the current naming convention comprising a prefix, a dash "
-" and a consecutive number with the number of digits specified under Min. digits will be shown.
Minimum. digits: Minimum number of digits for the consecutive number. The digits not allocated will be filled with zeros. Examples: If 2 is selected, the consecutive number of the first thin client will be 01, if 3 is selected, the consecutive number will be 001 and so on.
Apply to all thin clients: If you click on this button, all thin clients registered in the UMS will be renamed in accordance with the naming convention.
Reset counter and renumber
When all thin clients are renamed (as a result of clicking on Apply to all thin clients), this will result in continuous, end-to-end numbering. All names will be reallocated, even for thin clients that were already renamed in accordance with the naming convention. If numbers have become free because thin clients were taken out of service, these numbers will be used for other thin clients.
If all thin clients are renamed in accordance with the naming convention, numbers previously allocated will be retained. Only thin clients that do not yet conform to the naming convention will be renamed.