How to migrate Windows devices from another MDM to Hexnode?

Before undertaking an MDM migration, it is important to have proper planning. This guide will walk you through the detailed procedures involved in migrating your Windows devices from another MDM provider to Hexnode UEM.

Migration steps

To be successful in migrating your devices there are a few steps you need to perform:

1. Remove assets from current MDM and back up required data.
2. Create a provisioning package file (for enrolling Windows 10 devices in bulk).
3. Sync users from directory services to Hexnode UEM.
4. Migrate devices from Microsoft’s System Center Configuration Manager (SCCM) to Hexnode UEM.
5. Disenroll devices from current MDM.
6. Enroll devices into Hexnode UEM.

Step-1: Remove assets from current MDM and back up required data

To disconnect your devices from the current MDM, you may have to wipe your devices. So, it is recommended to back up all the required data prior to the device wipe. Before removing all the management profiles and users from the current MDM, download essential information like device details and user details which may come to use later.

Step-2: Create a provisioning package file

Create a .ppkg file using Windows Configuration Designer to enable large scale roll-out of Windows 10 devices.

• Download and install the Windows Configuration Designer on a Windows 10 device.
• Create a new project with project workflow as provisioning package.
• Customize the provisioning package with enrollment details like server URL, username and provide the secret key from your Hexnode MDM portal.
• Build the provisioning package.

Step-3: Sync users from directory services to Hexnode UEM

You can sync the users from various directory services such as Active Directory (AD), Azure AD and Google Workspace (G Suite) to the MDM console.

Unbind your current MDM vendor from the directory services and configure Hexnode UEM with them.

1. Active Directory
   • Configure Active Directory settings under Admin tab to get the users synced from the AD account to the Hexnode portal.
2. Azure AD
   • Configure Azure AD under Admin tab to get the users synced from the Azure AD account to the Hexnode portal.
3. G Suite
   • Configure G Suite under Admin tab to get the users and user groups synced from the G Suite account to the Hexnode portal.

Step-4: Migrate devices from Microsoft’s System Center Configuration Manager (SCCM) to Hexnode UEM

Unbind your current MDM from SCCM and integrate Hexnode UEM to sync the devices from SCCM server to the Hexnode portal.

• Download and install the Hexnode SCCM Agent app on the SCCM server.
• Provide the site code of the SCCM server and the portal name of Hexnode console to which the SCCM server is to be integrated.
• For direct enrollment into Hexnode portal, download the Hexnode MDM app for Windows 10 devices (v1709+).
• Deploy the application.

On deploying the application, Windows devices from SCCM server will now be synced on to your Hexnode console.

Step-5: Disenroll devices from current MDM

Disenroll all your devices from the current MDM. This can be done in two ways:

• Perform disenroll action from the current MDM.
• Manually remove management from the device settings.

Step-6: Enroll devices into Hexnode UEM

Use any of the following methods to get your devices enrolled to Hexnode UEM. Enrollment steps vary for Windows phones and laptops.

PPKG enrollment

Use the enrollment package created in Step-2 to bulk-enroll Windows 10 devices to Hexnode UEM. To apply the package to a device:

• Tap on add a package in the device settings.
• Select the package from the removable media containing the .ppkg file to be installed.

The device gets enrolled with Hexnode UEM.

Bulk enrollment with CSV import

Use the device and user details downloaded in Step-1 to enroll devices in bulk.

• Bulk user import – Send enrollment instructions to users in bulk via email by uploading the user details as a CSV file.
• Pre-approved enrollment – Bulk import a list of devices based on their serial numbers via a CSV file. You can proactively assign device management policies to these devices and the policies automatically take effect upon enrollment.

Self-enrollment

Provide either the user’s AD credentials, or email and password set in the portal to get the device enrolled.

Open enrollment

Allow users to enroll without authentication using only their email id and server URL.

Email/SMS enrollment

Users can enroll their devices with the server address, username and password received via email or SMS.