– if you use Exchange 2003 and have the need for connectivity to Windows Server 2008 or higher OS DCs, you have to use at least Exchange 2003 SP2. – Exchange 2003 can’t be installed on Windows Server 2012. – Exchange 2003 can’t be installed on Windows Server 2008.
!!!Keep in mind this isn’t supported configuration!!!Įxchange Server 2003 and Windows Server 2008/2008 R Operating System/Domain Controllers See also Directory server detection and DSAccess usage and Revert DSAccess to default for details. Open ESM and choose the “Directory Access” tab of the Exchange server properties. – if you really must use both in the same site then some additional configuration should help to hardcode (default is automatic discovery) the DSAccess on the Exchange 2000 to DCs with Windows Server 2003 or Windows 2000 Server OS. !!!Keep in mind this isn’t supported configuration!!! – if there is no other option then it should be possible to use the Windows Server 2008 DCs in a different site then the Exchange 2000 SP3.
– for upgrading to Windows Server 2008 or higher you have to check that no Exchange Mangled Attributes exist, this applies also for Windows Server 2008. – Exchange 2000 SP3 isn’t supported when working together with Windows Server 2008 or higher DCs. – Exchange 2000 can’t be installed on Windows Server 2008. They now maybe have to coexist even with Windows server 2003/2008/2008R2 and Exchange Server 2003/2007/2010 or should be upgraded to new versions.Įxchange Server 2000 and Windows Server 2008 Operating System/Domain Controllers Within the last years we’ve got several new Windows Server versions, 20 R2 and now Windows Server 2012, and also some new Exchange Server versions, 2007, 2010 and now 2013. Even if some are NOT supported i will list them here as they should work. This article should give an overview about the relationships with the different Exchange Server versions and the requirements for Windows server 2008/2008R2 and Windows Server 2012 Domain controllers.
0 kommentar(er)
