However, if you have not introduced any Windows Server 2008-based domain controller in your forest but want to be able to control via Group Policies some of enhancements introduced in Vista, such as wired and wireless connectivity, as well as Bit Locker Drive Encryption and Trusted Platform Module functionality, you will need to extend Active Directory schema.
In the case of the former, you can follow instructions outlined in the Tech Net article Active Directory Schema Extensions for Windows Vista Wireless and Wired Group Policy Enhancements.
Effectively, it was not unlikely for the Group Policy setting provided some relief to Windows XP and Server 2003 based IT staff when dealing with this issue; however, this workaround was contingent on having copies of all templates used across the enterprise on each administrative system.
While this approach had its advantages (allowing you to remove ADM files from the share), it also introduced management overhead (forcing you to develop a methodology ensuring that consistent set of templates is maintained on all systems from which Group Policy is viewed or edited).
Vista and Windows Server 2008 help you resolve these problems by leveraging ADMX templates (the name is indicative of their new XML-based format), which offer a number of important advantages over their predecessors: bloat caused by multiple copies of the same templates scattered across individual Group Policy Template folders is eliminated, since ADMX files are automatically loaded from a couple of designated locations.
The first one is the share, replicated across all domain controllers in the same domain (such approach minimizes volume of replication traffic and eliminates management overhead associated with maintaining set of templates on each administrative workstation).
However, their initial implementation exhibited some undesired behavior.
The majority of problems were related to the mechanism used to present registry-based settings in Group Policy editing tools, which relied on specially formatted files, known as Administrative Templates (also referred to as ADM files).
Instead, they will appear in the "Extra Registry Settings" section of the Group Policy Management Console-based reports.
By continuing to browse our site you agree to our use of data and cookies.
In the previous installment of our series dedicated to the most prominent Directory Services-related features available in the Windows Server 2008, we started discussing Group Policy functionality by describing its basic principles and providing an overview of innovations incorporated into its client-based components.
The procedure required to support the latter is also documented on Tech Net site in the article Bit Locker Drive Encryption Configuration Guide: Backing Up Bit Locker and TPM Recovery Information to Active Directory.
Next, copy all content stored in the (including ADMX files and language specific subfolders with ADML resource files) to the newly created folder on the domain controller.