I agree - I am finding that from some SUSE machine still forcing an election even after the change. David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764
From: Jeff Bunting [mailto:[email protected]] Sent: Friday, June 12, 2009 1:29 PM To: NT System Admin Issues Subject: Re: DC and "IsDomainMaster" key That article is a little ambiguous in its wording. I think you're still at the mercy of the browser election process no matter how this key is set. Jeff On Fri, Jun 12, 2009 at 3:49 PM, David Lum <[email protected]<mailto:[email protected]>> wrote: Thanks and yeah, I found that article and a couple of others but didn't see anything saying "only one DC should have this", although that's what I assumed and implemented. Dave From: Jeff Bunting [mailto:[email protected]<mailto:[email protected]>] Sent: Friday, June 12, 2009 12:24 PM To: NT System Admin Issues Subject: Re: DC and "IsDomainMaster" key Hit send too soon.... according to the KB article that would only be set on the one server you want to be the master browser. On Fri, Jun 12, 2009 at 2:51 PM, Jeff Bunting <[email protected]<mailto:[email protected]>> wrote: That is for setting preferred master browsers. http://technet.microsoft.com/en-us/library/cc959923.aspx Jeff On Fri, Jun 12, 2009 at 1:23 PM, David Lum <[email protected]<mailto:[email protected]>> wrote: Should this key value be set to TRUE for ALL domain controllers, or just one? David Lum // SYSTEMS ENGINEER NORTHWEST EVALUATION ASSOCIATION (Desk) 971.222.1025 // (Cell) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
