Solved

Install second Exchange 2010 on the network to perform migration

Posted on 2012-03-21
6
474 Views
Last Modified: 2012-05-14
We are taking over a network that has Exchange 2010 that we don't trust (it may have problems) and need to install another Exchange 2010 to perform migration and then retire the old one. Is there a guide I could follow to make sure I do it right? Any other suggestions I should follow?

Thank you
0
Comment
Question by:piotrmikula108
[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
  • 3
6 Comments
 
LVL 74

Accepted Solution

by:
Glen Knight earned 500 total points
ID: 37789294
Step 1. Install second Exchange Server with all roles (CAS, HT, Mailbox)
Step 2. Set the RPCClientAccess Attribute for the existing databases to the new server.  See here for further details: http://technet.microsoft.com/en-us/library/bb123971.aspx
Step 3. Update rules for OWA, ActiveSync and SMTP on firewall to come to new server instead of old one
Step 4. move all mailboxes.  Including Arbitration and Arxive mailbox.  Use the command Get-Mailbox -database database-name -arbitration and the same command with -archive to view them
Step 5. If using, move public folder replicas to new server
Step 6. Uninstall Exchange from old server
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 37789302
Oops! Step 1.5 Install SSL Certificate on new server which has correct names relative to the new server.
0
 
LVL 1

Author Comment

by:piotrmikula108
ID: 37791087
Thx

Do I need any transport rules between the two servers while they coexist?
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 37791135
Nope! As long as you don't mess around with the default receive connectors on either server then the boxes will transfer email between each other accordingly. (You need to ensure Exchange Server permissions and authentication are enabled at the very minimum, otherwise the boxes can't authenticate with each other and mail will back up in the queues).

-Matt
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 37791220
No, as Matt said, you don't need Send Connectors between the servers.

However, a common problem is that the Receive Connector called DEFAULT SERVERNAME has had the FQDN changed.  This needs to be the internal fully qualified domain name of the server it's hosted on.

Also, on the new server the anonymous user permission needs to be enabled otherwise you won't be able to receive any email.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
exchange, squid, proxy, linux 6 43
exchange 2007 1 16
Exchange 2016 Size restrictions. 13 46
FTP servers in Windows 2008 3 58
Find out what you should include to make the best professional email signature for your organization.
In-place Upgrading Dirsync to Azure AD Connect
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
how to add IIS SMTP to handle application/Scanner relays into office 365.

726 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