We are currently running windows 2000 and exchange 2000 we are looking to upgrade to new hardware and software (to server 2003 and exchange 2007) we introduced a new DC a couple weeks ago. win2k3 and did the whole forest prep domain prep and have the dc working perfectly we would like to keep both exchange servers working together until everyone is ported over and the manager feels like it is ok to shut off the old exchange. what order should we take on this upgrade path, given that we currently have 1 ek2000 server 2 win2k servers(as dc) and 1 win2k3 DC in mixed mode? Keyboard Not Detected - Press F1 to continue

Hi CitrusFizz,I would start out by getting your Exchange 2007 server achitecture figured out. If you could use Windows 2008 Server rather then Windows 2003 server I would definatly go that route.First thing you need your Schema Master to be at leaston Windows 2003 Server with SP1. All Global Catalogs in your org should be Windows Server 2003 with SP1.If you can't do W2K3 SP1 in your entire Org then I would make sure all GCs in the same AD site where Exchange 2007 will reside will be W2K3 SP1. Once you have that in place you can go to your Install folder for exchange and run "setup /prepareAD" (assuming you are installing Exchange 2007 sp1). This process will prep your schema, the domain and prepare the legacy exchange permissions. You can run that command as many times as you want.Once the AD environment is prepped by running the command above you will want to deploy the Exchange 2007 Client Access Server Role, then the Hub Transport Role, then the Mailbox Server role. If you're using the Edge Transport Server or UM roles you can deploy those at any time but you need to deploy the CAS role first. When you deploy the first HT server it will establish a RGC between the 2000 and 2007 environment.Once the new 2007 environment is up start testing communication between the two Exchange environments, mail routing, owa etc. Once you have confirmed the tests and everything looks good migratate some test mailboxes. Make sure they work, then perform a pilot of 5 to 20 users and see how they like things. Once that's done you ahve the rest of the users you can migrate. If you are using BeS you will have to add some special security rights for users. Otherwise also see these:Exchange 2007 System Requirements:http://technet.microsoft.com/en-us/library/aa996719.aspxHow to Prepare Active Directory and Domains:http://technet.microsoft.com/en-us/library/bb125224.aspxHope this gives you an idea on what needs to be done.BP

We are small and got a good price on win2k3 servers. is there a huge compelling reason to upgrade to 2008? also thanks for the kick ____ info. Keyboard Not Detected - Press F1 to continue

2008 has better memory management and security which is nice with Exch 2007.I've seen memory leaks when using Server 2003.Glad I could help, take care and good luck!BP

can we have exchange 2007 installed on 2008 run with a 2003 DC and 2000 DC's?Keyboard Not Detected - Press F1 to continue

Server 2008 is just another server. I don't see why you would have a problem running Windows 2008 Server in a Windows 2000 native environment.Exchange 2007 is really the picky one.BP

i guess i worded that wrong.. can we have windows 2008 as a DC in a win2k enviroment with exchange 2007 running on the 2008 DC?Keyboard Not Detected - Press F1 to continue

Technically Exchange 2007 is not supported on a DC. Windows 2008 can support Windows 2000 native mode and up.You will have to make Schema Extentions to add a W2K8 DC to your environment though.All Windows 2000 Servers will also need to be at SP4 to support W2K8.http://blogs.techrepublic.com.com/datacenter/?p=308andhttp://www.petri.co.il/understanding-windows-server-2008-active-directory-domain-and-forest-functional-levels.htmBP