We're currently on a Server 2003 domain/forest with Exchange 2007 SP1. I understand that we need to prepare our domain/forest for Server 2008 with adprep and forestprep. What I would like to know is that what major changes do I need to perform on Exchange 2007? As long as Exchange can talk to the Schema/Global Catalog/DC, I think everything should be fine. Any thoughts? Thanks. -Jose

Hello Jose, Running adprep /forestprep, adrep /domainprep, adprep /gpprep will not affect your Exchnage 2007 SP1..The only time you may worry about exchange is if you decide to upgrade to exchnage 2010.Isaac Oben MCITP:EA, MCSE

I have been reading that Server 2008 R2 does not play nice with Exchange 2007 SP2. Can you confirm this? We might be virtualizing Server 2008 R2 on a VMWare ESXi environment. What do you think? What has been the issue that you found out with upgrading to Exchange 2010(which we will not do yet). Thank you sir for your response.

Yes, at the moment, Exchnage 2007 SP2 is not supported on W2K8 R2. But according the MS exchange team blog, they are working on a fix so this can be possible. Some rumors that it might happened in the next release of W2K8 R2 SP1 or exchange 2007 SP3. You can read more here: http://msexchangeteam.com/archive/2009/11/04/453026.aspx Isaac Oben MCITP:EA, MCSE

Any preferred environment for virtualizing Server 2008 R2? VMWare ESXi? VMWare ESX? Thanks.

If you are talking about Exchange 2007 in Windows 2008 AD environment, then it is fully supported. Please read these articles: http://msexchangeteam.com/archive/2009/11/30/453327.aspx http://technet.microsoft.com/en-us/library/ee338574(EXCHG.80).aspx Santhosh Sivarajan | MCTS, MCSE (W2K3/W2K/NT4), MCSA (W2K3/W2K/MSG), CCNA, Network+ Houston, TX http://blogs.sivarajan.com/ http://publications.sivarajan.com/ This posting is provided "AS IS" with no warranties, and confers no rights.

When doing schema updates for Domain Controllers, Exchange might be affected. Not in a terrible way but still affected.After schema updates, run EXBPA, there is a chance that you might need to do something with purported serach and possibly restart then Exchange services. lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com