{"id":27937,"date":"2026-05-05T03:30:21","date_gmt":"2026-05-05T03:30:21","guid":{"rendered":"https:\/\/www.insentragroup.com\/au\/?p=27937"},"modified":"2026-05-05T03:30:23","modified_gmt":"2026-05-05T03:30:23","slug":"igel-ums-12-demo-setup-guide-deploy-and-onboard-igel-os-devices","status":"publish","type":"post","link":"https:\/\/www.insentragroup.com\/au\/insights\/geek-speak\/modern-workplace\/igel-ums-12-demo-setup-guide-deploy-and-onboard-igel-os-devices\/","title":{"rendered":"IGEL UMS 12\u00a0Demo Setup Guide. Deploy and Onboard IGEL OS Devices"},"content":{"rendered":"\n

A technical guide to deploying a working demo IGEL Universal Management Suite environment from infrastructure setup to your first onboarded endpoint and connecting through to back-end services.<\/em> <\/p>\n\n\n\n

What This Guide\u202fCovers <\/h2>\n\n\n\n

This guide is designed to walk IT teams, consultants, and platform architects through the complete setup of an IGEL UMS environment from provisioning a server to onboarding your first IGEL OS 12 device. The goal is a\u202fworking, demo environment\u202fthat lets you explore IGEL’s management capabilities before committing to production architecture.<\/p>\n\n\n\n

How long it should take to setup the demo environment <\/h2>\n\n\n\n

Once you have the server available for install the effort required to complete the below guide is 4-6 hours. This can be broken up in to logical parts so it can be distributed across a week duration.<\/p>\n\n\n\n

What’s Covered and What Isn’t<\/h2>\n\n\n\n
\u202f\u202fIn Scope <\/strong><\/td>Out of Scope <\/strong><\/td><\/tr>
\u2022 UMS prerequisites and sizing 
\u2022 Core UMS installation 
\u2022 IGEL Cloud Services enablement 
\u2022 Microsoft Entra ID integration 
\u2022 IGEL OS 12 onboarding setup 
\u2022 Profile and device validation <\/td>		\u2022 Production hardening
\u2022 UMS scale-out and HA
\u2022 External database migration
\u2022 IGEL Cloud Gateway
\u2022 Ongoing operational processes  <\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Who This Is For <\/h2>\n\n\n\n

Customer IT Infrastructure and EUC teams, delivery and implementation consultants, platform architects, and operational support teams. <\/p>\n\n\n\n

Demo Account &\u202fTrial Licensing<\/h2>\n\n\n\n

Before anything else, you’ll need two separate portal registrations. Both require an\u202findividual work email address<\/strong> generic or shared mailboxes are not supported. <\/p>\n\n\n\n

    \n
  1. Register in the IGEL Customer Portal<\/strong>\u202fusing your work email. This account controls UMS onboarding, cloud services configuration, and identity setup Welcome to IGEL Cloud Services! – Customer Portal<\/a> <\/li>\n<\/ol>\n\n\n\n
      \n
    1. Register in the IGEL License Portal<\/strong>\u202f(same or different work email). You’ll use your exported UMS ID to associate trial licenses with your environment  
      IGEL License Portal<\/a>\u202f <\/li>\n<\/ol>\n\n\n\n
        \n
      1. Await trial license assignment<\/strong>\u202fafter registration approval. Refer to IGEL’s onboarding documentation for specific initiation steps once approval is confirmed 
        How to Start with IGEL<\/a>\u202f <\/li>\n<\/ol>\n\n\n\n

        Infrastructure\u202fSizing <\/h2>\n\n\n\n

        The following specs represent a solid baseline for test and evaluation environments. Production deployments will need separate sizing assessments based on scale, availability requirements, and your operational model. <\/p>\n\n\n\n


        UMS Server<\/strong> 
        \u2022 OS:<\/strong> Windows Server 2025\/2022 (preferred)\u202f 
        \u2022 vCPU:<\/strong> 8 vCPU\u202f 
        \u2022 Memory:<\/strong> 16 GB\u202f 
        \u2022 Disk:\u202f<\/strong> 
        \u2022 100 GB OS\u202f 
        \u2022 100+ GB data (profiles, logs, backups)\u202f 
        \u2022 TLS:<\/strong> Certificate trusted by endpoints (default or enterprise CA)\u202f 




        <\/td>        		Database\u00a0<\/strong>\u00a0
        \u2022 Embedded database supported and recommended for test environments\u202f\u00a0
        \u2022 External\u202fSQL \/ HA\u202fdesigns\u202fare out of scope for this guide\u00a0

        Network\u00a0<\/strong>
        \u2022 Required ports opened per IGEL guidance\u202f\u00a0
        \u2022 DNS resolution for UMS FQDN\u202f\u00a0
        \u2022 Internet access for IGEL Cloud Services\u202f\u00a0
        \u2022 Network reachability to managed endpoints\u202f\u00a0
        <\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        The following article details the firewall rules required between the components, for the demo environment the primary set of rules are between the IGEL OS 12 endpoint, the UMS server and the IGEL Cloud services: <\/p>\n\n\n\n