1
00:00:03,050 --> 00:00:08,030
So in this demo, I'm going to do a couple of things to kind of illustrate what I just talked about.

2
00:00:08,920 --> 00:00:15,700
The first thing I'm going to do is I'm on my client's system and I'm going to do it's called the Update

3
00:00:15,700 --> 00:00:18,370
Command, which I'm about to talk about in detail.

4
00:00:18,490 --> 00:00:22,750
But it's suffice to say that this is a way of manually forcing a group policy update.

5
00:00:23,620 --> 00:00:28,390
And what's going on here is that my domain controller is not available, so I'm going to be trying to

6
00:00:28,390 --> 00:00:32,230
update group policy while the domain controller is basically offline.

7
00:00:33,100 --> 00:00:37,900
And we can see what happens when the client tries to run the group policy processing cycle.

8
00:00:38,800 --> 00:00:45,460
So what you see is it's trying to run user policy updating and it's giving this message that processing

9
00:00:45,460 --> 00:00:48,910
failed Windows cannot obtain the name of the domain controller.

10
00:00:49,870 --> 00:00:55,990
So obviously a lack of a domain controller prevents group policy processing from succeeding completely.

11
00:00:56,880 --> 00:01:01,920
Now the other piece of the puzzle that I wanted to sort of demo is how you can change the behavior of

12
00:01:01,920 --> 00:01:03,420
group policy processing.

13
00:01:04,230 --> 00:01:09,090
And so what I'm going to do is go ahead and bring back my domain controller and bring up group policy

14
00:01:09,090 --> 00:01:10,130
management console.

15
00:01:10,140 --> 00:01:12,750
And I'm just going to go ahead and edit a group policy.

16
00:01:13,630 --> 00:01:16,090
And open up under computer configuration.

17
00:01:16,090 --> 00:01:17,380
Administrative Templates.

18
00:01:17,380 --> 00:01:17,830
System.

19
00:01:17,830 --> 00:01:18,730
Group Policy.

20
00:01:19,590 --> 00:01:22,530
And you see a lot of the options that I've mentioned in here.

21
00:01:23,480 --> 00:01:28,250
So I can configure behavior for various group policy client side extensions.

22
00:01:29,170 --> 00:01:34,230
For example, if I wanted the script CC to always process even over a slow link.

23
00:01:35,150 --> 00:01:37,190
I could click this option here and apply it.

24
00:01:37,190 --> 00:01:42,770
And any computers that process this policy will always run scripts, even if a slow link is detected.

25
00:01:43,690 --> 00:01:49,270
I could also for security policy, for example, I could go ahead and say process this even if group

26
00:01:49,270 --> 00:01:51,220
policy objects have not changed.

27
00:01:52,090 --> 00:01:56,770
And what this effectively does is for the security client side extension only.

28
00:01:57,650 --> 00:02:01,220
It will run during both foreground and background refresh cycles.

29
00:02:02,120 --> 00:02:04,760
It will run and reprocess all the settings.

30
00:02:05,690 --> 00:02:12,290
So instead of basically doing no work because nothing has changed, it will say it will sort of assume

31
00:02:12,290 --> 00:02:15,380
that something's changed and reprocess all of those policies.

32
00:02:16,250 --> 00:02:21,500
And I've seen organizations use that feature, especially for security policy, to ensure that if for

33
00:02:21,500 --> 00:02:27,110
some reason somebody had gone in and managed to unset a security setting, a group policy processing

34
00:02:27,110 --> 00:02:27,950
would come along.

35
00:02:27,980 --> 00:02:33,080
You know, at 90 minute intervals or 5 minutes on server and reapply those security settings.

36
00:02:34,010 --> 00:02:40,790
So these are the kinds of handy features you can use some of these configuration settings for to change

37
00:02:40,790 --> 00:02:44,480
the default behavior of group policy under different circumstances.