is it possible to have a configuration in a Windows 2003 SBS environment where in the event that the SBS box crashed/turned off/ or is being worked on that there can still exist a path to the internet for domain users and visitors to still use?
I would like to have the standalone router issue DHCP IPs. The primary DNS would point to the SBS, the secondary wouuld point to the ISP DNS Server.
My theory was that if someone was using the internet and the SBS box went down they wouldn't be able to access the network shares but still be able to use the internet. (We are moving everything into the clouds with Google Apps Non-Profit)
Does this seem like a reasonable configuration? Or are they're pitfalls that I will fall into?
Well I would eventually like to get away from the server environment. No one knows how to manage the thing except me since we are all volunteers that come in with our own specialty. We can't afford to pay for a tech either (Its a volunteer ambulance corps). Do they make a domain controller appliance? I dread the idea of the SBS server going down and having to fix it. The internet is most important for everyone since I moved the email server and calendar into the clouds (Google Apps). The SBS server is more of a luxury. Its used for My Documents folder redirection, and some policies as well. Thats about it.
Any way to put the server into the clouds so I don't have to manage it either? lol
I was doing some testing with the configuration and found that it didn't really work well. I had an active gateway connection but no where to resolve domain names when the server was off, and when I released/renewed the network card configuration I had no access to My Documents, but I did have internet access.
I suppose there is no way that my ISP will put a pointer in their DNS that can point back to my server? Probably doesn't even exist, just an idea lol.
Can I have a second domain controller on a small business server environment?
Thanks for your input!