DE · EN

Call us

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: igel/igel-onboarding-service locale: en labels: vendor: IGEL Onboarding Service capability/modern-workplace: 1.72 capability/automation: 1.83 capability/managed-services: 2.90 vendor/igel: 3.14 annotations: source: src/content/solutions/en/igel/igel-onboarding-service.md route: /en/solutions/igel/igel-onboarding-service/ schema: /nerd/schema/solutions.json markdown: /en/solutions/igel/igel-onboarding-service.mdspec: title: Onboarding Service tags: [modern-workplace, automation, managed-services] vendors: [igel] summary: >- A device finds its own management server on first boot. Nobody has to configure it, and nobody has to be in the same building as it. 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 vendorName: IGEL Onboarding Service status: current practice: >- Draft, not yet reviewed. This is the piece that decides whether a remote rollout is a courier job or a project. We test it with one device on a home connection before ordering the batch, because the failure modes are all network and none of them show up in the lab. practiceReview: true sections: - heading:

What it is

body: | On first boot a device contacts the Onboarding Service and is told which UMS or cloud environment it belongs to. The person in front of it signs in with their company credentials, and that registration is what assigns the device to its configuration, policies and group. Everything else follows automatically: policies, network configuration, certificates, software packages. - heading:

What it is for

body: | Shipping hardware to people instead of to a staging bench. A device can go straight from the distributor to a home office and arrive managed, which is the difference between a remote rollout and a lot of driving. It is equally the answer for a site with no IT staff, which is most branch offices. - heading:

What to watch

body: | The device has to reach the service before it is anything at all, so the failure modes are network ones: captive portals in hotels, a home router with an unusual DNS, a firewall rule nobody remembers writing. None of those appear on a test bench with a wired connection.status: corpus: 309 services: - {ref: services/service-desk, score: 0.46} - {ref: services/managed-service, score: 0.37} - {ref: services/monitoring, score: 0.37} - {ref: services/platform, score: 0.31} posts: - {ref: posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change, score: 0.54} - {ref: posts/how-to-igel-ud-pocket-bios-uefi-settings, score: 0.34} - {ref: posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos, score: 0.34} - {ref: posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem, score: 0.34} - {ref: posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem, score: 0.34} - {ref: posts/send-workspace-one-hub-notifications, score: 0.34} experts: - {ref: experts/valentina-cicmak, score: 0.25} - {ref: experts/mike-schmid, score: 0.21} neighbours: - {ref: solutions/omnissa/workspace-one/workspace-one-itsm-connector, score: 0.70} - {ref: solutions/igel/igel-app-portal, score: 0.69} - {ref: solutions/igel/addon/igel-ums-as-a-service, score: 0.68}

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "igel/igel-onboarding-service", "locale": "en", "labels": { "vendor": "IGEL Onboarding Service", "capability/modern-workplace": "1.72", "capability/automation": "1.83", "capability/managed-services": "2.90", "vendor/igel": "3.14" }, "annotations": { "source": "src/content/solutions/en/igel/igel-onboarding-service.md", "route": "/en/solutions/igel/igel-onboarding-service/", "schema": "/nerd/schema/solutions.json", "markdown": "/en/solutions/igel/igel-onboarding-service.md" } }, "spec": { "title": "Onboarding Service", "tags": [ "modern-workplace", "automation", "managed-services" ], "vendors": [ "igel" ], "summary": "A device finds its own management server on first boot. Nobody has to configure it, and nobody has to be in the same building as it.", "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", "vendorName": "IGEL Onboarding Service", "status": "current", "practice": "Draft, not yet reviewed. This is the piece that decides whether a remote rollout is a courier job or a project. We test it with one device on a home connection before ordering the batch, because the failure modes are all network and none of them show up in the lab.\n", "practiceReview": true }, "sections": [ { "heading": "

What it is

", "body": "On first boot a device contacts the Onboarding Service and is told which UMS or cloud\nenvironment it belongs to. The person in front of it signs in with their company\ncredentials, and that registration is what assigns the device to its configuration,\npolicies and group.\n\nEverything else follows automatically: policies, network configuration, certificates,\nsoftware packages." }, { "heading": "

What it is for

", "body": "Shipping hardware to people instead of to a staging bench. A device can go straight from\nthe distributor to a home office and arrive managed, which is the difference between a\nremote rollout and a lot of driving.\n\nIt is equally the answer for a site with no IT staff, which is most branch offices." }, { "heading": "

What to watch

", "body": "The device has to reach the service before it is anything at all, so the failure modes are\nnetwork ones: captive portals in hotels, a home router with an unusual DNS, a firewall rule\nnobody remembers writing. None of those appear on a test bench with a wired connection." } ], "status": { "corpus": 309, "services": [ { "ref": "services/service-desk", "score": "0.46" }, { "ref": "services/managed-service", "score": "0.37" }, { "ref": "services/monitoring", "score": "0.37" }, { "ref": "services/platform", "score": "0.31" } ], "posts": [ { "ref": "posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change", "score": "0.54" }, { "ref": "posts/how-to-igel-ud-pocket-bios-uefi-settings", "score": "0.34" }, { "ref": "posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos", "score": "0.34" }, { "ref": "posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem", "score": "0.34" }, { "ref": "posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem", "score": "0.34" }, { "ref": "posts/send-workspace-one-hub-notifications", "score": "0.34" } ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.25" }, { "ref": "experts/mike-schmid", "score": "0.21" } ], "neighbours": [ { "ref": "solutions/omnissa/workspace-one/workspace-one-itsm-connector", "score": "0.70" }, { "ref": "solutions/igel/igel-app-portal", "score": "0.69" }, { "ref": "solutions/igel/addon/igel-ums-as-a-service", "score": "0.68" } ] }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "igel/igel-onboarding-service"locale = "en"[metadata.labels]vendor = "IGEL Onboarding Service""capability/modern-workplace" = "1.72""capability/automation" = "1.83""capability/managed-services" = "2.90""vendor/igel" = "3.14"[metadata.annotations]source = "src/content/solutions/en/igel/igel-onboarding-service.md"route = "/en/solutions/igel/igel-onboarding-service/"schema = "/nerd/schema/solutions.json"markdown = "/en/solutions/igel/igel-onboarding-service.md"[spec]title = "Onboarding Service"tags = ["modern-workplace", "automation", "managed-services"]vendors = ["igel"]summary = "A device finds its own management server on first boot. Nobody has to configure it, and nobody has to be in the same building as it."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"vendorName = "IGEL Onboarding Service"status = "current"practice = '''Draft, not yet reviewed. This is the piece that decides whether a remote rollout is a courier job or a project. We test it with one device on a home connection before ordering the batch, because the failure modes are all network and none of them show up in the lab.'''practiceReview = true[[sections]]heading = "

