Migrating from SBS 2000 to SBS 2008

Can anybody point me to documentation for migrating from SBS 2000 to SBS
2008? I can see documentation for SBS 2003 to 2008........

Thanks

 

Hello,

Thank you for posting here.

According to your description, I understand that:

You have a concern about how to migrate from SBS 2000 to SBS 2008.

If I have misunderstood the problem, please don't hesitate to let me know.

Currently, there is no direct migration path from SBS 2000 to SBS 2008. SBS
2008 setup will crash if you attempt to join an existing SBS 2000 domain
during a migration.

I will forward this request to the product groups and if there is any
update I will post it in this thread for your reference.
Thanks for the reporting.

Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

Hi,

As Miles mentioned, we cannot migrate SBS 2000 to SBS 2008 directly. To
migrate user and computer accounts, you can install ADMT 3.1 on a member
2008 server in the destination domain. You must first complete SBS 2008
setup as a clean install in its own domain prior to this. Exchange
mailboxes must be exported using exmerge and copied to the SBS 2008 server,
where you can run the import-mailbox cmdlets.

I hope that the above information can be of assistance.

Best regards,
Laura Zhang

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

Check out Jeff's site: http://www.sbsmigration.com
Don't hesitate to email him directly.

Fred

 

Here is a link to documents that should help.

My guess is that you will need to do a two stage migration.

You will need a new 64 bit server with a MINIMUM of 4 GB of RAM. and a
minimum boot partition of 60GB.

Setup a temporary server using a PC running Virtual Server 2005 and do a
swing migration of SBS 2000 to SBS 2003. You can do this with Jeff's Swing
migration kit listed below

Then migrate to SBS2008 using a document from this series
http://technet.microsoft.com/en-us/library/cc707659.aspx

Just FYI, I'm running SBS2008 in two fashions. One on server 2008 using
Hyper-V and the other in a VMware environment. So you COULD actually setup
SBS entirely in a Virtual environment.

Hope this helps

Michael Patrick, Engineering Coordinator The Mirazon Group
MCITP-Enterprise, MCSE-2003, MCT, MCSA-M, MCDST, MS Small Business
Specialist
312 Whittington Pkwy, Suite 111 Louisville, KY 40222
Office 502-240-0404
Fax 502-240-0409

 

Hi Gang,

I want to add some clarification on this thread so nobody gets confused
about what I'm soon supporting for migration to SBS 2008 vs what are being
suggested as hypothetical below.

I will be supporting SBS 2003 to SBS 2008, but that Kit is not released yet.
I expect to support 2000 to 2008 as well.

I expect to provide a Swing Migration project scenario for migration from
SBS 2003 to SBS 2008, to be release (hopefully) in mid Nov 2008. The project
solution and path I will offer is intended to continue to provide the list
of benefits most people associate with a Swing Migration, including "nothing
to undo", parallel construction offline with open timeline, preserve the
server name, preserve the domain name and configuration, and the predictable
result at the workstations saving the profiles unchanged. I will incorporate
essential and useful elements in the SBS Setup so that the installation you
get on your final server is "by the book", but I think the end result will
be a much better one than what MS documentation path is going to provide.

The Swing Migration scenario for SBS 2003 to 2008 will be recognizable as
inspired by the procedural design compared to Swing to 2003 platforms, but
there's some unavoidable complications and some non-subtle differences and
tasks and procedures. Stated simply, you really can't just take the "old
swing docs" and to the migration to SBS 2008 because SBS 2008 has a
dramatically different setup automation now. Really different setup.
Likewise, you probably can't judge from the "2003 Swing" process where the
procedures for 2008 will diverge.

However, I want to quell any discussion that there will need to be any
situation where a "double-Swing" would be implied for any reason. I don't
see that as ever required or even beneficial. There are many options to
avoid that. I'm committed to providing a project solution that involves one
construction project offline, with on transition to live server replacement
that you can schedule for your convenience and only have the data move occur
in that transition period.

It will be more obvious what I'm talking about once I provide details of how
I intend a "normal" Swing Migration to SBS 2008 to work, you will almost
immediately recognize how the solution becomes available for migration from
SBS 2000 to SBS 2008 in an orderly manner.

Regarding the topic of VMs and whatnot, Swing Migration for 2008 platforms
will be possible with or without using VMs, it's a non-issue. It will be
neither a requirement, nor an impediment, nor a concern if you have a
preference one way or another. I'm as much in favor as anyone else for using
VM (Hyper-V or VMware) where it helps and not depending upon it. As I said
many times at SMB Nation last week, a virtual server environment is just a
different hardware platform that doesn't require dedicated hardware.

I anticipate adoption support for SBS 2000 to SBS 2008 fairly quickly after
releasing a Kit to support SBS 2003 to SBS 2008, I'm leaning toward that
being something I support with "one kit", not a pair of products. However I
do expect that there will be a different Technician Kit outlining the
migration to non-SBS platforms based upon Windows 2008 and/or Exchange 2007
on a non-SBS server. This is primarily because the SBS 2008 installation and
setup is very much not like what you would do with standard version of
Windows or Exchange.

Jeff Middleton SBS-MVP