Is there a performance penalty with assigning multiple IGEL UMS Profiles


Is there a performance penalty with assigning multiple profiles (new and updated) to a collection of thin clients? And, are profiles applied synchronously (1 per reboot), or are new and modified profile(s) applied at once during reboot of the thin client?

Learn more, read the entire thread inside the IGEL Community o Slack

No performance penalty, as the resultant configurations get combined into a single file (group.ini) before it gets to the thin clients. Multiple profiles that are logically broken up (a profile for Citrix settings, a profile for WLAN settings, a profile for UI/language settings, etc.) is typically better practice than a single large profile 🙂

Thin clients will pull new/modified profile settings during reboot, but you can also push them right from UMS. When a profile is modified, it’ll ask you if you want to apply the profile at reboot OR immediately


Perfect, thanks!

Continue reading and comment on the thread ‘Is there a performance penalty with assigning multiple IGEL UMS Profiles ‘.  Not a member? Join Here!

Learn more, search the IGEL Knowledge Base



Ask a question or comment on the above message thread?

Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.

Submit a question, or Join Today!


Popular Message Threads


Categories & Tags: