Shortest way to move from exchange 2000 to 2007.

Shortest way is to make sure your DCs are 2003 SP1/SP2. Make sure both your AD and Exchange are in Native Mode. Install 64bit Windows and Exchange 2007 on your new server. Then replicate public folders and move mailboxes.

That's it, two lines of text. Obviously there is a little more to it. You will need to manually create new settings on the send and receive connectors since they don't come over as they're different in 2007.

http://exchangepedia.com/blog/2006/09/how-to-install-anti-spam-agents-on-hub.html will show you how to do the anti spam on your single CAS/MB/HT server so that you don't need to use an Edge or an anti spam appliance. (unless you already have the appliance)

If you have more than 1 AD site I strongly recommend you check the site topology configuration in AD Sites and Services. Exchange 2007 AD Site Topology Service reads site information from AD and uses it to configure internal routing. It's best to get this right first time in order to optimize internal mail flow.

If your ditching Edge Transport you need to configure SMTP Connectors on the Hub Transport server along with Anti-Spam/Anti-Virus agents (as mentioned above).

Regards

easiest way to use exchange 2007 from 2000...
windows 2003 and exchange 2007  are ready configured, pitchup, all done.
There is not edge transport (means no spam configuration is required).
These is not site. All in one location.
No public folders are there to move from 2000 to 2007.
Simple question how to move mails of all users from 2k to 2k7.
Please read the question and then answer.
Thanks

And I quote: "and move mailboxes."
You can move the mailboxes using Exchange Management Console. You do not need to bother with any PST files or anything like that.

What other information do you need to select Move Mailbox?

Or would you like to mention that you have two forests? That might change matters?

There are always public folders to move across.
You may not be using public folders that you can see in public folders, but there will be system folders that contain free/busy information etc that need to be replicated to the new server.
Those need to be done first.
Once those have been replicated across you will use the Move Mailbox tools in Exchange 2007 Management Console to move the mailboxes to the new server. Once that is complete, leave both servers running for a while until all users have connected at least once so they are redirected to the new server and then you can remove the original Exchange 2000 server as per the instructions.

Simon.

Thanks to chris-k, czcdct and Sembee.
By your answers I got the picture clear.

One more question please,
Active Directory should be migrated from win2k to win2k3 or create all 100 users with similar username ID+email. We prefer creating new AD.
Still can we sync publish folder and move mailbox if we are creating new AD czcdct mentioned above?

No. If you create a new forest you are in to a whole new question.
You will then have to do a complete migration.
Users will, unless you choose to purchase some migration tools (Quest.com etc.), experience downtime and you will have a far more complex move than necessary.

Is there something wrong with your Active Directory that makes you think you should create a new forest?

No there not problem with AD (win2k). But trying to skip AD migration from 2k to 2k3. Then Exchange migration from 2k to 2k3 and then 2k7.

       we thought we will download all users email to their PC as POP3 or PST file.
THen we will remove them from exiting domain and add to new domain.
Exchange 2007 is also ready. So we will upload the mail from POP3/PST to Exhange server 2007 with new domain. And new AD we will make manually and similar. Is this a good idea if you want  to skip some extra headache. And have new AD.