What it is

"body = '''On first boot a device contacts the Onboarding Service and is told which UMS or cloudenvironment it belongs to. The person in front of it signs in with their companycredentials, and that registration is what assigns the device to its configuration,policies and group.Everything else follows automatically: policies, network configuration, certificates,software packages.'''[[sections]]heading = "

What it is for

"body = '''Shipping hardware to people instead of to a staging bench. A device can go straight fromthe distributor to a home office and arrive managed, which is the difference between aremote rollout and a lot of driving.It is equally the answer for a site with no IT staff, which is most branch offices.'''[[sections]]heading = "

What to watch

"body = '''The device has to reach the service before it is anything at all, so the failure modes arenetwork ones: captive portals in hotels, a home router with an unusual DNS, a firewall rulenobody remembers writing. None of those appear on a test bench with a wired connection.'''[status]corpus = 309[[status.services]]ref = "services/service-desk"score = "0.46"[[status.services]]ref = "services/managed-service"score = "0.37"[[status.services]]ref = "services/monitoring"score = "0.37"[[status.services]]ref = "services/platform"score = "0.31"[[status.posts]]ref = "posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change"score = "0.54"[[status.posts]]ref = "posts/how-to-igel-ud-pocket-bios-uefi-settings"score = "0.34"[[status.posts]]ref = "posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos"score = "0.34"[[status.posts]]ref = "posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem"score = "0.34"[[status.posts]]ref = "posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem"score = "0.34"[[status.posts]]ref = "posts/send-workspace-one-hub-notifications"score = "0.34"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.25"[[status.experts]]ref = "experts/mike-schmid"score = "0.21"[[status.neighbours]]ref = "solutions/omnissa/workspace-one/workspace-one-itsm-connector"score = "0.70"[[status.neighbours]]ref = "solutions/igel/igel-app-portal"score = "0.69"[[status.neighbours]]ref = "solutions/igel/addon/igel-ums-as-a-service"score = "0.68"

<?xml version="1.0" encoding="UTF-8"?><manifest kind="Solution"> <apiVersion>soultec.ch/v1</apiVersion> <metadata> <name>igel/igel-onboarding-service</name> <locale>en</locale> <labels> <vendor>IGEL Onboarding Service</vendor> <entry key="capability/modern-workplace">1.72</entry> <entry key="capability/automation">1.83</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-onboarding-service.md</source> <route>/en/solutions/igel/igel-onboarding-service/</route> <schema>/nerd/schema/solutions.json</schema> <markdown>/en/solutions/igel/igel-onboarding-service.md</markdown> </annotations> </metadata> <spec> <title>Onboarding Service</title> <tags> <item>modern-workplace</item> <item>automation</item> <item>managed-services</item> </tags> <vendors> <item>igel</item> </vendors> <summary>A device finds its own management server on first boot. Nobody has to configure it, and nobody has to be in the same building as it.</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</sourceNote> <vendorName>IGEL Onboarding Service</vendorName> <status>current</status> <practice>Draft, not yet reviewed. This is the piece that decides whether a remote rollout is a courier job or a project. We test it with one device on a home connection before ordering the batch, because the failure modes are all network and none of them show up in the lab. </practice> <practiceReview>true</practiceReview> </spec> <sections> <section> <heading>

