Approximately half of their devices were not joined to any directory. One of the domains was being completely deprecated. They had devices in two different domains. I created the original version of this tool to assist someone who needed to move devices that were in one of several different management states to a single, Azure Active Directory joined state. If a user stored data outside of the supported known folders, that data will still be available on the device. One advantage of this method is that the device is not wiped. OneDrive Known Folder move is the best option for migrating user data. With that being said, this tool is only designed to migrate the device state. This breaks that connection, so the profile must change when the domain is no longer available. Remember, that on a domain-joined computer the profile is directly tied to the Active Directory user object. Other profile information is not moved, but you could consider using a tool to capture a list of installed printers and user applications and apply those post-migration. There is an Intune policy in the target tenant that turns on known folder move, allowing content in a user’s Documents, Desktop, and Pictures folder to move seamlessly between the old profile and new profile. To avoid any issues with profile migration, this solution turns on OneDrive known folder move and points it at the target tenant. I have heard of mixed results when using tools that claim to migrate a user’s profile. There are some third-party tools that claim to do that, but I personally believe migrating a user profile is the riskiest and most time-consuming part of the process.
In most cases, people are asking for a migration path that will migrate a user’s profile. I may make some updates to the tool, but those updates will largely be done as skill builders for me personally, not intended to make this a production tool. I want to echo and amplify his statement, ”This is not a Microsoft supported process today.” I will not be offering support for this tool, but I did want to share it with the community as an alternative method for you to test and consider in your environment. He did share a proof of concept on how it could be done without Configuration Manager using a provisioning package and PowerShell. Adam Nichols talked about how this could be accomplished at MMS in May, but focused on how it could be done using Configuration Manager.
I highly recommend using one of the commonly supported methods to begin your cloud endpoint journey, but I also acknowledge that in some instances organizations require minimal downtime and end user impact. I wanted to find a solution to allow an organization to migrate their devices to a cloud-only join state without using hybrid join or wipe their devices. The recommended and most common path for moving to Azure-AD only join is to hybrid join existing devices, while using Autopilot to join Azure AD for all new devices. The only officially supported method of doing this is through a wipe and reload. Over the years, a lot of people have been looking for a solution to migrate on-premises Active Directory joined devices to Azure Active Directory cloud-only join. In today’s post, I am going to take a slightly different approach. I normally approach these posts with an in-depth, step-by-step analysis of how the tool works. I also promised to share another tool with the community, and that’s what today’s post will do.
#Modern domainer update#
In my last blog post, I shared a tool that uses a proactive remediation and Azure Automation webhook to dynamically set and update the primary user on an Intune-enrolled device. Your mileage may vary, and if you choose to use it, please test thoroughly before using in production.
Please note: This is not an officially supported solution. Instead of my normal, in-depth step by step, this post will provide a high-level overview on how the tool works. Hello, and welcome back! Today I am sharing a tool to help you migrate a domain-joined device to a cloud-only, Azure AD joined state. Migrating AD Domain Joined Computer to Azure AD Cloud only join
0 kommentar(er)
