An on-premise install of Microsoft Dynamics CRM 2015 requires:
- Windows Server 2012 or later
- SQL Server 2012, SQL Server 2012 R2 or SQL 2014
Microsoft Dynamics CRM 2013 with Service Pack 1 (or later) can be upgraded to CRM 2015.
Client: Windows 7 or later
Browsers: IE10, IE11, Chrome, Safari and Firefox
Optional Items
ADFS 2.0, 2.1 2.2 (ADFS 2.0 must be installed on a different server from CRM)
Exchange 2010 or 2013
Outlook 2010 or 2013 (cached Exchange mode)
Windows SharePoint 2010 SP1 and 2013
Discontinued Support
Windows Server 2008 and 2008 R2
SQL Server 2008 and 2008 R2
Windows Small Business Server all versions
2008 Terminal Servers
Windows Vista
SharePoint 2007
Office 2007
Exchange 2007
IE 8 and IE9 – will direct to main application not mobile express but not supported
Upgrade
Cannot uninstall the upgrade to revert to CRM 2013
CRM 2015 Beta 1 is not upgradeable to RTM
Must start from CRM 2013 with SP1 or later (6.1 or later)
In Place or Migration (recommended)
Customer Service enhancements in SP1 will be automatically installed if not already. Cannot prevent this.
Email Router must be upgraded to the 2015 version or reinstalled using the 2015 version
Reporting Extensions must be uninstalled and then reinstalled using the 2015 version
Table Merge
Base and Extension Base table will be merged during upgrade if not already done. Cannot prevent this. The merge tool (in CRM 2013) is removed and the registry key to prevent merging is ignored.
Solutions
CRM 2013 managed and unmanaged solutions (6.0 and 6.1) can be imported into CRM 2015 (but not CRM 2011)
CRM 2015 will not allow Export As to earlier versions.
Forms
v5 and v6 forms – CRM 2011 v5 form upgrades to CRM 2013 and is rendered as a v5 form. New forms are v6 forms.
v5 forms can continue to be used in CRM 2015 but they will be disabled in the next major release. No more form developments for the v5 forms.
The status of v5 forms will not be changed during upgrade.
Form named Information is the v5 form, form with the same name as the entity is the v6 form. Use Merge Forms in a v6 form to migrate v5 forms.
Use metadata query to check the Introduced Version on forms to determine whether it is a v5 or v6 form.