The Microsoft Dynamics CRM Team Blog
News and views from the Microsoft Dynamics CRM Team
The Microsoft Dynamics CRM Sustained Engineering (SE) team released Microsoft Dynamics CRM 2011 Update Rollup 4 on Thursday, September 22, 2011.
The links below will take you to the necessary information about Update Rollup 4. If a link does not work, please refer to the Release Channel Schedule below to make sure it is past the release date listed.
Release Channel Schedule
General Details about Update Rollup 4
Client packages installed manually by downloading the packages and running install will require administrative privileges. If the client packages are installed via the Windows Update (Microsoft Update) system, they will not require administrative privileges.
For help with installation, please see the Installation Information section in KB2556167.
Dates for Future Update Rollups
While the CRM team strives to deliver Update Rollups every 8 weeks, there are some scheduling changes that affect Update Rollup 5 and Update Rollup 6. The dates below are for informational purposes and may change. Changes will not be made to this blog post but included in the Update Rollup 5 blog entry.
Update Rollup 5 will be delivered earlier than the 8-week cycle and is scheduled to release at the end of October 2011.
Update Rollup 6 will be delivered on its predefined schedule, 16 weeks after Update Rollup 4, which puts the delivery in January 2012.
How to Get Support for Update Rollup 4
For support, please contact Microsoft Product Support. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft web site: http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS.
Note: In special cases, charges ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.