none
Exchange 2003 and Active Directory 2012 RRS feed

Answers

  • Hi Darren,

    Since AD 2012 is not listed in the supportability matrix, I'm afraid this is not supported.


    Frank Wang
    TechNet Community Support

    • Marked as answer by darrenpoyner Sunday, January 13, 2013 11:22 PM
    Friday, January 11, 2013 6:22 AM

All replies

  • The Exchange Server Supportability Matrix does not mention Active Directory 2012.

    http://technet.microsoft.com/en-us/library/ff728623(v=exchg.141).aspx

    Is Exchange Server 2003 supported with Active Directory 2012?

    Thanks,

    Darren

    yes please let us know...
    we are searching for days if there is a way to co-exist  windows 2012 server (essentials in my case) active directory within an existing windows 2003 standard server active directory with exchange 2003 without migration.
    We want to keep it both.
    any help will be greatly appreciated.  
    Thursday, January 10, 2013 10:08 AM
  • Hi Darren,

    Since AD 2012 is not listed in the supportability matrix, I'm afraid this is not supported.


    Frank Wang
    TechNet Community Support

    • Marked as answer by darrenpoyner Sunday, January 13, 2013 11:22 PM
    Friday, January 11, 2013 6:22 AM
  • Thanks Frank.

    Darren

    Sunday, January 13, 2013 11:22 PM
  • I just built a test environment, with VMs that are identical to my production servers and Exchange 2003 seems to be just fine with Windows 2012 active directory servers (the forest and domain level are working on the 2008 r2).  My 2 original Win2003sp2 AD servers were replaced by 2 new Windows 2012 DC.  I did some tests afterward with Exchange 2003 and Outlook and everything seems to be running just fine.  Even though this configuration does not seem to be supported by Microsoft, did anyone else tried this config ?  (I look forward to going in prod with this config and do the transition to Exchange 2013 in a couple of months... should I instead go to 2008r2 DC until I migrate my Exchange server to 2013, before introducing 2012 DC in my environment ?)
    • Edited by Eric Bibaud Thursday, April 18, 2013 6:58 PM
    Thursday, April 18, 2013 6:55 PM
  • Please see my thread:

    http://social.technet.microsoft.com/Forums/exchange/en-US/9a8bc14b-1a45-4b8b-ac3a-38d63e66a7da/exchange-predeployment-analyzer-exchange-2010-compatibility-check-does-not-recognize-windows?forum=exchangesvrdeploylegacy

    Seems I managed to put that situation into production before I found out that it wasn't supported by Microsoft

    Either way, Exchange has been working fine for 5 months with a new 2012 R2 Domain Controller carrying all the FSMO roles, with two legacy 2003 R2 DCs all of which being Global Catalog servers.

    About 1 month ago, I demoted the secondary DC, removed it from the domain, wiped it, installed Server 2012 R2 on the box (Poweredge 310) and promoted it to DC and GC.

    A couple of weeks later, I demoted the last of the 2003 R2 DCs and left it domain joined as a member server. The Exchange org is still humming along, but I am pissed that I didn't find anything about the unsupported Exchange 2003 / AD 2012 when I did otherwise exhaustive legwork putting together a deployment plan.

    I am wondering if the unsupported status just means that Microsoft did not do regression testing against Exchange 2003 in an AD forest that contains 2012 or higher DCs.

    Regardless of the Forest and Domain Functional level (in our case, Server 2003) Microsoft does NOT support the combo.

    I am currently hoping someone has been in this state with their exchange org and AD setup, and has done a Transition from Exchange 2003 to Exchange 2010 successfully and might be able to allay my nervousness. We are planning to start the Transition within the next few weeks.

    Chris.


    "Time is an illusion, Lunchtime, doubly so..." - Ford Prefect

    Tuesday, September 16, 2014 3:16 PM
  • Not supported != Doesn't work.

    MS doesn't include that set of software in its testing. That's why they say "not supported" -- it's also more polite than "you're on your own if there's a problem".


    --- Rich Matheisen MCSE&I, Exchange MVP

    Wednesday, September 17, 2014 2:11 AM