App Portal

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: igel/igel-app-portal locale: en labels: vendor: IGEL App Portal capability/modern-workplace: 1.72 capability/automation: 1.83 vendor/igel: 3.14 annotations: source: src/content/solutions/en/igel/igel-app-portal.md route: /en/solutions/igel/igel-app-portal/ schema: /nerd/schema/solutions.json markdown: /en/solutions/igel/igel-app-portal.mdspec: title: App Portal tags: [modern-workplace, automation] vendors: [igel] summary: >- IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system. 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 addon: false sourceNote: >- soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day vendorName: IGEL App Portal status: current sections: - heading:

What it is

body: | The App Portal is where the applications come from. IGEL OS 12's base image deliberately contains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktop client and the browsers are all selected in the portal and pushed to devices or device groups from there. It is part of the IGEL cloud services rather than something you install. - heading:

Why the split matters

body: | Applications are delivered as containers, managed apart from the operating system. So a client update is a package update, not an OS release, and the two stop being scheduled against each other. That is the actual argument for IGEL OS 12 over 11 in an estate where the VDI client version is dictated by someone else's upgrade calendar. - heading:

What to watch

body: | An estate with no route to the internet does not reach the portal. IGEL's answer is the distributed app repository, where devices pull packages from a local server instead, and that is an Enterprise-licence feature. There is also peer update, where a device pulls from another device on the same network, and that one is in every edition. Which of the two you need is an air-gap question, and it belongs in the design.status: corpus: 309 services: - {ref: services/platform, score: 0.41} posts: - {ref: posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change, score: 0.85} - {ref: posts/how-to-igel-ud-pocket-bios-uefi-settings, score: 0.49} - {ref: posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos, score: 0.49} - {ref: posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem, score: 0.49} - {ref: posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem, score: 0.49} - {ref: posts/send-workspace-one-hub-notifications, score: 0.49} neighbours: - {ref: solutions/microsoft/easylife-365-collaboration, score: 0.70} - {ref: solutions/omnissa/omnissa-freestyle-orchestrator, score: 0.70} - {ref: solutions/igel/igel-onboarding-service, score: 0.69}

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "igel/igel-app-portal", "locale": "en", "labels": { "vendor": "IGEL App Portal", "capability/modern-workplace": "1.72", "capability/automation": "1.83", "vendor/igel": "3.14" }, "annotations": { "source": "src/content/solutions/en/igel/igel-app-portal.md", "route": "/en/solutions/igel/igel-app-portal/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/igel/igel-app-portal.md" } }, "spec": { "title": "App Portal", "tags": [ "modern-workplace", "automation" ], "vendors": [ "igel" ], "summary": "IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system.", "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", "addon": false, "sourceNote": "soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day", "vendorName": "IGEL App Portal", "status": "current" }, "sections": [ { "heading": "

What it is

", "body": "The App Portal is where the applications come from. IGEL OS 12's base image deliberately\ncontains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktop\nclient and the browsers are all selected in the portal and pushed to devices or device\ngroups from there.\n\nIt is part of the IGEL cloud services rather than something you install." }, { "heading": "

Why the split matters

", "body": "Applications are delivered as containers, managed apart from the operating system. So a\nclient update is a package update, not an OS release, and the two stop being scheduled\nagainst each other.\n\nThat is the actual argument for IGEL OS 12 over 11 in an estate where the VDI client\nversion is dictated by someone else's upgrade calendar." }, { "heading": "

What to watch

", "body": "An estate with no route to the internet does not reach the portal. IGEL's answer is the\ndistributed app repository, where devices pull packages from a local server instead, and\nthat is an Enterprise-licence feature. There is also peer update, where a device pulls from\nanother device on the same network, and that one is in every edition.\n\nWhich of the two you need is an air-gap question, and it belongs in the design." } ], "status": { "corpus": 309, "services": [ { "ref": "services/platform", "score": "0.41" } ], "posts": [ { "ref": "posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change", "score": "0.85" }, { "ref": "posts/how-to-igel-ud-pocket-bios-uefi-settings", "score": "0.49" }, { "ref": "posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos", "score": "0.49" }, { "ref": "posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem", "score": "0.49" }, { "ref": "posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem", "score": "0.49" }, { "ref": "posts/send-workspace-one-hub-notifications", "score": "0.49" } ], "neighbours": [ { "ref": "solutions/microsoft/easylife-365-collaboration", "score": "0.70" }, { "ref": "solutions/omnissa/omnissa-freestyle-orchestrator", "score": "0.70" }, { "ref": "solutions/igel/igel-onboarding-service", "score": "0.69" } ] }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "igel/igel-app-portal"locale = "en"[metadata.labels]vendor = "IGEL App Portal""capability/modern-workplace" = "1.72""capability/automation" = "1.83""vendor/igel" = "3.14"[metadata.annotations]source = "src/content/solutions/en/igel/igel-app-portal.md"route = "/en/solutions/igel/igel-app-portal/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/igel/igel-app-portal.md"[spec]title = "App Portal"tags = ["modern-workplace", "automation"]vendors = ["igel"]summary = "IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system."photoNeed = "An IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk"stub = falsedraft = falsekind = "product"addon = falsesourceNote = "soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day"vendorName = "IGEL App Portal"status = "current"[[sections]]heading = "

What it is

"body = '''The App Portal is where the applications come from. IGEL OS 12's base image deliberatelycontains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktopclient and the browsers are all selected in the portal and pushed to devices or devicegroups from there.It is part of the IGEL cloud services rather than something you install.'''[[sections]]heading = "

Why the split matters

"body = '''Applications are delivered as containers, managed apart from the operating system. So aclient update is a package update, not an OS release, and the two stop being scheduledagainst each other.That is the actual argument for IGEL OS 12 over 11 in an estate where the VDI clientversion is dictated by someone else's upgrade calendar.'''[[sections]]heading = "

What to watch

"body = '''An estate with no route to the internet does not reach the portal. IGEL's answer is thedistributed app repository, where devices pull packages from a local server instead, andthat is an Enterprise-licence feature. There is also peer update, where a device pulls fromanother device on the same network, and that one is in every edition.Which of the two you need is an air-gap question, and it belongs in the design.'''[status]corpus = 309[[status.services]]ref = "services/platform"score = "0.41"[[status.posts]]ref = "posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change"score = "0.85"[[status.posts]]ref = "posts/how-to-igel-ud-pocket-bios-uefi-settings"score = "0.49"[[status.posts]]ref = "posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos"score = "0.49"[[status.posts]]ref = "posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem"score = "0.49"[[status.posts]]ref = "posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem"score = "0.49"[[status.posts]]ref = "posts/send-workspace-one-hub-notifications"score = "0.49"[[status.neighbours]]ref = "solutions/microsoft/easylife-365-collaboration"score = "0.70"[[status.neighbours]]ref = "solutions/omnissa/omnissa-freestyle-orchestrator"score = "0.70"[[status.neighbours]]ref = "solutions/igel/igel-onboarding-service"score = "0.69"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>igel/igel-app-portal</name> <locale>en</locale> <labels> <vendor>IGEL App Portal</vendor> <entry key="capability/modern-workplace">1.72</entry> <entry key="capability/automation">1.83</entry> <entry key="vendor/igel">3.14</entry> </labels> <annotations> <source>src/content/solutions/en/igel/igel-app-portal.md</source> <route>/en/solutions/igel/igel-app-portal/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/igel/igel-app-portal.md</markdown> </annotations> </metadata> <spec> <title>App Portal</title> <tags> <item>modern-workplace</item> <item>automation</item> </tags> <vendors> <item>igel</item> </vendors> <summary>IGEL OS 12 ships with no applications. Everything a person uses arrives from here as a package, and updates without touching the operating system.</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> <addon>false</addon> <sourceNote>soultec.ch/solutions/igel, read 2026-08-30; igel.com product navigation, same day</sourceNote> <vendorName>IGEL App Portal</vendorName> <status>current</status> </spec> <sections> <section> <heading>

What it is

</heading> <body>The App Portal is where the applications come from. IGEL OS 12's base image deliberatelycontains none, so the Citrix client, the Omnissa Horizon client, the Azure Virtual Desktopclient and the browsers are all selected in the portal and pushed to devices or devicegroups from there.It is part of the IGEL cloud services rather than something you install. </body> </section> <section> <heading>

Why the split matters

</heading> <body>Applications are delivered as containers, managed apart from the operating system. So aclient update is a package update, not an OS release, and the two stop being scheduledagainst each other.That is the actual argument for IGEL OS 12 over 11 in an estate where the VDI clientversion is dictated by someone else's upgrade calendar. </body> </section> <section> <heading>

What to watch

</heading> <body>An estate with no route to the internet does not reach the portal. IGEL's answer is thedistributed app repository, where devices pull packages from a local server instead, andthat is an Enterprise-licence feature. There is also peer update, where a device pulls fromanother device on the same network, and that one is in every edition.Which of the two you need is an air-gap question, and it belongs in the design. </body> </section> </sections> <status> <corpus>309</corpus> <services> <item> <ref>services/platform</ref> <score>0.41</score> </item> </services> <posts> <item> <ref>posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change</ref> <score>0.85</score> </item> <item> <ref>posts/how-to-igel-ud-pocket-bios-uefi-settings</ref> <score>0.49</score> </item> <item> <ref>posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos</ref> <score>0.49</score> </item> <item> <ref>posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem</ref> <score>0.49</score> </item> <item> <ref>posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem</ref> <score>0.49</score> </item> <item> <ref>posts/send-workspace-one-hub-notifications</ref> <score>0.49</score> </item> </posts> <neighbours> <item> <ref>solutions/microsoft/easylife-365-collaboration</ref> <score>0.70</score> </item> <item> <ref>solutions/omnissa/omnissa-freestyle-orchestrator</ref> <score>0.70</score> </item> <item> <ref>solutions/igel/igel-onboarding-service</ref> <score>0.69</score> </item> </neighbours> </status></manifest>

What it is

Why the split matters

What to watch

What it is

Why the split matters

What to watch

What it is

Why the split matters

What to watch

What it is

Why the split matters

What to watch

What it is

Why the split matters

What to watch

Posts about it

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

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

Who works with it