Your company has an Active Directory forest. The company has servers that run Windows
Server 2008 R2 and client computers that run Windows 7. The domain uses a set of GPO
administrative templates that have been approved to support regulatory compliance
requirements.
Your partner company has an Active Directory forest that contains a single domain. The
company has servers that run Windows Server 2008 R2 and client computers that run
Windows 7.
You need to configure your partner company’s domain to use the approved set of
administrative templates.
What should you do?

A.
Use the Group Policy Management Console (GPMC) utility to back up the GPO to a file.
In each site, import the GPO to the default domain policy.

B.
Copy the ADMX files from your company’s PDC emulator to the PolicyDefinitions folder
on the partner company’s PDC emulator.

C.
Copy the ADML files from your company’s PDC emulator to the PolicyDefinitions folder
on the partner company’s PDC emulator.

D.
Download the conf.adm, system.adm, wuau.adm, and inetres.adm files from the Microsoft
Updates Web site. Copy the ADM files to the PolicyDefinitions folder on thr partner
company’s emulator.

Explanation:
http://support.microsoft.com/kb/929841
How to create the Central Store for Group Policy Administrative Template files in Windows
Vista Windows Vista uses a new format to display registry-based policy settings. These
registry-based policy settings appear under Administrative Templates in the Group Policy
Object Editor. In Windows Vista, these registry-based policy settings are defined by
standards-based XML files that have an .admx file name extension. The .admx file format
replaces the legacy .adm file format. The .adm file format uses a proprietary markup
language.

In Windows Vista, Administrative Template files are divided into .admx files and languagespecific .adml files that are available to Group Policy administrators.
..
Administrative Template file storage
In earlier operating systems, all the default Administrative Template files are added to the
ADM folder of a Group Policy object (GPO) on a domain controller. The GPOs are stored in
the SYSVOL folder. The SYSVOL folder is automatically replicated to other domain
controllers in the same domain. A policy file uses approximately 2 megabytes (MB) of hard
disk space. Because each domain controller stores a distinct version of a policy, replication
traffic is increased.
Windows Vista uses a Central Store to store Administrative Template files. In Windows
Vista, the ADM folder is not created in a GPO as in earlier versions of Windows. Therefore,
domain controllers do not store or replicate redundant copies of .adm files.
The Central Store
To take advantage of the benefits of .admx files, you must create a Central Store in the
SYSVOL folder on a domain controller. The Central Store is a file location that is checked by
the Group Policy tools. The Group Policy tools use any .admx files that are in the Central
Store. The files that are in the Central Store are later replicated to all domain controllers in
the domain.
To create a Central Store for .admx and .adml files, create a folder that is named
PolicyDefinitions in the following location:
\\FQDN\SYSVOL\FQDN\policies
Note: FQDN is a fully qualified domain name.
…
http://www.frickelsoft.net/blog/?p=31
How can I export local Group Policy settings made in gpedit.msc?
Mark Heitbrink, MVP for Group Policy came up with a good solution on how you can
“export” the Group
Policy and Security settings you made in on a machine with the Local Group Policy
Editor (gpedit.msc) to other machines pretty easy:
Normal settings can be copied like this:
1.) Open %systemroot%\system32\grouppolicy\
Within this folder, there are two folders – “machine” and “user”. Copy these to folders to the
“%systemroot%
\system32\grouppolicy – folder on the target machine. All it needs now is a reboot or a
“gpupdate /force”.
Note: If you cannot see the “grouppolicy” folder on either the source or the target machine,
be sure to have your explorer folder options set to “Show hidden files and folders”…
For security settings:
1.) Open MMC and add the Snapin “Security Templates”.
2.) Create your own customized template and save it as an “*inf” file.
3.) Copy the file to the target machine and import it via command line tool “secedit”: secedit
/configure /db %temp%\temp.sdb /cfg yourcreated.inf
Further information on secedit can be found here:
http://www.microsoft.com/resources/documentation/
windows/xp/all/proddocs/en-us/secedit_cmds.mspx?mfr=true
If you’re building custom installations, you can pretty easy script the “overwriting” of the
“machine”/”user”- folders or the import via secedit by copying these file to a share and copy
and execute them with a script.