IGEL OS12 editing of RAS settings from multiple sources

IGEL provides a dedicated server, Unified Management Server (UMS), for bulk management of OS and application settings on IGEL thin clients. The settings interface is shared between the UMS server and the local OS settings.

However, IGEL’s bulk application settings management overlaps with existing mechanisms for configuring Parallels RAS client settings, creating additional complexities. Not all configurable settings are managed through IGEL’s UMS, which means multiple sources can modify RAS client settings, including:

1. UMS-pushed application settings

2. Local modifications via the Settings app in IGEL OS 12

3. Changes made directly in the RAS client launcher

4. Policies applied through the Parallels RAS Server

This multi-source configuration can lead to confusion, as users may inadvertently overwrite settings they did not intend to change.

Resolution

To maintain clarity, administrators managing Parallels RAS client settings must be aware of the multiple sources that influence configurations. Conflicts in settings are resolved as follows:

• If no Parallels RAS Server policy is applied:
  • The most recent changes from the RAS client launcher or the UMS/Settings app take precedence.
     
• If a Parallels RAS Server policy is applied:
  • Changes made through UMS or the Settings app are disregarded, except during initial installation. In this case, the policy is applied upon first connection, and any subsequent modifications from UMS or the Settings app are ignored

By understanding these configuration mechanisms, administrators can effectively manage settings while minimizing unintended conflicts.