 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  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.  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 . 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 .  SQL Server Agent service  SQL Server full-text indexing The following components must be installed and running on the computer 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
Microsoft Dynamics CRM for Outlook software feature prerequisites The following software must be installed and running on the computer before you run Microsoft Dynamics CRM for Outlook Setup: Web Browser. One of the following:  Supported versions of Internet Explorer  Important Internet Explorer 7 or earlier versions are not supported for use with Microsoft Dynamics CRM 2013 for Microsoft Office Outlook. Microsoft Office. One of the following:  Microsoft Office 2013  Microsoft Office 2010  Microsoft Office 2007 Important Outlook 2003 versions are not supported for installing and running CRM 2013 for Outlook. To install and run the 64-bit version of CRM for Outlook, a 64-bit version of Microsoft Office is required. Before you run the Configuration Wizard to configure CRM for Outlook, a Microsoft Office Outlook profile must exist for the user. Therefore, Microsoft Outlook must be run at least once to create the user's Microsoft Outlook profile. Both the web application and CRM for Outlook require JavaScript enabled for certain features, such as Activity Feeds, dashboard areas, and the display of certain panes or menus. Although the web application displays error messages when JavaScript is disabled, CRM for Outlook doesn’t. To verify if JavaScript is enabled in Internet Explorer 9, start Internet Explorer, on the Tools menu click or tap Internet options. On the Security tab, click or tap Internet, and then click or tap Custom level. In the Security Settings dialog box under Scripting, Active scripting must be set to Enable.
 Hardware and software requirements. A brief overview of the computer hardware and software requirements, and where you can find more information about the requirements.  Active Directory considerations. Supported Active Directory forest and domain  SQL Server and SQL Server Reporting Services installation and configuration. A summary of how Microsoft SQL Server and Microsoft SQL Server Reporting Services must be deployed and configured to install Microsoft Dynamics CRM.  Planning Exchange Server or POP3. A summary of how Exchange Server or a POP3-compliant e-mail server must be deployed to install and use the Email Router to send and receive Microsoft Dynamics CRM e-mail messages.  Security considerations. Information about how you can make the Microsoft Dynamics CRM system more secure.  Supported configurations. Information about the supported network, domain, and server configurations for Microsoft Dynamics CRM.  Upgrading from a previous version of Microsoft Dynamics CRM. How Microsoft Dynamics CRM upgrades your current system and what happens to items such as existing reports and customizations. See Also Hardware requirements Software requirements SQL Server installation and configuration Planning integration Microsoft Dynamics CRM 2013 supported configurations
