Compartilhar via

Software requirements for Microsoft Dynamics CRM Server 2013

  • Artigo

 

Applies To: Dynamics CRM 2013

This section lists the software and application requirements for Microsoft Dynamics CRM Server 2013.

In This Topic

Windows Server operating system

Supported Windows Server 2012 editions

Supported Windows Server 2008 editions

Compatibility for client computers running Windows 8.1 Update for x64-based Systems

Server virtualization

Active Directory modes

Internet Information Services (IIS)

SQL Server editions (database engine)

Accessing Microsoft Dynamics CRM from the Internet - Claims-based authentication and IFD requirements

SQL Server Reporting Services

Software component prerequisites

Verify prerequisites

Windows Server operating system

Microsoft Dynamics CRM Server 2013 can be installed only on Windows Server 2008 or Windows Server 2012 64-bit-based computers. The specific versions and editions of Windows Server that are supported for installing and running Microsoft Dynamics CRM Server 2013 are listed in the following sections.

Important

The following Windows Server versions are not supported for installing and running Microsoft Dynamics CRM Server 2013:

  • Windows Server 2012 Foundation

  • Windows Server 2012 Essentials

  • Microsoft Windows Small Business Server editions

  • The Windows Server 2003 family of operating systems

Supported Windows Server 2012 editions

The following editions of the Windows Server 2012 operating system are supported for installing and running Microsoft Dynamics CRM Server 2013:

  • Windows Server 2012 R2 Datacenter

  • Windows Server 2012 R2 Standard

  • Windows Server 2012 Datacenter

  • Windows Server 2012 Standard

Important

Running on Windows Server 2012 R2 requires Microsoft Dynamics CRM 2013 Service Pack 1 (SP1) or at least Microsoft Dynamics CRM 2013 Update Rollup 2.

Supported Windows Server 2008 editions

The following editions of the Windows Server 2008 operating system are supported for installing and running Microsoft Dynamics CRM Server 2013:

  • Windows Server 2008 Standard SP2 (x64 versions) or Windows Server 2008 Standard R2 SP1

  • Windows Server 2008 Enterprise SP2 (x64 versions) or Windows Server 2008 Enterprise R2 SP1

  • Windows Server 2008 Datacenter SP2 (x64 versions) or Windows Server 2008 Datacenter R2 SP1

  • Windows Web Server 2008 SP2 (x64 versions) or Windows Web Server 2008 R2 SP1

Important

  • Windows Server 2008 installed by using the Server Core installation option is not supported for installing and running Microsoft Dynamics CRM 2013 Server.

  • Windows Server 2008 for Itanium-based systems isn’t supported for installing and running Microsoft Dynamics CRM Server 2013.

Compatibility for client computers running Windows 8.1 Update for x64-based Systems

  • Microsoft Dynamics CRM 2013 Service Pack 1 Update Rollup 1 or Microsoft Dynamics CRM 2013 Update Rollup 3 include compatibility for the Microsoft Dynamics CRM web application client running Internet Explorer 11 and Windows 8.1 Update for x64-based Systems.

  • CRM for Outlook with Update Rollup 1 for Microsoft Dynamics CRM 2013 Service Pack 1 is compatible with Windows 8.1 Update for x64-based Systems (KB2919355). Notice that there isn't an Update Rollup 3 for CRM for Outlook and therefore you must apply Update Rollup 1 for Microsoft Dynamics CRM 2013 Service Pack 1 for compatibility with CRM for Outlook running on Windows 8.1 Update for x64-based Systems (KB2919355). For more information, see Microsoft Dynamics CRM 2013 Update Rollup 3.

  • Microsoft Dynamics CRM 2013 Service Pack 1 (SP1) (SP1) compatibility with Windows 8.1 Update for x64-based Systems (KB2919355) is expected in the next update rollup for CRM 2013 Service Pack 1 (on-premises) and is planned to include CRM for Outlook.

Server virtualization

Microsoft Dynamics CRM servers can be deployed in a virtualized environment by using Windows Server 2008 or Windows Server 2012 with Hyper-V or virtualization solutions from vendors who participate in the Microsoft Windows Server Virtualization Validation Program (SVVP). You must understand the limitations and best practices of server virtualization before you try to virtualize your installation of Microsoft Dynamics CRM. For information about Hyper-V, see the Microsoft Virtualization website.

Active Directory modes

The computer that Microsoft Dynamics CRM Server 2013 is running on must be a member in a domain that is running in one of the following Active Directory directory service forest and domain functional levels:

  • Windows Server 2003 Interim

  • Windows Server 2003

  • Windows Server 2008 

  • Windows Server 2008 R2

  • Windows Server 2012

  • Windows Server 2012 R2

For more information about Active Directory domain and forest functional levels, see the Active Directory Domains and Trusts Microsoft Management Console (MMC) snap-in Help.

