1
00:00:07,020 --> 00:00:12,180
The availability of your office environment is critical.

2
00:00:12,810 --> 00:00:18,960
When service is in office, 365 are enabled for federated authentication.

3
00:00:19,560 --> 00:00:28,260
For example, if your federation server is unavailable, all users or certification requests will fail

4
00:00:28,470 --> 00:00:34,230
and users will not be able to access Office 365 services.

5
00:00:35,010 --> 00:00:43,380
Similarly, if your Federation's Brooks is unavailable, external user authentication or request will

6
00:00:43,380 --> 00:00:52,380
not be passed to your Federation server, and this users will not be able to access Office 365 services.

7
00:00:53,010 --> 00:01:01,110
Therefore, it is essential that the preparation for a first deployment and good planning for the high

8
00:01:01,110 --> 00:01:09,180
availability of your first Federation servers out of the area first for duration, proxies, servers,

9
00:01:09,900 --> 00:01:14,550
area first availability effects on the user authentication.

10
00:01:14,820 --> 00:01:19,350
It does not and does not affect Office 365 services.

11
00:01:19,860 --> 00:01:28,980
For example, if users are not able to access their email in office 365, their mailboxes in exchange

12
00:01:28,980 --> 00:01:31,680
alone will continue to receive email.

13
00:01:32,900 --> 00:01:33,200
No.

14
00:01:33,200 --> 00:01:41,930
Let's talk about different methods of high availability for duration of server form.

15
00:01:42,500 --> 00:01:50,870
With Windows Server 2012 or earlier, you can deploy the first four duration server as a standalone

16
00:01:50,870 --> 00:01:54,290
server or in a federation server farm.

17
00:01:55,130 --> 00:02:02,750
However, it is recommended that you always deploy more than one server in a federation server for.

18
00:02:03,910 --> 00:02:09,460
Even if the form initially consists only of one refrigeration server.

19
00:02:09,730 --> 00:02:18,190
This deployment method provides you with the option of adding more for duration servers later for load

20
00:02:18,190 --> 00:02:20,560
balancing or fault tolerance.

21
00:02:21,370 --> 00:02:27,550
However, if the first Federation server is deployed as a standalone server.

22
00:02:28,620 --> 00:02:37,980
You will not be able to add servers later with Windows Server 2012 or two or later, you can deploy

23
00:02:37,980 --> 00:02:43,650
the first Federation server only in a Federation server form.

24
00:02:44,430 --> 00:02:51,090
Although this deployment method provides you with the option of adding more for duration service later.

25
00:02:51,540 --> 00:02:59,190
It was recommended that you deploy more than one federation server in a form for your production environments.

26
00:03:00,270 --> 00:03:02,310
The next option is and I will be.

27
00:03:02,910 --> 00:03:12,060
You should use network load balancing or nhlbi or all forms of clustering to allocate a single IP address

28
00:03:12,060 --> 00:03:14,850
for multiple a deferred for duration service.

29
00:03:15,480 --> 00:03:22,830
With this deployment option, the failure of a single for duration server should not affect the federation

30
00:03:22,840 --> 00:03:24,330
services for users.

31
00:03:24,810 --> 00:03:32,340
Similarly, you should also use an old build to provide an area first proxy array in the Perimeter Network

32
00:03:32,670 --> 00:03:41,160
to help ensure that external clients are not impacted by the failure of an IT first proxy computer.

33
00:03:42,580 --> 00:03:49,660
Please know that you can deploy a hardware or a load balancer instead of an object to provide high aerial

34
00:03:49,660 --> 00:03:55,150
ability to your for duration servers and for duration proxies servers.

35
00:03:55,780 --> 00:04:01,600
However, the details of this process are beyond the scope of this call.

36
00:04:02,590 --> 00:04:05,860
The next option is configuration database.

37
00:04:06,250 --> 00:04:16,330
If you choose Windows Internal Database or WIOD as your area of first data storage, a copy of the configuration

38
00:04:16,330 --> 00:04:19,090
database exists on each server.

39
00:04:19,600 --> 00:04:28,330
However, if you choose Microsoft SQL Server as your ideal first data storage, you need to plan a high

40
00:04:28,330 --> 00:04:37,840
availability SQL Server deployment as opposed to WIOD deploying an idea first for duration server farm

41
00:04:37,840 --> 00:04:45,970
with SQL Server does not enable higher well ability for the configuration database by default.

42
00:04:46,480 --> 00:04:54,430
For example, if the server running SQL Server is unavailable, the idea first for duration server will

43
00:04:54,430 --> 00:05:02,830
be unable to connect to the configuration database and the 11 servers will not start.

44
00:05:03,490 --> 00:05:11,680
For this reason, you should consider deploying data files with the SQL Server cluster or a single server

45
00:05:11,950 --> 00:05:13,840
failover partner.

46
00:05:14,410 --> 00:05:18,430
Although you can enable the single server cluster at any time.

47
00:05:18,820 --> 00:05:27,040
The cycle server cluster cluster for a lower partner can be enabled only during the eight hour first

48
00:05:27,040 --> 00:05:29,290
deployment or afterward.

49
00:05:29,860 --> 00:05:35,290
This is because you use the first to configure the fail over partner.

50
00:05:36,780 --> 00:05:39,900
For more availability on the SQL Server.

51
00:05:40,230 --> 00:05:48,570
High availability solutions, you can refer to High Reliability Solution Server on this link.

52
00:05:49,380 --> 00:05:52,170
Next up, we'll be talking about capacity planning.