Universal Management Suite

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: igel/igel-ums locale: en labels: vendor: IGEL Universal Management Suite capability/modern-workplace: 1.72 capability/endpoint-security: 2.85 capability/managed-services: 2.90 vendor/igel: 3.14 annotations: source: src/content/solutions/en/igel/igel-ums.md route: /en/solutions/igel/igel-ums/ schema: /nerd/schema/solutions.json markdown: /en/solutions/igel/igel-ums.mdspec: title: Universal Management Suite tags: [modern-workplace, endpoint-security, managed-services] vendors: [igel] summary: >- The management server for every IGEL endpoint. Policies, firmware, certificates and apps, applied to one device or ten thousand. photoNeed: >- An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk stub: false draft: false kind: product acronym: UMS addon: false sourceNote: >- soultec.ch/solutions/igel, read 2026-08-30, for the architecture; kb.igel.com IGEL OS Editions feature matrix, read the same day, for which feature sits at which licence level vendorName: IGEL Universal Management Suite status: current practice: >- Draft, not yet reviewed. We size the UMS before the endpoints, and the question that decides it is not device count but whether the estate has to survive the server being down. Distributed UMS is a Standard-licence feature and a day-one architecture decision; retrofitting it after two thousand devices are registered is not a config change. practiceReview: true sections: - heading:

What it is

body: | The UMS is the server the endpoints answer to. Configuration, grouping, monitoring, policies, firmware, certificates, network settings and software packages all come from it, applied to a single device or to a group. It manages IGEL OS 11 and 12 side by side, which matters because most estates are mid-migration for longer than they planned. - heading:

Two consoles, on purpose

body: | UMS 12 has a browser-based **Web App** and a Java-based **Console**. The Web App is where day-to-day work happens; the Console still carries the deeper administrative functions. Anyone expecting the browser to have replaced the desktop client will be disappointed for a while yet, and it is better to know that before the rollout plan says otherwise. - heading:

How it talks to the endpoints

body: | Through the **Unified Protocol**, a WebSocket connection that carries everything between UMS 12 and IGEL OS 12, and only between those two. One consequence is worth the sentence: because it is a single WebSocket, an external load balancer such as F5 BIG-IP or Citrix NetScaler can sit in front of it, which is how you get load distribution and availability in the management layer rather than in a script. For real high availability there is **Distributed UMS**: several UMS servers on one shared database. - heading:

What the licence level decides

