Installing Exchange Server 2013 Pre-Requisites on Windows Server 2012 or Windows Server 2012 R2

Exchange Server 2013 can be installed on Windows Server 2012 and Windows Server 2012 R2, either Standard or Datacenter edition.

Windows Server 2012 will support any of the Exchange 2013 server roles. Unlike Windows Server 2008 R2, if you want to run Exchange Server 2013 Mailbox servers as members of a Database Availability Group you can still do so with the Standard edition of Windows Server 2012. Enterprise edition is not required for DAG members.

Note: Exchange Server 2013 Service Pack 1 added support for installing on Windows Server 2012 R2. For the purposes of this article any mention of Windows Server 2012 includes R2, and assumes that you will be installing Exchange Server 2013 SP1 or later.

As there are only two mandatory Exchange Server 2013 server roles there are only two combinations of pre-requisites required:

  • Mailbox servers, or combination Mailbox and Client Access servers
  • Client Access servers

Both of these server role installation scenarios are covered in this article.

For the third server role, Edge Transport, the pre-requisites are quite minimal. Find out more about installing Exchange 2013 Edge Transport here.

Installing Pre-Requisites for an Exchange Server 2013 Mailbox, or Mailbox and Client Access Server

For a Windows Server 2012 server that will host either the Exchange 2013 Mailbox server role, or both the Mailbox and Client Access server roles, the following PowerShell commands is used to install the required server roles and features.

Note: the Add-WindowsFeature command is quite lengthy and you will need to scroll across to be able to copy/paste all of it.

PS C:\> Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, 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

