Deployment of an Exchange Server 2013 server goes through three main stages.
- Preparing Active Directory (if you are installing Exchange Server 2013 for the first time)
- Installing the Exchange Server 2013 pre-requisites on the server
- Running Exchange Server 2013 setup
Preparing Active Directory for Exchange Server 2013
When you are installing Exchange Server 2013 for the first time the Active Directory needs to be prepared.
There are a series of requirements for Active Directory preparation to be successful:
- Schema master running Windows Server 2003 with SP2, or a later version of Windows Server
- At least one Global catalog server per site that Exchange will be installed in that is running Windows Server 2003 SP2 or later
- At least one Domain controller per site that Exchange will be installed in that is running Windows Server 2008 or later
- Forest functional mode of Windows Server 2003 or higher
- An account with Schema Admins, Domain Admins, and Enterprise Admins permissions to run Exchange setup
Although Active Directory preparation can occur as part of the installation of the first Exchange Server 2013 server, you can also run the Active Directory preparation as a separate task beforehand on a 64-bit server running Windows Server 2008 or higher.
Because the Active Directory preparation requires the RSAT-ADDS tools I am running it on the domain controller in my test lab.
Alternatively, you can install the tools on a member server to run Exchange 2013 Active Directory preparation.
For Windows Server 2008 R2 (SP1 or later), in PowerShell run:
Import-Module ServerManager Add-WindowsFeature RSAT-ADDS
For Windows Server 2012, in PowerShell run:
Install-WindowsFeature RSAT-ADDS
If you are installing Exchange Server in the AD forest for the first time run the following Exchange 2013 setup command to prepare Active Directory:
setup /PrepareAD /OrganizationName: "your organization name" /IAcceptExchangeServerLicenseTerms
Note: if your organization name contains spaces then it must be enclosed in quotes as shown above.
If an Exchange organization already exists you can omit the /OrganizationName parameter.
setup /PrepareAD /IAcceptExchangeServerLicenseTerms
For other Active Directory preparation scenarios, such as multiple forests or multiple domains, refer to this article on TechNet.
Installing the Exchange Server 2013 Pre-Requisites
Exchange Server 2013 can be installed on either Windows Server 2008 R2 (SP1 or later) or Windows Server 2012. Depending on the server roles you are installing the pre-requisites vary.
- Installing Exchange Server 2013 Pre-Requisites on Windows Server 2008 R2
- Installing Exchange Server 2013 Pre-Requisites on Windows Server 2012
Installing Exchange Server 2013 Using the Setup Wizard
After installing the pre-requisites a restart of the server may be required. If you proceed without restarting then setup may be unable to proceed when it detects the pending restart.
From the location where you have stored your Exchange 2013 files run Setup.exe.
The first dialog gives you the opportunity to check for updates to the setup files before you proceed.
Check for updates to Exchange 2013 setup files
After the setup files have updated click Next to continue.
Click Next to continue past the Introduction message.
Exchange 2013 setup introduction
Accept the license agreement and click Next to continue.
Exchange 2013 license agreement
Choose whether or not to enable Error Reporting and click Next to continue.
Configure Exchange 2013 error reporting
After a check that all the pre-requisites are installed the setup wizard will move on to the next step automatically (if the check was successful).
Now we can choose the server roles to install. If this is the first server you’re installing Microsoft recommends you install the Mailbox server role first (this can be either a Mailbox-only server or a combined Mailbox/Client Access server).
Choose the Exchange 2013 server roles to install
Verify that you have enough disk space for the installation, or choose a path that does have enough disk space, and click Nextto continue.
Choose the location to install Exchange 2013
If there is no existing Exchange organization in Active Directory, and you haven’t already prepared Active Directory for Exchange, you will be prompted to enter an Exchange organization name.
When installing the Mailbox server role you are given the option to disable malware protection. If you disable it now you can enable it again later.
Configure anti-malware protection for the Mailbox server
Some readiness checks are performed. If this is the not the first server you’re installing and there is no Send Connector defined for outbound email then you may see a warning, but you can still proceed with the server installation.
Setup can’t detect a Send connector with an address space of ‘*’. Mail flow to the Internet may not work properly.
Exchange 2013 setup pre-requisite warning
When you are ready to proceed you can click Install to begin.
Begin the installation of Exchange 2013
The install is a fairly lengthy process, so you may want to go and do something else while you wait. When setup has finished click Finish.
Exchange 2013 setup is finished
About Paul Cunningham
Hi Paul, I am trying to get an instance of Exchange 2013 up and running on a single lab VM with MS SharePoint 2013 Preview. My principal aim is to explore the new Site Inbox functinality that SP2013 now offers. I understand that I need Exchange 2013 for this. My VM is running Server 2012 Preview, as well as SQL Server 2012 Preview and AD server 2012 Preview. I have the 200-something Contoso users set up both in AD and as SP2013 users. I know little to nothing about Exchange and am looking for resources, scripts or just plain instructions on how to set up a minimal Exchange configuration for this purpose. Any help would be greatly appreciated. Kind regards, Robert
I have tried to run the “setup /PrepareAD /OrganizationName: “your organization name” /IAcceptExchangeServerLicenseTerms” command in Windows Server 2012 Evaluation Datacenter machine and get the error “a setup term is not recognized…”. The command “Install-WindowsFeature RSAT-ADDS” has been executed corractly. Did I miss something? An Exchange Server downloaded file ha a name “Exchange-x64.exe” – “no setup.exe”, so what “setup” should I use, please? Thanks.
Sorry, I have got the setup file after exchange-x64 unzip, sorted out. I had to run it as “.\setup …” command.
Can you install exchange 2013 in a server 2012 domain controller
It is possible to install Exchange 2013 in a DC but it is not advisable in a production environment but rather in a test lab.
This TechNet document should enlighten you further:
http://technet.microsoft.com/en-us/library/ms.exch.setupreadiness.warninginstallexchangerolesondomaincontroller.aspx
Hi,
How to Configure Outllok e-mail account useing exchage 2013 useraccount..
Regards,
Prashant
And also you did’t get client array server option..when you installed exchage 2013..How did you configure new cas array on exchage 2013…?
Regards,
Prashant
Hi Paul,
You prerequisites are wrong. You do not require Windows Server 2008 DC/GC per site, according to Microsoft, Windows Server 2003 SP2 or later is required “http://technet.microsoft.com/en-us/library/bb691354.aspx#prereq”
Thanks!
David
i have a exchange 2007 sp3 RU10 with win 2k8 enterprise running in a production site, and i have a exchange 2013 with server 2k8R2 Enterprise , it is now coexistence, i would like to know how to move mailbox over from exchange 2007 to exchange 2013 ?
Hello Keith,
Please see: http://technet.microsoft.com/en-us/library/jj150543.aspx
Thanks,
David
Hi,
when I install Exchange 2013 in Window 2008 R2, I met an error as below:
—————–
Step 7 of 14: Mailbox role: transport service
The following error was generated when “$error.Clear();
if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
{
Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
}
” was run: “Database is mandatory on UserMailbox. Property Name: Database”.
—————–
Could you help me how to solve it, please ?
Thanks.
Hi Paul,
Good article. Encouraging in that you refer to Windows Server 2008 R2 SP2, which I had hoped to use for base OS for Exchange 2013. These pre-requisites are of course necessary to install the Exchange 2013 product on the selected base OS of either Windows server 2008 R2 Sp1 or Windows Server 2012 and mentioned in your article.
I am attempting to install Exchange 2013 in a lab environment consisting of Windows Server 2008 R2 SP1. (Two DC’s a CAS and a MB server).
When attempting to install the pre-requisite “Windows Management Framework 3.0″ on Windows Server 2008 R2 SP1 I get an error “This update is not applicable to your computer” which for this OS is Windows6.1-KB2506143-x64. This is required for both the CAS and MB server and introduces PS 3.0 to the OS.
After several attempts I have moved on, to install on Windows Server 2012 Standard edition as this has power shell 3.0 inbuilt.
However both you and MS claim that it is possible to install Windows Management Framework 3.0, to allow Exchange 2013 installed on 2008 R2 SP1.
Do you know why this fails?
As per MS TechNet article the following pre-requisites were installed.
http://technet.microsoft.com/en-us/library/bb691354.aspx
Any help appreciated.
WMF 3.0 requires .NET Framework 4.0 be installed first.
Hi,
i’m trying to setup an Exchange 2013 server but the prerequisites says, there’s an Exchange 2003 Server running in my domain. But i’m shure, there’s no one. Only an Exchange 2007.
Any hints what to do?
Thanks
Tom
Perhaps you have an Exchange 2003 server that was not properly uninstalled. You would possibly only see that by digging into ADSIEdit.
Thanks, this helps. There was really an old 2003 in the deeps of the AD. I’ve found some notes howto fix this and now it works.
Cheers
Tom