Microsoft releases Microsoft Dynamics CRM 2013 Best Practices Analyzer today. This is a diagnostic tool that gathers information about Microsoft Dynamics CRM 2013 server roles and offers recommendations.
The Microsoft Dynamics CRM 2013 Best Practices Analyzer is a diagnostic tool that performs the following functions:
- Gathers information about the CRM 2013 server roles that are installed on that server.
- Determines if the configurations are set according to the recommended best practices.
- Reports on all configurations, indicating settings that differ from recommendations.
- Indicates potential problems in the CRM 2013 features installed.
- Recommends solutions to potential problems.
You may download the CRM 2013 Best Practice Analyzer from the Microsoft download center.
This diagnostic tool requires Microsoft Baseline Configuration Analyzer 2.0. Microsoft Baseline Configuration Analyzer 2.0 (MBCA 2.0) can help you maintain optimal system configuration by analyzing configurations of your computers against a predefined set of best practices, and reporting results of the analyses. You may download the Baseline Configure Analyzer 2.0 from the Microsoft download center as well.
The tool is pretty easy to install and use. I installed ran the tool in less than 5 minutes on my Azure lab. Sample output below.
At this moment, The only way to change the org URL is to uninstall and reinstall the MoCA app. Happy to be corrected.
I got another interesting question from my customer today. How many users configured the CRM Outlook client? Thanks to my PFE friend, KG, he provided us the SQL query to get that information.
To get the # of subscription clients in CRM, you may execute the query against the [ORGNAME]_MSCRM database below.
select distinct MachineName from SubscriptionClients
Customer asked me to see if they can change their CRM Organization Display Name. I didn’t pay attention to these small details in CRM therefore I don’t know. But I did some research and evaluated the impact of changing the name. So it’s possible to change the organization display name and the impact is minor since we are not changing the schema name of the organization.
To change the Display Name of a CRM organization, you may follow the steps below.
- Logon to the CRM Application Server.
- Navigate to Start | Microsoft Dynamics CRM 2011 | Deployment Manager.
- Click on Organizations on the left navigation to display the organizations in the environment.
- Select the organization that you want to change the Display Name.
- Click Disable from the Action Pane on the right.
- Click Edit Organization from the Action Pane on the right.
- On the Edit Organization Wizard screen. enter the desired organization name in the Display Name textbox, then click Next to move to the confirmation screen.
- Click Next on the System Checks screen.
- Click Apply on the Ready to Apply Changes screen.
- Click Finish to close the Edit Organization Wizard.
- After the update is completed, click Enable on the Action Pane to re-enable the organization.
The customer asked me today if WIF is really required for CRM 2011 On-Premise deployment without using Claims-based authentication. Hmm… It’s a good question, I know it’s required for CRM 2011 but I don’t really know the reason behind why WIF is required for a pure AD on-premise deployment.
So I did some research and pinged some of my Microsoft friends in the CRM product team. Found out that the reason that WIF is required for CRM is because it is used for claims-based authentication and it’s built into the CRM SDK, and it’s statically linked to the CRM binaries and there’s no easy way to separate them at this moment, therefore it’s required for all deployments.
I’ve learned something new today!
After almost 3 year, I am done with a global CRM implementation for a life science company in California. My travel between Chicago and Los Angeles finally comes to the end. Looking back at the past 3 years, I have learned a lot from this project and this customer. I also got to know many great people and got a chance to build good relationships with everyone of them. I really want to thank my team for everything that they have done on this project. Thanks to everyone at Microsoft who supported this project as well.
Just for Laugh – Fun Facts for this project
- Airline Miles: >1 million miles
- Hotel Nights: >500 nights
- Pound of Sushi: >100 pound consumed
- Celebrated Festivus: 2 times
After the new year, I’ll be heading to a brand new project in Milwaukee, I’ll be missing a lot of airline mile.
I ran into a problem today that CRM IE7, 8, 9 hangs after 30 minutes because I have many XmlHttpRequest calls on the form. I found a blog on MSDN that helped me out and I believe all of the us as a CRM developer should pay attention to. The title of the blog article is Why You Should Use XMLHttpRequest Asynchronously, it’s a good read.