How to migrate from a CMT solution to UEM ?

Description

This document elucidates the necessary steps required for you to migrate from a CMT solution, to a UEM solution, like Endpoint Central MSP. The process of migrating from a CMT solution to a UEM one could pose several difficulties for an administrator, especially if the number of endpoints (and the types of endpoints) that are being managed is significantly high. Therefore, a custom application, the UEM Migration Tool, has been chiefly designed to ensure that the migration proceeds seamlessly.

Note:
(i) This tool has been specifically designed to migrate from SCCM to Endpoint Central MSP.
(ii) Resources and Collections are migrated from SCCM to Endpoint Central MSP.

Prerequisites

  • The Endpoint Central MSP build should be 11.1.2242.01 or above.
  • The SCCM SQL server should be accessible from the same computer.

Steps

  1. Download the UEM Migration Tool from the below-mentioned URL:
    Migration Tool. The MD5 checksum value is 993efb37a66e7e54878e59d2fcb40ee5.
  2. Extract the tool to your desired location
  3. Go to <Tool_Installation_Directory>/conf and insert the values mentioned below in the following files:
    >>File Name: sccm/mssql-config.properties:
    Enter the following values besides the corresponding keys in the properties file where,
       >>> db.name is the name of the MSSQL database.
       >>> db.host is the host name of the MSSQL database.
       >>> db.port is the port used to access the MSSQL server.
       >>> db.domain is the domain name, of which, the SCCM SQL server is part of.
       >>> db.username is the username of the user who can access the required database in the MSSQL server.
       >>> db.password is the password for the username provided above.
       >>> db.authenticatemode determines the type of authentication. Ther are two methods to authenticate a user: using Windows or SQL. Please specify the key as Windows or SQL depending on the choice of your authentication method.
    >>File name: desktop-central-server-details.properties:
    Enter the following values besides the corresponding keys in the properties file where,
       >>> uemserver.host is the host name of the UEM server.
       >>> uemserver.ip is the ip address of the computer in which the UEM server is running. If the UEM Server is not accessible using the host name, you can enter the server's IP address for accessibility. Ensure that the uemserver.host's value is deleted before selecting this option.
       >>> uemserver.installedlocation is the absolute path of the installation directory of the UEM server. Here, the individual values in the key have to be separated by double backslashes. For example: C:\\Program Files\\DesktopCentral_Server
       >>> uemserver.login is the username of the registered user in the UEM server with the administrative privileges. By default, the username is admin.
       >>> uemserver.auth is the corresponding password of the user mentioned above. By default, if there are no registered users, the password is admin, which is associated with the default user, admin, in the UEM server.
       >>> uemserver.http.port is the http port number used to access the UEM server. By default, the port number 8020 is used.
       >>> uemsserver.importmethodfallback is a flag used to choose the method of migration. This should be left blank. Only in the case of failure, setting this flag to true will run the tool in Fail-safe mode. The migration will take place seamlessly even without configuring the value for this key.
    Note: If this key is set to true, please ensure that the tool is run
    (a) With administrative privileges, and
    (b) From the same machine where Endpoint Central MSP has been installed.
    >>File name:msp.properties
    msp.customername
    is a required field that is used to identify which customer profile data should be imported.

    Note: The user should have set up the customer profile in their MSP server console before initiating the customer import process using this tool.
     
  4. Now, run the tool by opening the command prompt. Navigate to <Tool_Installation_Directory>/bin and run the batch file: run.bat.
  5. Now, the process of importing the details of endpoints will begin. It will log its progress in the EMSMigrationDefault0.txt file, located in <Tool_Installation_Directory>/logs.

You have successfully completed the migration using the Migration Tool.

Remote Desktop & Mobile Device Management Software for MSPs trusted by