Solved

Upgrading Active Directory domain controller & domain functionality level from Windows Server 2003 into 2012 R2 ?

Posted on 2014-10-19
12
853 Views
Last Modified: 2016-03-28
Hi All,

What are the caveats and the pitfalls to avoid when performing the Active Directory domain controller upgrade & raising domain functionality level from Windows Server 2003 into 2012 R2 ?

in my current AD domain, the Exchange Server 2010 SP2 is working without issue communicating with the AD Server 2003.

Thank you in advance.
0
Comment
  • 4
  • 4
  • 3
  • +1
12 Comments
 
LVL 5

Expert Comment

by:Armenio
ID: 40391424
We just performed an upgrade this week  from server 2003 to 2013 r2. My advise is upgrade to 2008 first then 2012 works perfectly with no issues and is a safe bet.
1
 
LVL 7

Author Comment

by:Senior IT System Engineer
ID: 40391486
Ok so in this case what's the operating system ?

Does that 2008 first is the domain functionality level ?
0
 
LVL 34

Accepted Solution

by:
Seth Simmons earned 500 total points
ID: 40391996
Exchange 2010 SP2 is no longer supported since April and does not support Windows 2012 R2 domain controllers.
Upgrade Exchange to SP3 and at least update rollup 5 (recommend 7 as it's the latest) to support a Windows 2012 R2 AD environment.  you also don't need 2008 as a stepping stone; you can install a 2012 R2 domain controller in a 2003 AD environment

Exchange Server Supportability Matrix
http://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx

Microsoft Exchange Server 2010 Service Pack 3 (SP3)
http://www.microsoft.com/en-us/download/details.aspx?id=36768

Update Rollup 7 For Exchange 2010 SP3 (KB2961522)
http://www.microsoft.com/en-us/download/details.aspx?id=44023

Microsoft Exchange Server 2010 Service Pack 2
http://support2.microsoft.com/lifecycle/search/default.aspx?alpha=exchange+server+2010&Filter=FilterNO
0
 
LVL 7

Author Comment

by:Senior IT System Engineer
ID: 40392027
Seth,

Thanks for the reply so in this case I'll need to upgrade the SP2 into SP3 with CU 7 first and then migrate the FSMO role into Windows Server 2012 R2 DC ?

after that demote or decommission the old Windows Server 2003 so that the new Exchange Server 2010 SP3-CU7 can use the new DC/GC setting on WIndows Server 2012 R2 ?
0
 
LVL 34

Assisted Solution

by:Seth Simmons
Seth Simmons earned 500 total points
ID: 40392059
upgrade exchange first before promoting your first 2012 R2 domain controller
once exchange is at SP3 then you can promote your 2012 R2 server

after that demote or decommission the old Windows Server 2003

i would let the 2 domain controllers run together for a little while (perhaps a week) to make sure they are taking to each other ok and replicating.  once that looks good, transfer your FSMO roles and demote.  i would suggest the demote be done after hours just in case exchange has issues.  it shouldn't, but just in case.  if it does have issues, restart the exchange topology service (which, in turn will restart all other exchange services thus a brief outage) and it should be ok after discovering the new domain controller
0
 
LVL 5

Expert Comment

by:Armenio
ID: 40393340
One gotcha I experienced with a demotion of server 2003 and was that the exchange did not see the new Global catalog server and I had to manually force the new Gc server.   One last thing before demotion I would turn off the old server a a day or so just to make sure that the domain is fully functional with out the old server.
0
Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

 
LVL 7

Author Comment

by:Senior IT System Engineer
ID: 40393352
Armenio,

So what was the solution to your problem before, in case Exchange Server does not see the new DC/GC ?
0
 
LVL 5

Expert Comment

by:Armenio
ID: 40393364
I just had to manually specify in exchange that I wanted to to use the new DC as its GC

these were the instructions I followed.


    Start the Microsoft Management Console (MMC) Exchange System Management (ESM) snap-in (Start, Programs, Microsoft Exchange, System Manager).
    In the treeview pane, navigate to Administrative Groups, &ltadministrative group name&gt, Servers.
    Right-click the server and select Properties.
    Select the Directory Access tab.
    From the Show drop-down list, select Global Catalog Servers.
    Clear the "Automatically discover servers" check box.
    Click Yes in the confirmation box.
    Click Add.
    Enter the name of the GC to use.
    Click OK.

Thanks to the below website.
http://windowsitpro.com/windows/q-how-can-i-specify-global-catalog-gc-i-want-my-microsoft-exchange-server-system-use
0
 
LVL 7

Author Comment

by:Senior IT System Engineer
ID: 40393368
Cool, because I assume that after the Exchange Server services restart, it should all picking up the DC/GC within the AD sites.
0
 
LVL 5

Expert Comment

by:Armenio
ID: 40393498
That is the Theory but in my case it dint. Its just a heads up in case you decommission the old server and exchange stops working. good luck
0
 
LVL 34

Assisted Solution

by:Seth Simmons
Seth Simmons earned 500 total points
ID: 40399520
the exchange topology service should automatically find this
the link armenio posted is for exchange 2003; this is 2010
if this were 2003 i would have suggested that because it is finicky about domain controllers just disappearing but that shouldn't be an issue here
0
 

Expert Comment

by:ranweb
ID: 41525262
I'm not providing a solution, more of an 'additional' comment(s) in reference to my process.  I'm just wrapping up a migration from 2003 AD to 2012 R2 AD.  Performed several test without incident and have proceeded to move forward with a live migration.  Everything has gone great.  I currently have no 2003 AD Domain controllers and I only have 2012R2 AD Domain controllers.  Users are authenticating, DC's are replicating and Exchange is working...

When I performed my testing, after removing my last 2003 server, I was able to change the forest functionality and domain functionality from 2003 to 2012R2 (The choices were 2008, 2008R2, 2012 and 2012R2).  

Now that I'm in live, when attempting to change the functionality level of both forest and domain, my choices are 2008 or 2008R2.  I currently have 2008 and 2008R2 server in production; however, none of them are Domain controllers.  All of the domain controllers are 2012R2.

Is there something I missed that is not allowing me to change to 2012R2?
1

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Learn to move / copy / export exchange contacts to iPhone without using any software. Also see the issues in configuration of exchange with iPhone to migrate contacts.
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

895 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now