bartokk

Test environment was created on seperate network and now that you mention it I think I used 2003 enterprise. Sorry for the misinformation. Now, why would I use SBS if I had enterprise? Because SBS has Exchange. At this point I need the best option for making a copy of the "old" server on the "new" server and take the "old" one off of the network. There are only about 45 users so the 75 limit is of no immediate concern.

Here's the situation I'm in. We currently have our 2003 DC running on a workstation. This server has Exchange/AD/DHCP/DNS and is the sole DC. We recently purchased "real" servers (Dell 2850) and I would like to get rid of the existing workstation. My question is what would be the best way of doing this. To try to keep things as simple as possible I'll refer to the existing workstation/server as "old" and the Dell server as "new". A) Install 2003 SBS on the "new" server. Configure AD to replicate the "old" server. Once replication is complete, uninstall AD on the "old" server. B) Install 2003 SBS on the "new" server. Cluster the servers and then take the "old" server down. C) Quit D) ....... Now, here are my thoughts on those options. A) This just sounds too easy. I setup a test environment were I added a second SBS server as a child and had it successfully replicate AD. However, I only tested removing AD from the 2nd server, not the parent. B) I'm only familiar with clustering in theory and what I've read up on it. I haven’t tested this yet due to the fact that there are only 7 days in a work week....if I only had an extra day! C) Not a viable option D) ..........