So let's wrap up this chapter with a summary of what we went over here.
So the first thing is that the group policy processing cycle is composed of two phases.
It's the core phase that does the job of figuring out what GPOs apply to the computer and user.
And it's the CSI phase that basically fires up each client side extension in turn and processes those
GPOs in order to apply the group policy settings.
Group policy processing can run either in the foreground, which is a computer startup or user log on
or in the background, which is that every 90 minute plus 30 minute random offset on workstations or
every 5 minutes on servers.
Group policy processing can run asynchronously, which is the default in every version of Windows client
since Windows XP or SYNCHRONOUSLY, which is the default on Windows Server.
And that's also it can be enabled on the client and obviously will slow down group policy processing
and therefore slow down the log on experience and the start up experience for the user.
But nonetheless, there are reasons to do it because of policy.
Areas that require synchronous foreground processing to run GP processing requires a DC to be present
without a DC.
Nothing can happen with respect to group policy processing.
It just doesn't work.
Slow links that are detected between the client and the DC can change which CCS will run.
And in that case, that sometimes clients add extensions like software installation or folder redirection
simply will skip that time if a slow link is detected.
And then finally, GP processing can be manually forced using either the command line update utility
a PowerShell complete group or group policies UI based update feature.