Microsoft Dynamics CRM Team Blog: Important information about supported configurations in the next release for CRM

[Blog bot]

Источник: http://blogs.msdn.com/b/crm/archive/...e-for-crm.aspx
==============

As we ship the Microsoft Dynamics CRM 2013 Service Pack 1 and CRM Online Spring ‘14 releases, we’re looking ahead to our next release of CRM. As with other releases of CRM in the past, we find the need to add and remove items from our supported configurations list to keep current with technology, and allow us to provide you the best product possible.

Changes in supported platform software

For the next release, we’re removing the following operating systems from our Microsoft Dynamics CRM Server support matrix:

• Windows Server 2008
• Windows Server 2008 R2
• Windows Small Business Server (All versions)

We’re removing the following SQL Server versions from our Microsoft Dynamics CRM Server support matrix:

• Microsoft SQL Server 2008
• Microsoft SQL Server 2008 R2

We’re removing Microsoft Dynamics CRM for Outlook support for:

• Windows Vista
• Windows Server 2008 Remote Desktop Services
• Microsoft Office 2007

Our current plan for Microsoft Dynamics CRM Server is to target only Windows Server 2012, Windows Server 2012 R2, and SQL Server 2012 for the next release time frame.

Note that we’re exploring support for SQL Server 2014 with Microsoft Dynamics CRM Server, but we haven’t made a decision at this time.

Changes in items specific to the CRM application

Client API (JS)

We’re removing the following client SDK (JavaScript) APIs:

• GetServerUrl()
• IsOutLookClient()
• IsOutlookOnline()

This means that if your customizations are using any of these API commands, your code will likely break after you upgrade CRM.

We’re modifying the possible return values from GetFormType() to remove the ReadOnly and CRM 4.0 QuickForm Types. This means that we’re removing two values from the possible results of GetFormType(). However, it’s unlikely that your code will be affected by this because we removed the forms types in CRM 2013.

Please see Client-side Context Reference for CRM 2013 for alternative methods to use

Form system

We’re removing the following form items:

• Read-optimized forms
• CRM 2011 forms that were updated in CRM 2013

This means that you must upgrade your forms to use the new CRM 2013 form system before upgrading to the next release.

Entities

The Kit type of Product will be deprecated, which means that we’ll do base testing only and will be removing this feature in the next release. Please update your customizations to not use this entity.

Upgrade rules

We’re making database merge mandatory on upgrade. This means that you won’t be able to bypass this process during the upgrade from CRM 2013 to the next release of CRM.

Email Router

Support for Exchange 2007 connectivity to and from the CRM Email Router will be deprecated, which means that we’ll do base testing only and will be removing this capability from the CRM Email Router in a future release.

Browsers

We’re dropping support for Internet Explorer 8 and Internet Explorer 9.

Note that Internet Explorer 8 and 9 won’t route to Microsoft Dynamics CRM for phones by default, they will continue to route to the main application. However, they won’t provide an optimal experience and any issues reported will need to be validated on a supported browser.

2007 SDK SOAP Endpoint

We’ll be removing this endpoint, which was deprecated in CRM 2013. You shouldn’t use this endpoint for any new extensions.




Источник: http://blogs.msdn.com/b/crm/archive/...e-for-crm.aspx