CREATED by PAUL RYAN, Date: Monday, February 14, 2014 | Download Complete PDF:

In Microsoft Exchange Server, System Attendant regulates three basic functions: Maintenance, Monitoring, and Directory Lookups. Basically, it is a collection of sub-components that is meant to control internal functions of Exchange Server and relies to the requests of Proxy Active Directory. The executable file of System Attendant is MAD.EXE that is located at Program Files\Exchsrvr\Bin folder and its components exists as .dll file.

Some of the common responsibilities of System Attendant include mounting database, management of mailbox, examining the Directory Server etc. Since most of the Exchange related services are dependent on it, System Attendant functioning is it positive or negative will affect performance of Exchange Server.

In Exchange Server version 2003, mounting database is not possible until SA service is not active. In addition to this, working of Information Store is also dependent on SA service. In versions prior of 2003, there are various operations that could not be completed if System Assistant is not running.

For Example: There are number of functions in Exchange Server 2000 and 2003 that completely relies on smooth working of System Attendant. Due to any reason if SA is not in consistent state, problems while mounting database on Server are experienced plus error messages can be encountered. Example: Failure of this service can result in error message like:

"Could not start the Microsoft Exchange System Attendant Service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion."

To work around Exchange Server error 1053, you can take help of Exchange Server Best Practices Analyzer Tool. It checks out if the Exchange Server is configured accordingly for performing defined tasks.

The default User Container is checked out for -Exchange Services, Exchange Enterprise Services, Exchange Domain Servers when the SA starts. In case any group is missing, System Assistant refuses to start. To work around, three groups should be moved to default user container.

About Components of Exchange System Attendant

• DSAccess Component: The main task of DSAccess is to respond to the information that is being requested, cache it and then give pass the required result to the component that requested for it.
• DSProxy Component: In case of DSAccess, the query comes from the Exchange Server while in case of DSProxy, it is from MS Outlook. In many version of Outlook, the client is incapable of communicating with the Global Catalog Server, so the DSProxy.dll performs this task on behalf of Outlook.
• Recipient Update Service: Abv_dg.DLL is a sub component of System Assistant that enforces recipient-policies to the user-enabled objects.
• Mailbox Manager Component: It is responsible for implementing policies that help in regulating the size of information store and the retention policy for mailboxes.
• Server Monitor Component: It has the job of maintaining the link state of Exchange Server so as to ensure that Server does not have to rely upon the static entries in routing table.
• Offline Address Book Generator: OADgen.dll is a sub component of SA helps in accessing contact details when not connected with Exchange Server. This is meant for mobile users who cannot retrieve GAL and thus can rely upon the Offline Address Book.
• Free/Busy Component: The meetings and schedules can be organized according to the free/busy updates of the attendees. This can be possible if the Free/Busy option is enabled so that the Exchange is able to read the free or busy status of the attendee.
• Metabase Update Service: The IIS metabase is a file that keeps a record of IS configuration information. This component of SA is responsible for making up-dations in IIS metabase.