I'm an application developer consultant and have worked at a few dozen different organizations over the past few years. Everyone I've worked with has multiple domain controllers on the network. My understanding has been that this enables users to log on if ANY ONE of the domain controllers is available. So this increases the network's availability and can share the work -- all good things.
Now I'm working with an organization with only one domain controller (Windows 2003). They have four Windows servers (two are 2000, two are 2003) in two locations. The locations are connected together via T1. There are been occasions when the T1 goes down and people in one of the locations can't log on since the DC is on the other side of the T1.
So I've suggested making one or two of the non DC servers into a second DC. The networking people say this would take 6-8 hours of labor and it's not worth it. But what I read about the process is that it's pretty automated and that although it requires a couple of reboots on the new DC server, it's not that labor intensive.
What you you guys say -- are we getting snowed by the network technical people? Or is running dcpromo to add a DC to the network something that is easy and doesn't take much labor?