Using SBS to to link together 7 remotes sites with 1 central administration office?
Posted on 2010-08-24
Here it is.
I have found myself in a local that is VERY outdated (all win 2000 machines, and linux servers from about 8 years ago)
I like SBS becuase of the price and it includes everything i need all in one cal as well (ISA, SQL exchange. etc)
Each remote office will have maximum 40 users, so I think SBS would be best for them becuase of cost and cals. So what would you guys think would be the best way to do this? I understand on ONE domain you can only have one SBS server. So would it be ok to do this:
Main Office: Windows Server 2007, Primary DC
SBS server for all other office apps
Loc1-7: SBS server with remote access for admin management. Each office will have its own email domain (as they do now) and I will just point the MX entry to the exchange server per location. my question is, is it possible to have all these servers on one primary business domain? Or is that impossible. My goal here is just keeping costs down. Each location MUST have ISA, SQL, Exchange? (perhaps) (i might change this depending on your recommended setup).
No 2 locations will share data, but the main office will need data from all locations. I could set up SBS individually per location and have VPN's for each location installed on the managements computers to access files and run programs etc. Perhaps static Ip's for each server for better remote management.
Each location will also contain a back-up DC for redundancy and hardware will be top of the line etc. (this is what Im good at) not enterprise development. Problem being, there is nobody at this far away remote location that can do the job, so they put it on me becuase of my experience with a smiler setup in egypt. As Im the IT man (on contract ) for 5 remote locations and find SBS the easiest for remote management and ticket support.
Or could I simply have windows server installed in all locations, with a primary DC located in the Data center that controls everything (except for the fact i will still need to configure exchange for all those remote locations and users, as well as a local SQL for business apps.
One problem is I have no experience putting remote locations on a primary business domain, all projects I have done before have been for either single offices that need serious upgrades and a 2 remote projects for contracted IT support (where they actualy DID NOT want to share anything between offices). I know I'm out of my league here but I'm a super fast learner, so any help is appreciated, the goal of this question is to see what other experts think is the best for this project...