Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All

Active Directory


Applies to: Exchange Server 2016

Topic Last Modified: 2015-06-08

Microsoft Exchange Server 2016 uses Active Directory to store and share directory information with Windows. Starting with Exchange 2013, we made some changes to how Exchange works with Active Directory. These changes are discussed below.

The Active Directory driver is the core Microsoft Exchange component that allows Exchange services to create, modify, delete, and query for Active Directory Domain Services (AD DS) data. In Exchange 2013 and later, all access to Active Directory is done using the Active Directory driver itself. In previous versions of Exchange, DSAccess provided directory lookup services for components such as SMTP, message transfer agent (MTA), and the Exchange store.

The Active Directory driver also uses Microsoft Exchange Active Directory Topology (MSExchangeADTopology), which allows the Active Directory driver to use Directory Service Access (DSAccess) topology data. This data includes the list of available domain controllers and global catalog servers available to handle Exchange requests. For more information about the Active Directory Driver, see Active Directory Domain Services.

Exchange 2016 adds new attributes to the Active Directory domain service schema and also makes other modifications to existing classes and attributes. For more information about Active Directory changes when you install Exchange 2016, see Exchange 2016 Active Directory schema changes.

To learn more about how Exchange 2016 stores and retrieves information in Active Directory so that you can plan access to it, see Access to Active Directory.

For more information about Active Directory forest design, see AD DS Design Guide.

To learn more about computers running Windows in an Active Directory domain and deploying Exchange 2016 in a domain that has a disjoint namespace, see Disjoint namespace scenarios.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft