Hello, We are preparing to upgrade our five Windows Server 2003 domain controllers to Windows Server 2008 R2. We were planning to completely wipe the 2003 OS and put a clean install of Server 2008 R2. We will continue using Exchange 2003 after these upgrades. My question is what becomes of the Exchange 2003 "frontend" in Active Directory after all the DCs have Windows Server 2008 R2 installed on them? By frontend I'm referring to the Exchange tabs that are integrated with AD on Windows Server 2003. My understanding is that these tabs are not compatible with Server 2008 R2, yet they seem to be the only way to configure permissions and other settings for users' Exchange accounts. As far as I can tell, the only solution is to leave one of our domain controllers with Windows Server 2003, and the use that one DC to configure users' Exchange settings in AD. Is this correct or is there an alternative? What does Microsoft recommend in this scenario? I appreciate any assistance. Thank you.

Just install the 2003 support tools on the Exchange 2003 server. You can run ADUC remotely from there and mailbox enable users, etc. Or you could setup a dedicated XP or 2003 machine with ESM and the 2003 support tools installed.Mike Pfeiffer | Exchange: MCM/MVP | blog: mikepfeiffer.net | twitter: @mike_pfeiffer

Just install the 2003 support tools on the Exchange 2003 server. You can run ADUC remotely from there and mailbox enable users, etc. Or you could setup a dedicated XP or 2003 machine with ESM and the 2003 support tools installed.Mike Pfeiffer | Exchange: MCM/MVP | blog: mikepfeiffer.net | twitter: @mike_pfeiffer

I forgot about ADUC on the Exchange 2003 Server. If I can just use that, then that's what I'll do. I guess I was just fixated on Exchange 2003 having to be integrated with a domain controller. Thanks for the answer, Mike!

I forgot about ADUC on the Exchange 2003 Server. If I can just use that, then that's what I'll do. I guess I was just fixated on Exchange 2003 having to be integrated with a domain controller. Thanks for the answer, Mike!