3 DCs in a domain?


i thinking how best patch servers (and specifically, dcs) , mentioned how have 3 dcs in domain - 1 of "dev dc" (ie testbed patches before rolling out other 2 dcs). fyi, abide best practises such not running auto updates etc on servers.

is 3 dcs in domain idea? guess holds no fsmo roles? also, need dns on it? 3 crowd say. also, happen if 2 dcs (which specified in dns settings of member servers) go down? dc able keep things up?

thanks

is 3 dcs in domain idea?
minimum recommendation 2, 3 better.  might not need 3 won't hurt you.

also, need dns on it?
if running ad integratated dns recommend runs well.  recommend running global catalog.  having dc's gc's idea.

also, happen if 2 dcs (which specified in dns settings of member servers) go down? dc able keep things up?
dc able handle load, couldn't tell sure since didn't list load model.  rule of thumb quality dc 4 gb ram, etc... can handle 5000 users domain.  guess small shop , load place on dc won't cause struggle.  problem is, if don't have dc part of clients dns nic settings clients won't able find , no 1 able authenticate.

ps: suggest have test domain, don't patch dc part of production domain.  test dc, still providing authentication clients isn't providing dns services.  think it, if dc being used test production domain test domain.

--
paul bergson
mvp - directory services
mcitp: enterprise administrator
mcts, mct, mcse, mcsa, security+, bs csci
2008, vista, 2003, 2000 (early achiever), nt4
http://www.pbbergs.com    twitter @pbbergs
http://blogs.dirteam.com/blogs/paulbergson

please no e-mails, questions should posted in newsgroup. posting provided "as is" no warranties, , confers no rights.



Windows Server  >  Directory Services



Comments

Popular posts from this blog

some help on Event 540

WMI Repository 4GB limit - Win 2003 Ent Question

Event ID 1302 (error 1307) DFS replication service encountered an error while writing to the debug log file