[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 380
  • Last Modified:

Exchange Server 2013 upgrade steps from Exchange Server 2007

Hi Folks,

Can anyone please suggest me what is the steps to do to make sure that the side-by-side installation of the Exchange Server 2013 is working seamlessly with my current Exchange Server 2007 ?

I will be installing it on top of Vmware with Windows Server 2012 R2.
My Windows AD forest level is still on 2003
Senior IT System Engineer
Senior IT System Engineer
5 Solutions
Vijaya Babu SekarAssociate Ops ManagerCommented:
As per my understanding. best to follow up with microsoft deployment assistance


and refer the below below blogs. Step by step process


Senior IT System EngineerIT ProfessionalAuthor Commented:
Cool, thanks guys, so in this case I should wait until next year probably ... :-/
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Seth SimmonsSr. Systems AdministratorCommented:
I don't know what you have for licensing, but if you have 2012 available to you, then it will work fine there.  Only R2 it's not possible yet.  I personally haven't seen anything about an Exchange update that will work with R2.
Senior IT System EngineerIT ProfessionalAuthor Commented:
Do I have to delete the old Exchange Server 2003 to 2007 replication log connector first before upgrading to / migrating to 2013 ?
Seth SimmonsSr. Systems AdministratorCommented:
NetoMeter ScreencastsCommented:
If you are not pressed on time, it is a good idea to wait for Exchange 2013 CU3 (or SP1). Most probably, it will:

1. Add support for Windows 2012R2 OS
2. Fix a lot of bugs and client issues

The most confusing part is probably figuring out and setting the internal and external namespaces (eight of them) which are:
- Outlook Anywhere
- Autodiscover (only internal - SCP)
- Offline Address Book (OAB)
- ActiveSync
- WebServices
- PowerShell

A couple of additional advices:
- You don't (and you can't) move the OAB from Exchange 2007 to Exchange 2013. You will find misleading instructions and advices to do so in many articles or posts. The OAB management and administration is different in Exchange 2013 due to architecture changes - the mailbox server hosting the Organization Mailbox will generate all OAB’s.
- Transport rules are not migrated automatically from Exchange 2007 to 2013. You will have to export/import them manually in EMS.
- First you move the mailboxes, then the Public Folders.
- Even if you have a small number of mailboxes, it is a good idea to plan for co-existence. It is nice to have the upgrade completed successfully within a weekend, but if you hit a problem, you can roll back and troubleshoot easily.
Senior IT System EngineerIT ProfessionalAuthor Commented:
Public Folders ?

So in this case can I still migrate the existing Public folder or it is not recommended anymore ?
Seth SimmonsSr. Systems AdministratorCommented:
you can migrate public folders from 2007 to 2013

Migrate Public Folders to Exchange 2013 From Previous Versions
Senior IT System EngineerIT ProfessionalAuthor Commented:
Cool, so I guess the only caveats here are as follows:

1. make sure that there is no Exchange Server 2003 attributes or remnants in the AD
2. in Windows Server 2012, manually create the Cluster Network Object (CNO) and provision the CNO by assigning permissions to it.
3. configure CAS role first (new-clientaccessarray) and then followed by the Mailbox server role.

Do I need to create replication connector as before between the 2007 MBX and 2013 CAS role ?

Featured Post

Free Backup Tool for VMware and Hyper-V

Restore full virtual machine or individual guest files from 19 common file systems directly from the backup file. Schedule VM backups with PowerShell scripts. Set desired time, lean back and let the script to notify you via email upon completion.  

Tackle projects and never again get stuck behind a technical roadblock.
Join Now