Migrating existing group policies and creating equivalent MDM policies in MaaS360 using the SCCM Migration Tool

Migrate existing Group Policy Objects that are currently rolled out through AD and SCCM and create an equivalent MDM policy in MaaS360® using the SCCM Migration Tool on any Windows 10+ endpoint that is managed by SCCM. After you create the MDM policy, you can deploy the policy to an endpoint device that is migrated from SCCM to MDM.

Procedure

  1. Download the SCCM Migration Tool from the MaaS360 Portal at Devices > Enrollments > Other Enrollments > CMT Co-existence, and then click Install.
  2. Provide the username and password for the administrator who authenticates with MaaS360, and then click Next.
    SCCM Policy Migration Tool login window
    If authentication is successful, the installation wizard continues to the next steps.
  3. From the Migration Type window, select Policy Migration, and then click Next.
    Policy Migration option
  4. Provide the policy name that you configured and want to migrate to the IBM® MaaS360 Portal.
    Migration starts and an MDM policy published successfully message is displayed.
  5. Click View Migration Summary to generate an HTML report that summarizes the Group Policy Objects to MDM migration.
    This report provides the following information:
    • Group Policy Objects policies that were migrated with the SCCM Migration Tool.
    • Group Policy Objects policies that were not migrated with the SCCM Migration Tool because MaaS360 or the MDM does not support those policies.

    For a complete list of the Group policies that can be migrated, see List of Group policies migrated to MaaS360 Windows MDM policies using the SCCM Migration Tool.

  6. Go to Security > Policies to view the published policy in the IBM MaaS360 Portal.
  7. If migration is successful, you can view and edit values for the policy.
  • Only policies from a domain controller are migrated. Local policies are not migrated.
  • You cannot apply policies that are created with the migration tool to a device if the desktop and laptop service is disabled.
  • For workflows that are not present in MaaS360, continue to use SCCM examples that are OS deployment based on golden images and app distribution.