Solved

Exchange 2007 SP3 to Exchange 2013 migration

Posted on 2013-12-16
9
1,374 Views
Last Modified: 2014-01-01
I am in the process of upgrading our exchange to 2013.

I am following these 2 documents which are sligthly different. Neither one is working for me.

1. http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx

2. http://msexchangeguru.com/2013/04/29/install-e2013/

I got to the point where I have to do ADPREP

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms /OrganizationName:”NAME”

and its telling me
Exchange organization name cannot be specified. There already exists an Exchange

 organization with name 'NAME'.

I am confused at this point. This is a coexistance upgrade not a new install.
Do I even need to run ADPREP since my AD already contains the Exchange 2007 name?

I ran the prepareschema just before and that was COMPLETED fine.

Does anyone have a better step by step document for Exchange 2007 to Exchange 2013 migration
How do I get past this step?

Thank you
0
Comment
Question by:baysysadmin
  • 8
9 Comments
 

Author Comment

by:baysysadmin
ID: 39722725
I figured it out.
Looks like the steps above included 2013 new setup.
Since mine was upgrade i just had to exclude the /OrganizationName:”NAME”
part and run only

setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
0
 

Author Comment

by:baysysadmin
ID: 39722765
I was able to confirm all settings are correct except ONE.
Its missing, even after replicating and refreshing ad.


ObjectVersion attribute value of the Organization container should be 15449

msExchProductId attribute value of the Organization Container should be 15.00.0516.032

ObjectVersion attribute value of the “Microsoft Exchange System Objects” OU in the root domain should be 13236

A New group called “Exchange Install Domain Servers” is created under the MESO OU (read previous line).

Check  if the “Microsoft Exchange Security Groups” OU is created in the root domain and it contains the default RBAC Security Groups:
0
 
LVL 34

Expert Comment

by:Seth Simmons
ID: 39724174
what is missing?  msExchProductId?
0
 

Author Comment

by:baysysadmin
ID: 39724272
Yes the whole ID and its value. I succesfully finished installing exchange 2013 but it did not appear.

I am looking on the Sites and Services>Services>Microsoft Exchange>NAME properties...atributes tab but its not there.
0
What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

 

Author Comment

by:baysysadmin
ID: 39724434
I used ADSI Edit CONFIGURATION and found the msExchProductId there.

Interesting thing now is that In exchange 2013 I can also see the 2007 server and 2013 database but I cant see the 2007 database.

The instructions im following say they are for both 2007 and 2010 but I think they lean more towards 2010 which is not exactly the same.
In 2007 they were not called databases but rather information stores and they appear in a different container under ADSI
See attached.

I looked around and found another document which was better explained.
http://blogs.technet.com/b/justin_gao/archive/2013/04/15/upgrading-from-exchange-2007-amp-2010-to-2013.aspx
Only 2010 and 2013 databases will show but when you go to move a user then 2007 will show also.
exge-database.png
0
 

Author Comment

by:baysysadmin
ID: 39725000
So far it has been ok until
STEP 3.Exchange 2013 name space & virtual directories configurations
On this document.

http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx

When I execute the scripts in Ex2013 shell on my sv-bayexge-01 server it returns a error.

The operation couldn't be performed because object 'e15-01\OWA (Default Web Site)' couldn't be found on
'SV-BAYDC-01..
    + CategoryInfo          : NotSpecified: (:) [Set-OwaVirtualDirectory], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : 5263D259,Microsoft.Exchange.Management.SystemConfigurationTasks.SetOwaVirtualDirectory
    + PSComputerName        : sv-bayexge-01.

Why is it trying to execute on the domain controller when I am connected to exchange local shell.


So I went ahead and did the certificate and successfully migrated a mailbox but I am not able to send from mailbox on 2013 to mailbox on 2007 or vice versa.
I configured the send and recieve connectors to match ex2007.

Also I keep getting a security popup on the Client outlook, with the sv-bayexge-01 name INSTEAD of exchange.domain.com name which is what the certificate says.
And some of the other users with outlook 2013 which have not been migrated yet got that warning but they are alteast still working and sending/receiving emails ok.
0
 

Author Comment

by:baysysadmin
ID: 39727265
Is there anyone who can help with exchange?

I am at a point where I can telnet from ex2013 to ex2007 and succesfully send a email.
AND VICE VERSA.
But when I send it using outlook from one user to another the emails just get queued with no error message attached and never get delivered.

Users can send to local users on same exchange server but not on the other ex server.

I followed this document to fix the send connectors but its not working
http://social.technet.microsoft.com/Forums/exchange/en-US/e7bed849-5cc4-4876-bff4-53a2fd1334f8/cannot-send-mail-from-exchange-2013-to-exchange-2007?forum=exchangesvrdeploy

i updated ex2013 to CU2 but no help.

We do have barracuda spam filter but its in another site, these 2 exchange servers are in the same domain and subnet so I am assuming email should pass directly between them?

We have 2 MX records with priorty 10 and 20.
10 is mail... which goes to barracuda.
20 is exchange... which goes directly to exchange. (this name is used on all services on exhange, except autodiscover.)

Let me explain at which point in migration I am.

I have successfully install ex2013 and setup all the certificate and connectors.
I have NOT made any dns changes yet. exchange.domain.com still points to ex2007.
To test client access I change the HOSTS file to point exchange.domain.com to ex2013 and it connected fine.
I also moved 1 mailbox ex2007 >>>ex2013
And created a new mailbox directly on ex2013
All was well except sending of emails between exchange users and also sending out to public from ex2013. ( ex2013 server replied '550 5.7.1 Unable to relay')
Sending from ex2007 OUT works fine.

I see this in the ex2013 logs
Established connection to 172.8.0.150
2013-12-18T17:43:35.550Z,08D0CA23DE480628,SMTP,site:default-first-site; version:8,-,Messages: 0 Bytes: 0 (Retry : Cannot achieve Exchange Server authentication)
I tried this KB but it didnt help.

http://support.microsoft.com/kb/979175/en-us

So i decided to delete the connectors I made using sugesstions above, and now email goes from ex2007 to ex2013 but NOT the other way around.
0
 

Accepted Solution

by:
baysysadmin earned 0 total points
ID: 39727621
Finally got it working.
I created the receive connectors on both sides using exchange authentication and each others specific IPs
and also made a send connector on ex2013 to point to smart host of ex2007.

I HAD to restart the transport service on both exchange in order for the changes to take affect.
It took a few minutes for the queue to flush and emails to come in.
0
 

Author Closing Comment

by:baysysadmin
ID: 39749626
Resolved my own issues.
0

Featured Post

VMware Disaster Recovery and Data Protection

In this expert guide, you’ll learn about the components of a Modern Data Center. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Question has a verified solution.

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

Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…

867 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

16 Experts available now in Live!

Get 1:1 Help Now