body: | All IGEL OS Editions include a UMS licence, so the question is never whether you have one. It is which one. An external database, the IGEL Cloud Gateway and Distributed UMS arrive with Standard; the distributed app repository and using the UMS as a certificate authority proxy arrive with Enterprise. Downgrading takes features away immediately, and IGEL says so in the manual. Nothing is deleted, so an upgrade restores it, but the afternoon in between is real.status: corpus: 309 services: - {ref: services/service-desk, score: 0.42} - {ref: services/managed-service, score: 0.35} - {ref: services/monitoring, score: 0.35} - {ref: services/modern-workplace, score: 0.34} posts: - {ref: posts/how-to-igel-ud-pocket-bios-uefi-settings, score: 0.31} - {ref: posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos, score: 0.31} - {ref: posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem, score: 0.31} - {ref: posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem, score: 0.31} - {ref: posts/send-workspace-one-hub-notifications, score: 0.31} - {ref: posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change, score: 0.28} experts: - {ref: experts/valentina-cicmak, score: 0.24} neighbours: - {ref: solutions/igel/igel-os, score: 0.73} - {ref: solutions/igel/igel-onboarding-service, score: 0.65} - {ref: solutions/igel/addon/igel-contextual-access, score: 0.64}

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "igel/igel-ums", "locale": "en", "labels": { "vendor": "IGEL Universal Management Suite", "capability/modern-workplace": "1.72", "capability/endpoint-security": "2.85", "capability/managed-services": "2.90", "vendor/igel": "3.14" }, "annotations": { "source": "src/content/solutions/en/igel/igel-ums.md", "route": "/en/solutions/igel/igel-ums/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/igel/igel-ums.md" } }, "spec": { "title": "Universal Management Suite", "tags": [ "modern-workplace", "endpoint-security", "managed-services" ], "vendors": [ "igel" ], "summary": "The management server for every IGEL endpoint. Policies, firmware, certificates and apps, applied to one device or ten thousand.", "photoNeed": "An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk", "stub": false, "draft": false, "kind": "product", "acronym": "UMS", "addon": false, "sourceNote": "soultec.ch/solutions/igel, read 2026-08-30, for the architecture; kb.igel.com IGEL OS Editions feature matrix, read the same day, for which feature sits at which licence level", "vendorName": "IGEL Universal Management Suite", "status": "current", "practice": "Draft, not yet reviewed. We size the UMS before the endpoints, and the question that decides it is not device count but whether the estate has to survive the server being down. Distributed UMS is a Standard-licence feature and a day-one architecture decision; retrofitting it after two thousand devices are registered is not a config change.\n", "practiceReview": true }, "sections": [ { "heading": "

What it is

", "body": "The UMS is the server the endpoints answer to. Configuration, grouping, monitoring,\npolicies, firmware, certificates, network settings and software packages all come from it,\napplied to a single device or to a group. It manages IGEL OS 11 and 12 side by side, which\nmatters because most estates are mid-migration for longer than they planned." }, { "heading": "

Two consoles, on purpose

", "body": "UMS 12 has a browser-based **Web App** and a Java-based **Console**. The Web App is where\nday-to-day work happens; the Console still carries the deeper administrative functions.\nAnyone expecting the browser to have replaced the desktop client will be disappointed for a\nwhile yet, and it is better to know that before the rollout plan says otherwise." }, { "heading": "

How it talks to the endpoints

", "body": "Through the **Unified Protocol**, a WebSocket connection that carries everything between\nUMS 12 and IGEL OS 12, and only between those two. One consequence is worth the sentence:\nbecause it is a single WebSocket, an external load balancer such as F5 BIG-IP or Citrix\nNetScaler can sit in front of it, which is how you get load distribution and availability\nin the management layer rather than in a script.\n\nFor real high availability there is **Distributed UMS**: several UMS servers on one shared\ndatabase." }, { "heading": "

What the licence level decides

", "body": "All IGEL OS Editions include a UMS licence, so the question is never whether you have one.\nIt is which one. An external database, the IGEL Cloud Gateway and Distributed UMS arrive\nwith Standard; the distributed app repository and using the UMS as a certificate authority\nproxy arrive with Enterprise.\n\nDowngrading takes features away immediately, and IGEL says so in the manual. Nothing is\ndeleted, so an upgrade restores it, but the afternoon in between is real." } ], "status": { "corpus": 309, "services": [ { "ref": "services/service-desk", "score": "0.42" }, { "ref": "services/managed-service", "score": "0.35" }, { "ref": "services/monitoring", "score": "0.35" }, { "ref": "services/modern-workplace", "score": "0.34" } ], "posts": [ { "ref": "posts/how-to-igel-ud-pocket-bios-uefi-settings", "score": "0.31" }, { "ref": "posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos", "score": "0.31" }, { "ref": "posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem", "score": "0.31" }, { "ref": "posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem", "score": "0.31" }, { "ref": "posts/send-workspace-one-hub-notifications", "score": "0.31" }, { "ref": "posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change", "score": "0.28" } ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.24" } ], "neighbours": [ { "ref": "solutions/igel/igel-os", "score": "0.73" }, { "ref": "solutions/igel/igel-onboarding-service", "score": "0.65" }, { "ref": "solutions/igel/addon/igel-contextual-access", "score": "0.64" } ] }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "igel/igel-ums"locale = "en"[metadata.labels]vendor = "IGEL Universal Management Suite""capability/modern-workplace" = "1.72""capability/endpoint-security" = "2.85""capability/managed-services" = "2.90""vendor/igel" = "3.14"[metadata.annotations]source = "src/content/solutions/en/igel/igel-ums.md"route = "/en/solutions/igel/igel-ums/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/igel/igel-ums.md"[spec]title = "Universal Management Suite"tags = ["modern-workplace", "endpoint-security", "managed-services"]vendors = ["igel"]summary = "The management server for every IGEL endpoint. Policies, firmware, certificates and apps, applied to one device or ten thousand."photoNeed = "An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk"stub = falsedraft = falsekind = "product"acronym = "UMS"addon = falsesourceNote = "soultec.ch/solutions/igel, read 2026-08-30, for the architecture; kb.igel.com IGEL OS Editions feature matrix, read the same day, for which feature sits at which licence level"vendorName = "IGEL Universal Management Suite"status = "current"practice = '''Draft, not yet reviewed. We size the UMS before the endpoints, and the question that decides it is not device count but whether the estate has to survive the server being down. Distributed UMS is a Standard-licence feature and a day-one architecture decision; retrofitting it after two thousand devices are registered is not a config change.'''practiceReview = true[[sections]]heading = "

