Solved

Exchange migration gone wrong...

Posted on 2013-10-27
3
266 Views
Last Modified: 2014-01-22
We are replacing an old exchange server (2007 SP2) with 2010 SP3 in preparation to cut over to 2013 within a year.

I moved roles over to the new server, and think I configured settings to match the old one correctly. I also renewed the SSL certificate to accept the new computer name of the new server.

I replaced the old server on the send connector to the new one. Outlook Web Access is up and operational, and I see mail going through the mailboxes. However, the clients cannot seem to connect to the exchange server on their outlook EXTERNALLY, or RPC over HTTP.

I went to my outside RPC URL https://mail.servername.com/rpc, and an authentication box came up... but I still cannot connect.
0
Comment
Question by:joe_edmond
  • 2
3 Comments
 
LVL 11

Accepted Solution

by:
NetoMeter Screencasts earned 500 total points
Comment Utility
Hi Joe,

Here is simplified plan for this migration.

I guess you are at item 5 - changing remote client access settings:
5. Change remote client access settings
5.6 Disable Outlook Anywhere in Exchange 2007
5.7 Configure ActiveSync URL in Exchange 2007
5.8 Configure legacy namespace in external OWA URL - Exchange 2007 EMC
5.9 Configure legacy namespace in OAB distribution external URL - Exchange 2007 EMC
5.10 Configure legacy namespace in Web Services external URL - Exchange 2007 EMS

#Replace E-2k7 with the name of your Exchange 2007 server
#Check current external URL

Get-WebServicesVirtualDirectory -Server E-2k7 | select ExternalUrl

#Set external URL - replace E-2k7 with the name of your Exchange 2007 server
#Replace legacy.netometer.com with actual legacy namespace

Set-WebServicesVirtualDirectory -Id E-2k7\* -ExternalUrl https://legacy.netometer.com/EWS/Exchange.asmx

#Confirm the change with Get-WebServicesVirtualDirectory

Double-check your external URL configuration.
0
 

Author Comment

by:joe_edmond
Comment Utility
That has worked, thank you very much. BUT now I notice that my Public Folders are not replicating correctly. A Majority of the folders are, but not all of them. And there is next to no content in the new public folder database.

I notice that there is a queue from the original server that has publicfolder things in it and it says retry.
0
 
LVL 11

Expert Comment

by:NetoMeter Screencasts
Comment Utility
I am glad you were able to fix the clients connectivity issue.

Public Folders replication is one of the most delicate parts of the transitioning process. I suggest that you post this as a new question.

Best Regards,

Dean
0

Featured Post

Wish Marketing would stop bothering you?

Is your marketing department constantly asking for new email signature updates? Are they requesting a different design for every department? Do they need yet another banner added? Don’t let it get you down! There is an easy way to manage all of these requests...

Join & Write a Comment

Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
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…
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

762 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

10 Experts available now in Live!

Get 1:1 Help Now