Solved

Microsoft Exchange System Attendant failed to add the lcoal computer

Posted on 2010-11-15
12
588 Views
Last Modified: 2012-06-27
Dear all,

My exchange is down now... all exchange services stopped.

in the event viewer i found these errors.
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=aaa,dc=local'.

my exchange server also a domain controller.

In Activedirectory users computers exchange domain servers i didn't find my exchange server account. Even in computers accounts also i didn't find my exchanger server account.

How to resolve this issue... please help me.

regards

0
Comment
Question by:nivasnet
  • 5
  • 3
  • 3
12 Comments
 
LVL 25

Expert Comment

by:Tony Johncock
ID: 34136338
Assuming the computer account hasn't been deleted (if you turn on advanced features in AD Users and Computers and then do a search in the entire domain for its name, when you right-click, properties, you can see a new tab called "Object" that will list the full path to the machine) the following may be of some use to you:

http://support.microsoft.com/kb/271335
0
 
LVL 5

Expert Comment

by:jawad1481
ID: 34136387
Hello,

open ADUC on Domain Controller --> Right click on Domain --> find ---> Search for Exchange server account. If its not present then go to run window --> Type ADSIEDIT.msc

Expand Configuration partition --> Services --> Microsoft Exchange --> First Org --> Administrative groups --> First ADMin groups --> Servers --> Exchange server object.

Check if you have Exchange Server object.

let me know.

regards,
:)

0
 

Author Comment

by:nivasnet
ID: 34136617
Yes, Computer Account is not there... ADUC---DomainControllers-- here i did not find exchanger server computer account.
so that i created manually... i added in Exchang domain servers group.

than i restarted eventhough not services not starting.

0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 25

Expert Comment

by:Tony Johncock
ID: 34136640
It's no good just looking in one place though - it could have been moved to another part of Active Directory.

However, if it let you recreate the account with the same name, that suggests somone deleted it and you have other problems if that's the case!
0
 

Author Comment

by:nivasnet
ID: 34136672
In the first Admin groups i can see my exchange server name: there i can see first information store also but when i am expanding i am getting error saying ms exchange information store service is not running... ...
0
 

Author Comment

by:nivasnet
ID: 34136701
yes r we can have a look. is it ok for you with teamviewer.
0
 

Author Comment

by:nivasnet
ID: 34136703
because i don't logme accounts.
0
 
LVL 5

Expert Comment

by:jawad1481
ID: 34136793
Ok
Team viewer...

regards,
:)
0
 
LVL 25

Expert Comment

by:Tony Johncock
ID: 34136830
Good luck tracking it down gents - give me a shout if I can be of any assistance, but I suspect you're in safe hands and won't need it.
0
 
LVL 5

Accepted Solution

by:
jawad1481 earned 0 total points
ID: 34147747
Hello all,
This was interesting case..
Author had migrated the environment from Physical box to VMware. IN doing so the DC which was also Exchange that had issues with Services not starting.
After further troubleshooting found that computer object is not present in ADUC --> domain controllers OU.
Whn i took over i found that Netlogon service will start and Nltest /dsgetsite returned error. And found taht Computer account is missing.
I searched DC object everywhere...ADUC, Sites and service in service mode... ADSIEDIT, no luck.

This being DC, will not let us disjoin and rejoin to domain. So we had to force fullu demote DC.
dcpromo /forceremoval.
we then disjoin and rejoin it to domain.
After that we found that Exchange service will start. But that DC was primary DNS server. So OWA and Outlook had some issues.

we tried promoting it to C, it was connecting or recognising the domain. we had another DC in Site. So we made it primary DNS server.

we had to clean the DNS entries for the DC+Exchange server. we then were able to promote it to DC again.

At the end everything was online.. OWA and outlook working fine.

Guys, this was bit difficult .... and tricky one.

Happy endings....
Regards,
Jawad.
we cleaned DNS.
0
 

Author Comment

by:nivasnet
ID: 34376426
ok i took precautionery steps, my request is don't delete points for jawad.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

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

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

837 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