Page 1
Page 1
Started By
Message

Exchange/Active Directory/Migration/Upgration

Posted on 1/26/15 at 9:08 am
Posted by BigSquirrel
Member since Jul 2013
1880 posts
Posted on 1/26/15 at 9:08 am
Need a little input here on what docs to read through next, or any input you guys have.

A client I'm working for needs to upgrade their AD and Exchange servers and software. They currently are running a Server 2003 physical server, which is also running their Exchange 2007. They need to be migrated to Server 2012 VMs (VMware), with separate VMs for AD and Exchange 2012.

One 2012 AD VM server is already built, and will do everything correctly according to DCDiag.exe, except the Advertising test, which from what I've read will always fail to see the 2012 server because the 2003 server would need it's domain functionality moved to 2008. So I believe it will do what it needs to do once the 2003 domain controller is demoted.

My question is this, I've never demoted a DC which is also running Exchange (which will have to run another week or so while the new mail server is built and Exchange 2012 is configured). Is that going to affect Exchange 2007 in any way? (more worried about the domain functional level moving from 2003 to 2012, and how THAT affects it) Are there any pitfalls I should watch for, or am I alone in this issue?
This post was edited on 1/26/15 at 9:10 am
Posted by brgirl09
Member since Jul 2009
423 posts
Posted on 1/27/15 at 10:48 am to
Why do you want to demote the DC before exchange is moved?

This is the minimum requirements for Exchange 2013 (I'm guessing that's what you meant as there is no 2012 version of exchange)

LINK

It lists the DC level can be 2003.

I'd move exchange make sure it works first then demote.
This post was edited on 1/27/15 at 10:50 am
Posted by Vood
Enjoying a Forty with Lando
Member since Dec 2007
8332 posts
Posted on 1/27/15 at 11:13 am to
This can be real simple.

Exchange
Bring the 2013 Exchange mailbox server up into the exchange environment. I think you also need a CAS server to run authentication and routing to the mailbox server. I am not 100% sure if you need the CAS but I would not bring Exchange 2013 up without it.

Once the mailbox server is up, move all Databases or mailboxes from the 2003 exchange server to the new 2013 server. You choose what route you want to take. Moving Mailboxes has much less downtime.

Once all the mailboxes are up and people are using it for about a week, remove the 2003 exchange server from the environment. This does not mean just shut it down. You have to remove it with some commands. Just google removing an exchange server from an exchange environment.

Once the exchange server is removed you can now remove AD


AD

Move the 5 FSMO rules to the new 2012 AD server
Let it run for a few days
DCPROMO the existing 2003 AD server
Raise your domain level to 2012 R2


You are done. It's much simpler than it sounds. Just be sure you test for serveral days before you completely remove each component.



This post was edited on 1/27/15 at 11:16 am
Posted by BigSquirrel
Member since Jul 2013
1880 posts
Posted on 1/28/15 at 7:47 am to
Vood, thanks for that. I'll try making the new Exchange Server first, I've actually done more Exchange 2012 spinups than AD work. You're 100% right about the CAS server, it has to be installed with 2012 unless you're just a glutton for punishment.

Posted by StraightCashHomey21
Aberdeen,NC
Member since Jul 2009
125394 posts
Posted on 1/28/15 at 8:11 am to
quote:

Exchange/Active Directory


ooo i hate that shite
first pageprev pagePage 1 of 1Next pagelast page
refresh

Back to top
logoFollow TigerDroppings for LSU Football News
Follow us on Twitter, Facebook and Instagram to get the latest updates on LSU Football and Recruiting.

FacebookTwitterInstagram