Migrate 2003 SBS from workstation to server

[bartokk]

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) ..........

Edited December 29, 2005 by bartokk

[cluberti]

You can't install SBS 2003 into an existing network containing another SBS server - it has to be the only SBS server on the WHOLE network, or it refuses to install as a DC. You might consider not using SBS 2003 in this situation, if you've got an AD to migrate, or you will have to install SBS 2003 as a new domain, create a trust, and move user accounts and mailboxes over...

I'm not entirely sure you had two SBS servers on the same network, because it's not possible. Here are the limitations of SBS (these aren't able to be changed, either):

Only 1 SBS Server on a network.

Only 1 Domain.

Only 1 Forest.

The SBS server must hold all the FISMO Roles.

The SBS Server must hold all the Server Applications included in the Suite.

SBS does not support clustering of any kind.

Maximum of 75 users and/or devices total.

Those are built into the software - you sure both SBS servers were the same version, and on the same network?

Edited December 29, 2005 by cluberti

[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.

[InTheWayBoy]

Why not just do a fresh load...since you would always have to install it new in any scenario, why not just export the info from AD and Exchange, install SBS on the new server, setup, then import the AD and Exchange info.

You can export AD:

http://www.microsoft.com/technet/prodtechn...o/bulkstep.mspx

http://www.computerperformance.co.uk/Logon...SVDE_Export.htm

http://www.myitforum.com/articles/12/view.asp?id=8499

You can export GPO by using the newish GPMC.

As for Exchange, I still have yet to spend more than an hour or two with it, so I can't speak of any tactics. But I'm sure it's possible, a quick google should set you straight. Or some other smarty will post an idea for the Exchange issue.

Also, I've never used SBS so some of those links may not apply to it since it seems like it's just different enough to matter. Also, I would take this as an opportunity to document the new install, so when something like this happens in the future you can ensure better reliability. Because what would happen if you didn't have a chance to have a functioning server, only a backup...good luck!