1
00:00:07,120 --> 00:00:15,100
Capacity planning for Federation servers helps you to assess the hardware requirements for each Federation

2
00:00:15,100 --> 00:00:19,390
server and the number of Federation servers to deploy.

3
00:00:20,140 --> 00:00:29,050
Capacity planning also helps you estimate and prepare for growth in the size of the ADF configuration

4
00:00:29,050 --> 00:00:29,800
database.

5
00:00:30,870 --> 00:00:34,350
Let's review the full and capacity planning spreadsheet.

6
00:00:35,010 --> 00:00:43,350
The idea of capacity planning spreadsheet includes calculator like functionality that takes expected

7
00:00:43,350 --> 00:00:53,610
usage data about users in your organisation and returns recommended optional number of durations servers

8
00:00:54,210 --> 00:00:56,880
forum area first production environment.

9
00:00:57,510 --> 00:01:03,030
The first capacity planning spreadsheet requires the following input.

10
00:01:03,420 --> 00:01:12,210
The value that best represents the percentage of total users expected to send authentication requests

11
00:01:12,210 --> 00:01:16,100
to IT officials during peak usage periods.

12
00:01:16,860 --> 00:01:25,260
Well, user best represents the length of the time the peak usage period is expected to last and the

13
00:01:25,260 --> 00:01:30,360
total number of users that will require as a so excess.

14
00:01:31,650 --> 00:01:40,560
Do the tortured claims are were application based on whether the users are signing in to do this from

15
00:01:40,560 --> 00:01:49,080
a computer on the corporate network remotely signing in to do this from a computer or signing in from

16
00:01:49,080 --> 00:01:54,930
another organisation or from a some old 2.0 identity provider.

17
00:01:57,260 --> 00:01:57,480
No.

18
00:01:57,500 --> 00:01:59,210
Let's review the estimation.

19
00:01:59,210 --> 00:02:09,530
Table 8/1 can scale to support tens of thousands of users and it allows you to add more Federation servers

20
00:02:09,530 --> 00:02:10,700
to a server form.

21
00:02:11,000 --> 00:02:20,020
As the company scales up, you can use the following table to help you estimate the minimum number of

22
00:02:20,150 --> 00:02:27,320
the first four duration servers and web application proxies, servers or application proxies servers

23
00:02:27,620 --> 00:02:29,180
that you need to deploy.

24
00:02:29,870 --> 00:02:37,700
This is dimensions are based on the number of users who will require SSL access, including remote access

25
00:02:38,030 --> 00:02:39,350
to the cloud servers.

26
00:02:40,750 --> 00:02:47,560
Unless otherwise noted, all of the Federation servers should be deployed in a Federation server farm

27
00:02:47,950 --> 00:02:48,910
with a W.

28
00:02:48,920 --> 00:02:57,640
I do store for the configuration database, although fewer Federation sunroofs might be possible in

29
00:02:57,640 --> 00:03:00,670
some of the scenarios in the following table.

30
00:03:02,710 --> 00:03:07,450
An additional four duration server is included to provide redundancy.

31
00:03:09,280 --> 00:03:20,650
Now if you have number of users accessing Office 365 services, fewer than 1000 unit minimum due for

32
00:03:20,650 --> 00:03:25,360
duration servers and two proxies with fewer users.

33
00:03:25,660 --> 00:03:32,110
Consider deploying the for duration servers on two existing domain controllers sell them, implement

34
00:03:32,110 --> 00:03:36,820
and load balancing by using MLB for the proxies.

35
00:03:36,820 --> 00:03:45,430
Consider use them to exist in web servers or proxies servers alone configure them both for the Federation

36
00:03:45,430 --> 00:03:51,460
server proxies role and or the for duration the web application proxy are all.

37
00:03:53,170 --> 00:04:00,880
If a number of users in your network exist and offer 3625 is 1000 turned.

38
00:04:02,450 --> 00:04:04,910
Up to 15,000 users.

39
00:04:05,210 --> 00:04:08,330
Unit two Federation Server Authentic Proxies.

40
00:04:09,250 --> 00:04:17,020
With minimum, two large organizations consider deploying the Federation servers on two dedicated computers

41
00:04:17,290 --> 00:04:22,870
with Arnold may consider deploying the proxies on two dedicated computers.

42
00:04:23,200 --> 00:04:33,070
With an old bill, if you have 15 to 60000 users, unit 3 to 5 for duration servers and two proxies

43
00:04:33,880 --> 00:04:44,950
for every increment of 15,000 users over 15,000, you should deploy an additional four duration server

44
00:04:45,250 --> 00:04:55,990
to the load balance for up to the maximum of five servers that W added support or more with a SQL Server

45
00:04:55,990 --> 00:04:58,960
database for the proxies.

46
00:04:58,990 --> 00:05:03,220
Consider deploying additional nodes to improve performance.

47
00:05:04,190 --> 00:05:12,260
And if you have more than 60,000 users, you have to consider five or more federation servers and three

48
00:05:12,260 --> 00:05:20,600
or more proxies because enterprises with over 60,000 users should implement five or more for duration

49
00:05:20,600 --> 00:05:26,090
servers that use SQL Server for the configuration database.

50
00:05:26,660 --> 00:05:34,610
You also should deploy three or more blocks that use hardware load balancing instead of an old bit.

51
00:05:36,410 --> 00:05:42,410
Next stop, we'll have a demonstration where we'll be installing the ADA first.

52
00:05:42,410 --> 00:05:43,220
Several.