The following roles and role services need to be installed.  Note that some of these roles or role services might not be required, but they were turned on by selecting other role services during the installation.  Also note that I have configured Reporting Services on the same machine, which would add to some of the requirements.

Application Server

• Application Server Foundation
• Web Server (IIS) Support
• Windows Process Activation Service Support
• Http Activation

File Services

• File Server
• Windows Server 2003 File Services
• Indexing Service

Web Server (IIS)

• Web Server
• Common Http Features
  • Static Content
  • Default Document
  • Directory Browsing
  • HTTP Errors
  • HTTP Redirection
• Application Development
  • ASP.NET
  • .NET Extensibility
  • ASP
  • ISAPI Extensions
  • ISAPI Filters
• Health and Diagnostics
  • HTTP Logging
  • Logging Tools
  • Request Monitor
  • Tracing
• Security
  • Basic Authentication
  • Windows Authentication
  • Digest Authentication
  • Client Certificate Mapping Authentication
  • URL Authorization
  • Request Filtering
  • IP and Domain Restrictions
• Performance
  • Static Content Compression
  • Dynamic Content Compression
• Management Tools
  • IIS Management Console
  • IIS Management Scripts and Tools
  • Management Service
  • IIS 6 Management Compatibility
    • IIS 6 Metabase Compatibility
    • IIS 6 WMI Compatability
    • IIS 6 Scripting Tools
    • IIS 6 Management Console

If you choose to install Reporting Services on the same server as your CRM server, it should be installed and verified to be functioning prior to installing CRM 4.  Also note that you should host the reporting services urls on a seperate website than the default website.  Reporting services and CRM will not function together in the same website.  CRM also needs to be able to use a website that maps to the machine name of the server, so it is highly recommended that you install reporting services on a website with a custom url, like reports.mydomain.com.

I had some issues with Windows 2008 security permissions with the standard Reporting Services installation, so I elected to configure it to use a seperate application pool with domain credentials.  That can be done manually, or through the reporting server configuration tool.  I had an error with the rsAccessDeniedToSecureData error, and I solved that by manually setting the domain credentials in the reporting services configuration file.

Prior to installing CRM, I created an empty website and set the bindings to the local machine name of the server.  I also created a new application pool that used network service credentials.  I have had a lot of problems in the past using domain credentials with CRM, so I decided to keep this set to Network Service.  The installation of CRM 4 goes through quite easily.

If you are setting up your CRM to be accessed outside of your network or in a hosting scenario, you will want to configure Internet Facing Deployment (IFD) authentication.  IFD is an authentication mode where the CRM server will analyze your source IP address and if you are outside of your corporate network, it will flip over to forms authentication mode.  If you are located inside your corporate network, you will be authenticated with integrated LAN authentication.  This means you need to enable IFD and configure the CRM to recognize your local subnets.

You must disable IPv6 on your server if you are going to use IFD otherwise the network detection mechanism will not work properly and you will have problems browsing from the server or any other machine in your network using IPv6 (ie: Vista).  You can disable IPv6 via the registry - simply unbinding it from your network adapter is not sufficient.  See the links below for more information.