Exchange 2003 - FSMO Roles transferred - Now services will not start.

Currently seeing an issue with a client as per this article :

http://forums.msexchange.org/m_1800395242/printable.htm

The setup/history of this configuration is:

Exchange 2003 running on a DC
Additional DC introduced running 2008 R2.
FSMO roles transferred from Exchange 2003 server to 2008 R2 server.
A week or so later the issues mentioned in the linked article are experienced.

I cannot select a different DC for Exchange using ESM because an error message is seen when attempting to view the Directory Access tab.

Any help appreciated.
utilizeAsked:
Who is Participating?
 
utilizeConnect With a Mentor Author Commented:
We ended up having to restore Exchange and the additional DC to a backup from a few days prior.

We originally restored just the Exchange box. The store mounted initially, but after replication it fell over with the same problem.
0
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
When Exchange is installed on a domain controller it MUST be a global catalog and Exchange will not use any other domain controller other than itself.

If you want Exchange to use other domain controllers you must move Exchange to another machine. Running DCPROMO on a server with Exchange installed on it is not supported and usually breaks Exchange.

Simon.
0
 
Kash2nd Line EngineerCommented:
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Guy LidbetterCommented:
You can force System Manager to point to another Domain controller, not sure if this works on a version installed on a DC, but it may be worth a try. Ensure the other DC is a GC.

Open MMC.exe
Add Snap-in > "Exchange System"
You should then get a "Change Domain Controller" window.
Slap in the DC FQDN into the "Change To" field and click OK.

You should then be connected to the other DC

Regards

Guy
0
 
utilizeAuthor Commented:
I've tried the suggestions so far and seen the article mentioned.

To be clear, there is no intention to DCPROMO out the Exchange 2003 server. What has happened is that the FSMO roles have been transferred to a different server running 2008 R2. Exchange 2003 is STILL a DC & GC.

Perhaps transferring the roles back will cure the issue?
0
 
Simon Butler (Sembee)ConsultantCommented:
Exchange doesn't care about the FSMO roles - it only cares about the global catalog roles.
Have you restarted any of the Exchange services since moving the roles? If not, then I would start with that.

Simon.
0
 
utilizeAuthor Commented:
Restarted the services, server, etc.

Good news about the FSMO roles. Not sure why it has dropped off then.

Just ran PolicyTest.exe which was successful
0
 
utilizeAuthor Commented:
Given points to Simon for assisting.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.