if all your domain controllers are GC, that does not apply , read below
Two exceptions to the "do not place the infrastructure master on a global
catalog server" rule are:
Single domain forest:
In a forest that contains a single Active Directory domain, there are no
phantoms, and so the infrastructure master has no work to do. The
infrastructure master may be placed on any domain controller in the domain,
regardless of whether that domain controller hosts the global catalog or
not.
Multidomain forest where every domain controller in a domain holds the
global catalog:
If every domain controller in a domain that is part of a multidomain forest
also hosts the global catalog, there are no phantoms or work for the
infrastructure master to do. The infrastructure master may be put on any
domain controller in that domain
"General recommendations for FSMO placement"
http://support.microsoft.com/kb/223346
--
Oz Casey Dedeal
Systems Engineer
MVP — (Exchange)
MCITP (EMA) ,MCITP(EA),MCITP(SA),
MCSE 2003| M+| S+ | MCDST
Security+|Project+| Server+|
http://smtp25.blogspot.com (Blog)
http://telnet25.wordpress.com/ (Blog)
"majortom1981" <> wrote in message
news:43D558B2-32DB-4302-A052-...
> We are replacing our 2003 x86 server with a new windows 2008 x64 server.
> It
> will be the domain controller. It will need the operation master roles
> moved
> to it. Its the global catalog server and a domain controller.
>
> The problem is that the microsoft documentation states that the operation
> master roles should not be a global catalog server.
>
> Any specific reason why they should be on a global catalog server? Can
> we
> still put them on if the target domain controller is one?