• 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 (SP1) or later. For more information about the Windows functional level, see Managing Domains and Forests.
  
• The full installation option of Windows Server 2008 with SP2 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.

Note:
If you're installing the Mailbox server role, the Task Scheduler must be enabled and running. In addition, if the Mailbox server will be a member of a DAG and host replicated databases, it’s required that the script is scheduled and run automatically. For more information about the script, see “CheckDatabaseRedundancy.ps1 Script” in the Monitoring High Availability and Site Resilience topic.

The following hotfixes are required for Windows Server 2008 SP2:

• Install the update described in Microsoft Knowledge Base article 977624, AD RMS clients do not authenticate federated identity providers in Windows Server 2008 or in Windows Vista. Without this update, Active Directory Rights Management Services (AD RMS) features may stop working.
  
• 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 979917, Two issues occur when you deploy an ASP.NET 2.0-based application on a server that is running IIS 7.0 or IIS 7.5 in Integrated mode. For more information, see these MSDN Code Gallery pages:
  
  • For additional background information, see KB979917 - QFE for Sharepoint issues - Perf Counter fix & User Impersonation.
    
  • For the available downloads, see KB979917 - QFE for Sharepoint issues - Perf Counter fix & User Impersonation.
    
• Install the update described in Knowledge Base article 973136, FIX: ArgumentNullException exception error message when a .NET Framework 2.0 SP2-based application tries to process a response with zero-length content to an asynchronous ASP.NET Web service request: "Value cannot be null".
  
• Install the update described in Knowledge Base article 977592, RPC over HTTP clients cannot connect to the Windows Server 2008 RPC over HTTP servers that have RPC load balancing enabled.
  

Warning:
The following hotfixes only apply to Windows Server 2008 R2 RTM. If you’re installing Exchange on Windows Server 2008 R2 SP1, you don’t need to apply these hotfixes.

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

• 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 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.
  

The following hotfix is required for Hub Transport and Mailbox servers 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.
  

The following hotfix is strongly recommended for Mailbox servers running Windows Server 2008 R2 that are members of a database availability group (DAG):

• Install the update described in Knowledge Base article 2550886, A transient communication failure causes a Windows Server 2008 R2 failover cluster to stop working. Without this update, the underlying cluster for a DAG could experience a race condition that causes a loss of quorum in the cluster and a loss of functionality in the DAG.
  

The following hotfixes are required for Windows 7 and Windows Vista:

• 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.
  
• 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).
    

1. Install Microsoft .NET Framework 3.5 Service Pack 1 (SP1). For details, see Microsoft .NET Framework 3.5 Service Pack 1.
   
2. 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 and Knowledge Base article 959209, An update for the .NET Framework 3.5 Service Pack 1 is available.
   
3. Install Windows Remote Management (WinRM) 2.0 and Windows PowerShell V2 (Windows6.0-KB968930.msu). For details, see Knowledge Base article 968930, Windows Management Framework Core package (Windows PowerShell 2.0 and WinRM 2.0).
   
4. On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For Exchange 2010 release to manufacturing (RTM), see 2007 Office System Converter: Microsoft Filter Pack. For Exchange 2010 SP1, see Microsoft Office 2010 Filter Packs. For more information about registering the Filter Pack, see Register Filter Pack IFilters with Exchange 2010.
   

   Note:
   On Exchange 2010 RTM, you can meet the prerequisite by installing 2007 Office System Converter: Microsoft Filter Pack. However, we recommend that you upgrade to the Microsoft Office 2010 Filter Packs.

5. Open an elevated command prompt, navigate to the \Scripts folder on the Exchange 2010 installation media, and then use one of the following commands 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.
     
     sc config NetTcpPortSharing start= auto
     ServerManagerCmd -ip Exchange-Typical.xml -Restart

   • This example is 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

   • This example is 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

   • This example is for a server that will host the Hub Transport and Mailbox server roles.
     
     ServerManagerCmd -ip Exchange-Typical.xml -Restart

   • This example is for a server that will host the Client Access and Mailbox server roles.
     
     sc config NetTcpPortSharing start= auto
     ServerManagerCmd -ip Exchange-Typical.xml -Restart

   • This example is for a server that will host only the Client Access server role.
     
     sc config NetTcpPortSharing start= auto
     ServerManagerCmd -ip Exchange-CAS.xml -Restart

   • This example is for a server that will host only the Hub Transport server role.
     
     ServerManagerCmd -ip Exchange-Hub.xml -Restart

   • This example is for a server that will host only the Mailbox server role.
     
     ServerManagerCmd -ip Exchange-MBX.xml -Restart

   • This example is for a server that will host only the Unified Messaging server role.
     
     ServerManagerCmd -ip Exchange-UM.xml -Restart

   • This example is for a server that will host the Edge Transport server role.
     
     ServerManagerCmd -ip Exchange-Edge.xml -Restart

 Install the Exchange 2010 SP1 Hotfixes for Windows Server 2008 SP2

The following hotfix is required for Windows Server 2008 SP2 and must be installed after the operating system prerequisites have been installed:

• 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.
    

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

1. On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For Exchange 2010 RTM, see 2007 Office System Converter: Microsoft Filter Pack. For Exchange 2010 SP1, see Microsoft Office 2010 Filter Packs. For more information about registering the Filter Pack, see Register Filter Pack IFilters with Exchange 2010.
   

   Note:
   On Exchange 2010 RTM, you can meet the prerequisite by installing 2007 Office System Converter: Microsoft Filter Pack. However, we recommend that you upgrade to the Microsoft Office 2010 Filter Packs.

2. 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

3. 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,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,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,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,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,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,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,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,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,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,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

 Install the Exchange 2010 SP1 and SP2 Hotfixes for Windows Server 2008 R2

The following hotfix is required for Windows Server 2008 R2 and must be installed after the operating system prerequisites have been installed:

• 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.
    

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

1. Install Microsoft .NET Framework 3.5 SP1. For details, see Microsoft .NET Framework 3.5 Service Pack 1.
   
2. 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 and Knowledge Base article 959209, An update for the .NET Framework 3.5 Service Pack 1 is available.
   
3. Install Windows Remote Management (WinRM) 2.0 and Windows PowerShell V2 (Windows6.0-KB968930.msu). For details, see Knowledge Base article 968930, Windows Management Framework Core package (Windows PowerShell 2.0 and WinRM 2.0).
   
4. Install the necessary operating system components:
   
   1. Open Control Panel, and then select Programs.
      
   2. Click Turn Windows features on or off.
      
   3. Navigate to Internet Information Services > Web Management Tools > IIS 6 Management Compatibility.
      
   4. Select the check box for IIS 6 Management Console, and then click OK.
      

1. Open Control Panel, and then select Programs.
   
2. Click Turn Windows features on or off.
   
3. Select Microsoft .NET Framework 3.5.1.
   
4. Navigate to Internet Information Services > Web Management Tools > IIS 6 Management Compatibility.
   
5. Select the check box for IIS 6 Management Console, and then click OK.