How to install Exchange 2013 (SP1) on Windows Server 2012 R2

Windows Server 2012 R2 and Exchange 2013 SP1

Exchange 2013  SP1 was released in February this year providing support for Windows Server 2012 R2. In this blog we’ll run through the installation process.

The demo environment I am using includes a Windows Server 2012 R2 domain controller and a Server 2012 R2 member server.

In the demo environment no previous versions of Exchange have been installed so as part of the installation the Exchange 2013 SP1 we will upgrade the AD Schema, even if you are running Exchange 2013, the installation of SP1 requires a Schema update. Note in this scenario we are going to jump straight to installing Exchange 2013 SP1, without installing Exchange 2013 first.

Finally before we start, always test in a demo environment before deploying in Production!

I hope this walk through helps.

Carl,
OxfordSBSGuy

1. On your 2012 R2 member server, download Exchange 2013 SP1, see here for the latest version here. Note: check for the latest cumulative Update and install directly from that to save you patching the install of SP1 once complete, currently the latest is CU11 released on 15/12/2015.

2. Once downloaded extract the files by running the Exchange 2013-x64-SP1 executable. In my environment I have extracted them to C:\Sw\Exchange2013SP1.

3. On a Server 2012 R2 member server, run PowerShell as Administrator.

PowerShell Run as Administrator

4. Run the following command to install the Active Directory Remote Administration Tool (Source: Exchange 2013 Prerequisites)

Install-WindowsFeature RSAT-ADDS

Install-WindowsFeature RSAT-ADDS

5. In the same PowerShell Window run the following command to prepare the server for the Mailbox or CAS server roles (Source: Exchange 2013 Prerequisites):

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-WindowsFeature for Exchanfe Mailbox and CAS Roles

6. Reboot the server to complete the installation of the Windows Features.

7. Download and install Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit (Source: Exchange 2013 Prerequisites).

Microsoft Unified Communications Managed API 4.0 RuntimeMicrosoft Unified Communications Managed API 4.0 Runtime 1Microsoft Unified Communications Managed API 4.0 Runtime 2Microsoft Unified Communications Managed API 4.0 Runtime 3Microsoft Unified Communications Managed API 4.0 Runtime 4

8. On the 2012 R2 member server, run Cmd as Administrator.

Run CMD as Administrator

9. Now let’s prepare the domain for Exchange 2013 SP1. Go to the location where you extracted Exchange 2013 SP1 installation files (C:\Sw\Exch2013SP1).

First run setup.exe /help to list the help options available to you.

Exchange 2013 SP1 Setup help

As this is the first Exchange Server in our environment we need to prepare the topology so next run setup.exe /help:preparetopology.

Exchange 2013 SP1 setup help preparetopology

The three commands we are interested in are the /PrepareSchema, /PrepareAD, /PrepareDomain, but as this is a new installation we’ll also need to use the /OrganizationName switch

10. So let’s run the first command:

Setup.exe /PrepareSchema

iacceptexchangeserverlicenseterms warning messageYou’ll see without adding the additional switch /IAcceptExchangeServerLicenseTerms we get a warning and the installation goes no further.

So let’s run the first command in full:

Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

setup prepareschema iacceptexchangeserverlicenseterms 1setup prepareschema iacceptexchangeserverlicenseterms 2setup prepareschema iacceptexchangeserverlicenseterms 3

11. Now we run Setup /PrepareAD with the /OrganizationName paramter as this is a new Exchange installation:

Setup.exe /PrepareAD /OrganizationName:OxfordSBSGuy /IAcceptExchangeServerLicenseTerms

exchange 2013 sp1 setup preparead organizationname oxfordsbsguy iacceptexchangeserverlicenseterms 1exchange 2013 sp1 setup preparead organizationname oxfordsbsguy iacceptexchangeserverlicenseterms 2exchange 2013 sp1 setup preparead organizationname oxfordsbsguy iacceptexchangeserverlicenseterms 3

12. Finally the last command we run is to prepare the domain, note in a multi domain environment there is the option to use /PrepareAllDomains:

Setup.exe /PrepareDomain /IAcceptExchangeServerLicenseTerms

exchange 2013 sp1 setup preparedomain iacceptexchangeserverlicenseterms 1exchange 2013 sp1 setup preparedomain iacceptexchangeserverlicenseterms 2

13. Now type Setup.exe and hit return. Click Next to check for updates.

Exchange 2013 Setup - Check for Updates14. Click Next.

Exchange 2013 Setup - No updates found

Exchange 2013 Setup - Copying Files

Exchange 2013 Setup - Initializing Setup15. Read the Introduction and click Next.

