We have already moved the catalog server function to a different domain controller. Referencing a document in Microsoft Knowledge Base, we think we just have to move Flexible Single Master of Operations (FSMO) roles and run DCPROMO.
We want to make sure we are not missing an important step though. Is it really that simple; no users will lose access to e-mail?
Requires Free Membership to View
Yes, you need to move the FSMO roles to another domain controller and then DCPROMO the machine to demote it from being a domain controller to simply a member server. You should have no problems.
MEMBER FEEDBACK TO THIS ASK THE EXPERT Q&A:
Per a Microsoft KB article, demoting a domain controller/global catalog after Exchange Server is installed will cause issues and is not supported. Here is the relevant excerpt from the article:
"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."
—Peter D.
******************************************
Moving the FSMO roles will not help. If Exchange Server is running the domain controller (DC), then it is not supported to demote it unless you move all the mailboxes on that server to a different Exchange server. The drawback is that it will corrupt the metabase if you demote the DC.
So, the best practice is to:
- Move all the mailboxes and public folders to other Exchange servers.
- Proceed with the demotion.
—Athif K.
******************************************
Do you have comments on this Ask the Expert Q&A? Let us know.
Related information from SearchExchange.com:
This was first published in March 2006
Join the conversationComment
Share
Comments
Results
Contribute to the conversation