Administrator does not have a Master Accont SID???

[reynolwi]

Im seeing this error message in the event viewer on the exchange server now...

Event Type: Warning
Event Source: MSExchangeIS
Event Category: General
Event ID: 9548
Date: 6/16/2008
Time: 8:20:43 PM
User: N/A
Computer: SERVER
Description:
Disabled user /o=DOMAIN/ou=First Administrative Group/cn=Recipients/cn=Administrator does not have a master account SID. Please use Active Directory MMC to set an active account as this user's master account.


What does this mean and how do i fix it???


Im also seeing where the exchange server is trying to reconnect to the OLD domain controller that held all the FSMO roles. That server was relaced by the new one. I checked the settings in exchange and it has the new server listed in the directory access page and i see some event logs that show its binding to the new server. How do i go about removing the references from the old server?

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[58sniper]

What have you searched for? A simple Google search yields plenty of results for the first issue.

Pat Richard
Microsoft Exchange MVP
Contributing author Microsoft Exchange Server 2007: The Complete Reference

 

[reynolwi]

I found some KBs from microsoft after i posted this for the first error...

http://support.microsoft.com/kb/555410

http://support.microsoft.com/kb/278966

http://support.microsoft.com/kb/316047

For the second i found this but is this what im looking for because I already had to do this when i was having AD issues with a server trying to replicate to an old server name.

http://www.petri.co.il/delete_failed_dcs_from_ad.htm

The exchange server was online when i was doing it all so i dont know why it has now decided that it wants to try and bind to it again. Is this something that happens sometimes when you reinstall exchange using the disasterrecovery switch?

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -

Network Error:
Hit any user to continue

 

[xmsre]

For the 9548s, you should be able to locate the NOMAS tool and fix them all at once. Dave Goldman is the MS keeper of the tool and could point you to where you can download it these days.

For your second issue, let's assume you've done the metadata cleanup with ntdsutil. You'll need to sieze the FSMO roles from the replacement DC, then make the replace ment a gloval catalog as well. Then go into sites & services and rempove the object for the old failed DC, and into DNS and remove any erronious entries as well.

 

[reynolwi]

The thing is for the second issue... I did all that a couple months ago. The new server has been running for months now and ive never seen that error before until after i did the disasterrecovery on the exchange server.

Wm. Reynolds
Premise Communications
Texas Public Safety Solutions

http://www.rrwds.com

http://www.txpubsafety.com

- - - - - - - - - - - - -

Network Error:
Hit any user to continue