Migrate Exchange 2000 to Exchange 2011

spcw

Has anyone done this. IS there tools to do it or do I need to step 2000 to 2003 or 07 first.

Thanks

Fysh

Having been part of a large corporate that spent over £500K on migrating from Exchange 5.5 to Exchange 2003 I wouldn't imagine that migrating from Exchange 2000 to Exchange 2010 is going to be at all straightforward, and I would guess that trying to do it in one fell swoop will be tough going.

Is there any particular reason you're going from a version that's 3 major revisions back to the current version in this upgrade? Ie could you scale back the project to go from Exchange 2000 to Exchange 2007 instead?

testicle

Exchange 2011 doesn't exist, so I assume you mean 2010!

There's no upgrade path from 2000, you'll have to upgrade to at least Exchange 2003 Service Pack 2 at a minimum first.

spcw

its a customer driven request to go to SBS 2011. they ofen feel like you are doing a disservice loading less than the latest release although that what we do in our own company ( a lot less hassle). Its a small business 16 users so I suppose we can alway export the pst files and import to the new setup.

thanks for the replies

Capt'n Midnight

If it works don't fix it, especially with mission critical systems.



Ask them how long they can do without email for.

Ask them what NEW features of the newer product will they use ?

And if they are using PST's then certainly aren't even using the message store :rolleyes:



Since it's SBS you can't migrate the users to a second box.


Since it's SBS and using PST's ( how do they get backed up ?? are they over 500MB ??) , I'd guess you could export the GAL, use CSVDE to dump the email accounts to a file., save any rule that exist


then do a clean install , import the CSVDE and do the rules manually
Yes it sounds like it would take longer than an upgrade, but you have the old machine ready to failover to at any time. Doing an upgrade on a single server isn't fun when it goes pear shaped.

William Powell

Capt'n Midnight wrote: »

...
And if they are using PST's then certainly aren't even using the message store :rolleyes:

Since it's SBS and using PST's ( how do they get backed up ?? are they over 500MB ??) ...

I read the PST bit to mean the OP was going to export the message store accounts one at a time to PST files then import them into a the new message store not that the users were using PST files (although many do:rolleyes:)

Capt'n Midnight

William Powell wrote: »

I read the PST bit to mean the OP was going to export the message store accounts one at a time to PST files then import them into a the new message store not that the users were using PST files (although many do:rolleyes:)

Sorry but ranting about using PST's with exchange is an involuntary reflex :pac:


The fights we've had over using OST's and people wanting multi-GB PST's :rolleyes: "it's not supported , the bigger it is the more likely it will break, it'll take bleedin ages to run the repair tool, etc."

and the fun and games trying to tell/explain to laptop users "server's down - DON'T use your email or it will re-sync your OST to nothing"

exmerge - it's a Godsend , it's the only reason I could justify using exchange if it were used as nothing more than an email server. Mdaemon rocks. The number of times you could restore emails without faffing about with tape drives.

testicle

Capt'n Midnight wrote: »

Sorry but ranting about using PST's with exchange is an involuntary reflex :pac:


The fights we've had over using OST's and people wanting multi-GB PST's :rolleyes: "it's not supported , the bigger it is the more likely it will break, it'll take bleedin ages to run the repair tool, etc."

and the fun and games trying to tell/explain to laptop users "server's down - DON'T use your email or it will re-sync your OST to nothing"

exmerge - it's a Godsend , it's the only reason I could justify using exchange if it were used as nothing more than an email server. Mdaemon rocks. The number of times you could restore emails without faffing about with tape drives.

WTF? The last time you saw Exchange must have been 1995...

spcw

William Powell wrote: »

I read the PST bit to mean the OP was going to export the message store accounts one at a time to PST files then import them into a the new message store not that the users were using PST files (although many do:rolleyes:)

thats the plan, donkey style its only 16 users.

Capt'n Midnight

spcw wrote: »

thats the plan, donkey style its only 16 users.

exmerge is yer only man

matt-dublin

you'll have to upgrade/migrate to SBS 2003 and then upgrade/migrate to SBS 2011

i would always suggest migrate as the upgrades never work smoothly especially the exchange element of things.

or, PST all of your mailboxes using exmerge, create a new sbs 2011 server, create new accounts and import them using exmerge or powershell scripts.

either which way you're talking a solid day or two worth of work.

testicle

Capt'n Midnight wrote: »

exmerge is yer only man

