1
00:00:01,140 --> 00:00:06,540
Migrate Active Directory Objects to Windows Server 2022.

2
00:00:06,540 --> 00:00:09,350
So let's take up the question of why would you consider

3
00:00:09,350 --> 00:00:13,340
doing a domain and/or forest migration.

4
00:00:13,340 --> 00:00:17,610
Well, there's four good reasons that you can find in the Microsoft Docs.

5
00:00:17,610 --> 00:00:20,840
One would be a merger or acquisition.

6
00:00:20,840 --> 00:00:25,740
You're company a.com, let's say, and you have a single AD DS forest,

7
00:00:25,740 --> 00:00:29,390
and you acquire company b.com who has their own forest.

8
00:00:29,390 --> 00:00:33,260
You could, of course, do a forest trust and just leave it at that,

9
00:00:33,260 --> 00:00:36,800
but there's some good reasons why consolidation makes sense.

10
00:00:36,800 --> 00:00:40,240
I'll give you six reasons, actually, in the next slide.

11
00:00:40,240 --> 00:00:43,750
Another driver for consolidation and migration is the

12
00:00:43,750 --> 00:00:45,620
dissolution of a business unit.

13
00:00:45,620 --> 00:00:48,040
You may just be downsizing your business,

14
00:00:48,040 --> 00:00:50,840
simplifying your organizational structure.

15
00:00:50,840 --> 00:00:54,220
You realize that you have too much sprawl in terms of multiple

16
00:00:54,220 --> 00:00:57,790
forests or multiple domains within forests.

17
00:00:57,790 --> 00:00:59,440
You want to simplify.

18
00:00:59,440 --> 00:01:03,010
You may realize that your company has changed its name,

19
00:01:03,010 --> 00:01:04,290
its focus, whatever,

20
00:01:04,290 --> 00:01:09,410
and maybe the original domain name or domain names don't make sense from

21
00:01:09,410 --> 00:01:12,560
a legal standpoint or from a performance standpoint.

22
00:01:12,560 --> 00:01:13,890
I remember years ago,

23
00:01:13,890 --> 00:01:17,820
I made a rookie mistake of naming a forest root domain

24
00:01:17,820 --> 00:01:20,850
with a .local DNS top‑level domain,

25
00:01:20,850 --> 00:01:26,870
and if you've worked with Apple environments with dynamic and multicast DNS,

26
00:01:26,870 --> 00:01:30,740
.local's not a good fit for a business domain for sure.

27
00:01:30,740 --> 00:01:31,850
These things happen,

28
00:01:31,850 --> 00:01:37,150
and these would be drivers to lead to migration to a new forest with a new name.

29
00:01:37,150 --> 00:01:40,650
And lastly, I hope that you don't have a security compromise,

30
00:01:40,650 --> 00:01:50,000
but sometimes a security compromise can lead a business to realize we need to re‑architect our Active Directory forest from the ground up.