Success Restart Needed Exit Code      Feature Result
------- -------------- ---------      --------------
True    Yes            SuccessRest... {Application Server, HTTP Activation, .NET...
WARNING: You must restart this server to finish the installation process.

A restart is required after the roles and features have finished installing.

Next, install the following software in this order.

  1. Unified Communications Managed API 4.0 Runtime
  2. Microsoft Office 2010 Filter Pack 64 bit
  3. Microsoft Office 2010 Filter Pack SP1 64 bit

Installing Pre-Requisites for an Exchange Server 2013 Client Access Server

For a Windows Server 2012 server that will host only the Exchange 2013 Client Access server role, the following PowerShell command is used to install the required roles and features.

Note: the Add-WindowsFeature command is quite lengthy and you will need to scroll across to be able to copy/paste all of it.

PS C:\> Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, 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

Success Restart Needed Exit Code      Feature Result
------- -------------- ---------      --------------
True    Yes            SuccessRest... {Application Server, HTTP Activation, .NET...
WARNING: You must restart this server to finish the installation process.

A restart is required after the roles and features have finished installing.

Next, install the following software. This is the same requirement as the Mailbox server role just without the Office Filter Pack.

The server is now ready for the installation of Exchange Server 2013.

Comments

  1. says

    Paul, you mentioned that uninstall “Microsoft Visual C++ 11 Beta Redistributable(x64)”. I don’t see that but i am seeing “Microsoft Visual C++ 2012 Resdistributable(x64)”. Do I need to uninstall this? Please clarify.

    Thanks,
    Pallavi

  2. SAM says

    just want to install Exchange 2013 management tools on windows 2012 server but it always failed with following error ..
    do you have any solution for the same.. ?

    Error:
    The Exchange management tools are supported on servers running Windows Server 2012 and Windows Server 2008 R2 SP1 or later, and also on Windows 8 and Windows 7 client computers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersionForAdminTools.aspx

    Thanks in advanced
    Sam

  3. Mostafa sharaf says

    Sorry for error message we do not need to run exchangeserver before run setup exchange i think i did something wrong to have this error in setup

  4. Gary says

    Regarding “If you want to run Exchange Server 2013 Mailbox servers as members of a Database Availability Group you can still do so with the Standard edition of Windows Server 2012″

    Does this apply to Exchange Server 2010 also?

    I want to install Exchange 2010 on Windows Server 2012 Std.

  5. kanagaraj says

    Thank you Paul !! I referred from a book and tried the steps, it failed. This page is simple and to the point.

    You Rock !!

  6. Jim Sparks says

    Paul – I’ve relied on your posts for a very long time, thanks for all the great information over the years. Technet lists an additional two features for Mailbox and CAS roles on the same server; “RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell”. Appears the additional features are for clustering management,. Any reason I shouldn’t add these features? I’m not sure the omission was purposeful.

    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx

  7. Tony Holdgate says

    HI Paul,
    In your windows features script you install “Desktop Experience”. We are just wondering if this is essential and if so what it is needed for?
    Cheers
    Tony

  8. David says

    Paul,

    Your article gave me some good advice but your script left out installing Media Foundation. Just thought I’d mention that.

    Thanks again for the article.

    David

  9. Sandeep says

    Hi Paul,

    I installed the Exchange Server 2013 on top of Windows Server 2012 with both roles (Server & Client access role) on the same machine in my lab environment. The setup installed successfully but I am not able to login both on OWA-ECP as well as in Exchange Management Shell.

    The error I receive on Shell is:

    VERBOSE: Connecting to Server2012.FOETRON.local.
    New-PSSession : [server2012.foetron.local] Connecting to remote server server2012.foetron.local failed with the
    following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
    At line:1 char:1
    + New-PSSession -ConnectionURI “$connectionUri” -ConfigurationName Microsoft.Excha …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
    gTransportException
    + FullyQualifiedErrorId : AccessDenied,PSSessionOpenFailed

    ==========================================================================

    Does anybody have any idea what’s wrong?

    The user I am logged in as is a ‘member of’ Administrators, Schema Admins, Domain Admins, Organization Management, Compliance Managements etc.

  10. Jeya kuamr says

    hange Server Pro
    Chat Conversation Start
    a few seconds ago
    Hi Paul , I have installed exchange 2013 server for my client. one worst day i changed sonicwall firewall (im not sure about the reason) exchange 2013 mail flow suddenly stopped .. no incoming and outcoming..its like a silence of hell . i made somechanges in mail flow settings..now im clueless.. im going back to windows 2008 R2 and exchange 2010 sp3 . from windows 2012 R2 and exchn2013 sp1.
    can u suggest me somthing ..i have few days to confirm my plan to my manager ..

    Jeya kumar T
    jeyakumar@outlook.com

    • says

      If you made a change to the firewall and that broke mail flow then the immediate solution is to reverse that change.

      Exchange requires inbound and outbound TCP port 25 (SMTP) for mail flow. Exchange also needs to be able to resolve external domain names in DNS.

      So you should check the following to start with:
      - use the ExRCA.com tool to test inbound SMTP connectivity
      - from your Exchange server, use telnet to test outbound SMTP connectivity
      - from your Exchange server, use nslookup or resolve-dnsname (PowerShell) to test external domains can be resolved in DNS
      - when mail flow is not working check the queue (Get-Queue) and the stuck messages (Get-Queue | Get-Message) to see the last error which should indicate why they are stuck
      - check your event logs for any other Transport errors

      You will only be able to go back to Exchange 2010 if you already had Exchange 2010 servers in the organization in the past.

  11. Irakoze Clovis says

    Hello Paul,

    I have Exchange 2010 sp3 running on win server 2012 R2 sp1 standanrd. I would like to upgrade to exchange 2013 and I read that installation of exchange 2013 is coexistent with exchange 2010 already installed. But When I try to install exchange 2013 I keep getting this error :”Exchange server is in an inconsistent state. Only disaster recovery mode is available. Please use Setup /m:RecoverServer to recover this Exchange server.” But after closing set up the server is still running fine.

    • says

      If you’re trying to install Exchange 2013 onto the same server that Exchange 2010 is already on, that is not possible. Exchange 2013 needs to be installed on a new server. There is no in-place upgrade for Exchange.

      • Irakoze Clovis says

        Oh thanks.

        I had interpreted coexistence as two exchange versions on same sever but I guess you meant coexistence in the same organization i.e. using the same Active directory.

      • Irakoze Clovis says

        I had interpreted coexistence as two exchange versions on same sever but I guess you meant coexistence in the same organization i.e. using the same Active directory.

        Thanks a lot.

  12. ines says

    Lors de l’installation d’exchange server 2013 j’ai obtenu cette erreur
    Erreur :

    L’erreur suivante est survenue lors de l’exécution de “$error.Clear();

    $InternalOwaUrl = “https://” + $RoleFqdnOrName + “/owa”;

    new-OwaVirtualDirectory -Role ClientAccess -DomainController $RoleDomainController -InternalUrl $InternalOwaUrl;

    ” : “Une erreur est survenue lors de la création du répertoire virtuel IIS « IIS://Sifast.server.local/W3SVC/1/ROOT/owa » sur « SIFAST ».”.

  13. Aliyu Garba says

    Hello Sir. Apaul.

    Am having this issue during Exchange 2013 Installation.

    setup /PrepareAD /OrganizationName: FORTISMFB /IAcceptExchangeServerLicenseTerms

    Error:
    Installing product C:\Users\administrator.FORTISMFB\Downloads\SETUP\zh-hant\ClientLanguagePack.msi failed. Fatal error during installation. Error code is 1603. Last error reported by the MSI package is ‘Source file not found: C:\Users\administrator.FORTISMFB\Downloads\SETUP\zh-hant\Setup\ServerRoles\Common\zh-hant\Microsoft.Exchange.AirSync.Resources.dll. Verify that the file exists and that you can access it.’. It was running the command ‘Install-MsiPackage -PackagePath ‘C:\Users\administrator.FORTISMFB\Downloads\SETUP\zh-hant\ClientLanguagePack.msi’ -LogFile ‘C:\ExchangeSetupLogs\Install.zh-hant.Client.20140423-201533.msilog’ -Features ‘AdminTools’,’Mailbox’,’ClientAccess’,’Gateway’,’Bridgehead’,’UnifiedMessaging’,’ClientLanguagePack’ -PropertyValues ‘LOGVERBOSE=1 TARGETDIR=”C:\Program Files\Microsoft\Exchange Server\V15″”.

    Pleased Any help on this Issue.

  14. Vicki C says

    I have 2 servers, running 2012 R1 and Exchange 2013 cu3 in a DAG and they are working great. (In many ways thanks to the help I’ve received here!)

    My understand is that I can not upgrade to Server 2012 R2 with Exchange 2013 in place.

    Would it work if I was to remove the DAG, run the system using one server while I wipe and reload the second server with Windows Server R2 and then reload Exchange 2013 with SP1.

    Then I would restore the database to the new server and use it as our primary email server, while I do the same thing to the original server.

    Then the two updated servers could be re-set up as a Dag.

    Any thoughts on how practical this would be?

    We have a very small organization, under 200 mailboxes and not a huge amount of load. There would be some risk in running with only one server for a short period of time, but not too much.

    Thank you for your help,

    Vicki

  15. David says

    Hi Paul

    Re: your original advice above 2012, re:
    “Installing Pre-Requisites for an Exchange Server 2013 Client Access Server”- using PowerShell commands.
    Are these still required today if SP1 or CU 3 is on the server. Just noticed that is now 2 years ago?
    I’m reinstalling Exchange2013 on a Hyper-v 2012 R2 machine.
    Thanks

  16. Kirld says

    Hi Paul,

    I have tried installing Exchange 2013 in a 2012 Server. However, it will not go thru and encountered an error at its 97% of installation.i went thru exchange setup logs and this is what i got.

    It says
    Error details No Minimal Required Number of Suitable Directory Servers Found in Forest qualfoncenter.local Site Default-First-Site-Name and connected Sites..

    in fact.. when i do a query from the 2012 machine, it can see the GC,DC.. Please help…

    Thanks

Leave a Reply

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