Exchange 2010 Prerequisites

Article
06/29/2011

Applies to: Exchange Server 2010

This topic provides steps for installing the necessary Windows Server 2008 Service Pack 2 (SP2) or later or Windows Server 2008 R2 operating system prerequisites for all Microsoft Exchange Server 2010 server roles. It also includes the steps for installing the Windows Vista and Windows 7 operating system prerequisites for the Exchange Management Tools.

Prerequisites

Make sure that the functional level of your forest is at least Windows Server 2003, and that the Schema Master is running Windows Server 2003 with Service Pack 1 or later. For more information about the Windows functional level, see Managing Domains and Forests.
The full installation option of Windows Server 2008 with Service Pack 2 or later or Windows Server 2008 R2 must be used for all servers running Exchange 2010 server roles or management tools.
For all server roles other than the Edge Transport server role, you must first join the computer to the appropriate internal Active Directory forest and domain.

Note

If you're installing the Mailbox server role and you intend the server to be a member of a database availability group (DAG), you must be running the Enterprise Edition of Windows Server 2008 or Windows Server 2008 R2. The Standard Edition doesn't support the features needed for DAGs. You can't upgrade Windows when Exchange is installed on the server.

What Do You Want to Do?

Install the Windows Server 2008 operating system prerequisites
Install the Windows Server 2008 R2 operating system prerequisites
Install the Windows Vista operating system prerequisites for the Exchange management tools
Install the Windows 7 operating system prerequisites for the Exchange management tools

Install the Windows Server 2008 SP2 operating system prerequisites

Install Microsoft .NET Framework 3.5 Service Pack 1 (SP1). For details, see Microsoft .NET Framework 3.5 SP1.
Install the Microsoft .NET Framework 3.5 Family Update for Windows Vista x64, and Windows Server 2008 x64 updates. For details, see Microsoft .NET Framework 3.5 Family Update for Windows Vista x64, and Windows Server 2008 x64. See also Microsoft Knowledge Base article 959209, An update for the .NET Framework 3.5 Service Pack 1 is available.
Install Windows Remote Management (WinRM) 2.0 and Windows PowerShell V2 (Windows6.0-KB968930.msu). For details, see Install Windows Management Framework.
On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For details, see 2007 Office System Converter: Microsoft Filter Pack.
Open an elevated command prompt, navigate to the Scripts folder on the Exchange 2010 installation media and use one of the following commands to install the necessary operating system components:
1. For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox role:
```
sc config NetTcpPortSharing start= auto
ServerManagerCmd -ip Exchange-Typical.xml -Restart
```
2. For a server that will host the Client Access, Hub Transport, Mailbox, and Unified Messaging server roles:
```
sc config NetTcpPortSharing start= auto
ServerManagerCmd -i Desktop-Experience
ServerManagerCmd -ip Exchange-Typical.xml -Restart
```
3. For a server that will host the Client Access and Hub Transport server roles:
```
sc config NetTcpPortSharing start= auto
ServerManagerCmd -ip Exchange-Typical.xml -Restart
```
4. For a server that will host the Hub Transport and Mailbox server roles:
```
ServerManagerCmd -ip Exchange-Typical.xml -Restart
```
5. For a server that will host the Client Access and Mailbox server roles:
```
sc config NetTcpPortSharing start= auto
ServerManagerCmd -ip Exchange-Typical.xml -Restart
```
6. For a server that will host only the Client Access role:
```
sc config NetTcpPortSharing start= auto
ServerManagerCmd -ip Exchange-CAS.xml -Restart
```
7. For a server that will host only the Hub Transport role:
```
ServerManagerCmd -ip Exchange-Hub.xml -Restart
```
8. For a server that will host only the Mailbox role:
```
ServerManagerCmd -ip Exchange-MBX.xml -Restart
```
9. For a server that will host only the Unified Messaging role:
```
ServerManagerCmd -ip Exchange-UM.xml -Restart
```
10. For a server that will host the Edge Transport role:
```
ServerManagerCmd -ip Exchange-Edge.xml -Restart
```

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

Install the Windows Server 2008 R2 operating system prerequisites

On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For details, see 2007 Office System Converter: Microsoft Filter Pack.
On the Start Menu, navigate to All Programs, then Accessories, then 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:

For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox 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

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

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

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

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

For a server that will host only the Client Access 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

For a server that will host the Hub Transport or the Mailbox 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

For a server that will host only the Unified Messaging 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

For a server that will host the Edge Transport role:

Add-WindowsFeature NET-Framework,RSAT-ADDS,ADLDS -Restart

On servers that will have the Client Access Server role installed, after the system has restarted, 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
```