Important

  • The computer that Microsoft Dynamics CRM is running on shouldn’t function as an Active Directory domain controller.

  • When you use the Add Users Wizard, only users from trusted domains in the current forest will be displayed. Users from trusted external forests aren’t supported and don’t appear in the wizard.

  • Installing Microsoft Dynamics CRM Server in an LDAP directory that is running in Active Directory Application Mode (ADAM) is not supported.

  • Running in Windows Server 2012 R2 mode requires Microsoft Dynamics CRM 2013 Update Rollup 2.

Internet Information Services (IIS)

Microsoft Dynamics CRM Server 2013 supports Internet Information Services (IIS) versions 7, 7.5, 8.0, and 8.5.

We recommend that you install and run IIS in Native Mode before you install Microsoft Dynamics CRM Server 2013. However, if IIS is not installed and it is required for a Microsoft Dynamics CRM server role, Microsoft Dynamics CRM Server Setup will install it.

Important

Microsoft Dynamics CRM can’t use a website that has more than one http or https binding. Although IIS supports multiple http and https bindings, there is a limitation in using additional bindings with Windows Communication Foundation (WCF). WCF is required when you use CRM for Outlook. Before you install or upgrade, you must remove the additional bindings from the website used for Microsoft Dynamics CRM or select a different website.

SQL Server editions (database engine)

Any one of the following Microsoft SQL Server editions is required and must be installed on Windows Server 2008 (x64 SP2 or R2) versions or Windows Server 2012 (64x RTM or R2) 64-bit-based computers, running, and available for Microsoft Dynamics CRM:

  • Microsoft SQL Server 2008, Standard Edition, x64 SP3 or R2 SP2

  • Microsoft SQL Server 2008, Enterprise Edition, x64 SP3 or R2 SP2

  • Microsoft SQL Server 2008 Datacenter x64 SP3 or R2 SP2

  • Microsoft SQL Server 2008 Developer x64 SP3 or R2 SP2 (for non-production environments only)

  • Microsoft SQL Server 2012, Enterprise, 64-bit SP1, SP2, or *SP3

  • Microsoft SQL Server 2012, Business Intelligence, 64-bit SP1, SP2, or *SP3

  • Microsoft SQL Server 2012, Standard, 64-bit SP1, SP2, or *SP3

  • Microsoft SQL Server 2012, Developer, 64-bit SP1, SP2, or *SP3 (for non-production environments only)

  • Microsoft SQL Server 2014, Enterprise, 64-bit RTM or *SP2

  • Microsoft SQL Server 2014, Business Intelligence, 64-bit RTM or *SP2

  • Microsoft SQL Server 2014, Standard, 64-bit RTM or *SP2

  • Microsoft SQL Server 2014, Developer, 64-bit RTM or *SP2 (for non-production environments only)

Important

  • 32-bit versions of Microsoft SQL Server 2008 or Microsoft SQL Server 2012 database engine are not supported for this version of Microsoft Dynamics CRM.

  • Microsoft SQL Server 2008 Workgroup, Web, Compact, or Microsoft SQL Server 2008 Express Edition editions are not supported for use with Microsoft Dynamics CRM 2013 Server.

  • Running 64-bit Microsoft SQL Server 2008 versions for Itanium (IA-64) systems in conjunction with Microsoft Dynamics CRM will receive commercially reasonable support. Commercially reasonable support is defined as all reasonable support efforts by Microsoft Support that do not require Microsoft Dynamics CRM code fixes. Microsoft Dynamics CRM 2013 supports a named instance of Microsoft SQL Server for configuration and organization databases.

  • Running on Windows Server 2012 R2 requires at least Microsoft Dynamics CRM 2013 Update Rollup 2.

  • Support for Microsoft SQL Server 2014 requires at least Update Rollup 2 for Microsoft Dynamics CRM 2013 Service Pack 1.

  • Support for Microsoft SQL Server 2012 Service Pack 2 requires at least Update Rollup 3 for Microsoft Dynamics CRM Service Pack 1.

  • *Compatibility with this version of SQL Server requires Update Rollup 4 for Microsoft Dynamics CRM 2013 Service Pack 1 or later update.

Accessing Microsoft Dynamics CRM from the Internet - Claims-based authentication and IFD requirements

The following items are required or recommended for Internet-facing deployment (IFD). This topic assumes you will be using Active Directory Federation Services (AD FS) as the security token service (STS). For more information about configuring Microsoft Dynamics CRM for claims-based authentication, download the Claims-based Authentication White Paper from the Microsoft Download Center.

Important

Exposing the Microsoft Dynamics CRM website to the Internet is not supported unless claims-based authentication is used and Microsoft Dynamics CRM is configured for IFD.