Exchange 2013 Setup - Introduction16. Accept the license agreement and click Next.

Exchange 2013 Setup - License Agreement17. User recommended settings, click Next.

Exchange 2013 Setup - Recommended Settings18. Select the server roles you require, for my test lab I am selecting Mailbox and  the Client Access roles, click Next.

Exchange 2013 Setup - Server Role Selection19. Choose a location to install, click Next.

Exchange 2013 Setup - Installation Space and Location20. Choose Malware settings and click Next.

Exchange 2013 Setup - Malware Protection Settings21. Once the readiness check has completed click Install.

Exchange 2013 Setup - Readiness Checks

Exchange 2013 Setup - Setu Progress

22. Tick the box to Launch the Exchange Administration Center, and click Finish. Exchange 2013 Setup - Setup CompleteYou have successfully installed Exchange 2013.

Now Exchange 2013 has been installed check out the multi-part series on Exchange 2013 Initial Configuration Settings.

Source Material:

  1. Technet Exchange 2013 Prerequisites
  2. Technet Exchange 2013 System Requirements
  3. Released: Exchange Server 2013 Service Pack 1
  4. Technet Prepare Active Directory and Domains
  5. The Exchange Guy – Preparing Active Directory and Schema for Exchange 2013 Release Preview

Related Posts:

1. How to install Exchange 2016 (CU3 and beyond) on Windows Server 2016

2. Exchange 2013 Initial Configuration Settings multi-part series

3. Exchange Server and Update Rollups Build Numbers

4. Exchange PowerShell: How to list all SMTP email addresses in Exchange

5. Exchange PowerShell: How to enumerate Distribution Lists, managers and members