What it is

</heading> <body>On first boot a device contacts the Onboarding Service and is told which UMS or cloudenvironment it belongs to. The person in front of it signs in with their companycredentials, and that registration is what assigns the device to its configuration,policies and group.Everything else follows automatically: policies, network configuration, certificates,software packages. </body> </section> <section> <heading>

What it is for

</heading> <body>Shipping hardware to people instead of to a staging bench. A device can go straight fromthe distributor to a home office and arrive managed, which is the difference between aremote rollout and a lot of driving.It is equally the answer for a site with no IT staff, which is most branch offices. </body> </section> <section> <heading>

What to watch

</heading> <body>The device has to reach the service before it is anything at all, so the failure modes arenetwork ones: captive portals in hotels, a home router with an unusual DNS, a firewall rulenobody remembers writing. None of those appear on a test bench with a wired connection. </body> </section> </sections> <status> <corpus>309</corpus> <services> <item> <ref>services/service-desk</ref> <score>0.46</score> </item> <item> <ref>services/managed-service</ref> <score>0.37</score> </item> <item> <ref>services/monitoring</ref> <score>0.37</score> </item> <item> <ref>services/platform</ref> <score>0.31</score> </item> </services> <posts> <item> <ref>posts/how-to-intelligent-hub-macos-not-synchronizing-after-active-directory-user-name-change</ref> <score>0.54</score> </item> <item> <ref>posts/how-to-igel-ud-pocket-bios-uefi-settings</ref> <score>0.34</score> </item> <item> <ref>posts/how-to-fix-workspace-one-admin-assistant-parsing-failed-macos</ref> <score>0.34</score> </item> <item> <ref>posts/how-to-enterprise-wipe-vs-device-wipe-vs-unenroll-vs-delete-device-in-workspace-one-uem</ref> <score>0.34</score> </item> <item> <ref>posts/how-to-enroll-windows-server-2025-in-omnissa-workspace-one-uem</ref> <score>0.34</score> </item> <item> <ref>posts/send-workspace-one-hub-notifications</ref> <score>0.34</score> </item> </posts> <experts> <item> <ref>experts/valentina-cicmak</ref> <score>0.25</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.21</score> </item> </experts> <neighbours> <item> <ref>solutions/omnissa/workspace-one/workspace-one-itsm-connector</ref> <score>0.70</score> </item> <item> <ref>solutions/igel/igel-app-portal</ref> <score>0.69</score> </item> <item> <ref>solutions/igel/addon/igel-ums-as-a-service</ref> <score>0.68</score> </item> </neighbours> </status></manifest>

Solution · IGEL

Onboarding Service

The vendor calls it: IGEL Onboarding Service

A device finds its own management server on first boot. Nobody has to configure it, and nobody has to be in the same building as it.

Topics Modern Workplace 1.72 Automation 1.83 Managed Services 2.90

Vendors IGEL 3.14

04Services

06Posts

03Capabilities

309Corpus

photograph wantedAn IGEL endpoint in place: a UD Pocket in a laptop, or a thin client at a working desk

What it is

On first boot a device contacts the Onboarding Service and is told which UMS or cloud environment it belongs to. The person in front of it signs in with their company credentials, and that registration is what assigns the device to its configuration, policies and group.

Everything else follows automatically: policies, network configuration, certificates, software packages.

What it is for

Shipping hardware to people instead of to a staging bench. A device can go straight from the distributor to a home office and arrive managed, which is the difference between a remote rollout and a lot of driving.

It is equally the answer for a site with no IT staff, which is most branch offices.

What to watch

The device has to reach the service before it is anything at all, so the failure modes are network ones: captive portals in hotels, a home router with an unusual DNS, a firewall rule nobody remembers writing. None of those appear on a test bench with a wired connection.

What we do with it

Draft, unreviewed

Draft, not yet reviewed. This is the piece that decides whether a remote rollout is a courier job or a project. We test it with one device on a home connection before ordering the batch, because the failure modes are all network and none of them show up in the lab.

This paragraph is a draft and nobody at soulTec has confirmed it yet. Everything above it describes the product and is checkable against the vendor.

Posts about it

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

14 Jul 2026

After changing a user's name in Active Directory, the new information may already be visible in Workspace ONE UEM and Omnissa Access while Intelligent Hub on the Mac still displays the old name.

Automation 1.83 Modern Workplace 1.72

Boot IGEL UD Pocket – Required BIOS/UEFI Settings

14 Aug 2026

The IGEL UD Pocket allows IGEL OS to run directly from a USB device without replacing the operating system installed on the computer.

Modern Workplace 1.72

Fix Workspace ONE Admin Assistant Parsing Failures on macOS

7 Aug 2026

When using Omnissa Workspace ONE Admin Assistant on macOS, parsing can fail even if the application file itself is valid. One possible cause is a missing macOS privacy permission.

Modern Workplace 1.72