Using the Administrative Template sections of the Object Editor, you can deploy modifications to user (HKCU) portions of the Registry of computers targeted by your Group Policy Object (GPO). All you need to do is to link your GPO to the appropriate site, domain, or organizational unit (OU) and let Group Policy processing do its job. Note that the administrative templates do not themselves modify the Registries of the target computers--all they do is creating the GUI elements in the Object Editor that let you configure Registry settings for computers targeted by your GPO.
Custom templates for Archive Manager Outlook Add-in Installer can manage archive and retrieve server settings for selected users. These changes will take an effect, when the user logs on to the computer. Combination of custom templates, with assigning Add-in Installer.msi method is recommended for users with limited privileges.
The following sections describe the process for MS Windows Server 2012 / 2012 R2 / 2016 / 2019.
Microsoft since Windows Vista and Windows Server 2008 is introducing a new format for displaying registry-based policy settings. Registry-based policy settings (located under the Administrative Templates category in the Group Policy Object Editor) are defined using a standards-based, XML file format, known as ADMX files. These new files replace ADM files, which used their own markup language.
Unlike ADM files, ADMX files are not stored in individual GPOs by default; however, this behavior is supported for less common scenarios. For domain-based enterprises, administrators can create a central store location of ADMX files accessible by anyone with permission to create or edit GPOs.
ADMX files are divided into language-neutral (ADMX) and language-specific (ADML) resources, available to all Group Policy administrators. These factors allow Group Policy tools to adjust their UI according to the administrator's configured language. Add-ing a new language to a set of policy definitions is achieved by ensuring that the language-specific resource file (ADML) is available. All ADMX files are authored as one language neutral file (.admx) and a set of language-dependent files that will be localized for all supported languages (.adml).
Steps to create a language-neutral (ADMX) file
The language-neutral file, .admx, determines the number and type of policy settings and their location by category in the Group Policy Object Editor display.
1.Start Notepad or any text editor to create your template.
2.Create an Archive Manager Outlook Add-in.ADMX file. For example:
<policyDefinitions revision="1.0" schemaVersion="1.0">
<target prefix="fullarmor" namespace="FullArmor.Policies.DA2B2B72_B85C_4D69_8B2B_C24939A38BF7" />
<using prefix="windows" namespace="Microsoft.Policies.Windows" />
<supersededAdm fileName="" />
<resources minRequiredRevision="1.0" />
<definition name="SUPPORTED_WindowsXP" displayName="$(string.SUPPORTED_WindowsXP)" />
<category name="ID_OutlookAdd-inCategory" displayName="$(string.ID_OutlookAdd-inCategory)" />
<policy name="ID_OutlookAdd-inPolicy" class="User" displayName="$(string.ID_OutlookAdd-inPolicy)" explainText="$(string.ID_OutlookAdd-inPolicy_Help)" presentation="$(presentation.ID_OutlookAdd-inPolicy)" key="Software\Metalogix\PAM4Exchange Outlook Add-in">
<parentCategory ref="ID_OutlookAdd-inCategory" />
<supportedOn ref="SUPPORTED_WindowsXP" />
<text id="ID_RetrieveServer" key="Software\Metalogix\PAM4Exchange Outlook Add-in" valueName="RETRIEVESERVER" />
<text id="ID_ArchiveServer" key="Software\Metalogix\PAM4Exchange Outlook Add-in" valueName="ARCHIVESERVER" />
Steps to create a language-resource (ADML) file
The language resource files, .adml, provide the language specific information needed by the language neutral file. The language neutral file will then reference specific sections of the language resource file in order for the Group Policy Object Editor to display a policy setting in the correct language.
1.Start Notepad or any text editor to create your template.
2.Create an Archive Manager Outlook Add-in.ADML file. For example:
<policyDefinitionResources revision="1.0" schemaVersion="1.0">
<description>Custom ADMX template for Archive Manager Outlook Add-in setup can manage archive and retrieve server settings for selected users. These changes will take an effect, when the user logs on to the computer. Combination of custom ADMX template, with assigning Add-in Installer.msi method is recommended for users with limited privileges. </description>
<string id="ID_OutlookAdd-inCategory">Archive Manager Outlook Add-in</string>
<string id="ID_OutlookAdd-inPolicy">Set Archive, Retrieve servers</string>
<string id="ID_OutlookAdd-inPolicy_Help">Custom ADMX template for Archive Manager Outlook Add-in setup can manage archive and retrieve server settings for selected users. These changes will take an effect, when the user logs on to the computer. Combination of custom ADMX template, with assigning Add-in Installer.msi method is recommended for users with limited privileges. </string>
<string id="SUPPORTED_WindowsXP">At least Microsoft Windows XP Professional or Windows Server 2003 family</string>
<label>Retrieve server name</label>
<label>Archive server name</label>
One of the main benefits of using the new ADMX files is the central store. The central store is a folder structure created in the Sysvol directory on the domain controllers in each domain in your organization. You will need to create the central store only once on a single domain controller for each domain in your organization. The File Replication service then replicates the central store to all domain controllers. It is recommended that you create the central store on the primary domain controller because the Group Policy Management Console and Group Policy Object Editor connect to the primary domain controller by default.
The central store consists of a root-level folder containing all language-neutral ADMX files and subfolders containing the language-specific ADMX resource files.
To perform this procedure, you must be a member of the Domain Administrators group in Active Directory.
Steps to create the central store
1.Create the root folder for the central store %systemroot%\sysvol\domain\policies\PolicyDefinitions on your domain controller.
2.Copy the Archive Manager Outlook Add-in.admx into %systemroot%\sysvol\domain\policies\PolicyDefinitions folder.
3.Create a subfolder under %systemroot%\sysvol\domain\policies\PolicyDefinitions for each language that your Group Policy administrators will use. Each subfolder is named after the appropriate ISO-style Language/Culture Name. For a list of ISO-style Language/Culture Names, see Locale Identifiers. For example, to create a subfolder for U.S. English, create the subfolder: %systemroot%\sysvol\domain\policies\PolicyDefinitions\EN-US.
4.Copy the Archive Manager Outlook Add-in.adml into %systemroot%\sysvol\domain\policies\PolicyDefinitions\EN-US sub-folder.
1.Start the Group Policy Management.
2.In the console tree, expand your Group Policy Objects
3.Expand context menu on newly created policy (described in Create a Group Policy Object), and click on edit.
4.Under User Configuration, expand Administrative Templates. The Group Policy Object Editor automatically reads all ADMX files stored in the central store. The Add-in policy must be listed on the right pane of the administrative template
5.To change that policy setting from its current state, double-click the name of the policy setting.
6.In the policy setting dialog box, click Enabled, which means: The registry reflects that the policy setting is selected.
7.Fill the Archive Manager archive, retrieve server names into this policy and apply these changes.