Close Menu
    Facebook X (Twitter) Instagram
    Trending
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    • Speaking at Modern Endpoint Management Summit 2022
    • Speaking at Nordic Virtual Summit 2022 – 3nd Edition
    • CoLabora Recordings – January 2022
    RONNIPEDERSEN.COM
    • Home
    • Enterprise Mobility
      • Configuration Manager
      • Identity and Access
      • Information Protection
      • Intune
    • Cloud and Data Center
      • Data Center Management
      • Group Policy
      • Enterprise Security
      • Hyper-V
      • PowerShell
    • Guides
    • Webcasts
    • Links
    • About
      • Contact me
      • Disclaimer
    RONNIPEDERSEN.COM
    You are at:Home»Enterprise Mobility»Configuration Manager»Prepare for Co-Management: Migrate Intune Devices without user affinity

    Prepare for Co-Management: Migrate Intune Devices without user affinity

    1
    By Ronni Pedersen on January 30, 2018 Configuration Manager, Enterprise Mobility, Intune

    Introduction

    With the release of Configuration Manager 1710, Microsoft now supports co-management, so Windows 10 clients can be managed by both SCCM and Intune at the same time.

    There are a few pre-requirements that need to be completed if you want to use co-management, and the most important one is that you need have your MDM authority in Intune set to Intune.

    The following are general prerequisites for you to enable co-management:

    • Configuration Manager version 1710 or later
    • Azure AD
    • EMS or Intune license for all users
    • Azure AD automatic enrollment enabled
    • Intune subscription (MDM authority in Intune set to Intune)

    See all the requirements here: https://docs.microsoft.com/en-us/sccm/core/clients/manage/co-management-overview

    Some customers might have “user less devices” that needs to be migrated, and this blog post will explain how to migrate these devices without user affinity, from being manage by Intune hybrid scenario, to Intune standalone.

    Migrate devices without user affinity

    Devices enrolled by using a device enrollment manager and devices without user affinity are not automatically migrated to the new MDM authority. To solve this, Microsoft has released a new PowerShell Cmdlet (Switch-MdmDeviceAuthority), that you can use to switch between Configuration Manager and Intune management authority.

    Import the module

    The Switch-MdmDeviceAuthority Powershell Cmdlet is part of the Microsoft Intune Data Importer v1.1, that can be downloaded from github:

    https://github.com/ConfigMgrTools/Intune-Data-Importer/releases

    Download the self-extracting, import the Cmdlet by running the following command to import the new module (Make sure you download the latest version, otherwise you won’t have this module available):

    Import-Module .\MicrosoftIntuneDataImporter.Commands.dll

    SNAGHTML5131147

    Get the Device ID

    When you run the PowerShell Cmdlet, you need to use the SMSID (Device ID) as the device identifier. You can get the Device ID in the SCCM Console, or by running the following PowerShell command:

    Get-CMDevice -Name <Name of the device> | Select Name, SMSID

    SNAGHTML536dbff

    SNAGHTML5136524

    Switch MDM Authority for the Device

    The cmdlet switches the management authority of MDM devices without user affinity (For example, bulk-enrolled devices). The cmdlet switches between Intune and Configuration Manager management authorities for the specified devices based on their management authorities when you run the cmdlet.

    Switch-MdmDeviceAuthority -DeviceIds $deviceId

    SNAGHTML51209ca

    You can verify that the Device has been successfully migrated by checking in the Intune Portal. Notice that since this is a user less device you don’t have a user assigned to the device.

    SNAGHTML514c37b

    More Information

    • Migrate devices without user affinity: https://docs.microsoft.com/da-dk/sccm/mdm/deploy-use/migrate-mixed-authority#migrate-devices-without-user-affinity
    • Microsoft Intune Data Importer: https://github.com/ConfigMgrTools/Intune-Data-Importer/releases
    • Co-management for Windows 10 devices: https://docs.microsoft.com/en-us/sccm/core/clients/manage/co-management-overview

    /Enjoy

    +Ronni Pedersen

    • Tweet
    • Share 0
    • +1
    • LinkedIn 0

    Related

    Ronni Pedersen
    • Website
    • Facebook
    • X (Twitter)
    • LinkedIn

    My name is Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

    Related Posts

    Speaking at Nordic Virtual Summit

    Workplace Ninja User Group Denmark February Meetup

    Speaking at Modern Endpoint Management Summit 2022

    1 Comment

    1. Sebi on March 31, 2024 20:41

      Hi Ronni Pedersen,

      Thank you very much for the great tutorial. Unfortunately the Microsoft Intune Data Importer is no more available to use. What are the alternative ways in 2024 to Switch MDM Authority for the Device?

      Your kind reply will be highly appreciated.

      Thanks in advance.

      Reply
    Leave A Reply Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Follow
    APENTO

    Follow APENTO here:

    Subscribe to Blog via Email

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    About
    My name i s Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Endpoint Management and Security, based on Microsoft technologies. I'm also a Microsoft Certified Trainer and a dual Microsoft MVP in both Security and Windows.
    Recent Posts
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    Archives
    TOP POSTS
    • Find the TimeZoneName for your SCCM/MDT Deployments
    • SCCM: Failed to Get Client Identity (80004005)
    • SCCM 2012 R2: Where is the SMSTS.log located?
    • Active Directory Based Activation in an multi domain environment
    • Missing “UserType” attribute in Azure AD
    RECENT COMMENTS
    • Sebi on Prepare for Co-Management: Migrate Intune Devices without user affinity
    • Vadim P on SCCM: Failed to Get Client Identity (80004005)
    • TM on Active Directory Based Activation in an multi domain environment
    • unkown on Setting OSDComputerName using CustomSettings.ini
    • TJ Scott on Setting OSDComputerName using CustomSettings.ini
    DISCLAIMER
    The content on this website is presented "as-is" with no guarantees. The use of scripts from this website is at your own risk. Always test before putting something in production! Opinions expressed are my own.
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.