Solved

Exch 2007 to Exch 2013 Migration

Posted on 2013-12-17
5
483 Views
Last Modified: 2015-01-08
My Firm is in the process of Migrating to Exchange 2013.  

Among the several questions I have  I will start with the simplest that I have.

I have a 2007 Exchange Environment in place, 2 HUB/CAS all Traffic goes to NLB NIC on CAS Servers.

I have 2x 2013 Cas Server also with an NLB nic and for now one MBX/HUB Server, no users have been migrated yet so everyone is still in the 2007 Exch Environment.

Digi Cert is in,  Autodiscover,OWA have been configured to match whats on the 2007 CAS Servers.  

I just needed to know what needs to be done to the 2013 CAS servers so once I route all mail to the NLB NIC it routes properly From 2013 CAS > 2007 CAS/HUB > 2007 MBX.

This is where I am getting stuck.
0
Comment
Question by:jgutierr76
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 37

Accepted Solution

by:
Mahesh earned 500 total points
ID: 39725917
The first step in configurations of certificate. By default Exchange 2013 is installed with self-signed certificate, You need to replace this certificate with appropriate public ssl cert to include the correct SAN names (legacy is required pointing to Exchange 2007 CAS so that same certificate can be used on Exchange 2007)
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx

Then you need to Move Client Access from Exchange 2007 to Exchange 2013.
On Exchange 2007 CAS server, you need to run no of shell commands for OWA, OAB, ActiveSync and so on
Check below step by step
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx

Mahesh
0
 

Author Comment

by:jgutierr76
ID: 39727552
Digi Cert is done minus the legacy name which I will do today.
Thank you for the how to.

In the Diag on part 1 there was a smtp proxy is that the 2013 cas?
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 39728400
No, it is not Exchange 2013

It is TMG acting as reverse proxy

Its not related to your scenario.

All you need to do, all send receive operations (mail Flow) need to be done through Exchange 2013 server

Mahesh
0
 

Author Comment

by:jgutierr76
ID: 39730419
Understood thank you very much for the info Very Helpful!!
0
 
LVL 5

Expert Comment

by:CoSmismgr
ID: 40538419
0

Featured Post

Free eBook: Backup on AWS

Everything you need to know about backup and disaster recovery with AWS, for FREE!

Question has a verified solution.

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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
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…
This video discusses moving either the default database or any database to a new volume.

751 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