fmdb
asked on
Small Branch Office - Windows 2003 Server Alternative?
I am working with a medium size business that has 3 branch offices. Only the main office has a Windows 2003 Server AD infrastructure. The three branches are connected via point-to-point T1 circuits but they have no local server. The circuits route Internet traffic to a single gateway at the main office and also to replicate a proprietary database application. There are less than 10 workstations at each branch.
The branch offices have no backups, no domain security and no centralized storage. DHCP is provided by a NETGear router and DNS is pointed to the ISP's public DNS servers.
Once I clean up the infrastructure mess, I'd like to put a Windows 2003 Server at each branch location. As a cost effective alternative, are their any appliances that will perform that function? I wasn't sure if I could find a NAS device that could plug into the existing AD platform, provide data storage with security and also handle DHCP. I could always use a DHCP relay so that isn't the most important issue.
Any suggestions on products that work well?
The branch offices have no backups, no domain security and no centralized storage. DHCP is provided by a NETGear router and DNS is pointed to the ISP's public DNS servers.
Once I clean up the infrastructure mess, I'd like to put a Windows 2003 Server at each branch location. As a cost effective alternative, are their any appliances that will perform that function? I wasn't sure if I could find a NAS device that could plug into the existing AD platform, provide data storage with security and also handle DHCP. I could always use a DHCP relay so that isn't the most important issue.
Any suggestions on products that work well?
ASKER
That's an option, for sure.
It appears that the T1 circuits are overkill.
I may explore obtaining a local DSL circuit at each location and then using internet security appliances to create site-to-site VPN's. Would you still recommend centralizing the home directories if I'm pushing the tracffic over the VPN tunnels? I'd be relieving the VPN tunnels of all internet traffic.
What do you think would be an accectable upload speed on sDSL circuits (ignoring the database replication requirements)? 384k? 768k?
It appears that the T1 circuits are overkill.
I may explore obtaining a local DSL circuit at each location and then using internet security appliances to create site-to-site VPN's. Would you still recommend centralizing the home directories if I'm pushing the tracffic over the VPN tunnels? I'd be relieving the VPN tunnels of all internet traffic.
What do you think would be an accectable upload speed on sDSL circuits (ignoring the database replication requirements)? 384k? 768k?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
For file share, look at an addon to Windows 2003 called Windows SharePoint Services.. it is a beautiful thing!
From the info you provided, I see no justification for adding remote servers, unless you like to travel :)