1
00:00:03,030 --> 00:00:10,680
If you have an existing idea for 2016 environment, it's pretty easy to upgrade to ad FS 2019.

2
00:00:11,550 --> 00:00:19,290
You can also upgrade to AD First 2019 directly from DFS in Windows Server 2012 or two with a couple

3
00:00:19,290 --> 00:00:20,220
of extra steps.

4
00:00:21,090 --> 00:00:28,020
What makes this possible is a concept introduced in Ad FS 2016, and that's the farm behavior level.

5
00:00:28,930 --> 00:00:33,280
This is a farm wide setting that determines the features that ADF's can use.

6
00:00:34,210 --> 00:00:40,120
You can add newer versions of add chefs to an existing farm of older servers and the farm will continue

7
00:00:40,120 --> 00:00:42,430
to run at the earlier farm behaviour level.

8
00:00:43,330 --> 00:00:49,000
This is called a mixed farm and you can't use new features of ADF s while the farm is in this state.

9
00:00:49,880 --> 00:00:52,370
It runs with the features of the older version.

10
00:00:53,240 --> 00:00:59,960
Once all the new notes have been added to the farm, you delete the ad fs 2016 or 2012 or two nodes

11
00:00:59,960 --> 00:01:04,670
from the ADF's farm, and then you can raise the farm behaviour level to the latest version.

12
00:01:05,540 --> 00:01:09,800
Then you have access to all the newest features in ADF's 2019.

13
00:01:10,660 --> 00:01:17,380
Upgrading the farm behaviour level creates a new ADF's configuration database with a new name that corresponds

14
00:01:17,380 --> 00:01:18,790
to the farm behaviour level.

15
00:01:19,680 --> 00:01:28,710
If you're upgrading to add UFC 2019 or even to add UFC 2016 from DFS in Windows Server 2012 or to you

16
00:01:28,710 --> 00:01:31,350
may need to upgrade the schema inactive directory.

17
00:01:32,200 --> 00:01:35,080
It needs to be at level 85 at a minimum.

18
00:01:35,950 --> 00:01:42,670
You'll need the Windows Server installation media for Server 2016 or 2019, and you need to run a couple

19
00:01:42,670 --> 00:01:45,560
of commands to update the forest and domain schemas.

20
00:01:46,470 --> 00:01:53,280
I have another demo environment configured with the Windows Server 2016 domain controller and a 2016

21
00:01:53,280 --> 00:01:54,480
ADF's server.

22
00:01:55,380 --> 00:02:00,510
There's a network load balancer set up with a virtual IP that represents the ADF's service.

23
00:02:00,660 --> 00:02:03,930
And the Nhlbi just points to a single ADF server.

24
00:02:04,830 --> 00:02:11,220
We're going to add in ADF's 2019 server to the load balancer, make it the primary server in the farm,

25
00:02:11,370 --> 00:02:17,890
then remove the 2016 ADF's server and upgrade the farm behaviour level to ADF's 2019.

26
00:02:17,910 --> 00:02:19,260
So let's do all that next.