• State Verified Answer
  • Replies 3 replies
  • Subscribers 114 subscribers
  • Views 1441 views
  • Users 0 members are here
Options
Related

On-Demain Migration - Is Migrating Windows 10 Workgroup to Entra ID a supported Scenario?

matt wailes
11 months ago

Subject says it all,

We have a client that has all their workstations currently setup as a workgroup. Is it possible to use ODM to perform the automation to translate the local user, flip the Office registration and join it to Entra? 

Assuming I can figure out the local user accounts and build a manual translation table is this possible/?

  • +1 11 months ago

    Hi Matt, ODM does not currently support migrations from a Workgroup.

    As you mentioned, one challenge is that you would need to get the correct attributes of the local accounts to build valid mapping files that could be used by the ReACL process.  Another challenge is that there is not currently a method for ODM to display Workgroup devices in the "Ready Devices" portion of the ODM UI to allow submitting the ReACL and Cutover actions that perform the profile switch and Entra Join.

    However, we do plan on adding Workgroup to Entra device migration as a supported scenario in the future.

  • 0 1 month ago in reply to Becky Cross

    Hello, just following up on this thread. Is migrating user profiles for workgroup devices still unsupported for ODM? If not do you have an approximant timeline where this will be possible? Thanks for your help

  • 0 1 month ago in reply to matt wailes_49987

    Hi Matt, this is still unsupported in ODM, but is still on our list to develop. Unfortunately, we don't have a committed date at this time as we have had to prioritize other features.  In the meantime, you could possibly use a combination of scripting and the product Entra ID for Devices, which accepts CSV files for the discovery & scoping.  This would require a fair amount of scripting and testing and results would not be guaranteed.

    If this is something you want to attempt, you would need to get the local user object details from the device via scripting to build the mapping file (since the ODM workstation agent does not have that functionality built in yet).  Then you could test running the ReACL action from the ODM UI, which would use the mapping file you provide.  For the device cutover, you would likely need to create a script that runs ReACL.exe locally on the device with the JSON file configured to do the Win10Profile switch and then runs the bulk enrollment package (since the Cutover action in ODM would attempt to perform a domain unjoin and likely fail if ran from the UI).

    Hopefully we will be able to share some concrete timelines soon for when we'll be able to officially support this scenario.