Hi, if you have sbs2011 and it runs as a domain controller, then I gather that I should have a secondary domain controller within the domain, right?
My question is, since I know very little about network setup, is this just like setting up a domain service that works like active directory, and provides the domain authentication to users if the primary domain controller (ie the server) goes down?
And if that's right, why couldn't I just run it on a windows 7 domain client? I mean it's a service, like IIS, and why shouldn't it run on a lowly pc. It would just have to tide the naming over for a little while, not run the network or anything. Ok, that's a beginner's view, so expert, what's the real case?
Then, I'd like to simplify the question into real hardware. What's the minimum I need from a financial perspective on the basic level of box and license. But, really, it's more about identifying intermediate range options, as well as the minimum, for introducing a secondary domain name controller. For example, currently with sbs2011 standard, if I had an upgrade (or is it new purchase?) to a premium version, that'd be an option. While for the minimum option, maybe just an old SBS 2003 license, running on some old neglected box would do fine. This is a question ideally suited to someone who has setup and designed their own networks. In my context I'm the administrator of my own small business, so I'm free to look at whatever routes appeal, and I'd like to learn about the general purpose and function for the secondary. And, if you like, how the sql server would normally (optimally) sit in the network (probably on the secondary?).
I'm hoping for a general guidance answer here. Ideally: Brief purpose of secondary, and simple discussion of hardware & license combinations that meet my goal of understanding minimum and intermediate range options for the secondary name controller.