ExMerge ceased to exist with Exchange 2007.

matt-dublin

Exmerge still exists it's just no longer shipped with exchange. It will still work with exchange 2007/2010 if you have outlook 2003 on the machine doing the import/export

However it's just as easy to use the exchange powershell

matt-dublin

Exmerge still exists it's just no longer shipped with exchange. It will still work with exchange 2007/2010 if you have outlook 2003 on the machine doing the import/export

However it's just as easy to use the exchange powershell. Bear in mind though to do the import using powershell u will need outlook 2007/2010 installed on a 32bit machine so itself u can't do the import on the server as it needs to be x64 for exchange 2010

Capt'n Midnight

testicle wrote: »

ExMerge ceased to exist with Exchange 2007.

The OP has Exchange 2000

Also it's SBS





A few minutes with ExMerge and it'll be exporting into individual pst's for each account. Very straightforward, and you can relax because the original server is unchanged, and no matter what happens there is the option to give each user a pst file with their old email. It's not sexy or high tech, it just works and as an admin you don't need to loose any sleep because you have a Plan B.

It's only 16 users, so setting up them on a new server manually isn't going to take forever. You could even just use outlook to import the emails from the PST's if you want to do as little directly on the exchange server as you can. There is a lot to be said to do things in the simplest way possible, where every operation is inside your comfort zone and you don't take any risks.

Obviously you would take a different approach with bigger organisations. And if SBS is being used for more than just exchange then those uses would also need to be considered.

testicle

matt-dublin wrote: »

Exmerge still exists it's just no longer shipped with exchange. It will still work with exchange 2007/2010 if you have outlook 2003 on the machine doing the import/export

However it's just as easy to use the exchange powershell. Bear in mind though to do the import using powershell u will need outlook 2007/2010 installed on a 32bit machine so itself u can't do the import on the server as it needs to be x64 for exchange 2010

You don't need Outlook to Export/Import with Exchange 2010 SP1.

Capt'n Midnight wrote: »

The OP has Exchange 2000

He'll be importing to Exchange 2007/2010.......... :rolleyes:

Best Practices, Best Practices, people. Just because you can do something, doesn't mean you should.

Fysh

testicle wrote: »

Best Practices, Best Practices, people. Just because you can do something, doesn't mean you should.

Surely having a quick and easy rollback option like "plug in and power on the original server" is a pretty good practice for a project involving 16 end users and by the sound of it one person doing both support and project work?

testicle

Fysh wrote: »

Surely having a quick and easy rollback option like "plug in and power on the original server" is a pretty good practice for a project involving 16 end users and by the sound of it one person doing both support and project work?

I never said migrating was better than upgrading, in fact I never mentioned either, other than to say that you can't upgrade from 2000 to 2010 without going to 2003 SP2 first.

Be aware that if you are going down the migrating route and want to roll back like you said, you will need a new Active Directory Domain also, including removing/adding the client workstations from said Domain.

matt-dublin

testicle wrote: »

I never said migrating was better than upgrading, in fact I never mentioned either, other than to say that you can't upgrade from 2000 to 2010 without going to 2003 SP2 first.

Be aware that if you are going down the migrating route and want to roll back like you said, you will need a new Active Directory Domain also, including removing/adding the client workstations from said Domain.

Not necessarily, you can migrate exchange without having to migrate domain.

But again maybe overly complex

testicle

matt-dublin wrote: »

Not necessarily, you can migrate exchange without having to migrate domain.

But again maybe overly complex

Read what I said again. He mentioned rolling back. Installing a version of Exchange into a domain with a previous version of Exchange in it, is called co-existence. You can't co-exist Exchange 2000 and Exchange 2010, you have to install Exchange 2003 SP2 first, and then remove all the Exchange 2000 servers, before trying to install Exchange 2010.

Trust me, I know what I'm talking about. I'm an Exchange Admin as my primary trade.

matt-dublin

testicle wrote: »

Read what I said again. He mentioned rolling back. Installing a version of Exchange into a domain with a previous version of Exchange in it, is called co-existence. You can't co-exist Exchange 2000 and Exchange 2010, you have to install Exchange 2003 SP2 first, and then remove all the Exchange 2000 servers, before trying to install Exchange 2010.

Trust me, I know what I'm talking about. I'm an Exchange Admin as my primary trade.

as is here, i was just providin another option not having a go at you. (i missed the rolling back apologies )