Improve company productivity with a Business Account.Sign Up

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

Exchange 2013 P2P

Hi Experts, need to migrate a physical Exchange 2013 with all roles installed to another physical Exchange 2013 server. OS will be changing to 2012R2 on new server. What is the process to do this? I have reviewed http://exchangeserverpro.com/performing-like-like-exchange-server-migration/ this article. Is there any other information that would be useful

There are no plans to virtualize or to restore from backups so we are looking at alternate solutions

TIA
0
abhijitm00
Asked:
abhijitm00
1 Solution
 
MAS (MVE)Technical Department HeadCommented:
2
 
abhijitm00Author Commented:
Thanks MAS
0
 
abhijitm00Author Commented:
Will addition of new 2013 Server cause any autodiscover issues?
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
MAS (MVE)Technical Department HeadCommented:
Install the server certificate immediately after the new server installed.
When 1st CAS server is unreachable it will search the netx avaialble CAS server.
If you are ready with certificate you are safe.
http://exchangeserverpro.com/exchange-2013-ssl-certificate-export-import/
0
 
AkhaterCommented:
at first yes it might, that's why you should directly change the autodicsoveruri on the new one to match the one on the old one

once you do that you will not have any issues with autodiscover and you can finish your installation quietly
1
 
MAS (MVE)Technical Department HeadCommented:
Check this to configure autodiscover. I missed this  in my above post. Thanks Akhater for pointing this missed point.
https://www.experts-exchange.com/articles/13676/Out-Of-office-not-working.html
1
 
abhijitm00Author Commented:
Thanks I will review and update
0
 
abhijitm00Author Commented:
Guys, the certificate on the old server is a different name than the new server i.e. mail.domain.com versus exchange.domain.com. We would still like to use same OWA, can we reuse this certificate if names don't match?
0
 
MAS (MVE)Technical Department HeadCommented:
You have to set the same URLs on both servers
Please check this to set the URLs
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
Internal FQDN can be anything.internaldomain.com.
You can export and import the certifcate from old server to the new server.
http://exchangeserverpro.com/exchange-2013-ssl-certificate-export-import/
0
 
abhijitm00Author Commented:
Hi MAS, I have changed all services URLs on new server to match those of the old server. I have also exported and imported the cert to the new server but I am still getting an error with certificate when pulling from the new server. Do I need to regenerate? The cert does not contain name of new server and only contains name of old server in SAN
0
 
abhijitm00Author Commented:
I am getting error message in Outlook. On clicking OK Outlook then connects to old Exchange server "There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site exchange.domain.com". Outlook is unable to connect to the proxy server (Error Code 10)
0
 
MAS (MVE)Technical Department HeadCommented:
Hi,
Can you post the URLs configured?
Can you post the result of this command?
Get-ExchangeCertificate | fl subject,CertificateDomains,issuer

Open in new window

0
 
Veerappan SundaramSenior Technical ConsultantCommented:
Did you check this MS KB? -  https://support.microsoft.com/en-in/kb/923575
0
 
abhijitm00Author Commented:
Answered question correctly
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

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