Category Archives: Exchange Installation

Steps to move arbitration mailbox in Exchange 2013

In this article we will be looking at how to move arbitration mailbox from exchange 2010 to Exchange 2013

The arbitration mailbox is used to store the original message that’s awaiting approval. By default, one arbitration mailbox is created for moderated transport during setup. It’s used for all moderated recipients. You can add additional arbitration mailboxes for load balancing purposes. If you’re using multiple arbitration mailboxes, you need to specify which mailbox to use for each moderated recipient

The main reason being why we are moving the arbitration mailbox is because after post migration it will not allow us to decommission the legacy exchange 2010/2007 server unless we move these system mailboxes to Exchange 2013.

 Run the below command to check the arbitration mailbox name.


Now use EAC to move these system mailboxes to Exchange 2013.

Open EAC – Click on recipients and click on Migration Tab.


Now click on add  and select the option move to a different database



Now click on add and select the system mailboxes of legacy servers to be migrated to Exchange 2013




Now we need to select the target database and click ok.Click on next and finally we are done with moving the arbitration mailbox to Exchange 2013.


Click on next and proceed with the instruction and the arbitration mailbox will be moved successfully.

Steps to install Exchange 2013 in Exchange 2010 environment

In this article we will be looking at the steps to install Exchange 2013 in Exchange 2010 environment.

Following Prerequisite checks needs to be confirmed before installation
1) Ensure that you do not have any exchange 2003 servers running in the environment. If so you have to decommission them.
2) Ensure if there is any Exchange 2007 in the environment make sure they have the atleast Exchange 2007 SP3 RU10
3)IF you have Exchange 2010 running in the environment just ensure that they have atlease Exchange 2010 SP3
4) Auto discover DNS records Configure the Auto discover public DNS records for your existing SMTP domains to point to an on-premises Exchange 2013 Client Access server
5) Certificates Install and assign Exchange services to a valid digital certificate else users might face problem in accessing emails via active sync
6) Ensure the administrator who is going to perform the installation has member of the Schema Admins group and the Enterprise Admins group
7) AD Forest Level- Active Directory must be atleast Windows Server 2003 forest functionality mode or higher.
8) You can use IPV6 in Exchange 2013.If you plan to use IPV6 ensure that you have both IPV4 and IPV6 enabled.
9) DC and GC Versions – Below only versions of DC’s and GC’s should be present
Windows Server 2003 Enterprise Edition with SP2 or later (32-bit or 64-bit)
Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or later (32-bit or 64-bit)
Windows server 2008 RTM or Later (applicable for both standard and enterprise)
Windows server 2012 RTM or Later (applicable for both standard and enterprise)
10) Outlook 2003 is not supported in Exchange 2013 environment. Ensure that all the clients have atleast Outlook 2007 SP3 installed.

Install the below feature for CAS & MBX role combination
Open windows power shell and run the below command
Run Import-module servermanager
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Install the Following softwares

Microsoft .NET Framework 4.5
Windows Management Framework 3.0
Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
Microsoft Office 2010 Filter Pack 64 bit
Microsoft Office 2010 Filter Pack SP1 64 bit
Microsoft Knowledge Base article KB974405 (Windows Identity Foundation)
Knowledge Base article KB2619234
Knowledge Base article KB2533623

You need to install the remote tools administration pack.Run the below command in powershell
Add-WindowsFeature RSAT-ADDS

Uninstall Microsoft Visual C++ 11 Beta Redistributable (x64)

After installing the following prerequisite on the server that we are going to install exchange 2013 we need to join that server into the domain.

In our case we are installing Exchange 2013 in Windows 2008R2


Open elevated command prompt and navigate to the setup where we have the exchange server setup and run the below command


It goes through the prerequisite analysis as shown below


Next it goes through the active directory schema and completes the schema extension completely as shown below


Once schema is completed open the setup and it shows the below screen


Setup starts copying files as shown below


Once the copy is complete it starts initializing the setup as shown below


Then it brings into the introduction screen as shown below.Click next and accept the license agreement


Then it takes to the recommended settings as shown below


Click on next and it takes to the server role selection


Click on next and choose the installation location


Click on next and it takes to the malware protection settings. Choose the required setup and click on next


Setup goes through 1 to 15 steps and usually takes less than a hour


Once the setup completes it shows the below screen as shown below


After a reboot is completed we are done with the exchange 2013 server setup.
Open Exchange Management Shell and ensure that Exchange 2013 is installed in the domain by running the below command


Then try opening EAC by typing https:\\www.exchange2013casfqdn\eac
Admin account should have permission to open EAC and it should be a member of domain admin,enterprise admin and schema admin else we will not be able to open EAC

Inorder to acheive this task we can either move admin account mailbox from exchange 2010 to exchange 2013 or we can create an admin account in 2013 and grant appropriate permissions
In our case we will move the admin account from ex2010 to ex2013
Run the below command to move admin mailbox from exchange 2010 to 2013

Before that you can run get-mailbox database to identify the mailbox DB name in Exchange 2013 and then run the below command with the exchange 2013 database as the target database


Once the move request is completed you can try logging into EAC in Exchange 2013 and you will be able to login without any issues.

Moving mailboxes in Exchange 2013

In Exchange 2013 the mailbox move have been improved. It has lot of additional features added in like it gives us the results of the status of move, synched, moved and failed.

The below article will help us in performing mailbox move in Exchange 2013 through EAC.

Open EAC select recipients and click on the migration tab


Click on the + sign and select the option move mailbox to a different database. This option can  be selected while we move any mailbox from Exchange 2007,2010 to Exchange 2013.

The second option move to this forest can be performed while performing a cross forest migration.


Now we can select the mailboxes that we need to migrate.


Also we have an option in which we can upload the CSV file which contains the users list.


Here we can specify the Migration batch name. We have 3 options where it gives us options to move the primary mailbox and the archive or only the primary according to the requirement.

This is one of the best features which make the admins to migrate both the mailbox and the archive mailbox all at one go.

We need to specify the target database of the mailbox and the archive if specified.


We have an option where the mail can be triggered to admins once the batch is completed.Also we have 2 options like automatically starting the batch and manually starting them as well.


This will be the final output of the result which shows the batch status. Here it gives lot of info which will be very useful while performing the migration.






%d bloggers like this: