1
00:00:03,060 --> 00:00:06,900
So let's wrap up this chapter with a summary of what we went over here.

2
00:00:07,800 --> 00:00:12,690
So the first thing is that the group policy processing cycle is composed of two phases.

3
00:00:13,590 --> 00:00:18,930
It's the core phase that does the job of figuring out what GPOs apply to the computer and user.

4
00:00:19,830 --> 00:00:25,380
And it's the CSI phase that basically fires up each client side extension in turn and processes those

5
00:00:25,380 --> 00:00:28,230
GPOs in order to apply the group policy settings.

6
00:00:29,150 --> 00:00:34,610
Group policy processing can run either in the foreground, which is a computer startup or user log on

7
00:00:34,760 --> 00:00:41,180
or in the background, which is that every 90 minute plus 30 minute random offset on workstations or

8
00:00:41,180 --> 00:00:43,190
every 5 minutes on servers.

9
00:00:44,090 --> 00:00:49,790
Group policy processing can run asynchronously, which is the default in every version of Windows client

10
00:00:49,790 --> 00:00:55,400
since Windows XP or SYNCHRONOUSLY, which is the default on Windows Server.

11
00:00:56,260 --> 00:01:03,340
And that's also it can be enabled on the client and obviously will slow down group policy processing

12
00:01:04,180 --> 00:01:08,770
and therefore slow down the log on experience and the start up experience for the user.

13
00:01:09,640 --> 00:01:12,970
But nonetheless, there are reasons to do it because of policy.

14
00:01:12,970 --> 00:01:20,530
Areas that require synchronous foreground processing to run GP processing requires a DC to be present

15
00:01:21,430 --> 00:01:22,420
without a DC.

16
00:01:22,420 --> 00:01:25,720
Nothing can happen with respect to group policy processing.

17
00:01:26,560 --> 00:01:27,940
It just doesn't work.

18
00:01:28,860 --> 00:01:34,050
Slow links that are detected between the client and the DC can change which CCS will run.

19
00:01:34,920 --> 00:01:40,200
And in that case, that sometimes clients add extensions like software installation or folder redirection

20
00:01:40,350 --> 00:01:43,260
simply will skip that time if a slow link is detected.

21
00:01:44,130 --> 00:01:50,820
And then finally, GP processing can be manually forced using either the command line update utility

22
00:01:50,850 --> 00:01:55,470
a PowerShell complete group or group policies UI based update feature.