If you found this post useful, please share!

    Related Posts

    13 thoughts on “How to install Exchange 2013 (SP1) on Windows Server 2012 R2

    1. gazmend

      i have problem with Exchange Server 2013,i want to install Exchange 2013 to Windows Server 2012R2.

      Extending Active Directory schema FAILED

      C:\Sw>setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

      Welcome to Microsoft Exchange Server 2013 Service Pack 1 Unattended Setup Copying Files… File copy complete. Setup will now collect additional information needed for installation.

      Performing Microsoft Exchange Server Prerequisite Check

      Prerequisite Analysis COMPLETED
      Configuring Microsoft Exchange Server

      Extending Active Directory schema FAILED
      The following error was generated when “$error.Clear();
      install-ExchangeSchema -LdapFileName ($roleInstallPath + “Setup\Data\”+$
      RoleSchemaPrefix + “schema0.ldf”)

      ” was run: “There was an error while running ‘ldifde.exe’ to import the schema f ile ‘C:\Windows\Temp\ExchangeSetup\Setup\Data\PostWindows2003_schema0.ldf’. The error code is: 8224. More details can be found in the error file: ‘C:\Users\Admi nistrator\AppData\Local\Temp\1\ldif.err'”.

      The Exchange Server setup operation didn’t complete. More details can be found in ExchangeSetup.log located in the :\ExchangeSetupLogs folder.

      info from file:ldif.err

      Entry DN: CN=ms-Exch-Access-Control-Map,CN=Schema,CN=Configuration,DC=woodgrove,DC=local Add error on entry starting on line 1: Operations Error The server side error is: 0x21a2 The FSMO role ownership could not be verified because its directory partition has not replicated successfully with at least one replication partner. The extended server error is: 000021A2: SvcErr: DSID-030A0B6B, problem 5012 (DIR_ERROR), data 8610

      An error has occurred in the program

      i hope someone can help me for this. thnaks

      Reply
      1. OxfordSBSguy.com Post author

        Hi Gazmend, I’ve seen this error before and the problem is with AD replication. The the error states the directory partition hasn’t succesfully replicated yet between all your domain controllers. Once it replicates the CU should install. Try the command repadmin /showrepl on your domain controllers to see which is causing the issue.
        Cheers,
        Carl
        OxfordSBSGuy.com

        Reply
    2. gazmend

      please i have this error message when installing exchange 2013 on windows server 2012 R2 on the step 10 of 14 Mailbox

      the following error was generated when $error.clear()

      start-Setupservice-ServiceName MSExchangeSubmission

      “was run: “Service ‘ MSExchangeSubssimin ‘ failed to reach status Running on this server “

      Reply
    3. Carlos Uriel Aragon Mancera

      Please Help! i got this error
      Error:
      The following error was generated when “$error.Clear();
      Install-ExchangeCertificate -WebSiteName “Exchange Back End” -services “IIS, POP, IMAP” -DomainController $RoleDomainController -InstallInTrustedRootCAIfSelfSigned $true
      if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
      {
      Install-AuthCertificate -DomainController $RoleDomainController
      }
      ” was run: “Could not grant Network Service access to the certificate with thumbprint 97135443C077948DC77F26715C89DA445A6834C9 because a cryptographic exception was thrown.”.

      Reply
    4. Richard Goberdhansingh

      Good day I am getting the following error when trying to install exchange server 2013 SP1 on Server 2012 R2 Essential.
      I have followed your steps and got everything right just this error when the actual install runs

      An unsupported operating system was detected. Exchange Server 2013 Client Access, Mailbox, and Edge Transport server roles support Windows Server 2008 R2 SP1 or later and Windows Server 2012

      Thanks in advance to your response

      Reply
      1. OxfordSBSguy.com Post author

        Hi Richard, 2012 R2 Essential is not a supported operating system, 2012 R2 is but the two are different. Installing Exchange on a DC isn’t supported which I why i suspect you are seeing the error message.

        Reply
    5. johan

      ok, am already stuck at step 10

      Configuring Prerequisites COMPLETED
      Prerequisite Analysis FAILED
      The Client Access server role is already installed on this computer.
      For more information, visit: http://technet.microsoft.com/library(EXCH
      )/ms.exch.setupreadiness.CafeRoleAlreadyExists.aspx

      The Exchange Server setup operation didn’t complete. More details can be fo
      in ExchangeSetup.log located in the :\ExchangeSetupLogs folder

      when checking the exchangesetup logfile, i notice several errors, like:

      [01/02/2017 11:41:13.0723] [1] Failed [Rule:CafeRoleAlreadyExists] [Message:The Client Access server role is already installed on this computer.]

      and

      [01/02/2017 11:41:13.0723] [1] Failed [Rule:CafeRoleAlreadyExists] [Message:The Client Access server role is already installed on this computer.]

      but i dont know how to proceed now

      Reply
    6. Fernan

      Hi Oxford Guy!

      I ‘ve done a successful migration from a SBS2003 AD to Windows 2012R2 , then I setup another member server, replicate AD, and begin with installation
      i’ve got following message

      Performing Microsoft Exchange Server Prerequisite Check

      Prerequisite Analysis FAILED
      Cannot find the Recipient Update Service responsible for domain ‘DC=ARGENBULKDC
      ,DC=local’. New and existing users may not be properly Exchange-enabled.
      For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms
      .exch.setupreadiness.RusMissing.aspx

      One or more servers in the existing organization are running Exchange 2000
      Server or Exchange Server 2003. Installation can’t proceed until all Exchange 20
      00 or Exchange 2003 servers are removed.
      For more information, visit: http://technet.microsoft.com/library(EXCHG.150
      )/ms.exch.setupreadiness.Exchange2000or2003PresentInOrg.aspx

      This computer requires .NET Framework 4.6.2 (https://support.microsoft.com/
      kb/3151802).
      For more information, visit: http://technet.microsoft.com/library(EXCHG.150
      )/ms.exch.setupreadiness.MinimumFrameworkNotInstalled.aspx

      How can i remove old Exchange 2003? I’ve already demoted SBS 2003 (dcpromo) and power off the virtual server
      Any suggestion??
      Thanks !
      All tested in a Hyperv Lab.

      Reply
      1. OxfordSBSguy.com Post author

        Hi Fernan, you can’t upgrade directly from Exchange 2003 to 2013 you have to “double hop” and upgrade to Exchange 2010 first and then onto 2013/2016. From where you are at the moment I think you’ll need to either power on the SBS2003 server to uninstall exchange so it removes itself fro AD or so you can install Exchange 2010 and uppgrade to that first, or spend some time in ADSI edit and remove references to it manually. Good luck!
        Carl

        Reply
        1. Fernan

          hi Carl, thanks for the answer, in case i do first. Should i migrate to 2010 over W2008R2 OS, or 2012r2 is fine too (i’ve read exchange 2010 wont support 2012r2)?
          At the moment no AD is in SBS2003 as i demote it.
          thanks!

          Reply
            1. Fernan

              hi Oxfguy!
              I’ve succesfully migrated sbs2003 to exchange 2010 over w2010R2, (test environment) (only local server, no mx records), but now i got a problem with POP. Outlook is not downloading all messages through POP , connection is ok, authentication is ok too,
              I’ve tried send a message from another account and sent is ok, message will be displayed in Owa and if i connect to outlook directly to exchange that’s ok too, but Outlook wont download it using POP.
              What could it be happening??
              thanks!

    Leave a Reply

    Your email address will not be published. Required fields are marked *