1
00:00:06,420 --> 00:00:13,680
When plan an Active Directory functionality you should consider the following high level aspects of

2
00:00:13,810 --> 00:00:15,260
all you design.

3
00:00:15,270 --> 00:00:18,550
The first aspect is administrative purpose.

4
00:00:18,570 --> 00:00:26,300
The O use structure should rely on primarily to administrative purposes such as your Active Directory

5
00:00:26,310 --> 00:00:30,690
tasks delegation modal and your GP.

6
00:00:30,810 --> 00:00:38,690
Avoid mimicking your organizational chart unless it benefits the administrative modal organization charts

7
00:00:38,700 --> 00:00:45,540
change frequently and it's not practical to change your or your structure that often.

8
00:00:45,690 --> 00:00:53,850
If you have requests for department specific GP O's it might be preferable to reflect those departments

9
00:00:53,970 --> 00:00:57,080
in a lower level of the O use structure.

10
00:00:57,090 --> 00:01:05,670
However it is also likely that you have a security and distribution group to reflect the users in this

11
00:01:05,670 --> 00:01:12,140
department and you can instead use security filtering for that purpose.

12
00:01:12,180 --> 00:01:20,310
Users and managers usually do not see the O use structure so there is no benefit in list and corporate

13
00:01:20,310 --> 00:01:22,090
hierarchies there.

14
00:01:22,260 --> 00:01:30,060
If you want to enable users to browse the organizational structure ensure that you fill in the manager

15
00:01:30,150 --> 00:01:32,850
attribute of the user object.

16
00:01:32,850 --> 00:01:41,040
This enables users to use current and previous versions of Microsoft Outlook in combination with the

17
00:01:41,370 --> 00:01:51,390
Exchange server message an infrastructure Microsoft Office 365 and Microsoft Exchange sort of SharePoint

18
00:01:51,390 --> 00:01:56,310
Server to navigate through the organizational structure.

19
00:01:56,310 --> 00:02:00,840
The O U is for administrative purposes only.

20
00:02:00,840 --> 00:02:03,340
Another aspect is inheritance.

21
00:02:03,360 --> 00:02:13,320
Inheritance is an important aspect of all new functionality both for delegation of control and GPO application.

22
00:02:13,320 --> 00:02:20,940
You should design their or use structure to include objects that require the same administrative control

23
00:02:20,940 --> 00:02:26,280
or group policy settings within the same you structure.

24
00:02:26,280 --> 00:02:34,260
This way you can assign the delegation of control or the GPO was set in only once at a higher level.

25
00:02:34,260 --> 00:02:39,670
In the all you structure rather than individually at each child level.

26
00:02:39,780 --> 00:02:47,310
Remember that you can block inheritance for a certain child or use if you do not want the US to apply

27
00:02:47,310 --> 00:02:52,970
the sentence for a higher or you level to a certain child or use.

28
00:02:53,220 --> 00:03:02,520
And lastly the change aspect design your own use structure to accommodate change after you implement

29
00:03:02,520 --> 00:03:04,230
an all you structure.

30
00:03:04,320 --> 00:03:12,480
It can be difficult to change especially if you also change design strategies such as changing from

31
00:03:12,480 --> 00:03:17,760
an organization based strategy to a resource based strategy.

32
00:03:17,790 --> 00:03:26,430
Ensure that your or use structure leaves room for organizational growth and a reasonable level of structural

33
00:03:26,640 --> 00:03:27,320
change.