Exchange 2010 SP1 OS requirements

Posted: December 15, 2010 in Exchange
Tags: , , , ,

In order to Install Exchange 2010 SP1 on Windows Server 2008 R2 we have to install The following hotfixes and also the required OS roles and features as described below.

The following hotfixes are required for the Client Access server for Windows Server 2008 R2:

Install the update described in Knowledge Base article 979099, An update is available to remove the application manifest expiry feature from AD RMS clients. Without this update, the AD RMS features may stop working.

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

Install the hotfix described in Knowledge Base article 982867, WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1. For more information, see these MSDN Code Gallery pages:
For additional background information, see KB982867 – WCF: Enable WebHeader settings on the RST/SCT.
For the available downloads, see KB982867 – WCF: Enable WebHeader settings on the RST/SCT.

====================================================
Install the update described in Knowledge Base article 979744, A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application.

==================================================
Install the update described in Knowledge Base article 983440, An ASP.NET 2.0 hotfix rollup package is available for Windows 7 and for Windows Server 2008 R2. For more information, see these MSDN Code Gallery pages:
For additional background information, see KB983440 – Win7 rollup package (PR for QFE 810219).
For the available downloads, see KB983440 – Win7 rollup package (PR for QFE 810219).

===================================================
Install the update described in Knowledge Base article 977020, FIX: An application that is based on the Microsoft .NET Framework 2.0 Service Pack 2 and that invokes a Web service call asynchronously throws an exception on a computer that is running Windows 7.

=====================================================
=====================================================
Then we have to install the required OS roles and features by using the below PowerShell commands,

On the Start menu, navigate to All Programs > Accessories > Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command.

==============================
Import-Module ServerManager
==============================

Use the Add-WindowsFeature cmdlet to install the necessary operating system components:

This example is for a server that will have the typical installation of the Client Access, Hub Transport, and Mailbox server roles.
==============================
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
==============================

This example is for a server that will host the Client Access, Hub Transport, Mailbox, and Unified Messaging server roles.
==============================
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy,Desktop-Experience -Restart
==============================

This example is for a server that will host the Client Access and Hub Transport server roles.
==============================
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
==============================

This example is for a server that will host the Hub Transport and Mailbox server roles.
==============================
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server -Restart
==============================

This example is for a server that will host the Client Access and Mailbox server roles.
==============================
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
==============================

This example is for a server that will host only the Client Access server role.
==============================
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy -Restart
==============================

This example is for a server that will host the Hub Transport or the Mailbox server role.
==============================
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server -Restart
==============================

This example is for a server that will host only the Unified Messaging server role.
==============================
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Desktop-Experience -Restart
==============================

This example is for a server that will host the Edge Transport server role.
==============================
Add-WindowsFeature NET-Framework,RSAT-ADDS,ADLDS -Restart
==============================

On servers that will have the Client Access server role installed, after the system restarts, log on as an administrator, open an elevated Windows PowerShell console, and configure the Net.Tcp Port Sharing Service for automatic startup by running the following command.
==============================
Set-Service NetTcpPortSharing -StartupType Automatic
==============================

After installing the preceding prerequisites and before installing Exchange 2010, I recommend that you install any critical or recommended updates from Microsoft Update.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s