Migration from SBS 2003 Std to SBS 2003 Prem R2 Plus new hardware)

Migration from SBS 2003 Std to SBS 2003 Prem R2 Plus new hardware)

Post by ZG91Z » Thu, 12 Jul 2007 23:34:04

I gather this isn't as automated as I had hoped judging from the list of
similar issues and depth/detail of the replies I've seen.

I have older hardware running SBS 2003 Std. It is running Exchange 2000,
DNS, no DHCP, 1 NIC, IIS. It is my home setup (training, lab, websites).

I have new server sitting and waiting. It has 1 NIC, but I wouldn't mind
adding 2nd NIC if recommended. Currently routers allowing all servers/WSs to
access internet.

I have not seen much on migrating from SBS 2003 to SBS 2003 R2 (mostly just
2000 and pre-2000).

I would like to transfer Exchange mailboxes and mail. logins/settings, DNS
settings, AD. Ideally, I'd like to end up with same IP on new server, but
I'm not married to the idea.

Also, I "think" I made a mistake setting up my original SBS server. My
public domain is "myDomain.com". I created my server as "local.myDomain.com"
and that seems to haunt me to this day as I run DNS tests from external sites
testing how well my site comforms to standards. I'm guessing I probably pay a
penalty if I don't keep the exact same nasme on new server?

This is just me mostly on this SBS server and WSs - but I have other member
servers, work stations, actually 3 routers (1 wires, 1 wireless, 1 wireless
dedicated to xBoxs - long story), so I'd have to tweak a limited number of
devices to change to a new internal DNS IP if I picked a new one. But I
would like to retain my mail on several mail ids (my personal, the admin).
Maybe I should not bother to try to "clone" old server to new server - just
create new SBS server and manually rebuild taking old SBS off network?

Migration from SBS 2003 Std to SBS 2003 Prem R2 Plus new hardware)

Post by Lanwench [ » Thu, 12 Jul 2007 23:45:46

I don't like two NICs on a domain controller/DNS/WINS box - if you aren't
using ISA, don't bother.

The IP address can always be changed later ...unlike your internal DNS
domain name.

If you want to move your entire AD structure over, then you're stuck with
it. But I don't see why you would think local.mydomain.com would be a
problem....it shouldn't, if your DNS server is configured properly. I use
stuff like that all the time. If local.mydomain.com is not a valid *public*
subdomain then it should work fine.

Check out www.sbsmigration.com for just the ticket.