DE · EN

Call us

build 6ddc7a35 | content blog-content@417154f · 338 posts | profiles 32 · corpus 315 | ● 0 skipped | built 2026-10-21 12:35 UTC format run

$ soultec get solution/igel/igel-onboarding-service -o yaml$ soultec get solution/igel/igel-onboarding-service -o json$ soultec get solution/igel/igel-onboarding-service -o toml$ soultec get solution/igel/igel-onboarding-service -o xml$ python3 igel/igel-onboarding-service.pyPS> ./igel/igel-onboarding-service.ps1$ go run igel/igel-onboarding-service.go$ node igel/igel-onboarding-service.js

apiVersion: soultec.ch/v1kind: Solutionmetadata: name: igel/igel-onboarding-service locale: en labels: vendor: IGEL Onboarding Service capability/modern-workplace: 1.69 capability/automation: 1.81 capability/managed-services: 2.65 vendor/igel: 3.03 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. We test the service with one device on a home connection before ordering the batch, because the failure modes are all network ones. 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: | A device can go straight from the distributor to a home office and arrive managed. 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 gets its configuration, so the failure modes are all network ones: captive portals in hotels, a home router with an unusual DNS, a firewall rule nobody remembers writing.status: corpus: 315 services: - {ref: services/service-desk, score: 0.45} - {ref: services/managed-service, score: 0.37} - {ref: services/monitoring, score: 0.37} - {ref: services/lizenzmanagement, score: 0.36} experts: - {ref: experts/valentina-cicmak, score: 0.50} - {ref: experts/michael-steg, score: 0.39} - {ref: experts/mike-schmid, score: 0.21} neighbours: - {ref: solutions/igel, relation: parent} - {ref: solutions/igel/igel-app-portal, score: 0.70} - {ref: solutions/omnissa/workspace-one/workspace-one-itsm-connector, score: 0.70} - {ref: solutions/igel/addon/igel-ums-as-a-service, score: 0.68} search: /en/search.json

