Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am having an issue with an Exchange 2003 Server I setup.

It seems to be working for the most part (pending MX record / PTR). The problem I am having now is the Exchange server is generating event ID 9187 and looks like this.

Microsoft Exchange System Attendant failed to add the local computer as a member of the DS group object 'cn=Exchange Domain Servers,cn=Users,dc=campbellsurvey,dc=local'. 

Please stop all the Microsoft Exchange services, add the local computer into the group manually and restart all the services. 

I don't have a clue what is going on, I have done a search and found a Microsoft KB Article relating to the problem. At first I thought it helped but about 15 mins later the error repeated. It seems to be trying what ever it is trying about every 15 mins.

share|improve this question
I assume you have restarted the Microsoft Exchange System Attendant... right? Also, please could you link to the Microsoft solution you tried? (I'm guessing this one but could you clarify?) – Ben Pilbrow Mar 22 '11 at 23:07
Yeah that is one I looked at – ianc1215 Mar 22 '11 at 23:16
And by the way I have tried this 3 times, once I just restarted the service, another I actually stopped all of the services and made the changes and the 3rd I rebooted the system (Not in actual order). – ianc1215 Mar 22 '11 at 23:22
OK, I started writing my answer before you put the comment about restarting the machine, but there are a couple of things in my answer that might help you out. – Ben Pilbrow Mar 22 '11 at 23:26
up vote 1 down vote accepted

I've only ever seen this message logged after moving the Exchange server computer object to a different OU in Active Directory. Restarting the System Attendant and all dependant services (Warning: Information Store - don't do in the middle of the day!) should solve your problem.

Looking at this Microsoft KB article, you can try taking the Exchange computer object out of the Exchange Domain Servers group, add it back in and bounce the System Attendant service.

Other quick digging reveals this note which basically says to make sure the primary group of your Exchange Server's computer object is Domain Computers as opposed to Exchange Domain Servers.

Failing all of the above, you could also try raising the diagnostic logging for the System Attendant to see if that reveals anything useful.

share|improve this answer
That very well may have been the problem, The primary domain group was NOT domain computers. I will know in about 20 mins whether it is fixed or not. – ianc1215 Mar 22 '11 at 23:35
I'd also just like to add my standard spiel of checking your AD replication is all healthy and in sync - there's nothing like 2 Domain Controllers telling you 2 totally conflicting things :-) – Ben Pilbrow Mar 22 '11 at 23:38
yeah that was the first thing I was thinking, AD is work flawless. – ianc1215 Mar 23 '11 at 0:00
Well its been 30 mins roughly and no error I am calling this one fixed. – ianc1215 Mar 23 '11 at 0:00

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.