Once the GPO hits the clients, any background caching will stop. The actual setting is called Configure Group Policy Caching and it should be set to Disabled. Disabling the feature can be done using Group Policy from:Ĭomputer Configuration\Policies\Administrative Templates\System\Group Policy Our recommendation is to disable caching on clients if dictionaries are being used. These lists, which can be hundreds of megabytes in size, are copied at every Group Policy interval to the computers. This is not an issue from a security perspective, but obviously an unnecessary network operation. Leaving the Group Policy Caching in its default state will download the password dictionaries and hash lists stored in the Group Policy. Here’s the issue as it relates to Specops Password Policy. Even if no changes have been made to the Group Policy, and no local Group Policy Client Side Extension (CSE) is installed for the settings, the behavior will remain the same. Here’s the drawback: for every Group Policy update interval, Group Policy Caching will download, and store a local copy of all Group Policies that apply to the computer or user. Its purpose is to reduce the time it takes to perform certain scenarios for s ynchronous foreground Group Policy refresh. The release of Windows 8.1 and Server 2012 R2 introduced a new Group Policy concept called Group Policy Caching.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |