Exchange 2003 SP2 and Windows Server 2008 R2 Domain Controllers

  • Thread starter JDC IT Department
  • Start date Views 7,487
J

JDC IT Department

I'm looking at adding two Windows Server 2008 R2 Domain Controllers into our

Windows Server 2003 domain to support our Exchange 2003 SP2 server and

replace a retiring Windows Server 2003 Server.

Our Domain and Forest functional levels are currently Windows Server 2003,

which supports domain controller operating systems (Windows Server 2008 R2,

Windows Server 2008 and Windows Server 2003) according to the "Appendix of

Functional Level Features" on Technet .

So there should not be an issue other than running adprep /forestprep and

adprep /domain.... right!?

But, according to the Exchange Server Supportability Matrix, Windows Server

2008 R2 Active Directory Servers are not supported as global catalog servers

or domain controllers in a Exchange 2003 SP2 environment!!!???

This was a shock to me... How can Windows Server 2008 R2 be a DC for a

Windows Server 2003 domain and forest, but not communicate with an Exchange

2003 SP2 server?

Hopefully, I'm not the first to see this issue (or maybe I am), but I know a

lot of Exchange 2003 admins will not be happy if there is not a work

around... or is Microsoft trying to push everyone automatically to Exchange

2010...
 
J

JJessop

I am in the same situation. I found an article online stating that it can work.

http://www.winvistatips.com/adding-2008-dc-2003-environment-w-exchange-t711618.html

I am going to try and capture my network onto virtual drives and test this

out. Any other ideas would be great.

Thanks,

"JDC IT Department" wrote:



> I'm looking at adding two Windows Server 2008 R2 Domain Controllers into our
> Windows Server 2003 domain to support our Exchange 2003 SP2 server and
> replace a retiring Windows Server 2003 Server.

> Our Domain and Forest functional levels are currently Windows Server 2003,
> which supports domain controller operating systems (Windows Server 2008 R2,
> Windows Server 2008 and Windows Server 2003) according to the "Appendix of
> Functional Level Features" on Technet .

> So there should not be an issue other than running adprep /forestprep and
> adprep /domain.... right!?

> But, according to the Exchange Server Supportability Matrix, Windows Server
> 2008 R2 Active Directory Servers are not supported as global catalog servers
> or domain controllers in a Exchange 2003 SP2 environment!!!???

> This was a shock to me... How can Windows Server 2008 R2 be a DC for a
> Windows Server 2003 domain and forest, but not communicate with an Exchange
> 2003 SP2 server?

> Hopefully, I'm not the first to see this issue (or maybe I am), but I know a
> lot of Exchange 2003 admins will not be happy if there is not a work
> around... or is Microsoft trying to push everyone automatically to Exchange
> 2010...
 

mckinneyb

Member
We have successfully set this up as of last week. Previously all 2003 SP2 domain controllers and servers, running Exchange 2003. We added one brand new 2008 R2 domain controller and all went well. The only thing we ran into was a problem with activesync users not being able to get their email after the upgrade. We've had that happen one other time in the past, so I can't confirm that the 2008 DC was the cause, but certainly coincided with the timing of adding it.




If you run into that issue, Microsoft KB article 817379 is what we used to restore mobile connectivity.




Otherwise, things have been smooth. I definitely would not upgrade the functional level of the domain until you have upgraded to a newer version of Exchange, though.
 
Top