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 wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Adding SBS2003 to a Windows 2000 Server network

Status
Not open for further replies.

brettban

Technical User
Aug 7, 2002
14
I'm currenty running a small network (15 users)on a Windows 2000 server running AD, it is also the DHCP server with the IP scope of 192.168.1.1 through 192.168.1.30. I just purchased a new Dell with SBS2003 pre-loaded. The following is what I want to do - what is the best way?

I want to add the SBS2003 server to the existing physical network but with a different domain name, then have existing users log on to the new server and domain. It will be running our MSOffice, Exchange e-mail, and remote access. I want to keep the old 2000 server, which runs our acct'g and payroll software, to become a member of the new SBS2003 domain to allow access from our existing users.

I've gone through the initial set-up and wizards on SBS2003, however, when it tried to set-up the DHCP service, it recognize the 2000 server DHCP and would not continue that portion of set-up and gave itself an IP of 192.168.1.43. Should I still keep the DHCP server on the Windows 2000 machine? Can SBS2003 use DHCP on an older server? Where should the client computers get their IP addressing? Any help would be great!
 
I hope you did lots of research before you purchased SBS, chances are the money you saved buy it you will end up spending in support The marketing brochure and reality often don't meet, and you really need to read the fine print.

It shouldn't matter which server is running DHCP however you need to remember that you can push out more than just IP addresses to the DHCP clients so you need to understand what each of the DHCP Scope Options do and the impact they can have on the functionality of your network. Review your existing DHCP Server and the options that are set in the active scope and don't make any changes unless you understand what each of them are for.

 
A few things are note worthy here. First, I think you will find that SBS2003 is a lot more stable than t=previous versions. If you want to get the DHCP running on the SBS machine, you can either disable DHCP on the 2K box, or just unplug the NIC from the 2K box.

Now that your SBS machine has an IP address, I would highly advise against changing it. If you decide you do want to change it, you will need to be careful. There are at least a dozen places the IP gets recorded between AD, DNS and DHCP.

You should run DCPROMO on the 2K box to make it a member of a workgroup and remove AD. If you are running DDNS on the 2K box, you will need to remove it first before you can remove AD. Once this is a member server, finish setting up your SBS, then you can have your 2K box join the domain as a member server.

To have your workstations join the new domain you will need to run from each of the workstations. Take note that the ability to preserve profiles only works for local profiles.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
Mark - you are right about changing the IP address on a SBS2003 machine - it caused all kinds of problems. Since I have not load anything on the new server, I decided to start from scratch and reload the operating system. If I'm understanding everything right - when the SBS03 server comes to install point of setting up the DHCP, I should disconnect the old server to allow DHCP to be set-up on the new server. Should I use a new range of IP addresses? Once the new server is set-up with all new user accounts, I can then add each workstation, then I demote the old server and it to the new server and domain - correct?
 
Bretban, you've got it. Good luck with everything.

If you want to set up your SBS without messing with your current stuff you can do so but the SBS server will need to be plugged into a hub or switch (even if nothing else is plugged into it). This is a requirement of the SBS wizards.

I like SBS 2003 but hate any and all wizards. I have learned however that when dealing with SBS I need to put my dislikes aside and let the system do its thing its way. If you follow that cardinal rule your setup will be quite solid.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
If SBS detects the other DHCP server later, that will cause problems...

JTB
Have Certs, Will Travel
"A knight without armour in a [cyber] land."

 
jtb, the suggestion here is to get the SBS running seperately, then do away with the DHCP on the existing server when he is ready to roll the old server into the new domain.

I hope you find this post helpful. Please let me know if it was.

Regards,

Mark
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top