Microsoft Exchange System Attendant Service

I have a question regarding Microsoft Exchange System Attendant Service. While I was in Services console, I have realized that Exchange System Attendant Service is not running. I am not sure if this service should be running all the time? should I start it? or leave it alone? No one complained yet about anything. I don't see any event log errors as well.
Please advise.
Tech ManAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

Schnell SolutionsConnect With a Mentor Systems Infrastructure EngineerCommented:
By the way,

The same command: Test-ServiceHealth will let you know the specific exchange critical services for your environment.

And this is amazing, if you have many exchange servers, from any EMS console you just need to execute:
Get-ExchangeServer | Test-ServiceHealth
and it will let you know the service health for all your exchange servers.

Note: Check the output of the command, where it says services running and there you will have the list of exchange services that you are using (They are basically the services configured to start automatically that start with the name Exchange*). If there is any service included in ServicesNotRunning, there you will have services that need further attention, i.e. a manual start.
Tech ManAuthor Commented:
Sorry, I forgot to clarify that I have Exchange 2010, Domain functional Level Windows Server 2008R2. Domain Controllers : Windows Server 2008R2 and Windows Server 2012 R@
Schnell SolutionsSystems Infrastructure EngineerCommented:

This service should be started and running, it is in charge of providing monitoring, maintenance, and directory lookup services in Exchange. It is not related directly to the final users like other services, but you can eventually have many internal exchange infrastructure issues if this is not running.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Peter HutchisonSenior Network Systems SpecialistCommented:
Yes, it should be running. Without it, you will be loosing the following services:
a) Directory lookups to a DC server for legacy Outlook clients
b) Generate e-mail addresses
c) Offline address books
d) Update free/busy info for legacy clients
e) Maintain permissions and group membership for the server.
Tech ManAuthor Commented:
Thank you, I started the service just now.. I am not sure how this service got stopped. Any ideas?
Schnell SolutionsSystems Infrastructure EngineerCommented:
Sometimes it happens that when Exchange starts some services do not start due mainly to dependencies that are not ready.

But the real way to know why this service was down is reviewing the application logs, if the information there is not enough, then it is necessary to increment the debugging log for that service and check the application log again.
Tech ManAuthor Commented:
Is there any way in Exchange 2010 to receive any type of notifications when critical Service is not running. For example, I check event log almost daily but did not see anything unusual. This time, I was doing something else and noticed this service is not running. Do we have a list of all critical services that should run and anyway to get an alert?
Schnell SolutionsSystems Infrastructure EngineerCommented:
Ideally you should have a monitoring software that checks services, free disk space, processor, memory, etc. From a Microsoft perspective there is a premium product that requires a separate license, which is called Microsoft System Center Operations Manager. Maybe this is the best application to monitor exchange but it requires a license and a special implementation, nonetheless, there are many third party tools in the market that they can make a decent job monitoring exchange as well.

Another native solution that you can implement, but it will require lot of manual work, is that you configure internal system alerts to monitor these services and other components. It is because windows has the capability to alert you by email for example, when an event occurs, such as a service not running.

Finally, a manual way of detecting very fast if there is any exchange service not running or with any issue, is executing the following command from the Exchange Management Shell:
This command will let you know about any required exchange service that is not running at the moment.
Tech ManAuthor Commented:
Thank you very much for such dedicated response.
This is what I got for now:
Services Health check
Schnell SolutionsSystems Infrastructure EngineerCommented:
Great. Notice that now the three areas of 'ServicesNotRunning' are empty. When you have at least one service not running it will appear there. You also have the list of critical exchange services there, the reason why this is separate, it is because the services are listed per role basics. The first group are the services related to 'Mailbox Server Role', and the second and third group about 'Client Access' and 'Hub Transport' respectively.
All Courses

From novice to tech pro — start learning today.