What impact will demoting a domain controller that has Exchange 2003 have on Exchange?

Here is the situation.
We have a customer that has a 2003 server standard backup domain controller running Exchange 2003 that has problems with Exchange services starting.
When trying to browse DNS manager we can connect to the primary domain controller from the bdc but cannot connect to the install of DNS on the domain controller that has Exchange installed.   This was setup before I got involved and obviously according to Microsoft a domain controller should never have had Exchange installed on it.

We were thinking that theoretically since the other domain controller is working that we could demote this domain controller to a member server and Exchange should still work.
Anyone had experience with this or any suggestions on how we should proceed?
kallatechAsked:
Who is Participating?
 
Neil RussellConnect With a Mentor Technical Development LeadCommented:
From Microsoft.

You can run Exchange Server 2003 on either a member server or on a domain controller. After you install Exchange Server 2003 on a server, do not change the role of the server. For example, if you install Exchange Server 2003 on a member server, do not use the Dcpromo tool to promote the server to a domain controller. Or, if you install Exchange Server 2003 on a domain controller, do not use the Dcpromo tool to demote the server to a member server. Changing the role of a server after you install Exchange Server 2003 may result in loss of some Exchange functionality and is not supported."
0
 
Neil RussellTechnical Development LeadCommented:
You would have to migrate exchange off the server to a new server first and then DCPROMO the machine down to a member server.

0
 
kallatechAuthor Commented:
Thank you that is what I thought.

Any recommendations on what we can do?
I was thinking our only option would be to build a new server 2008 standard with Exchange 2007 or 2010 and then see if I can restore data from the Exchange 2003 server is this even possible?
0
Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

 
AmitIT ArchitectCommented:
You don't need to restore database, simply move the mailboxes to new server.
0
 
kallatechAuthor Commented:
Is it possible to do the migration when Exchange services won't start?
0
 
AmitIT ArchitectCommented:
Not possible. You need to bring current Exchange server up and running. You can reinstall exchange with disaster recovery switch for Exchange. But these are advance level steps, and required advance level of skills for Exchange admins.
0
 
kallatechAuthor Commented:
I am definitely not an advanced exchange admin.

Since they are using pop 3 email to the server would it be okay to save their email to pst files and then import them into Exchange 2007 or 2010?
0
 
Neil RussellTechnical Development LeadCommented:
Would it not be simpler to troubleshoot the problems with DNS?
0
 
kallatechAuthor Commented:
Considering it is active directory and DNS that have caused the Exchange services not to start, and we can't remove DNS and set it up again.
I would think that would be our only option to export to pst and import the pst files into Exchange 2007 and 2010.
Am I missing some other options that you could recommend?
0
 
kallatechAuthor Commented:
Thanks for the quick response
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.