1
00:00:07,020 --> 00:00:11,850
Computer configuration settings apply at startup and are refreshed at regular intervals.

2
00:00:12,700 --> 00:00:15,250
Any startup scripts run at computer startup?

3
00:00:16,110 --> 00:00:20,940
The default interval is every 90 minutes, plus a random time between zero and 30 minutes.

4
00:00:21,090 --> 00:00:23,280
But this period of time is configurable.

5
00:00:24,150 --> 00:00:29,040
The exception to the set interval is domain controllers, which have their settings refreshed every

6
00:00:29,040 --> 00:00:29,790
5 minutes.

7
00:00:30,660 --> 00:00:35,450
User settings are applied at sign in and are refreshed at regular configurable intervals.

8
00:00:35,460 --> 00:00:39,930
The default also is 90 minutes, plus a random time between zero and 30 minutes.

9
00:00:40,830 --> 00:00:42,900
Any lag on scripts run at sign in.

10
00:00:43,770 --> 00:00:49,500
Note A number of user settings require to sign in before the user sees the effect of the GPO.

11
00:00:50,340 --> 00:00:55,410
This is because users who sign into the same computer use cached credentials to speed up sign ins.

12
00:00:56,310 --> 00:01:01,140
This means that although the policy settings are being delivered to the computer, the user is signed

13
00:01:01,140 --> 00:01:04,800
in already and the settings will therefore not take effect until the next sign.

14
00:01:05,790 --> 00:01:08,640
The folder redirection setting is an example of this.

15
00:01:09,540 --> 00:01:13,350
You can change the refresh interval by configuring a group policy setting.

16
00:01:14,190 --> 00:01:18,960
For computer settings, you can find the refresh interval setting in the computer configuration.

17
00:01:18,960 --> 00:01:20,130
Backslash Policies.

18
00:01:20,130 --> 00:01:21,930
Backslash Administrative Templates.

19
00:01:21,930 --> 00:01:22,890
Backslash System.

20
00:01:22,890 --> 00:01:24,570
Backslash Group Policy Node.

21
00:01:25,440 --> 00:01:31,140
For user settings, you can find the refresh interval in the corresponding settings under user configuration.

22
00:01:31,950 --> 00:01:34,980
An exception to the refresh interval is security settings.

23
00:01:35,880 --> 00:01:41,760
The security settings section of group policy is refreshed at least every 16 hours, regardless of the

24
00:01:41,760 --> 00:01:43,500
interval that you set for the refresh.

25
00:01:44,370 --> 00:01:47,040
This is not configurable via group policy.

26
00:01:47,910 --> 00:01:50,460
You can also refresh group policy manually.

27
00:01:51,330 --> 00:01:57,240
The command line utility pup date refreshes and delivers any new group policy configurations and removes

28
00:01:57,240 --> 00:01:59,040
settings that no longer apply.

29
00:01:59,880 --> 00:02:03,870
The update slash force command refreshes all the group policy settings.

30
00:02:04,770 --> 00:02:10,500
A new Windows PowerShell invoke update complete also performs the same function, but the coolant requires

31
00:02:10,500 --> 00:02:12,840
the Active Directory module to be installed.

32
00:02:13,760 --> 00:02:18,500
The advantage of the complete is that you can use it to refresh group policy on other computers than

33
00:02:18,500 --> 00:02:21,320
the one you were signed into by using the computer parameter.

34
00:02:22,190 --> 00:02:25,010
You cannot push group policy settings to a client.

35
00:02:25,910 --> 00:02:29,150
The client always pulls the settings from the domain controller.

36
00:02:30,020 --> 00:02:36,320
A feature introduced in Windows Server 2012 is the possibility to start a group policy refresh remotely.

37
00:02:37,160 --> 00:02:43,340
With this feature, administrators can use the PMC to target an O, u and force a group policy refresh

38
00:02:43,340 --> 00:02:46,190
on all of its computers and currently signed in users.

39
00:02:47,030 --> 00:02:51,050
To do this, you right click an EU and then click group policy update.

40
00:02:51,920 --> 00:02:53,810
The update occurs within 10 minutes.

41
00:02:54,710 --> 00:02:59,000
You will see a command line window open when the refresh is executing on the client.

42
00:02:59,900 --> 00:03:06,200
Note Sometimes the failure of a GPIO to apply is a result of problems with the underlying technology

43
00:03:06,200 --> 00:03:12,650
that is responsible for replicating ads and sizzle in Windows Server 2016.

44
00:03:12,740 --> 00:03:18,830
You can view the replication status by using the PMC, selecting the domain node, clicking the status

45
00:03:18,830 --> 00:03:20,750
tab and then clicking detect now.