Windows Server design

Hello folks -

I've been tasked with designing a Windows network which involves 2 locations (1 main site, 1 branch office). The main site has a SBS 2003 Server also running Exchange. The branch site currently has no users, since this site was recently built. However, users will start working at the branch site at the end of the month. Main site has about 75 users, and branch site will have 25 users. The 2 locations will have a point-2-point connection with Gigabit throughput. The branch site will connect to the main site for the Internet connection.

Here's how I am thinking of designing the network:

1. Migrate from SBS 2003 to Windows 2003 Std.
2. Migrate Exchange from SBS to a new Server
3. Deploy a new server at the branch site (for AD, DNS, DHCP etc.)

However, management may have budget limitations and it's possible they may not be able to deploy a new server at the branch site. That being said, do you think it would be prudent to have all the 25 users use the server at the main site for everything?

The main site has a DHCP scope setup like 10.0.0.x. If there is no new server deployed at the branch, then how should I configure the DHCP Server at the main site to assign IP addresses to workstations at the branch site?

Also, can you recommend how should I migrate my SBS 2003 box to Windows 2003 Std?

I know this is a long post but I've tried to be as detailed as possible.

All your help is greatly appreciated.

 

If you have a gigabit point to point and are confident of that link's up time, you can get away without the server at the remote site.

Are the people supplying the link, also supplying the routers? If so, I'd suggest you talk to them about setting up DHCP on the remote router. The remote site PC will need to have the ip address of your server set as their primary DNS.

What mask are you using? if you are using 10.0.0.0/255.0.0.0, then you'll either need to reconfigure your network, or use a totally different address space for your branch office (192.168.0.0/255.255.255.0 for example).

 

Reggie -

Thanks for your response.

We're using a SM of /24 with 10.0.0.x being the addressing scheme at the main site.

If we don't deploy a new server at the branch site, can I use 10.0.1.x for the branch site, and create this scope on the DHCP server at the main site? I also remember reading somewhere that you have to create a super scope for this kind of setup? Is that true?

The routers being used for the point-2-point link are not being provided by the ISP, so we will have to configure the routers ourselves. We will just run the DHCP relay agent on the router at the branch site in order to grab the IP addresses.

 

Yes. That should be fine.

This is something I am sure you can do, but is not something I have ever set up. The key thing is to ensure that DHCP gives out 10.0.0.0 addresses locally, and 10.0.1.0 address for addresses coming via the branch router.

I presume you want to do this so that you can use DHCP to keep DNS up-to-date. That is something worth trying for. If not, then I'd be tempted to set up DHCP on the branch router as that would be simpler.

This is a little more complicated than basic routing. If in your situation I'd pay the little extra to get Cisco routers. If you've come to the same conclusion then you may well find this link of use:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fipr_c/ipcprt1/1cfdhcp.htm

 

just my 2 cent.

SBS server has a limitation of 75 users/devices

So, if the company is growing beyond that,
an upgrade is a MUST!

 

the KB below shows you how to do it properly.
support.microsoft.com/kb/884453

although this method is not recommended ...


There is another kb says that there is a transition pack
http://support.microsoft.com/kb/555073

note: Microsoft advised you should have your exchange server seperate with your domain controller.