|Courtesy: Home Box Office - Game of Thrones|
The modern day "domain controller" is not a leadership figurehead of some war-monger nation, but a software application that helps our main server networks function smoothly and efficiently. The exact definition from Technopedia.com is as follows:
"A domain controller (DC) is a server that responds to security authentication requests within a Windows Server domain. It is a server on a Microsoft Windows or Windows NT network that is responsible for allowing host access to Windows domain resources. A domain controller is the centerpiece of the Windows Active Directory service. It authenticates users, stores user account information and enforces security policy for a Windows domain."
That definition is a bit complicated, but the bottom line is that a domain controller is kind of like a traffic cop in a Windows-based network. If your network traffic cop (the domain controller) is compromised or fails then nothing can move, there is no access, and everything grinds to a halt. So think about it, wouldn't it make sense to find a way to have a failover DC?
It doesn't have to be up and running all the time, it just has to be ready if and when you need it. So in a hosted backup configuration, this "cold" DC could be fired up in case of an emergency and the network can be restored in minutes rather than hours or days. For the SMB organization that relies so heavily on these systems being available, this could be the difference between prosperity and mere survival. Talk to your trusted technology partner to see how it could work for you. And bring your shield, just in case!