Hello fellow engineers. I have been asking around and looking for 2 different solutions to pave a path to my goal here. Here is a breakdown of my situation:
I currently have a Win 2012 R2 domain that has a lot of history, lots of mystery and I have floated the idea of moving a new fresh forest. I understand the applications an everything that is involved in this type of request but lets just say for entertainment
purposes that all of that is good to go. Here is the challenge:
How can I migrate/move from the old domain, to a new one and stay connected to the same O365 tenant?
One idea is creating all the users brand new in the new domain, then making sure the user in O365 is "cloud only" and modifying the UPN and the Immutable Object name for the user. Of course the new domain name would be added to O365 before
hand. Is that a valid option?
Second idea was to use ADMT to move the user objects to the new domain, then modifying the users UPN and Immutable Object to make sure it points to the same O365 tenant, but my assumption is that since the user object is migrating that it should hold the
attributes values to the O365 tenant.
Maybe there is a third option?
My question to this community of experts is:
1. I opened a ticket with my vendor (Insight) and they have a solution expert who said this is a common thing that happens but to make sure that this is what we want to do and not assume it is easy to perform. But if I need to do this then he
suggested option 1. Has anyone done something like this before? How did it go?
2. Anyone do something like this but use a 3rd party tool to do the heavy lifting? How did that go and what was the name of the tool?
Thank you all for your time on this.