Microsoft Exchange System Attendant Service

Posted on 2016-08-03
Last Modified: 2016-08-03
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.
Question by:Tech Man
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4

Author Comment

by:Tech Man
ID: 41740717
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@
LVL 14

Expert Comment

by:Schnell Solutions
ID: 41740762

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.
LVL 19

Expert Comment

by:Peter Hutchison
ID: 41740764
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.
Back Up Your Microsoft Windows Server®

Back up all your Microsoft Windows Server – on-premises, in remote locations, in private and hybrid clouds. Your entire Windows Server will be backed up in one easy step with patented, block-level disk imaging. We achieve RTOs (recovery time objectives) as low as 15 seconds.


Author Comment

by:Tech Man
ID: 41740770
Thank you, I started the service just now.. I am not sure how this service got stopped. Any ideas?
LVL 14

Expert Comment

by:Schnell Solutions
ID: 41740772
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.

Author Comment

by:Tech Man
ID: 41740789
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?
LVL 14

Expert Comment

by:Schnell Solutions
ID: 41740805
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.
LVL 14

Accepted Solution

Schnell Solutions earned 500 total points
ID: 41740812
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.

Author Comment

by:Tech Man
ID: 41740825
Thank you very much for such dedicated response.
This is what I got for now:
Services Health check
LVL 14

Expert Comment

by:Schnell Solutions
ID: 41740959
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.

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A project that enables an administrator to perform actions within a user session context not just at the time of login but any time later on day(s) or week(s) later.
Did you know that more than 4 billion data records have been recorded as lost or stolen since 2013? It was a staggering number brought to our attention during last week’s ManageEngine webinar, where attendees received a comprehensive look at the ma…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.

738 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question