Join, 2003 Domain with a 2008 R2 server error

I have added a 2008R2 server into a 2003 domain i have moved all the roles off the 2003 DC (as we are taking it out of service) and on to the new 2008R2 when making the Infrastructure operations master role i get this message, all other roles have moved over. what do i need to do about the Infrastructure role?

Error:
2008R2.domain.local is a global catalog (GC) server. The infrastructure operations master role should not be transferred t a GC server. Are you certain you want to transfer the infrastructure operations master role to this GC server?
mspencer100Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

smangognaCommented:
Microsoft doesn't recommend to have the two roles together, but if you have only a DC, you have to do it.
0
AustinComputerLabsCommented:
From: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_21717541.html

In your setup (you seem to have a single domain), you can ignore this message:
"Two exceptions to the "do not place the infrastructure master on a global catalog server" rule are:
* Single domain forest:
[...]
* Multidomain forest where every domain controller in a domain holds the global catalog"

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AustinComputerLabsCommented:
From MS: http://technet.microsoft.com/en-us/library/cc268210.aspx

If some of the forest root domain controllers are not configured as global catalog servers, then move the infrastructure master role to a domain controller that is not a global catalog server and ensure that the server is never configured as such. The infrastructure master role should not reside on a global catalog server unless all domain controllers in the domain are global catalog servers.
0
Kini pradeepDevelopment ManagerCommented:
as recomended by austincomp, if its a single domain then ignore the message. it is applicable to forest with multiple domains or child domains in the enterprise
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.