Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SBS 2003 and existing domain / servers

Status
Not open for further replies.

stussy

MIS
May 22, 2003
269
0
0
GB
Hi

We are a small site (approx 40 users) running a few dell poweredge servers, mainly Windows Server 2000 and 2003. (Our PDC is still NT4 though). These servers host Epos DB (MS Dynamics, formerly Navision), credit card software and security cameras. We're looking at taking on an even smaller office quite a distance away. There will be no more than 6 or 7 users at this smaller office, so Windows Small Business Server 2003 is offering itself as the best fit solution.

Are there any reasons NOT to go with SBS 2003? I don't want to spec this, only to find out later that there's something it can't do in conjunction with our existing network. I know it has to be the PDC, but having the new site run as a separate domain is not a problem. I will need to be able to remote desktop in to the server / workstations / tills for support. We may well also need to be able to share data across the two sites. Presumably this is going to require some kind of VPN?

Has anyone else ever set something similar up at all? Any advice gratefully received!

Cheers

Mike
 
Keep in mind that SBS must be the holder of all of the FSMO roles, and must be the forest root. No trusts.

That might not be what you're looking for. A Windows 2003 Standard R2 box might make more sense. Make it part of your domain so that it's easier to support. They could all hit the same Exchange server that you do, assuming there is good connectivity.

I'd upgrade your DC to 2003 R2, then put another R2 DC in the remote office.

Pat Richard, MCSE MCSA:Messaging CNA
Want to know how email works? Read for yourself -
 
58sniper has the best solution, but is cost is an issue then a basic VPN might do the trick.
 
Thanks 58sniper and dberg - cost is not so much of an issue, and keeping it part of the same domain for support reasons makes perfect sense.

Silly question, but I presume I'll still need to vpn into it, as I'll be going local network > router > internet > router > remote server ? Just the comment from dberg about a basic vpn has confused me a little!

Thanks

Mike
 
A site to site VPN was what I was refering to.
 
I'd almost forego the server, link up a secure vpn and get the users on terminal server straight into your network... 6 or 7 users isn't worth a server in their office is it?

~ K.I.S.S - Don't make it any more complex than it has to be ~
 
Thanks again for the replies. They need a server for the till units, otherwise yes, there would be little point.

Final question - I guess it makes much more sense to configure the server on-site rather than trying to join the domain thru a vpn connection (if that is even possible)?

Cheers

Mike
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top