1
00:00:07,780 --> 00:00:13,150
First new, the first feature that Windows Server 2012 introduces.

2
00:00:13,660 --> 00:00:21,340
The first version that ships with Windows Server 2012 includes several new features.

3
00:00:22,440 --> 00:00:31,830
Among them are integration with the Windows Server 2012 operating system and Windows Server 2012 eight.

4
00:00:32,040 --> 00:00:37,710
First is included as a server role that you can install by your then server manager.

5
00:00:38,220 --> 00:00:45,060
When you install the server roll all the required operating system components automatically install.

6
00:00:46,400 --> 00:00:50,270
Next integration with dynamic access control.

7
00:00:50,750 --> 00:00:57,560
When you deploy a dynamic access control, you can configure user and device claims that are issued

8
00:00:57,560 --> 00:00:59,660
by editors domain controllers.

9
00:01:00,470 --> 00:01:07,100
A first can consume the editors claims the domain controller issue.

10
00:01:07,490 --> 00:01:17,270
This means that it first can make authorisation decisions based on both user accounts and computer recalls

11
00:01:17,900 --> 00:01:26,300
and Windows PowerShell Command Line Interface Command lets for administering area for Windows Server

12
00:01:26,300 --> 00:01:34,970
2012 provides several and the and lets that you can use to install and configure the ADF first server

13
00:01:34,970 --> 00:01:35,390
rules.

14
00:01:37,010 --> 00:01:37,200
No.

15
00:01:37,250 --> 00:01:46,280
So it's about new idea first feature that Windows Server 2016 introduces the idea first version that

16
00:01:46,280 --> 00:01:51,890
ships with Windows Server 2016 includes the following new features.

17
00:01:54,240 --> 00:02:03,450
Support for any director that is light weight director, access pro article or L dub version three compliant.

18
00:02:03,810 --> 00:02:12,360
This allows your users to sign into any affairs from any third party directory that is older version

19
00:02:12,360 --> 00:02:13,890
3.3 compliant.

20
00:02:15,000 --> 00:02:22,980
This allows users to sign in from untrusted or partially trusted data elements and forests.

21
00:02:23,970 --> 00:02:31,590
New factors of authentication at first provides additional ways to authenticate users and devices.

22
00:02:31,920 --> 00:02:40,560
In addition to use an edit and held up version three directories, you can configure Azure multifactor

23
00:02:40,560 --> 00:02:43,860
authentication as an authentication method.

24
00:02:45,570 --> 00:02:53,250
Some improvements in Area First management, including application policies and delegated service management.

25
00:02:53,640 --> 00:03:02,520
As for application policies in a first for Windows Server 2016, you must use the claims rules language

26
00:03:02,520 --> 00:03:04,650
to create custom media.

27
00:03:04,650 --> 00:03:13,830
First policies in fails and Windows Server 2016 provides resort based management, making it easier

28
00:03:13,830 --> 00:03:16,200
to create custom policies.

29
00:03:16,680 --> 00:03:25,290
As for delegated source manager management area, firstly, Windows Server 2016 separates the idea of

30
00:03:25,310 --> 00:03:30,960
first server administrators from the area first service administrators.

31
00:03:31,770 --> 00:03:40,590
This means that the Area First Administrator is no longer required to be a local server administrator

32
00:03:41,160 --> 00:03:44,340
and conditional access at first.

33
00:03:44,340 --> 00:03:53,490
And Windows Server 2016 provides improvements in device registration by working with a user Active Directory

34
00:03:53,850 --> 00:04:02,310
to restrict devices or require a multiple factor of self authentication based on management or compliance

35
00:04:02,310 --> 00:04:02,970
status.

36
00:04:03,360 --> 00:04:12,690
For example, with conditional access, you can allow access from only those of your users devices that

37
00:04:12,690 --> 00:04:15,750
are managed or compliant with corporate standards.

38
00:04:16,740 --> 00:04:25,560
You can restrict access to computers, jump to the corporate domain, and couldn't manage managed devices

39
00:04:25,560 --> 00:04:28,140
and computers drawn to the domain.

40
00:04:28,650 --> 00:04:36,270
And you can require multifactor authentication with the help of conditional access.

41
00:04:36,660 --> 00:04:44,160
For computers that are not joined to the domain and devices that are not compliant.

42
00:04:44,820 --> 00:04:51,450
Next up, we'll be talking about how this enables SSL in a single organization.

43
00:04:51,810 --> 00:04:52,860
I will sue that.