Prerequisites For Installing Exchange 2013 On Windows 2008 R2 SP1

What are the prerequisites for installing Exchange 2013 on a Windows 2008 R2 SP1 machine? It’s more than what is required for Windows 2012 for sure! Exchange 2013 has only two roles – Client Access Server (CAS) and Mailbox. The Hub transport functionality has been bundled into the CAS role. The UM functionality is taken…

What are the prerequisites for installing Exchange 2013 on a Windows 2008 R2 SP1 machine? It’s more than what is required for Windows 2012 for sure!

Exchange 2013 has only two roles – Client Access Server (CAS) and Mailbox. The Hub transport functionality has been bundled into the CAS role. The UM functionality is taken care by the Mailbox role. Both Mailbox and CAS roles can be installed on separate servers or on the same box.

Mailbox Role Only Or Combined Mailbox & CAS Role

This section describes what needs to be done if you are either installing just the Mailbox role or both Mailbox & CAS on the same server. Once the Windows 2008 R2 SP1 machine is joined to the domain, run the following from an elevated PowerShell window to install the required features for Exchange 2013.

Import-Module ServerManager
Add-WindowsFeature RSAT-ADDS
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 –Restart

Once the server is back online after the restart, install the following in the order specified.

  1. Microsoft .NET Framework 4.5 RC
  2. Windows Management Framework 3.0(Install Windows6.1-KB2506143-x64.msu)
  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)– Link to the hotfix will be emailed and needs to be downloaded.
  8. Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution) – It is possible that Windows update would have installed the update if the server is fully patched.

In the Exchange 2013 Preview build, the Microsoft Visual C++ 11 Beta Redistributable (x64) needs to be uninstalled after UCMA (8th one in the above list) is installed, but before installing Exchange. Go to control panel and uninstall Visual C++ 11 Beta Redistributable (x64) – 11.0.50531.

Uninstall Visual C   Beta for Exchange 2013 install

The last step to make the server ready for Exchange 2013 install is to register ASP.NET with .NET Framework 4.5 in Internet Information Services (IIS). Run the two commands from an elevated command prompt.

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

You can now run the Exchange 2013 setup for installing a combined role or Mailbox role alone.

Client Access Role Only

This section describes what needs to be done if you are either installing just the CAS role on the server. Once the Windows 2008 R2 SP1 machine is joined to the domain, run the following from an elevated PowerShell window to install the required features for Exchange 2013.

Import-Module ServerManager
Add-WindowsFeature RSAT-ADDS
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 –Restart

Once the server is back online after the restart, install the following in the order specified. The list is the same as for the Mailbox role, except that Office 2010 Filter pack is not required.

  1. Microsoft .NET Framework 4.5
  2. Windows Management Framework 3.0(Install Windows6.1-KB2506143-x64.msu)
  3. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit
  4. 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)– Link to the hotfix will be emailed and needs to be downloaded.
  6. Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution) -– It is possible that Windows update would have installed the update if the server is fully patched.

In the Exchange 2013 Preview build, the Microsoft Visual C++ 11 Beta Redistributable (x64) needs to be uninstalled after UCMA (8th one in the above list) is installed, but before installing Exchange. Go to control panel and uninstall Visual C++ 11 Beta Redistributable (x64) – 11.0.50531.

Uninstall Visual C   Beta for Exchange 2013 install

The last step to make the server ready for Exchange 2013 install is to register ASP.NET with .NET Framework 4.5 in Internet Information Services (IIS). Run the two commands from an elevated command prompt.

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

You can now run the Exchange 2013 setup for installing the CAS role.

Leave a Reply

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