FSMO roles in Exchagne and DCs


We have four physical servers which three of them are running as DCs and the other one is just member server acting as application server.

I have just checked what operation masters roles are assigned to each DC and I have just found out that one DC which runs Exchange Server 2007 has all operation master roles assigned: Schema master, Domain naming master,PDC,RID pool manager and Infrastructure master.

I am just concerned about the roles are not being separated from each other. Is it something that needs a role separation? and what would be ideal scenario?
Who is Participating?
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
It is not an issue if one server holds all FSMO roles, however, if you choose you could move some to different DCs.  Your biggest concern should be Glbal Catalog server and you should have at least 2 GCs in your domain.
Imtiaz HashamTechnical Director / IT ConsultantCommented:
Ideal scenario - first recommendation, don't have Exchange on an AD Server.

My recommendation, I keep all FSMO roles on a single server, but that's because we manage so many clients, it's easier if the server were to crash to logon to a secondary server and force transfer the roles to the other server.
Lee W, MVPTechnology and Business Process AdvisorCommented:
If the Exchange server is an SBS (Small Business Server) then you CANNOT move the FSMO roles or Exchange.  If you are NOT using SBS, then the FSMO roles can be moved but unless you have MULTIPLE DOMAINS (not multiple domain controllers; multiple DOMAINS), then there's little point in separating the FSMO roles.
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

Lee W, MVPTechnology and Business Process AdvisorCommented:
Also, DO NOT demote (or promote) an the Exchange server - it's a DC, it MUST remain a DC - if it's NOT a DC, then you CANNOT make it a DC (if you do, you break exchange; once Exchange is installed you cannot add or remove DC functionality without FIRST UNINSTALLING EXCHANGE!)
If all domain controllers are also global catalog servers, leave all of the FSMO roles on the first DC in the forest.
If all domain controllers are not also global catalog servers, move all of the FSMO roles to a DC that is not a global catalog server.
Imtiaz HashamTechnical Director / IT ConsultantCommented:
I should've mentioned, don't remove the exchange server AD services - leave it the way it is.

There are 5 FSMO Roles - 3 non-replicable on a multiples DCs 2 are, make sure the 2 are on all servers.
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.