Add an Approver Attribute to an Exchange Mail-Enabled AD Security Group
Question details
The user needs to add an approver to a mail-enabled Active Directory security group when the required Exchange attributes are missing.

- Product
- Microsoft Exchange Server and Active Directory
- Device & OS
- not provided
- Scenario
- An administrator wants to configure message approval for a mail-enabled universal security group in an on-premises Active Directory environment.
- Observed behavior
- Exchange group attributes may not appear in Attribute Editor when the Active Directory schema has not been prepared for Exchange.
Check which Exchange Server version is appropriate for your environment and review Microsoft's Active Directory preparation prerequisites for that version. Confirm that you have the required Schema Admins and Enterprise Admins permissions and access to the schema master.
Prepare the Exchange schema and configure the group approver
Use this method when the Exchange schema attributes are missing and you need to configure group moderation.
Exchange schema preparation adds Exchange-specific attribute definitions to Active Directory; it does not by itself install Exchange Server or configure an approver.
Use Exchange management tools for group moderation rather than editing the underlying attributes directly.
In PowerShell with the Active Directory module, run Get-ADObject -SearchBase (Get-ADRootDSE).schemaNamingContext -LDAPFilter "(lDAPDisplayName=msExchModeratedByLink)" to check for the approver-related attribute.
From a suitable domain-joined computer in the schema master's domain and site, open an elevated Command Prompt and run Setup.exe /PrepareSchema from the appropriate Exchange installation files. Include the license-acceptance switch required by your Exchange version; for example, current Exchange 2019 releases use /IAcceptExchangeServerLicenseTerms_DiagnosticDataON or /IAcceptExchangeServerLicenseTerms_DiagnosticDataOFF.
After setup completes successfully, run repadmin /replsummary and allow schema changes to replicate. Repeat the PowerShell schema check against the relevant domain controller.
In an on-premises Exchange Management Shell, run Set-DistributionGroup -Identity "Group Name" -ModerationEnabled $true -ModeratedBy "Approver" using the group's identity and the intended approver's identity.
Run Get-DistributionGroup -Identity "Group Name" | Format-List ModerationEnabled,ModeratedBy in Exchange Management Shell to verify that moderation is enabled and the approver is listed.

Troubleshoot an incomplete Exchange schema preparation
Use this method if Exchange setup reports missing registry keys or an assembly-loading error.
Document Exchange Group Configuration with WPS Office
WPS Office is a free, lightweight Office alternative with a familiar interface and Microsoft Office format compatibility, making it easy to move existing documentation into WPS. Use it to record group moderation settings and administration procedures; Exchange tools are still required to change the schema or approver.

Frequently Asked Questions
Why can't I see the approver attribute in Attribute Editor?
The Exchange schema may not have been prepared, or Attribute Editor may be filtering out attributes without values. In Active Directory Users and Computers, enable View > Advanced Features, open the group's Properties > Attribute Editor, and check the filter settings.
Do I have to install Exchange Server to extend the schema?
No. Exchange setup supports a separate /PrepareSchema operation. Use the appropriate installation files, permissions, prerequisites, and license switch described in Microsoft's guidance for your Exchange version.
How do I check who can approve messages for the group?
In on-premises Exchange Management Shell, run Get-DistributionGroup -Identity "Group Name" | Format-List ModerationEnabled,ModeratedBy. The output shows whether moderation is enabled and which approvers are configured.
What should I do if Exchange setup fails while loading an assembly?
Check C:\ExchangeSetupLogs\ExchangeSetup.log for the underlying error, use locally extracted installation media, and verify the version-specific prerequisites before retrying. Do not treat the schema preparation as complete until setup reports success.