Similarly, Outlook Anywhere (RPC over HTTP) is not supported as a solution to connect CRM for Outlook to an on-premises deployment of Microsoft Dynamics CRM 2013 over the Internet. The on-premises deployment of Microsoft Dynamics CRM 2013 must be configured for IFD as described in the topic Configure a Microsoft Dynamics CRM Internet-facing deployment.

In order for Microsoft Dynamics CRM for tablets to successfully connect to a new deployment of Microsoft Dynamics CRM Server 2013, you must run a Repair of Microsoft Dynamics CRM Server 2013 on the server running IIS where the Web Application Server role is installed after the Internet-Facing Deployment Configuration Wizard is successfully completed. For repair instructions, see Uninstall, change, or repair Microsoft Dynamics CRM Server 2013.

  • The computer where Microsoft Dynamics CRM 2013 Server is installed must have access to a security token service (STS) service, such as Active Directory Federation Services (AD FS) federation server. Microsoft Dynamics CRM 2013 Server supports Active Directory Federation Services (AD FS) 2.0, 2.1, and 2.2 versions.

  • Note the following conditions for the web components before you configure IFD:

    • If you are installing Microsoft Dynamics CRM in a single server configuration, be aware that Active Directory Federation Services 2.0 installs on the default website. Therefore, you must create a new website for Microsoft Dynamics CRM.

    • When you run the Internet-Facing Deployment Configuration Wizard, Microsoft Dynamics CRM 2013 Server must be running on a website that is configured to use Secure Sockets Layer (SSL). Microsoft Dynamics CRM Server Setup will not configure the website for SSL.

    • We recommend that the website where the Microsoft Dynamics CRM 2013 web application will be installed has the “Require SSL” setting enabled in IIS.

    • The website should have a single binding. Multiple IIS bindings, such as a website with an HTTPS and an HTTP binding or two HTTPS or two HTTP bindings, are not supported for running Microsoft Dynamics CRM.

    • Access to the Active Directory Federation Services (AD FS) federation metadata file from the computer where the Configure Claims-Based Authentication Wizard is run. Note the following:

      • The federation metadata endpoint must use the web services trust model (WS-Trust) 1.3 standard. Endpoints that use a previous standard, such as the WS-Trust 2005 standard, are not supported. In Active Directory Federation Services 2.0, all WS-Trust 1.3 endpoints contain /trust/13/ in the URL path.

    • Encryption certificates. The following encryption certificates are required. You can use the same encryption certificate for both purposes, such as when you use a wildcard certificate:

      Important

      If you use a certificate that is created by using a custom certificate request, the template that was used must be the Legacy key template. Custom certificate requests created by using the CNG key template are incompatible with Microsoft Dynamics CRM. For more information about custom certificate request templates, see Create a Custom Certificate Request.

      • Claims encryption. Claims-based authentication requires identities to provide an encryption certificate for authentication. This certificate should be trusted by the computer where you are installing Microsoft Dynamics CRM 2013 Server so it must be located in the local Personal store where the Configure Claims-Based Authentication Wizard is running.

      • SSL (HTTPS) encryption. The certificates for SSL encryption should be valid for host names similar to org.contoso.com, auth.contoso.com, and dev.contoso.com. To satisfy this requirement you can use a single wildcard certificate (*.contoso.com), a certificate that supports Subject Alternative Names, or individual certificates for each name. Individual certificates for each host name are only valid if you use different servers for each web server role. Multiple IIS bindings, such as a website with two HTTPS or two HTTP bindings, aren’t supported for running Microsoft Dynamics CRM. For more information about available options, contact your certification authority service company or your certification authority administrator.

  • The CRMAppPool account of each Microsoft Dynamics CRM website must have read permission to the private key of the encryption certificate specified when configuring claims-based authentication. You can use the Certificates snap-in to edit permissions for the encryption certificate found in the Personal store of the local computer account.

SQL Server Reporting Services

Specific Microsoft SQL Server Reporting Services editions are used for reporting functionality.

Any one of the following Microsoft SQL Server editions is required and must be installed on Windows Server 2008 (x64 SP2 or R2) versions or Windows Server 2012 (x64 RTM or R2) 64-bit-based computers, running and available for Microsoft Dynamics CRM:

  • Microsoft SQL Server 2008, Standard Edition, x64 SP3 or R2 SP2

  • Microsoft SQL Server 2008, Enterprise Edition, x64 SP3 or R2 SP2

  • Microsoft SQL Server 2008 Datacenter x64 SP3 or R2 SP2

  • Microsoft SQL Server 2008 Developer x64 SP3 or R2 SP2 (for non-production environments only)

  • Microsoft SQL Server 2012, Enterprise, 64-bit SP1 or SP2

  • Microsoft SQL Server 2012, Business Intelligence, 64-bit SP1 or SP2

  • Microsoft SQL Server 2012, Standard, 64-bit SP1 or SP2

  • Microsoft SQL Server 2014, Enterprise, 64-bit

  • Microsoft SQL Server 2014, Business Intelligence, 64-bit

  • Microsoft SQL Server 2014, Standard, 64-bit

