You can configure a thin client via the UMS in the following ways:

  1. Via Structure tree > [Thin Client Context Menu] > Edit Configuration: Here, you can edit the client setup as you would if you were working at the device itself.
  2. Via a profile: You assign part-configurations to the client via a profile.
  3. Via shadowing with VNC: By shadowing the client, you can work in the setup on the device itself.

You can edit the thin client configuration locally in the client setup or directly for this client in the IGEL UMS:

Double-click on the thin client in the structure tree
or select Edit configuration from the menu / context menu
or select the corresponding symbol from the symbol bar.

The configuration dialog for a thin client in the UMS and the profile configuration procedure are structured in the same way as the local setup for a thin client. Details of this are set out in the relevant manual.

With a click on this symbol you can reset settings to the default value from UMS version 5.09.100 on.

From UMS Version 5.05.100, the start page of the configuration dialog contains a link to the page last opened. The symbol for the link is at the very top of the list of links. A link will also be created if the last page opened belongs to another thin client or to another profile. If the page last opened is not available in the configuration dialog that is currently open, a link to the next page up in the structure tree will be created. Example: In the configuration dialog for thin client 1, a setting for the RDP session My RDP Session was changed (menu path: Sessions > RDP > RDP Sessions > My RDP Session). The configuration dialog for thin client 2 is then opened but thin client 2 does not have a session with the session name My RDP Session. A link to the higher-level page RDP Sessions will therefore be shown (menu path: Sessions > RDP > RDP Sessions).

To determine when changes to the configuration are to take effect, proceed as follows.

  1. Change the configuration.
  2. Click on Save.
  3. Select when the settings are to take effect.
    • Next Reboot: The thin client will automatically retrieve its settings each time it boots.
    • Now: The settings will be transferred to the thin client immediately.

    If the thin client is not switched on, this operation cannot be performed and the thin client will be given its settings the next time it reboots. In both cases, the settings will initially be saved in the database.

    If you have selected Immediately, a pop-up dialog will ask the user whether the new settings should take effect immediately. You can change the user message using the following two registry parameters: userinterface.rmagent.enable_usermessage and userinterface.rmagent.message_timeout.