Microsoft exchange directory service

In this article. Provides Active Directory topology information to Exchange services. If this service is stopped, most Exchange services can't start. Provides Exchange SmartScreen spam definition updates. The existing SmartScreen spam definitions were left in place, but their effectiveness will likely degrade over time. Provides storage and database layout management for Mailbox servers in database availability groups DAGs. If you don't have any subscribed Edge Transport servers, you can disable this service.

Auto applies important security mitigations on Exchange Server to secure against known threats. Part of managed availability that monitors the health of key components on the Exchange server. Part of managed availability that attempts to recover unhealthy components on the Exchange server. By default, this service isn't running, so IMAP4 clients can't connect to the Exchange server until this service is started.

If you don't have any IMAP4 clients, you can disable this service. Each Exchange server must communicate with Active Directory to retrieve information about recipients and information about the other Exchange servers. Mailbox servers store configuration information about mailbox users and mailbox stores in Active Directory. Additionally, the Mailbox server stores information in Active Directory for the Client Access protocols, Transport service, Mailbox databases, and so on.

The Mailbox server handles all activity for the active mailboxes on that server. By default, whenever an Exchange server starts, it binds to a randomly selected domain controller and global catalog server in its own site. You can also use the Set-ExchangeServer cmdlet to configure a static list of domain controllers that an Exchange server should bind to or a list of domain controllers that should be excluded. Active Directory Recycle Bin helps minimize directory service downtime by enhancing your ability to preserve and recover accidentally deleted Active Directory objects without restoring Active Directory data from backups, restarting Active Directory Domain Services AD DS , or rebooting domain controllers.

The most important thing to understand about recovering deleted Exchange-related Active Directory objects is that Exchange objects don't exist in isolation. For example, when you mail-enable a user, several different policies and links are calculated for the user based on your current Exchange configuration. Two problems that may arise when you restore a deleted Exchange configuration or recipient object are:.

Collisions : Some Exchange attributes must be unique across a forest. For example, all email addresses on a mail-enabled object also known as proxy addresses must be unique. Two different mail-enabled objects can't have the same email address. Active Directory doesn't enforce proxy address uniqueness Exchange administrative tools check for uniqueness.

Exchange email address policies also automatically resolve possible conflicts in proxy address assignment based on deterministic rules. Therefore, restoring an Exchange user object might create a collision with proxy addresses or other attributes that should be unique. Misconfigurations : Exchange has automated rules that assign various policies or settings.

Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads.

Remove From My Forums. In Exchange and later, all access to Active Directory is done using the Active Directory driver itself. This data includes the list of available domain controllers and global catalog servers that are available to handle Exchange requests. Exchange add new attributes to the Active Directory domain service schema and also make other modifications to existing classes and attributes.

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