What it is

"body = '''The UMS is the server the endpoints answer to. Configuration, grouping, monitoring,policies, firmware, certificates, network settings and software packages all come from it,applied to a single device or to a group. It manages IGEL OS 11 and 12 side by side, whichmatters because most estates are mid-migration for longer than they planned.'''[[sections]]heading = "

Two consoles, on purpose

"body = '''UMS 12 has a browser-based **Web App** and a Java-based **Console**. The Web App is whereday-to-day work happens; the Console still carries the deeper administrative functions.Anyone expecting the browser to have replaced the desktop client will be disappointed for awhile yet, and it is better to know that before the rollout plan says otherwise.'''[[sections]]heading = "

How it talks to the endpoints

"body = '''Through the **Unified Protocol**, a WebSocket connection that carries everything betweenUMS 12 and IGEL OS 12, and only between those two. One consequence is worth the sentence:because it is a single WebSocket, an external load balancer such as F5 BIG-IP or CitrixNetScaler can sit in front of it, which is how you get load distribution and availabilityin the management layer rather than in a script.For real high availability there is **Distributed UMS**: several UMS servers on one shareddatabase.'''[[sections]]heading = "

What the licence level decides

"body = '''All IGEL OS Editions include a UMS licence, so the question is never whether you have one.It is which one. An external database, the IGEL Cloud Gateway and Distributed UMS arrivewith Standard; the distributed app repository and using the UMS as a certificate authorityproxy arrive with Enterprise.Downgrading takes features away immediately, and IGEL says so in the manual. Nothing isdeleted, so an upgrade restores it, but the afternoon in between is real.'''[status]corpus = 309[[status.services]]ref = "services/service-desk"score = "0.42"[[status.services]]ref = "services/managed-service"score = "0.35"[[status.services]]ref = "services/monitoring"score = "0.35"[[status.services]]ref = "services/modern-workplace"score = "0.34"[[status.posts]]ref = "posts/how-to-igel-ud-pocket-bios-uefi-settings"score = "0.31"[[status.posts]]ref = "posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos"score = "0.31"[[status.posts]]ref = "posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem"score = "0.31"[[status.posts]]ref = "posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem"score = "0.31"[[status.posts]]ref = "posts/send-workspace-one-hub-notifications"score = "0.31"[[status.posts]]ref = "posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change"score = "0.28"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.24"[[status.neighbours]]ref = "solutions/igel/igel-os"score = "0.73"[[status.neighbours]]ref = "solutions/igel/igel-onboarding-service"score = "0.65"[[status.neighbours]]ref = "solutions/igel/addon/igel-contextual-access"score = "0.64"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>igel/igel-ums</name> <locale>en</locale> <labels> <vendor>IGEL Universal Management Suite</vendor> <entry key="capability/modern-workplace">1.72</entry> <entry key="capability/endpoint-security">2.85</entry> <entry key="capability/managed-services">2.90</entry> <entry key="vendor/igel">3.14</entry> </labels> <annotations> <source>src/content/solutions/en/igel/igel-ums.md</source> <route>/en/solutions/igel/igel-ums/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/igel/igel-ums.md</markdown> </annotations> </metadata> <spec> <title>Universal Management Suite</title> <tags> <item>modern-workplace</item> <item>endpoint-security</item> <item>managed-services</item> </tags> <vendors> <item>igel</item> </vendors> <summary>The management server for every IGEL endpoint. Policies, firmware, certificates and apps, applied to one device or ten thousand.</summary> <photoNeed>An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk</photoNeed> <stub>false</stub> <draft>false</draft> <kind>product</kind> <acronym>UMS</acronym> <addon>false</addon> <sourceNote>soultec.ch/solutions/igel, read 2026-08-30, for the architecture; kb.igel.com IGEL OS Editions feature matrix, read the same day, for which feature sits at which licence level</sourceNote> <vendorName>IGEL Universal Management Suite</vendorName> <status>current</status> <practice>Draft, not yet reviewed. We size the UMS before the endpoints, and the question that decides it is not device count but whether the estate has to survive the server being down. Distributed UMS is a Standard-licence feature and a day-one architecture decision; retrofitting it after two thousand devices are registered is not a config change. </practice> <practiceReview>true</practiceReview> </spec> <sections> <section> <heading>

