Migrate Active Directory Objects to Windows Server 2022.
So let's take up the question of why would you consider
doing a domain and/or forest migration.
Well, there's four good reasons that you can find in the Microsoft Docs.
One would be a merger or acquisition.
You're company a.com, let's say, and you have a single AD DS forest,
and you acquire company b.com who has their own forest.
You could, of course, do a forest trust and just leave it at that,
but there's some good reasons why consolidation makes sense.
I'll give you six reasons, actually, in the next slide.
Another driver for consolidation and migration is the
dissolution of a business unit.
You may just be downsizing your business,
simplifying your organizational structure.
You realize that you have too much sprawl in terms of multiple
forests or multiple domains within forests.
You want to simplify.
You may realize that your company has changed its name,
its focus, whatever,
and maybe the original domain name or domain names don't make sense from
a legal standpoint or from a performance standpoint.
I remember years ago,
I made a rookie mistake of naming a forest root domain
with a .local DNS top‑level domain,
and if you've worked with Apple environments with dynamic and multicast DNS,
.local's not a good fit for a business domain for sure.
These things happen,
and these would be drivers to lead to migration to a new forest with a new name.
And lastly, I hope that you don't have a security compromise,
but sometimes a security compromise can lead a business to realize we need to re‑architect our Active Directory forest from the ground up.