1 00:00:00,420 --> 00:00:07,650 You must complete several processes before group policy settings actually apply to a user or a computer. 2 00:00:07,650 --> 00:00:10,840 In this lesson we'll discuss these processes. 3 00:00:10,870 --> 00:00:15,260 Your application must cure before GPO can take effect. 4 00:00:15,270 --> 00:00:22,640 The group policy container in 80 Days must replicate to the domain controller from which the group policy 5 00:00:22,650 --> 00:00:26,700 client service obtains its ordered list of Jabil. 6 00:00:26,910 --> 00:00:33,630 Additionally the group policy template in this wall must replicate to the same domain controller group. 7 00:00:33,630 --> 00:00:41,070 Changes must replicate if you have added a new group or changed the membership of a group that is used 8 00:00:41,070 --> 00:00:42,840 to filter the GPO. 9 00:00:42,840 --> 00:00:45,570 Then the change must be replicated. 10 00:00:45,600 --> 00:00:51,970 Also furthermore the change must be in the security token of the computer of the user which requires 11 00:00:51,970 --> 00:00:59,370 the registrar of the computer to update its group membership over sign in and sign out of the user to 12 00:00:59,670 --> 00:01:01,860 update their group membership. 13 00:01:01,890 --> 00:01:06,930 The next condition is that user or computer group policy refresh master cure. 14 00:01:07,110 --> 00:01:14,040 So group policy refresh happen set start up for computer resurgence at signing and for user settings 15 00:01:14,250 --> 00:01:19,770 and every 90 to 120 minutes thereafter by default. 16 00:01:19,770 --> 00:01:27,450 Please remember that the practical impact of the group policy Refresh Interval is what is when you make 17 00:01:27,450 --> 00:01:29,510 a change in your environment. 18 00:01:29,550 --> 00:01:37,980 It will be on average one half the time or 45 to 60 minutes before the change starts to take effect 19 00:01:38,160 --> 00:01:38,990 by default. 20 00:01:39,000 --> 00:01:43,570 Windows XP Windows Vista Windows 7 8 8 1. 21 00:01:43,710 --> 00:01:49,290 And term clients perform only background refreshes at startup ie on signing. 22 00:01:49,470 --> 00:01:56,370 Which means that a client might start up and a user might sign in without receiving the latest policies 23 00:01:56,370 --> 00:01:57,440 from the domain. 24 00:01:57,450 --> 00:02:04,680 It is highly recommended that you change this default behavior so that policy changes implement in a 25 00:02:04,680 --> 00:02:11,910 managed predictable way enable the policy settings or set and sorry which is called always wait for 26 00:02:11,910 --> 00:02:19,800 network at startup and log on for all windows clients asset and it is located in computer configuration 27 00:02:19,800 --> 00:02:24,330 policies administrative templates system and log on. 28 00:02:24,330 --> 00:02:28,100 Be sure to read the policy settings explanatory text. 29 00:02:28,110 --> 00:02:34,200 This does not affect the startup or sign in time for computers that are not connected to a network. 30 00:02:34,200 --> 00:02:39,980 If the computer detects that it is disconnected it doesn't wait for a network. 31 00:02:40,020 --> 00:02:45,770 The next condition at that user must sign out and sign in or computer must restore it. 32 00:02:45,960 --> 00:02:51,840 Although most said and supplied you run a background policy refresh some client side extensions do not 33 00:02:51,840 --> 00:02:56,330 apply the set and until the next start up or log on a wound. 34 00:02:56,340 --> 00:03:04,330 For example newly added startup and log on script policies do not run until the next computer startup 35 00:03:04,370 --> 00:03:07,260 or log on software installation will accurate. 36 00:03:07,260 --> 00:03:14,130 The next startup if the software is assigned in computer resurgence and also changes to folder redirection 37 00:03:14,130 --> 00:03:18,300 policies will not take effect until the next log on. 38 00:03:18,300 --> 00:03:21,220 Also consider manual refresh group policy. 39 00:03:21,480 --> 00:03:27,780 When you experiment with group policy process and you need to initiate a group policy refresh manually 40 00:03:27,990 --> 00:03:32,150 so that you do not have to wait for the next background to refresh. 41 00:03:32,160 --> 00:03:38,010 You can use the GP update command to initiate a group policy refresh used on its own. 42 00:03:38,010 --> 00:03:45,030 This command triggers process an identical it to group policy background refresh both the computer policy 43 00:03:45,060 --> 00:03:47,430 and the user policy are refreshed. 44 00:03:47,430 --> 00:03:57,030 You can use the slashed target column computer option or target column user parameter to limit the refresh 45 00:03:57,030 --> 00:04:03,870 to computer or user settings during background refresh my default settings are applied to only if the 46 00:04:03,870 --> 00:04:12,000 GPO has been updated or changed the slash forced switch causes the system to reapply all settings and 47 00:04:12,120 --> 00:04:16,100 all GP always scoped to user or computer. 48 00:04:16,200 --> 00:04:23,790 Some policies settings require a sign out and restore before they take effect the slashed log off and 49 00:04:23,880 --> 00:04:30,200 slash boot switches of GP update command cause a sign out or restart. 50 00:04:30,270 --> 00:04:35,760 You can use these switches when you apply settings that require sign out or restart. 51 00:04:35,760 --> 00:04:42,560 For example the command that will cause a total refresh application and if necessary restart and sign 52 00:04:42,560 --> 00:04:51,210 in to apply updated policy settings will be looking like that GP update slash force slash log off slash 53 00:04:51,210 --> 00:04:59,340 board and the last condition you have to consider about group policy about when settings become effective 54 00:04:59,500 --> 00:05:03,860 is that most Glenside side extensions do not reapply surgeons. 55 00:05:03,970 --> 00:05:05,730 The GPO has not changed. 56 00:05:05,740 --> 00:05:13,060 Remember that most client side extensions apply sentence in a GPO only if the GPL version has changed. 57 00:05:13,060 --> 00:05:19,750 This means that if a user can change a certain level group policy originally specified then the selling 58 00:05:20,020 --> 00:05:27,400 will not be brought back into compliance with a set of that the GPO specifies until the GPO changes. 59 00:05:27,400 --> 00:05:33,260 Fortunately most policy settings cannot be changed by a non administrative user. 60 00:05:33,370 --> 00:05:40,530 However if a user is an administrator of his or her computer or even the policies said in effect they 61 00:05:40,530 --> 00:05:46,370 are part of the registry or the system that the user has permissions to change. 62 00:05:46,430 --> 00:05:48,680 Then this could be a real problem. 63 00:05:48,700 --> 00:05:55,900 You have the option of instructing each client side extension to reply the sentence of yours even if 64 00:05:55,900 --> 00:05:57,950 the GOP rules have not been changed. 65 00:05:57,970 --> 00:06:04,030 You can configure the process and behavior of each client site extension in the policies set and found 66 00:06:04,090 --> 00:06:06,430 in computer configuration. 67 00:06:06,430 --> 00:06:08,060 Administrative templates. 68 00:06:08,110 --> 00:06:10,210 System group policy. 69 00:06:10,270 --> 00:06:13,920 So I guess this is the end of the of this part. 70 00:06:14,050 --> 00:06:18,400 And as a quick test and quick question for you please answer. 71 00:06:18,400 --> 00:06:23,050 Is it possible to link more than one w and my filter to a GPO.