How to Migrate from SCCM to Hexnode UEM: The Definitive Runbook

Migrating Endpoints from SCCM to Hexnode UEM

Migrating endpoints from Microsoft Configuration Manager (formerly System Center Configuration Manager, or SCCM) to a cloud-native unified endpoint management architecture like Hexnode UEM shifts your enterprise away from heavy on-premises infrastructure.

To execute a controlled migration, Hexnode provides a dedicated SCCM integration. This architecture works in two phases: first, installing a server-side connector on your SCCM server to sync device records directly into Hexnode, and second, utilizing your existing SCCM Software Library to push the Hexnode UEM client to your endpoints for direct enrollment.

Strategic Use Cases & Benefits of SCCM Integration

Rather than forcing a massive manual re-enrollment event or requiring factory resets, this integration acts as a strategic bridge between legacy on-premises management and modern cloud UEM. This method is highly recommended for the following scenarios:

• Zero-Touch, Zero-Wipe Transitions: If your devices are already deployed in the field (e.g., remote workers), this method allows you to push the Hexnode agent silently using SCCM’s background application deployment. Users are not interrupted, and devices do not need to be factory reset.
• Unified Inventory Visibility: By syncing the SCCM database with Hexnode first, IT administrators gain immediate visibility of their legacy fleet inside the cloud portal before pushing the enrollment client, making it easy to track migration progress and identify missing assets.
• Phased Co-Management: This strategy supports a staged rollout. You can deploy Hexnode to a small pilot group of SCCM devices, validate that cloud policies are applying correctly alongside legacy configurations, and progressively transition the rest of the fleet at your own pace to reduce operational risk.

Prerequisites for Migration

• Target Endpoints: Windows 10 devices running version 1709 or later.
• Access Requirements: Administrative access to the Hexnode UEM portal and your on-premises SCCM server (including the Hostname and User Credentials to connect to the SCCM database).
• Site Code: The three-character alphanumeric code used to identify sites in your SCCM server.

Phase 1: Establishing Server-to-Server Integration

Rather than deploying agents blindly, Hexnode allows you to link your SCCM database directly to your UEM console. This is achieved by installing the Hexnode SCCM Agent locally on your on-premises server.

Step 1: Install the Hexnode SCCM Agent

1. Log in to your Hexnode UEM console and navigate to Admin > SCCM.
2. Click the provided download link to retrieve the Hexnode SCCM Agent setup file.
3. Move this setup file to your actual SCCM server and launch the installation wizard.
4. Select the local destination path for the agent installation.
5. You will be prompted to provide the following routing details:
   • Site Code: The three-character alphanumeric site code obtained from your SCCM server.
   • Portal Name: Your Hexnode portal name (the tenant URL).
6. Next, provide the Hostname, Username, and Password required to securely connect to the SCCM server’s database.
7. Click Install, then Finish to exit the setup.

Step 2: Verify Device Synchronization

Once the server-side agent successfully authenticates against the SCCM database, it will sync your legacy device inventory into the cloud. Return to your Hexnode UEM portal and navigate to Admin > SCCM. All the devices currently managed by your SCCM server will now be listed here, establishing your migration baseline.

Phase 2: Building the Deployment Package in SCCM

With the server link established, you must now configure your legacy SCCM environment to deploy the Hexnode UEM MSI client to your target endpoints.

Step 1: Stage the Hexnode UEM Client

1. From the Hexnode portal (under Admin > SCCM or the standard Windows enrollment tab), download the Hexnode UEM app for Windows 10 devices.
2. Place this .msi file in a secure, shared network directory accessible by your SCCM infrastructure.

Step 2: Configure the Application Object in SCCM

1. Open your SCCM Console and navigate to the Software Library workspace.
2. Click +Create > Create Application.
3. In the application wizard, specify the following settings:
   • Type: Select Windows Installer (*.msi file).
   • Location: Provide the exact location of the Hexnode application using the UNC path format (e.g., \\ServerName\ShareName\HexnodeUEM.msi).
4. Click Next to view and verify the imported details from the Windows MSI file.
5. Proceed through the wizard to modify any internal deployment details (such as Publisher or Application Name) as required by your internal naming conventions.
6. Verify the details under the Summary page, click Next, and then click Close upon successful completion.
7. The Hexnode client is now fully staged and will appear in your SCCM console under Software Library > Overview > Application Management > Applications.

Phase 3: Deployment Execution

You can now use SCCM’s native deployment mechanics to push the Hexnode agent to your target collections.

1. In the SCCM Console, navigate back to Software Library.
2. Locate the newly created Hexnode application.
3. Right-click on the app and select Deploy.
4. The Hexnode application will be listed by default under the Software field. Follow the standard SCCM deployment prompts to target specific Device Collections.
   

   Note: This is where you execute the Phased Co-Management strategy discussed earlier by targeting a small pilot collection first, rather than your entire fleet.

Once SCCM successfully pushes the MSI package, those specific endpoints will install the Hexnode UEM agent and check in with your Hexnode UEM cloud environment. This completes the onboarding phase for that targeted group, allowing you to validate policies and co-manage them before repeating Phase 3 for the rest of your organization.