Personalized Community is here!
Quickly find the content you seek
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 1Discover 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 TimelineWatch the 2020 Release Wave 1 virtual launch event
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
Has anyone out there worked with support and have been requested by the engineer to run a diagnostic? Are you curious why we ask for this and how it may benefit your troubleshooting situation? If so, read on....
What is this diagnostic tool?
This is a tool generated internally by support for your individual support case
Why run the diagnostic tool?
The tool will help speed up the process of data collection. Once all of the data has been collected it is returned and processed through the case. This will be compared against a list of known issues, configuration issues, and other problem areas. If these are found, they will be flagged so that the engineer can potentially resolve the issue much faster than grabbing the data manually. By using the diagnostic to collect the information, we can reduce the number of back and forth communications asking for additional details about your system which can occur if we only request one or two pieces of information at a time. We also can eliminate any possible confusion about what information is being requested by having the diagnostic utility automatically recover the information instead of having to search the computer for the relevant information. This can also help eliminate several troubleshooting paths and can additional check the health of other areas of your environment where the engineer may provide you with proactive measures.
Overall, this can help reduce the time taken for troubleshooting a case to resolution, minimizing incorrect data collection, and making a overall better experience for you.
What is captured in these diagnostics?
There is far too much to list here about what is captured in each and every diagnostic. However, they focus on gathering key details and information such as:
The list goes on and on.
What diagnostics are there?
Client for Outlook Collector
Client for Outlook Configuration Collector
Client Performance Collector
CRM Server Platform Trace Collector
Server Baseline Collector
Email Router Collector
IIS Memory Dump Collector
Claims Based Authentication /AD FS / IFD Collector
There is also a link here to commonly asked questions about the diagnostics:
There will be more diagnostics coming in the future. As more troubleshooting points are found in each and every case, these are added and flagged in the diagnostics to better assist the next person that runs into that particular issue.
Business Applications communities