Re: Migration SBS2003 sp2 to Server 2008 & Exchange 2007


Hi Derek,
I'm also planning to do the same type of migration and have done my research
and planning. Most likely will do the migration over the weekend. Quick
question. Are you using SBS 2003 SP2 Premium with ISA 2004? I use ISA 2004
and am planning on implementing and using ISA 2006 as my new firewall.

I've read these 2 documents and it appears all I will need. Check them out
and let me know if you have any questions or concerns.

Migrate to Windows Small business Server 2008 from Windows Small Business
Server 2003
http://go.microsoft.com/fwlink/?LinkId=92482

Deploying Microsoft Internet Security and Acceleration (ISA) Server 2006
with Windows Small business Server 2008
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=7f341602-d2d0-45f5-bad0-bd5af3ed39fd


"DerekV" <DerekV@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1C032A23-8928-4009-89A2-1B895DCD6150@xxxxxxxxxxxxxxxx
Greetings SBS and Windows Server community,

I'm seeking advice on migrating a from a SBS 2003 sp2 domain with exchange
to a Server 2008 environment with Exchange 2007. Since I have fewer than
20
users, and am installing onto new hardware, I am planning to recreate the
users in the new AD by hand and then transfer files and emails over. I
realize that there are many other ways to do this, which is why I am
asking.
I'm looking to find out if there are any gotchyas with my plan or if
another
method is better, considering my situation.

Concerns:
-Due to two unrelated unfortunate incidents involving raid hardware, the
exchange database has become corrupted two separate times and recovery
involved some degree of low level "last resort" techniques. I have
suspicions that there might still be lingering corruptions within the
store.
I want a guarantee of a "clean slate" with no corruptions.
-I am aware that many things are done differently within SBS then in
standard business server. I do not want issues or annoyances down the
road
because of these differences. This is one reason to avoid using a trust
between the old and new domains to move AD users and computers.

Details:

From:
One machine: SBS2003 Premium SP1
Exchange 2003 SP1
Domain name: "OldDomain.local"
Desktop and My Documents folders are redirected.
20 users, as many mailboxes, 17 XP Pro devices (joined to domain)
Group Policy

TO:
Multiple Server 2008 instances running under virtualization.
Something like the following:
1) DC w/DNS, DHCP, Group Policy
2) Exchange 2007, antivirus for exchange
3) File server w/antivirus
Domain name: "NewDomain.ourFQDN.com"

I tested creating a new domain, exchange install, and exporting my own
mailbox with exmerge and importing it with "Import-Mailbox" as per
( http://technet.microsoft.com/en-us/library/bb691363.aspx )
And it appears to work fine.

Jist of plan:
1. Set up new server instances and roles on isolated network
2. Enable (except DHCP) and join to company LAN under new private subnet
3. Create some users in new AD with same login and primary email as
before.
4. Move user files and fix permissions.
5. Export mailboxes with exmerge, import with Import-Mailbox cmdlet
6. Set up old exchange server to forward email for users to new exchange
server's SMTP
7. Join users' computers to new domain.
8. Have users login , test critical functions, troubleshoot
10. Repeat 4-8 with rest of users

Apart from some issues sending email within the domain while in the middle
steps, does anyone have any major misgivings with my idea that they would
be
willing to share?

Thanks in advance!
_derek




.

Loading