Installing Exchange Server 2013 Pre-Requisites on Windows Server 2008 R2

This article is based on the Exchange 2013 Preview release and is subject to change when Exchange 2013 reaches RTM. Do not attempt to install Exchange 2013 Preview in a production environment.

Exchange Server 2013 can be installed on Windows Server 2008 R2 SP1, on either the Standard or Enterprise editions. Exchange 2013 can also be installed on Datacenter (RTM) edition.

Windows Server 2008 R2 Standard edition will support any of the Exchange 2013 server roles, however if you intend to deploy Exchange 2013 Mailbox servers in a Database Availability Group you will need to run the Enterprise edition (for the required Failover Clustering components).

In addition, the Windows Server 2008 R2 installation must be a Full installation. Server Core installation is not supported.

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

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

Both scenarios are covered in this article.

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

For an Exchange 2013 server that will host either the Mailbox server role, or both the Mailbox and Client Access server roles, the following PowerShell commands are 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:\> Import-Module ServerManager

PS C:\> Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, 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-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True    Yes            Succes... {Ink Support, .NET Framework 3.5.1, Config...

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

Next, install the following software in this precise order.

  1. Microsoft .NET Framework 4.5 RC (I recommend downloading the standalone redistributable installer)
  2. Windows Management Framework 3.0 (requires restart)
  3. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
  4. Microsoft Office 2010 Filter Pack 64 bit
  5. Microsoft Office 2010 Filter Pack SP1 64 bit
  6. Microsoft Knowledge Base article KB974405 (Windows Identity Foundation)
  7. Knowledge Base article KB2619234 (Enable the Association Cookie/GUID that is used by RPC over HTTP to also be used at the RPC layer in Windows 7 and in Windows Server 2008 R2) (restart required)
  8. Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution) (restart required)

These updates add up to around 350mb of files. One of the hotfixes even requires you to submit your email address to be emailed the download link. I recommend you download all the updates once and keep them stored on your network for use in subsequent Exchange 2013 Preview installs.

For the Mailbox server role the Task Scheduler service must also be enabled and running.

Continue to the end of this article for the final steps required.

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

For an Exchange 2013 server that will host only the Client Access server role, the following PowerShell commands are 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:\> Import-Module ServerManager

PS C:\> Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, 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-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI

Success Restart Needed Exit Code Feature Result
------- -------------- --------- --------------
True    Yes            Succes... {Ink Support, .NET Framework 3.5.1, Config...

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

Next, install the following software in this precise order (you may notice these are the same as the Mailbox server role, except for the Office Filter Pack not being required).

  1. Microsoft .NET Framework 4.5 RC (I recommend downloading the standalone redistributable installer)
  2. Windows Management Framework 3.0 (requires restart)
  3. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
  4. Microsoft Knowledge Base article KB974405 (Windows Identity Foundation)
  5. Knowledge Base article KB2619234 (Enable the Association Cookie/GUID that is used by RPC over HTTP to also be used at the RPC layer in Windows 7 and in Windows Server 2008 R2) (restart required)
  6. Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution) (restart required)

These updates add up to around 350mb of files. One of the hotfixes even requires you to submit your email address to be emailed the download link. I recommend you download all the updates once and keep them stored on your network for use in subsequent Exchange 2013 Preview installs.

Additional Required Steps for Any Exchange Server 2013 Server Roles

After installing the above software components, but before installing Exchange 2013, remove the Microsoft Visual C++ Beta Redistributable via the Control Panel.

This must be uninstalled before attempting to install Exchange Server 2013 Preview.

Open a command prompt and run the following commands (note that IISreset will reset any active connections to the server).

C:\> %SystemDrive%\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir -enable

C:\> IISReset

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

About Paul Cunningham

Paul is a Microsoft Exchange Server MVP and publisher of Exchange Server Pro. He also holds several Microsoft certifications including for Exchange Server 2007, 2010 and 2013. Connect with Paul on Twitter and Google+.

Comments

  1. Hi Paul

    Great article. however i/m stuck at trying to install exchange 2013. my original install failed, managed to uninstall it and now when try to double click on setup.exe the only thing to shows is a little window that says
    Welcome to Microsoft Exchange
    File c:\program files\microsft\exchange server\v15\bin\exsetupui.exe does not exist!

    what gives?

  2. Hi Paul,

    Your article are very good for understanding the exchange server. As per your guideline, I have try to install exchange server 2013 on VM’s. Client access server role is installed successfully, but the mailbox role getting error while installing.

    The following error was generated when “$error.Clear();
    if ($RoleProductPlatform -eq “amd64″)
    {
    $useAttachMode = $false;
    $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath “Search\Ceres\Installer”;
    $command = Join-Path -Path $fastInstallConfigPath -ChildPath “InstallConfig.ps1″;
    $fastDefaultDataFolderPath = Join-Path -Path $RoleBinPath -ChildPath “Search\Ceres\HostController\Data”;
    $dataFolderPath = $fastDefaultDataFolderPath;

    if ([System.IO.Directory]::Exists($fastDefaultDataFolderPath))
    {
    $useAttachMode = $true;
    }
    else
    {
    if ($RoleIsDatacenter -eq $true)
    {
    $preferredDataFolderPathRoot = “D:\”;
    if ([System.IO.Directory]::Exists($preferredDataFolderPathRoot))

    • Trying to install to C: or D: drive? I’m curious about that $preferredDataFolderPathRoot = “D:\”; in your output.

      If you’re truly stuck try the TechNet forum for the Exchange 2013 preview. At this early stage I haven’t encountered all the install bugs cropping up for people.

      http://social.technet.microsoft.com/Forums/en-us/exchangeserverpreview/threads

      • Hi, Paul

        My Lab setup is as follows.
        Total 3 Servers
        1. DC
        2. Client Access Role
        3. Mailbox Server Role

        Client access role is installed successfully, but when i try to install mailbox server role it is getting above mention error. Installation path is C Drive.

        2nd Lab setup.
        1. DC
        2. Client Access Role and Mailbox Role

        Both roles are installed successfully in this lab setup and mail send/received working fine.

  3. Mostafa sharaf says:

    before run exchange setup we need to run exchangeserver.exe because if not run when the exchange check the prerequest it is not continue and have error message you are not on admin groups ,… and other groups

  4. Hi Paul,

    I’ve 2 PCs with role as:
    PC1: Active directory
    PC2: Exchange 2013

    1. Could I install Exchange 2013 in this topology ? And assume that could you tell me that whether I can install Exchange 2013+Active directory in same PC, please ?

    2. If I can install Exchange 2013 in this topology, so In PC, which things will I need to install before deploy Exchange 2013 into PC2?

    Thanks,
    cuocdoi

  5. cuocdoi says:

    Hi Paul,

    I cannot excite the commandline:

    =======
    %SystemDrive%\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -ir -enable
    =======

    Window Power Shell displays error.

    Could you help me , please?

  6. Hi Paul,

    Why do you need to uinstall C++ Beta Redistributable via the Control Panel.?

    What happen if you don’t?

    Cheers Leo

  7. Fareedullah says:

    Hello Paul,

    Do you have Exchange 2013 server videos uploaded somewhere?

    Cheers,

  8. Paul! Love your work! Many, many admins owe you a big thank you for all you’ve done for us over the years! I just wanted to update the post here, “Add-WindowsFeature” has been replaced! Instead, use Install-WindowsFeature.

    http://technet.microsoft.com/en-us/library/ee662309.aspx

    Thanks again!

Leave a Comment

*

We are an Authorized DigiCert™ SSL Partner.