{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "igel/igel-onboarding-service", "locale": "en", "labels": { "vendor": "IGEL Onboarding Service", "capability/modern-workplace": 1.69, "capability/automation": 1.81, "capability/managed-services": 2.65, "vendor/igel": 3.03 }, "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. We test the service with one device on a home connection before ordering the batch, because the failure modes are all network ones.\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": "A device can go straight from the distributor to a home office and arrive managed.\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 gets its configuration, so the failure modes\nare all network ones: captive portals in hotels, a home router with an unusual DNS, a\nfirewall rule nobody remembers writing." } ] }, "status": { "corpus": 315, "services": [ { "ref": "services/service-desk", "score": "0.45" }, { "ref": "services/managed-service", "score": "0.37" }, { "ref": "services/monitoring", "score": "0.37" }, { "ref": "services/lizenzmanagement", "score": "0.36" } ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.50" }, { "ref": "experts/michael-steg", "score": "0.39" }, { "ref": "experts/mike-schmid", "score": "0.21" } ], "neighbours": [ { "ref": "solutions/igel", "relation": "parent" }, { "ref": "solutions/igel/igel-app-portal", "score": "0.70" }, { "ref": "solutions/omnissa/workspace-one/workspace-one-itsm-connector", "score": "0.70" }, { "ref": "solutions/igel/addon/igel-ums-as-a-service", "score": "0.68" } ], "search": "/en/search.json" }}

apiVersion = "soultec.ch/v1"kind = "Solution"[metadata]name = "igel/igel-onboarding-service"locale = "en"[metadata.labels]vendor = "IGEL Onboarding Service""capability/modern-workplace" = 1.69"capability/automation" = 1.81"capability/managed-services" = 2.65"vendor/igel" = 3.03[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. We test the service with one device on a home connection before ordering the batch, because the failure modes are all network ones.'''practiceReview = true[[spec.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.'''[[spec.sections]]heading = "

What it is for

"body = '''A device can go straight from the distributor to a home office and arrive managed.It is equally the answer for a site with no IT staff, which is most branch offices.'''[[spec.sections]]heading = "

What to watch

"body = '''The device has to reach the service before it gets its configuration, so the failure modesare all network ones: captive portals in hotels, a home router with an unusual DNS, afirewall rule nobody remembers writing.'''[status]corpus = 315search = "/en/search.json"[[status.services]]ref = "services/service-desk"score = "0.45"[[status.services]]ref = "services/managed-service"score = "0.37"[[status.services]]ref = "services/monitoring"score = "0.37"[[status.services]]ref = "services/lizenzmanagement"score = "0.36"[[status.experts]]ref = "experts/valentina-cicmak"score = "0.50"[[status.experts]]ref = "experts/michael-steg"score = "0.39"[[status.experts]]ref = "experts/mike-schmid"score = "0.21"[[status.neighbours]]ref = "solutions/igel"relation = "parent"[[status.neighbours]]ref = "solutions/igel/igel-app-portal"score = "0.70"[[status.neighbours]]ref = "solutions/omnissa/workspace-one/workspace-one-itsm-connector"score = "0.70"[[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.69</entry> <entry key="capability/automation">1.81</entry> <entry key="capability/managed-services">2.65</entry> <entry key="vendor/igel">3.03</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. We test the service with one device on a home connection before ordering the batch, because the failure modes are all network ones. </practice> <practiceReview>true</practiceReview> <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>A device can go straight from the distributor to a home office and arrive managed.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 gets its configuration, so the failure modesare all network ones: captive portals in hotels, a home router with an unusual DNS, afirewall rule nobody remembers writing. </body> </section> </sections> </spec> <status> <corpus>315</corpus> <services> <item> <ref>services/service-desk</ref> <score>0.45</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/lizenzmanagement</ref> <score>0.36</score> </item> </services> <experts> <item> <ref>experts/valentina-cicmak</ref> <score>0.50</score> </item> <item> <ref>experts/michael-steg</ref> <score>0.39</score> </item> <item> <ref>experts/mike-schmid</ref> <score>0.21</score> </item> </experts> <neighbours> <item> <ref>solutions/igel</ref> <relation>parent</relation> </item> <item> <ref>solutions/igel/igel-app-portal</ref> <score>0.70</score> </item> <item> <ref>solutions/omnissa/workspace-one/workspace-one-itsm-connector</ref> <score>0.70</score> </item> <item> <ref>solutions/igel/addon/igel-ums-as-a-service</ref> <score>0.68</score> </item> </neighbours> <search>/en/search.json</search> </status></manifest>

# Code generated by the soultec.ch build. DO NOT EDIT.import jsonPAGE = { "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": { "name": "igel/igel-onboarding-service", "locale": "en", "labels": { "vendor": "IGEL Onboarding Service", "capability/modern-workplace": 1.69, "capability/automation": 1.81, "capability/managed-services": 2.65, "vendor/igel": 3.03, }, "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. We test the service with one device on a home connection before ordering the batch, because the failure modes are all network ones.\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\n" "environment it belongs to. The person in front of it signs in with their company\n" "credentials, and that registration is what assigns the device to its configuration,\n" "policies and group.\n" "\n" "Everything else follows automatically: policies, network configuration, certificates,\n" "software packages." ), }, { "heading": "

What it is for

", "body": ( "A device can go straight from the distributor to a home office and arrive managed.\n" "\n" "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 gets its configuration, so the failure modes\n" "are all network ones: captive portals in hotels, a home router with an unusual DNS, a\n" "firewall rule nobody remembers writing." ), }, ], }, "status": { "corpus": 315, "services": [ { "ref": "services/service-desk", "score": "0.45", }, { "ref": "services/managed-service", "score": "0.37", }, { "ref": "services/monitoring", "score": "0.37", }, { "ref": "services/lizenzmanagement", "score": "0.36", }, ], "experts": [ { "ref": "experts/valentina-cicmak", "score": "0.50", }, { "ref": "experts/michael-steg", "score": "0.39", }, { "ref": "experts/mike-schmid", "score": "0.21", }, ], "neighbours": [ { "ref": "solutions/igel", "relation": "parent", }, { "ref": "solutions/igel/igel-app-portal", "score": "0.70", }, { "ref": "solutions/omnissa/workspace-one/workspace-one-itsm-connector", "score": "0.70", }, { "ref": "solutions/igel/addon/igel-ums-as-a-service", "score": "0.68", }, ], "search": "/en/search.json", },}if __name__ == "__main__": print(json.dumps(PAGE, indent=2, ensure_ascii=False))

# Code generated by the soultec.ch build. DO NOT EDIT.$Page = [ordered]@{ apiVersion = 'soultec.ch/v1' kind = 'Solution' metadata = [ordered]@{ name = 'igel/igel-onboarding-service' locale = 'en' labels = [ordered]@{ vendor = 'IGEL Onboarding Service' 'capability/modern-workplace' = 1.69 'capability/automation' = 1.81 'capability/managed-services' = 2.65 'vendor/igel' = 3.03 } annotations = [ordered]@{ 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 = [ordered]@{ 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. We test the service with one device on a home connection before ordering the batch, because the failure modes are all network ones.'@ practiceReview = $true sections = @( [ordered]@{ 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.'@ } [ordered]@{ heading = '

What it is for

' body = @'A device can go straight from the distributor to a home office and arrive managed.It is equally the answer for a site with no IT staff, which is most branch offices.'@ } [ordered]@{ heading = '

What to watch

' body = @'The device has to reach the service before it gets its configuration, so the failure modesare all network ones: captive portals in hotels, a home router with an unusual DNS, afirewall rule nobody remembers writing.'@ } ) } status = [ordered]@{ corpus = 315 services = @( [ordered]@{ ref = 'services/service-desk' score = '0.45' } [ordered]@{ ref = 'services/managed-service' score = '0.37' } [ordered]@{ ref = 'services/monitoring' score = '0.37' } [ordered]@{ ref = 'services/lizenzmanagement' score = '0.36' } ) experts = @( [ordered]@{ ref = 'experts/valentina-cicmak' score = '0.50' } [ordered]@{ ref = 'experts/michael-steg' score = '0.39' } [ordered]@{ ref = 'experts/mike-schmid' score = '0.21' } ) neighbours = @( [ordered]@{ ref = 'solutions/igel' relation = 'parent' } [ordered]@{ ref = 'solutions/igel/igel-app-portal' score = '0.70' } [ordered]@{ ref = 'solutions/omnissa/workspace-one/workspace-one-itsm-connector' score = '0.70' } [ordered]@{ ref = 'solutions/igel/addon/igel-ums-as-a-service' score = '0.68' } ) search = '/en/search.json' }}$Page | ConvertTo-Json -Depth 32

// Code generated by the soultec.ch build. DO NOT EDIT.package mainimport ( "encoding/json" "os")var page = map[string]any{ "apiVersion": "soultec.ch/v1", "kind": "Solution", "metadata": map[string]any{ "name": "igel/igel-onboarding-service", "locale": "en", "labels": map[string]any{ "vendor": "IGEL Onboarding Service", "capability/modern-workplace": 1.69, "capability/automation": 1.81, "capability/managed-services": 2.65, "vendor/igel": 3.03, }, "annotations": map[string]any{ "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": map[string]any{ "title": "Onboarding Service", "tags": []any{"modern-workplace", "automation", "managed-services"}, "vendors": []any{"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. We test the service with one device on a home connection before ordering the batch, because the failure modes are all network ones.\n", "practiceReview": true, "sections": []any{ map[string]any{ "heading": "

What it is

", "body": "On first boot a device contacts the Onboarding Service and is told which UMS or cloud\n" + "environment it belongs to. The person in front of it signs in with their company\n" + "credentials, and that registration is what assigns the device to its configuration,\n" + "policies and group.\n" + "\n" + "Everything else follows automatically: policies, network configuration, certificates,\n" + "software packages.", }, map[string]any{ "heading": "

What it is for

", "body": "A device can go straight from the distributor to a home office and arrive managed.\n" + "\n" + "It is equally the answer for a site with no IT staff, which is most branch offices.", }, map[string]any{ "heading": "

What to watch

", "body": "The device has to reach the service before it gets its configuration, so the failure modes\n" + "are all network ones: captive portals in hotels, a home router with an unusual DNS, a\n" + "firewall rule nobody remembers writing.", }, }, }, "status": map[string]any{ "corpus": 315, "services": []any{ map[string]any{ "ref": "services/service-desk", "score": "0.45", }, map[string]any{ "ref": "services/managed-service", "score": "0.37", }, map[string]any{ "ref": "services/monitoring", "score": "0.37", }, map[string]any{ "ref": "services/lizenzmanagement", "score": "0.36", }, }, "experts": []any{ map[string]any{ "ref": "experts/valentina-cicmak", "score": "0.50", }, map[string]any{ "ref": "experts/michael-steg", "score": "0.39", }, map[string]any{ "ref": "experts/mike-schmid", "score": "0.21", }, }, "neighbours": []any{ map[string]any{ "ref": "solutions/igel", "relation": "parent", }, map[string]any{ "ref": "solutions/igel/igel-app-portal", "score": "0.70", }, map[string]any{ "ref": "solutions/omnissa/workspace-one/workspace-one-itsm-connector", "score": "0.70", }, map[string]any{ "ref": "solutions/igel/addon/igel-ums-as-a-service", "score": "0.68", }, }, "search": "/en/search.json", },}func main() { enc := json.NewEncoder(os.Stdout) enc.SetEscapeHTML(false) enc.SetIndent("", " ") if err := enc.Encode(page); err != nil { os.Exit(1) }}

// Code generated by the soultec.ch build. DO NOT EDIT.const page = { apiVersion: "soultec.ch/v1", kind: "Solution", metadata: { name: "igel/igel-onboarding-service", locale: "en", labels: { vendor: "IGEL Onboarding Service", "capability/modern-workplace": 1.69, "capability/automation": 1.81, "capability/managed-services": 2.65, "vendor/igel": 3.03, }, 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. We test the service with one device on a home connection before ordering the batch, because the failure modes are all network ones.\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\n" + "environment it belongs to. The person in front of it signs in with their company\n" + "credentials, and that registration is what assigns the device to its configuration,\n" + "policies and group.\n" + "\n" + "Everything else follows automatically: policies, network configuration, certificates,\n" + "software packages.", }, { heading: "

What it is for

", body: "A device can go straight from the distributor to a home office and arrive managed.\n" + "\n" + "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 gets its configuration, so the failure modes\n" + "are all network ones: captive portals in hotels, a home router with an unusual DNS, a\n" + "firewall rule nobody remembers writing.", }, ], }, status: { corpus: 315, services: [ { ref: "services/service-desk", score: "0.45", }, { ref: "services/managed-service", score: "0.37", }, { ref: "services/monitoring", score: "0.37", }, { ref: "services/lizenzmanagement", score: "0.36", }, ], experts: [ { ref: "experts/valentina-cicmak", score: "0.50", }, { ref: "experts/michael-steg", score: "0.39", }, { ref: "experts/mike-schmid", score: "0.21", }, ], neighbours: [ { ref: "solutions/igel", relation: "parent", }, { ref: "solutions/igel/igel-app-portal", score: "0.70", }, { ref: "solutions/omnissa/workspace-one/workspace-one-itsm-connector", score: "0.70", }, { ref: "solutions/igel/addon/igel-ums-as-a-service", score: "0.68", }, ], search: "/en/search.json", },};console.log(JSON.stringify(page, null, 2));

# 73 lines · YAML · validated at build# 111 lines · JSON · validated at build# 114 lines · TOML · validated at build# 130 lines · XML · validated at build# 129 lines · Python · read back at build, equals the JSON record# 127 lines · PowerShell · read back at build, equals the JSON record# 133 lines · Go · read back at build, equals the JSON record# 118 lines · JavaScript · read back at build, equals the JSON record · served at /en/solutions/igel/igel-onboarding-service.md

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.69 Automation 1.81 Managed Services 2.65

Vendors IGEL 3.03

04Services

03Capabilities

315Corpus

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

A device can go straight from the distributor to a home office and arrive managed.

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 gets its configuration, so the failure modes are all network ones: captive portals in hotels, a home router with an unusual DNS, a firewall rule nobody remembers writing.

What we do with it

Draft, unreviewed

Draft, not yet reviewed. We test the service with one device on a home connection before ordering the batch, because the failure modes are all network ones.

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.