links were appeared a little ago

@eboocock: there is no CRM2011-Server-KB2795627-ENU-amd64.exe link on this page.

Microsoft Dynamics CRM 2011 Update Rollup 12 Server Bits have been posted: <a rel="nofollow" target="_new" href="www.microsoft.com/.../details.aspx;>www.microsoft.com/.../details.aspx</a>

Oh Microsoft...  "You've done it again!"

But don't be concerned...  A May 2012 release not out by January 2013 is still well within my expectations of Microsoft's reliability!

It's like being in a bad marriage. You keep hyping things up and trying to raise my expectations, yet with years and years and YEARS of broken hype, delays and dud releases.... I simply don't believe a thing you say anymore.

My customers... unfortunately they are not so understanding. I don't lie for you, but snip together media release "BS hype" and show them that I am not they lier, but that you are. I make it clear who is to blame in the failure of this marriage.

Rajeev Goel - gets it.

<a rel="nofollow" target="_new" href="www.geekwire.com/.../";>www.geekwire.com/.../microsoft-friends</a>

Bob ... May release slipped to December and then January. Now a plan to "repost ... within the next week" has turned into 19 days.

Are you planning on creating realistic schedule so we can plan at some point in the near future?

come to the end of January, the new release date is still not clear? Our customers says  how u can not give an exact date of the december update.We make it hard to explain this situation.

Thank you Bob for the update, looking forward to download UR12 Server bits soon.

I just found out the Outlook client issue is not widespread.  It's something to do with our customizations.  Just wanted to update this to avoid any panic :)

The lack of regard we are receiving might be related to Microsoft moving all North American CRM support overseas.

The RU12 CRM for Outlook Client got rolled out to all our customers in a Windows Update on Jan. 21st and it broke their Outlook to the point that they could not open their Outlook.  There was no communication about the Client not being backwards compatible with previous Rollups.  Our customers are not happy and our Support team is spending countless hours working with End Users to uninstall Rollup 12 and disable the automatic Windows Update (which is the recommendation from MS Support).  If the Rollup was not backwards compatible, it should not have been included in Windows Update.  We need time to test RU12 before rolling it into Production.  We're in damage control with our customers.  If there was communication about this beforehand, we would have sent out Communication to all our customers, i consider this a severe lack of communication.