What it is

</heading> <body>The UMS is the server the endpoints answer to. Configuration, grouping, monitoring,policies, firmware, certificates, network settings and software packages all come from it,applied to a single device or to a group. It manages IGEL OS 11 and 12 side by side, whichmatters because most estates are mid-migration for longer than they planned. </body> </section> <section> <heading>

Two consoles, on purpose

</heading> <body>UMS 12 has a browser-based **Web App** and a Java-based **Console**. The Web App is whereday-to-day work happens; the Console still carries the deeper administrative functions.Anyone expecting the browser to have replaced the desktop client will be disappointed for awhile yet, and it is better to know that before the rollout plan says otherwise. </body> </section> <section> <heading>

How it talks to the endpoints

</heading> <body>Through the **Unified Protocol**, a WebSocket connection that carries everything betweenUMS 12 and IGEL OS 12, and only between those two. One consequence is worth the sentence:because it is a single WebSocket, an external load balancer such as F5 BIG-IP or CitrixNetScaler can sit in front of it, which is how you get load distribution and availabilityin the management layer rather than in a script.For real high availability there is **Distributed UMS**: several UMS servers on one shareddatabase. </body> </section> <section> <heading>

What the licence level decides

</heading> <body>All IGEL OS Editions include a UMS licence, so the question is never whether you have one.It is which one. An external database, the IGEL Cloud Gateway and Distributed UMS arrivewith Standard; the distributed app repository and using the UMS as a certificate authorityproxy arrive with Enterprise.Downgrading takes features away immediately, and IGEL says so in the manual. Nothing isdeleted, so an upgrade restores it, but the afternoon in between is real. </body> </section> </sections> <status> <corpus>309</corpus> <services> <item> <ref>services/service-desk</ref> <score>0.42</score> </item> <item> <ref>services/managed-service</ref> <score>0.35</score> </item> <item> <ref>services/monitoring</ref> <score>0.35</score> </item> <item> <ref>services/modern-workplace</ref> <score>0.34</score> </item> </services> <posts> <item> <ref>posts/how-to-igel-ud-pocket-bios-uefi-settings</ref> <score>0.31</score> </item> <item> <ref>posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos</ref> <score>0.31</score> </item> <item> <ref>posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem</ref> <score>0.31</score> </item> <item> <ref>posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem</ref> <score>0.31</score> </item> <item> <ref>posts/send-workspace-one-hub-notifications</ref> <score>0.31</score> </item> <item> <ref>posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change</ref> <score>0.28</score> </item> </posts> <experts> <item> <ref>experts/valentina-cicmak</ref> <score>0.24</score> </item> </experts> <neighbours> <item> <ref>solutions/igel/igel-os</ref> <score>0.73</score> </item> <item> <ref>solutions/igel/igel-onboarding-service</ref> <score>0.65</score> </item> <item> <ref>solutions/igel/addon/igel-contextual-access</ref> <score>0.64</score> </item> </neighbours> </status></manifest>

What it is

Two consoles, on purpose

How it talks to the endpoints

What the licence level decides

What it is

Two consoles, on purpose

How it talks to the endpoints

What the licence level decides

What it is

Two consoles, on purpose

How it talks to the endpoints

What the licence level decides

What it is

Two consoles, on purpose

How it talks to the endpoints

What the licence level decides

Universal Management Suite UMS

What it is

Two consoles, on purpose

How it talks to the endpoints

What the licence level decides

What we do with it

Posts about it

Boot IGEL UD Pocket – Required BIOS/UEFI Settings

Fix Workspace ONE Admin Assistant Parsing Failures on macOS

Enterprise Wipe vs. Device Wipe vs. Unenroll vs. Delete Device in Workspace ONE UEM

Enroll Windows Server 2025 in Omnissa Workspace ONE UEM

Send Workspace ONE Hub Notifications to All Users

Intelligent Hub on macOS Not Synchronizing After an Active Directory User Name Change

Who works with it

Valentina Cicmak