Organization Web Service Supports running applications that use the methods described in the Microsoft Dynamics CRM End Server Individual, Group, or Full Web Application Server Runs the Web Application Server that is used to connect to Microsoft Dynamics CRM data. The Web Application Server role requires the Organization Web Service role. Front End Server Individual, Group, or Full Help Server Makes Microsoft Dynamics CRM Help available to users. Front End Server Individual, Group, or Full Service Processes queued asynchronous events, such as workflows, bulk or data import. Back End Server Individual, or Full Sandbox Processing Service Enables an isolated environment to allow for the execution of custom code, such Back End Server Individual, Group, or Full SDK
as plug-ins. This isolated environment reduces the possibility of custom code affecting the operation of the organizations. Integration Service Handles sending and receiving of email messages by connecting to an external email server. Back End Server Individual, Group, or Full Deployment Web Service Manages the deployment by using the methods described in the Microsoft Dynamics CRM Deployment Server Individual, Group, or Full Deployment Tools Consists of the Deployment Manager and Windows PowerShell cmdlets. Microsoft Dynamics CRM administrators can use the Windows PowerShell cmdlets to automate Deployment Server Individual, or Full SDK
Microsoft Dynamics CRM Server Role Prerequisites Component Back End Server End Server Deployment Administration Server Microsoft SQL Server Reporting Services ReportViewer control X SQL Server Native Client X X X Microsoft Application Error Reporting Tool X X X Microsoft Visual C++ Runtime Library X X X Windows Identity Foundation (WIF) Framework X X X Windows Server 2008 Web Server Role X X Indexing Service X Microsoft .NET Framework 4 X X X Microsoft Chart Controls for Microsoft .NET Framework X Windows Azure platform AppFabric X X X Windows PowerShell X
Microsoft URL Rewrite Module for IIS X File Server Resource Manager X The following describes the group membership for the Active Directory that is used by Microsoft Dynamics CRM. An “X” indicates the group membership required for the service to function. Group Membership Requirements Service PrivUserGroup SQLAccessGroup PrivReportingGroup ReportingGroup Deployment Web Service service account X X Web Application Service* X X Asynchronous Service service account X X Sandbox Processing Service service account** SQL Server service account X Microsoft SQL Server X X
upgrade issues occur because a roll back and reinstall of Microsoft Dynamics CRM will be required to avoid potential downtime. For detailed procedures for each of options, see the Upgrade from Microsoft Dynamics CRM 4.0 topics in the Installing Guide. For the latest product information, see the . Important Always run a full backup of the Microsoft Dynamics CRM databases before you upgrade to a new version of the product. For information about database backups, see in the Operating and Maintaining Guide. During an in-place upgrade, only the organization that you specify to upgrade to Microsoft Dynamics CRM 2011 is upgraded. If the Microsoft Dynamics CRM 2011 deployment contains additional organizations, those organizations are disabled and are not upgraded. You must upgrade those organizations using Deployment Manager. For more information, see Deployment Manager Help. For each organization that you upgrade, we recommend that the volume have free space that is at least three times the size of the organization database file (organizationName_MSCRM.mdf) and four times the size of the log file (organizationName_MSCRM.ldf). For example, if a single organization database and log file are located on the same volume where the mdf file is 326 MB and the ldf file is 56 MB, the recommended available space should be at least 1.2 GB to allow for growth ((326 x 3) + (56 x 4)). Notice that the database files that expand during upgrade do not reduce in size after the upgrade is complete. As part of organization upgrade, all entitynameBase and entitynameExtensionBase tables will be merged into a single table. To reduce downtime, consider deferring the table merge of large organization databases that are highly customized so that the table merge process can be run as a separate upgrade operation. For more information, see Run the Base and Extension table merge as a separate operation. Microsoft Dynamics CRM 2011 Server versions supported for upgrade The following Microsoft Dynamics CRM 2011 update rollup versions are supported for upgrade to Microsoft Dynamics CRM Server 2013. All other update rollup versions will receive an error message resembling the following and will not be upgraded.
About claims-based authentication The claims-based security model extends traditional authentication models to include other directory sources that contain information about users. This identity federation lets users from various sources, such as Active Directory Domain Services (AD DS), customers via the Internet, or business partners, authenticate with native single sign-on. The model has three components: the relying party, which needs the claim to decide what it is going to do; the identity provider, which provides the claim; and the user, who decides what if any information they want to provide. Microsoft provides a claims-based access solution called Active Directory Federation Services (AD FS). AD FS enables Active Directory Domain Services (AD DS) to be an identity provider in the claims-based access platform. AD FS consists of the following components:  AD FS Framework provides developers .NET security logic for building claims-aware applications, enhancing either ASP.NET or WCF applications.  Active Directory Federation Services (AD FS) is a security token service (STS) for issuing and transforming claims, enabling federations, and managing user access. Active Directory Federation Services (AD FS) supports the WS-Trust, WS-Federation, and Security Assertion Markup Language (SAML) protocols. Active Directory Federation Services (AD FS) can also issue manage information cards for AD DS users. For more information about AD FS, see:  Identity & Access  (Windows Server 2012 AD FS 2.1)  Download AD FS 2.0 for Windows Server 2008: Internet-facing server best practices Implement a strong password policy To reduce the risk of attacks" we strongly recommend that you implement a strong password policy for remote users who are accessing the domain where Microsoft Dynamics CRM is installed. For more information about how to implement a strong password policy in Windows Server, see on Microsoft TechNet and the "Understanding User Accounts" topic in Active Directory Users and Computers Help.