Hi,
What exactly do you mean by the new DC doing all the work? User
authentication?
The FSMO roles really are not at "work" all the time.
If you do not want Exchange to pull from this DC, do not make it a GC
Of all the operations master roles, the PDC emulator role has the
highest impact on the performance of the domain controller hosting that
role
PDC Emulator:
PDC Emulator is the root time server for synchronizing the clocks of
all Windows computers in your forest.
Another function of the PDC Emulator is that it is the domain
controller to which all changes to Group Policy are initially made
Finally, all password changes and account lockout issues are handled by
the PDC Emulator to ensure that password changes are replicated
properly and account lockout policy is effective.
RID Master:
The purpose of this role is to replenish the pool of unused relative
IDs (RIDs) for the domain and prevent this pool from becoming
exhausted. RIDs are used up whenever you create a new security
principle (user or computer account) because the SID for the new
security principle is constructed by combining the domain SID with a
unique RID taken from the pool.
So the only time the RID Master is "working" is when a DC runs out of
RIDS
Infrastructure Master:
Its purpose is to ensure that cross-domain object references are
correctly handled. For example, if you add a user from one domain to a
security group from a different domain, the Infrastructure Master makes
sure this is done properly. As you can guess however, if your Active
Directory deployment has only a single domain, then the Infrastructure
Master role does no work at all, and even in a multi-domain environment
it is rarely used except when complex user administration tasks are
performed, so the machine holding this role doesn't need to have much
horsepower at all.
Schema Master:
The purpose of this role is to replicate schema changes to all other
domain controllers in the forest. Since the schema of Active Directory
is rarely changed however, the Schema Master role will rarely do any
work. Typical scenarios where this role is used would be when you
deploy Exchange Server onto your network, or when you upgrade domain
controllers from Windows 2000 to Windows Server 2003, as these
situations both involve making changes to the Active Directory schema.
Domain Naming Master:
The Domain Naming Master role processes all changes to the namespace,
for example adding the child domain vancouver.mycompany.com to the
forest root domain mycompany.com requires that this role be available,
so you can't add a new child domain or new domain tree, check to make
sure this role is running properly.
What you can do is to adjust the priority or weight in the DNS
environment.
If you want to proportionately reduce the number of client
authentication requests received by a DC, adjust its weight. If you
want to ensure that the DC does not receive any client authentication
requests, adjust its priority.
306602 How to Optimize the Location of a Domain Controller or Global
Catalog
http://support.microsoft.com/?id=306602
Configure Operations Master Roles
http://technet2.microsoft.com/Windo...d551-44da-8412-9fd4e6d5c9111033.mspx?mfr=true
Good luck
Harj Singh
Power Your Active Directory Investment
www.specopssoft.com
