Domain Master Browser - ISDOMAINMASTER - what to set this?

Hi,
I have about 5 dc's and 40 member servers, plus a couple hundred xp clients
I get alot of errors about machines promoting themselves to be the master
browser and also a machine thinks another is the master browser.

I believe they are 8003 srxmb errors.

I started looking around the net and found a ton of information but nothing
to really define what I should do. i looked on the dc - all of them are 2003
dc's by the way- and the dc that has the pdc emulator role has the
ISDOMAINMASTER reg key set to FALSE. I changed that to TRUE.
Now what about the rest of the dc's and member servers?
Is it advised to turn off the computer browser service on all member servers
and clients except for a few that we are fine with letting become backup
browsers?
if they are going to be backup browsers do we need to change the
ISDOMAINMASTER key to TRUE, AUTO< or FALSE?

All machines which you want to become browse masters or potential browse
masters need to have the ISDOMAINMASTER set to TRUE or AUTO. TRUE should
give the machine a better chance of being elected. All machines which you
don't want to become master browsers should be set to FALSE, or have the
computer browser service stopped. It is a good idea to exclude multihomed
servers and RRAS servers from becoming browser masters. (See KB191611 for
the problems with multihomed browse masters). Note that Microsoft recommends
one backup browser for every 32 machines.

The behavior of the browser service and browser elections is complex. If
for any reason a machine cannot get a browse list, it will force a browser
election (if it has the browser service running. It does this by announcing
itself as the master browser). There is a description (with references for
further reading) in KB188001 . There is a troubleshooting guide in KB188305
.. The basic troubleshooting tools are browstat (from the support tools in
W2k/W2k3) and browcon, which is described in KB818092 .

jason wrote:
> Hi,
> I have about 5 dc's and 40 member servers, plus a couple hundred xp
> clients I get alot of errors about machines promoting themselves to
> be the master browser and also a machine thinks another is the master
> browser.
>
> I believe they are 8003 srxmb errors.
>
> I started looking around the net and found a ton of information but
> nothing to really define what I should do. i looked on the dc - all
> of them are 2003 dc's by the way- and the dc that has the pdc
> emulator role has the ISDOMAINMASTER reg key set to FALSE. I changed
> that to TRUE.
> Now what about the rest of the dc's and member servers?
> Is it advised to turn off the computer browser service on all member
> servers and clients except for a few that we are fine with letting
> become backup browsers?
> if they are going to be backup browsers do we need to change the
> ISDOMAINMASTER key to TRUE, AUTO< or FALSE?