Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1 Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 Timeline
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Updated on 8142013 – I removed the NumThreadsForIndexCreation registry key as there was an update rollup that removed the significance of that registry key and your organization importupgrade will actually fail if you use this NumThreadsForIndexCreation now. We have this documented in KB 2714807.
Sean McNellis, Ryan Anderson and I recorded a podcast (https://aka.ms/tndfbt) last Friday on Dynamics CRM Upgrade Best Practices. During the podcast we mentioned that we would be posting a blog article outlining the topics that we covered with links to more details. That podcast and this blog post are by no means all encompassing upgrade best practices, but are just meant to cover some of the common topics and practices that we have been doing with our premier support customers.
Registry keys on the CRM server that we recommend implementing for the CRM upgrade.
MaxUserPort - https://aka.ms/dims52
Leave in place
TCPTimedWaitDelay - https://aka.ms/xhts4r
OLEDBTimeout - https://aka.ms/yc14kw
Set back to previous value or delete key
*EnableRetrieveMultipleOptimization - https://aka.ms/bcii0b
* We used to recommend setting the EnableRetrieveMultipleOptimization to 2 or 1 for most of our customers with millions of records in the PrincipalObjectAccess table, but now with the UR10 optimizations we are recommending that customers set this to 0 or delete the key as CRM dynamically sets this now based on your dataset.
Jobs to update:
We ran out of time on this podcast to spend much time talking about upgrading the CRM Outlook clients, so we are planning to do a follow up podcast on that topic specifically. However, we do want to provide you with a few quick best practices for upgrading CRM Outlook clients
We could write an entire book on this and probably should some day, but for the purposes of this blog supporting our podcast we wanted to highlight a few areas.
Well, this blog post got a lot longer than I had anticipated, but I wanted to provide you with supporting details and URL’s to all of the topics that we covered during our podcast. I hope that you enjoyed listening to our podcast, or even just consuming the information in this blog post. Hopefully this will help your CRM 2011 upgrades go smoothly. Please let us know if you have any questions regarding this podcast andor blog, or if you are interested in learning more about Microsoft Premier Support and the services we deliver to our Premier Support customers.
Thanks! Sean McNellis, Ryan Anderson & Shawn Dieken
Business Applications communities