[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 278
  • Last Modified:

Exchange migration gone wrong...

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
joe_edmond
Asked:
joe_edmond
  • 2
1 Solution
 
NetoMeter ScreencastsCommented:
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
 
joe_edmondAuthor Commented:
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
 
NetoMeter ScreencastsCommented:
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

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

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