1
00:00:06,430 --> 00:00:11,830
You can link more than one beer so to a user or a security group.

2
00:00:11,830 --> 00:00:20,410
This happens when a user is a member of multiple security groups that might each already have an assigned

3
00:00:20,410 --> 00:00:27,730
peer so or when you're assigned multiple episodes directly to user object.

4
00:00:27,730 --> 00:00:35,190
In either case only one peer so can be the effective password policy if you assigned multiple pesos

5
00:00:35,200 --> 00:00:37,000
to a user or a group.

6
00:00:37,010 --> 00:00:45,300
The amass Diaz Desh password settings precedents attribute helps to determine the resultant.

7
00:00:45,330 --> 00:00:50,810
So appear so with a lower well you takes precedence or appear.

8
00:00:50,800 --> 00:00:58,770
So with a higher well you the following process describes how ADT is determines the resultant beer.

9
00:00:58,770 --> 00:01:08,320
So if you link multiple SOS to a user or a group one and appear so that you link directly to a user

10
00:01:08,320 --> 00:01:10,390
object is a resultant beer.

11
00:01:10,390 --> 00:01:19,270
So if you link multiple beers SOS directly to the user object they appear sober the lowest math details

12
00:01:19,310 --> 00:01:21,390
their passwords set and precedence.

13
00:01:21,390 --> 00:01:23,810
Well here is the resultant beer.

14
00:01:23,820 --> 00:01:32,600
So if two beers SOS have the same precedence that beer so with the mathematical smallest object.

15
00:01:32,740 --> 00:01:35,940
Greed is a resultant piece or two.

16
00:01:36,250 --> 00:01:40,640
If you do not link any beer so directly to the user object.

17
00:01:40,820 --> 00:01:49,660
Edit s compares the pure source for role global security groups that contain the user object.

18
00:01:49,750 --> 00:01:54,910
They appear sober the lowest amongst the s password sets precedents.

19
00:01:54,990 --> 00:02:01,750
Value is the resultant payer so if you apply multiple power source to the same user and they have the

20
00:02:01,750 --> 00:02:09,640
same password certain precedents well you edit it supplies Libya so with the mathematically smallest

21
00:02:10,000 --> 00:02:18,910
object greed in the first case and 3 if you do not link any beer so to the user object either directly

22
00:02:18,910 --> 00:02:21,940
or indirectly through group membership.

23
00:02:22,210 --> 00:02:30,830
Edit Yes applies the default domain policy all user objects contain a new attribute called Amex d s

24
00:02:30,860 --> 00:02:38,830
dash resultant beer so which I've already mentioned you can use this attribute to determine the distinguished

25
00:02:38,830 --> 00:02:44,310
name of the beer so that it is applies to the user object.

26
00:02:44,590 --> 00:02:52,030
If you do not link API so to the user object this attribute does not contain any well you and the default

27
00:02:52,030 --> 00:02:59,770
demand group policy contains the effective password policy to view the effective bill so that 8 ideas

28
00:03:00,130 --> 00:03:10,030
applies to a user open active directory user and computers and the view menu ensure that advanced features

29
00:03:10,330 --> 00:03:11,300
is enabled.

30
00:03:11,470 --> 00:03:19,030
You then should open the proper use of a user account and you can view the I must Diaz dash resultant

31
00:03:19,040 --> 00:03:23,310
P so attribute on the attribute editor tab.

32
00:03:23,410 --> 00:03:29,890
If you have configured the show constructed attributes option under the filter options.

33
00:03:29,950 --> 00:03:36,640
Please know that while you must define B as SOS from a highly privileged group such as demand admins

34
00:03:37,000 --> 00:03:41,700
you should train helpdesk administrators to evaluate their effective peers.

35
00:03:41,710 --> 00:03:43,310
SOS for a user.

36
00:03:43,330 --> 00:03:50,950
This helps administrators answer a user's questions when they do not understand which password sentence

37
00:03:51,060 --> 00:03:51,640
apply.