Exchange 2010 "CAS/MBX/HUB" with Exchange 2013 as MBX only server

Posted on 2014-03-10
Last Modified: 2014-06-15

We have a windows 2008R2 server running exchange 2010 STD, its now getting to the point where we want to move most of the mailboxes onto a new separate MBX server, I have already built the new MBX only exchange 2013 server with server 2012R2, the problem is I cant find anyone else who has this configuration, as it stands we cannot see the MBX server in the exchange 2010 console, do I have to also install CAS as well on the exchange 2013 server and move everything over, any help appreciated.
Question by:mfg1
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
  • 5
  • 2
  • 2

Expert Comment

ID: 39919184
Have you installed Exchange 2013 SP1 on your Server 2012 R2?

Server 2012 R2 isn't supported unless your Exchange 2013 has SP1 installed.

To move mailboxes from Exchange 2010 to 2013, you should use the 2013 ECP/EMS to create the move requests. See instructions here:

Author Comment

ID: 39919215
How do I check, I only get very limited access in /ecp because I only have the MBX role installed on the exchange 2013 server.
Should my configuration above be possible? so exchange 2010 "cas,hub,mbx" then exchange 2013 as only "mbx"?

Author Comment

ID: 39919225
I also noticed that I apparently need this update? "Cumulative Update 2" or is that still only for RTM?
Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.


Expert Comment

ID: 39919247
Open up EMS on your Exchange 2013 server and issue:
Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersion

Open in new window

The build number needs to be equal to or higher than "15.00.0847.032". You don't need Cumulative Update 2, as it's included in SP1.

In your situation, I would also run the CAS role on your Exchange 2013 server. Exchange 2013 handles client access a little differently than Exchange 2010.

The only way to definitively test your desired configuration would be to try it and see. You can always move some smaller mailboxes to the Exchange 2013 MBX and roll back if it doesn't work.

Author Comment

ID: 39919256
ok I was running "15.00.0516.032" , I used this site to work out the answer about the CU2 update.

I am now downloading SP1, its 0:19 here now so will update you tomorrow on progress.
LVL 12

Expert Comment

by:David Paris Vicente
ID: 39919280
You also need the CAS role.
The CAS role is responsible for all access to the 2013.

Besides what N-W said you also need to confirm if the requirements are in place:

•Exchange 2010 SP3 on all Exchange 2010 servers in the organization, including Edge Transport servers.

•Exchange 2013 CU2 or later on all Exchange 2013 servers in the organization.

Author Comment

ID: 39922973
Hi, I am running SP3 on my exchange 2010 server, I have now built the exchange 2013 server with SP1 and can see everything like mailboxes and both servers listed and other things like accepted domains journal rules etc.

I have tested a move of 1 mailbox and that went through fine, as this is the first exchange setup I have done where there is more than 1 exchange server I am not sure if all of these settings so things like journal rules receive connectors etc are replicated? ideally I would like to eventually decommission the old exchange 2010 server, could anyone give me some pointers on this?
LVL 12

Accepted Solution

David Paris Vicente earned 500 total points
ID: 39923083
I believe that the Journal Rules will be replicated to your new server, because this rules are stored in AD.

For the connectors you will have to export them and import with powershell.

Something like this:
$SourceServer = "SRV-Mail"
$DestinationServer = "SRV-Mail01"
$SourceReceiveConnector = ForEach-Object {Get-ReceiveConnector -Server $SourceServer}
ForEach ($Connector in $SourceReceiveConnector)
New-ReceiveConnector -Name $Connector.Name -Server $DestinationServer -Bindings $Connector.Bindings -AuthMechanism $Connector.AuthMechanism -PermissionGroups $Connector.PermissionGroups -RemoteIPRanges $Connector.RemoteIPRanges

I didn´t have the oportunity to test the script, but let us know.

For decomission  2010 you just have to uninstall it in the normal way, but be carefull, you have to confirm that everything is on your new server in this case 2013, because after you uninstall 2010, you cant install anymore a 2010 on your infra-strucuture

Here is a good article for migration 2010 to 2013: Migration From Exchange 2010 to Exchange 2013


Author Comment

ID: 40135737
thanks in the end I had to just create another exchange 2010 server as XP doesn't seem to connect with any outlook client to exchange 2013 properly.

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

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

Suggested Solutions

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
Utilizing an array to gracefully append to a list of EmailAddresses
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

735 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