Updating old group policy templates
Replicating such a folder over the WAN (especially when promoting a new DC) can be very problematic.
When you configure the Group Policy settings for WSUS, use a Group Policy object (GPO) linked to an Active Directory container appropriate for your environment.
Whenever you do not need the added feature anymore you can simply reverse the process and instead of adding new . Before removing an Administrative Template, make sure you modify its policy settings and wait for Group Policy to refresh on all the computers that were supposed to be effected by the GPO.
This is because removing an Administrative Template that was previously installed does not change or remove any Registry settings that the GPO deployed when Group Policy was last processed.
The amount of Policy settings that have been removed is curently around 40 over all versions of Windows, including settings added to Operating systems via patches, but not available in the RTM version of the next release.
For example the setting “Do not reinitialize a pre-existing roamed user profile when it is loaded on a machine for the first time” has been added to Windows Server 2012 and Windows Server 2012 R2 via an update ( Furthermore, for a few Policy settings essential information in the ADMX files, such as the key value or the enabled / disabled values have changed.When you multiply this size by each Policy that SYSVOL contains, you can see that much space is devoted to these templates.