Important

  • 32-bit versions of Microsoft SQL Server 2008 or Microsoft SQL Server 2012 Reporting Services are not supported for this version of Microsoft Dynamics CRM.

  • Microsoft SQL Server 2008 Workgroup, Web, Compact, or Microsoft SQL Server 2008 Express Edition editions are not supported for use with Microsoft Dynamics CRM 2013 Server.

  • Running 64-bit Microsoft SQL Server 2008 versions for Itanium (IA-64) systems in conjunction with Microsoft Dynamics CRM will receive commercially reasonable support. Commercially reasonable support is defined as all reasonable support efforts by Microsoft Support that do not require Microsoft Dynamics CRM code fixes.

  • Microsoft SQL Server 2008 Workgroup is not supported for running the Microsoft Dynamics CRM Reporting Extensions. This is because Microsoft SQL Server 2008 Workgroup does not support custom data extensions. Therefore, features such as creating, running, or scheduling Fetch-based or SQL-based reports will not work.

  • Using a Microsoft SQL Server 2012 Reporting Services server running in SharePoint mode is not supported with Microsoft Dynamics CRM. For more information about Microsoft SQL Server 2012 Reporting Services SharePoint mode, see Install Reporting Services SharePoint Mode as a Single Server Farm.

  • Running on Windows Server 2012 R2 requires at least Microsoft Dynamics CRM 2013 Update Rollup 2.

  • Support for Microsoft SQL Server 2014 requires at least Update Rollup 2 for Microsoft Dynamics CRM 2013 Service Pack 1.

  • Support for Microsoft SQL Server 2012 Service Pack 2 requires at least Update Rollup 3 for Microsoft Dynamics CRM Service Pack 1.

Software component prerequisites

The following SQL Server components must be installed and running on the computer that is running SQL Server before you install Microsoft Dynamics CRM 2013 Server:

  • SQL word breakers

    This is only required for some Microsoft Dynamics CRM language editions. For more information about word breaker versions for languages supported by SQL Server see Configure and Manage Word Breakers and Stemmers for Search.

  • SQL Server Agent service

  • SQL Server full-text indexing

The following components must be installed and running on the computer where Microsoft Dynamics CRM 2013 Server will be installed:

  • Services

    • Indexing Service

      To install this service, see the Windows Server documentation.

    • IIS Admin

    • World Wide Web Publishing

  • Windows Data Access Components (MDAC) 6.0 (This is the default version of MDAC with Windows Server 2008.)

  • Microsoft ASP.NET (Must be registered, but does not have to be running.)

Verify prerequisites

Before you install Microsoft Dynamics CRM 2013 Server, you should understand the following:

  • Microsoft SQL Server can be, but is not required to be, installed on the same computer as Microsoft Dynamics CRM 2013 Server.

  • If Microsoft Dynamics CRM 2013 Server and Microsoft SQL Server are installed on different computers, both computers must be in the same Active Directory directory service domain.

  • Microsoft SQL Server can be installed by using either Windows Authentication or mixed-mode authentication. (Windows Authentication is recommended for increased security and Microsoft Dynamics CRM will use only Windows Authentication).

  • The service account that SQL Server uses to log on to the network must be either a domain user account (recommended) or one of the built-in system accounts supported by SQL Server (Network Service, Local Service, or Local System). Installation of Microsoft Dynamics CRM will fail if the SQL Server service account is the local administrator.Installation of Microsoft Dynamics CRM will fail if the SQL Server service account is the local administrator.

  • The SQL Server service must be started and can be configured to automatically start when the computer is started.

  • The Microsoft SQL Server Reporting Services service must be started and configured to automatically start when the computer is started.

  • The SQL Server Agent service must be started. This service can be configured to automatically start when the computer is started.

  • Although it is optional, we recommend that you accept the SQL Server default settings for Collation Designator, Sort Order, and SQL Collation. Microsoft Dynamics CRM supports both case-sensitive and case-insensitive sort orders.

  • Microsoft Dynamics CRM Server Setup requires at least one network protocol to be enabled to authenticate by using SQL Server. By default, TCP/IP protocol is enabled when you install SQL Server. You can view network protocols in SQL Server Configuration Manager.

See Also

Microsoft SQL Server hardware requirements for Microsoft Dynamics CRM Server 2013
Microsoft Dynamics CRM 2013 Reporting Extensions requirements
Microsoft Dynamics CRM 2013 updates and hotfixes

© 2016 Microsoft Corporation. All rights reserved. Copyright