Need for Domain Controller / DNS Server Branch Office
I need help in putting together a justification for having a Domain Controller and a DNS server in our office. We are a state agency and with about 300 users. Our main office will be moving and merging with another office, we will have 100 users in this site and we will have 10 servers 3 of which are we servers (we currently have 60 users). The 5 regional offices connect back to use to access proprietary SQL applications. Currently we are part of a Win 2003 AD domain, we are in a building with other state agencies and we do not have a Domain Controller or DNS server, it is housed in another agency. We will be moving to a stand alone building connected back to the main site with a T1 line. I feel we should have our own Domain Controller and DNS server. Am I right? I’m thinking it would cut down on traffic if logon authentication and DNS name resolution happened in house rather than going over the T1 back to the main office. Also if the T1 goes down then we would not be able to login at all and could not print or access networked apps or files.