Installing CRM for Outlook: A Solution to Your Pending Restart Error

By Ryan Talsma, CRM Product Manager

I wanted to take a minute and share an issue I came across when troubleshooting a CRM for Outlook Client Install. To provide some background on my specific situation, I was trying to install CRM 2016 for Outlook on a Windows 10 machine that had prior versions of CRM for Outlook installed previously.

The Error

When trying to run the CRM for Outlook installer, I received the following warning:

Upon further investigation into the log file, I found an error stating:

09:51:59| Error | Microsoft update reports pending reboot required to complete updates

09:51:59| Warning | Error RebootError

09:51:59| Info | Pending restart is required

Obviously from this point I tried restarting, which didn’t work. I also tried several other solutions that I found while searching for a solution such as: running windows update, deleting temp files, trying to install prior versions and upgrading them directly, etc. Unfortunately, none of these worked.

My Solution

What did work was uninstalling, and reinstalling my Microsoft Office. I know, this is not an ideal solution, however, it certainly would have saved me a considerable amount of time had I just done this from the beginning. I would also consider this solution “safer” for a non-technical person who doesn’t feel comfortable making changes to the registry, deleting folders, etc., which is what many of the proposed solutions I found online suggested I do, and in the end, didn’t end up solving my issue anyways.

About Ryan Talsma:

Ryan Talsma is the CRM Product Manager at InterDyn BMI, who has previously spent time as a functional, technical, and support consultant. Ryan has extensive experience in CRM installs, upgrades, IFD/AD FS implementations, JavaScript, workflows, solution architecture, and implementing Microsoft Dynamics CRM Online as well as On Premise.

So What Happened to Microsoft Dynamics CRM?

Well, it has reinvented itself with a new name, new features and a new, flexible-licensing model. 

On November 1, 2016, Microsoft launched Dynamics 365—a modern, mobile and intelligent ERP AND CRM cloud business application. With this transition, the functionality of Microsoft Dynamics CRM is now within three distinct apps:

  1. Sales
  2. Marketing
  3. Service

Like the CRM you already know, these three Microsoft Dynamics 365 apps still work seamlessly together in the cloud.

New Name

Microsoft Dynamics CRM is now known as Microsoft Dynamics 365 for Sales, Marketing and Service.

New Features

Microsoft Dynamics 365 is simple to use and, because it lives in the cloud, you can access it from anywhere (on any device), simply by logging into your Microsoft account. Productivity tools like Office 365 and Adobe’s Marketing Cloud seamlessly integrate within Dynamics 365. Additionally, features that have previously been costly add-ons to Dynamics CRM, will now be built within these applications including social listening and knowledge management functionality.

Plus, intelligence features like Cortana, Power BI and Azure Learning Machine are integrated within the Dynamics 365 subscription. Speaking of subscription, Dynamics 365 is now licensed in a new, flexible way.

New License Model

Microsoft Dynamics 365 is built on a subscription licensing model, which means:

  • Lower monthly costs
  • The most up-to-date features and versions
  • Costs are based on consumption (per user/per month basis)

Start with what you need to run your business and then add apps as your needs change. The Sales, Marketing and Service Apps– are now separately licensed, but they will work together like the CRM you know and love. Microsoft Dynamics 365 gives businesses more choices.

There are two editions within Dynamics 365: Business and Enterprise.

The Business Edition (releasing in spring 2017) will include Sales, Marketing and Customer Service Apps for organizations with 0 users or less. Each business application will cost $40 per user/per month, or you can purchase a plan for $50, which includes all of the applications and functionality.

The Enterprise Edition (available now) includes: Sales, Marketing, Customer Service, Field Service and Project Service Automation for organizations with over 250 users. Each enterprise application is individually priced at $95 per user/per month, or you can purchase a plan starting at $70 per user/per month, which includes all of the applications.

Contact us to learn more about Microsoft Dynamics for Sales, Marketing & Service.

Implementing Editable Grids in Dynamics 365 Step-by-Step

By Ryan Talsma, CRM Product Manager

What Are Editable Grids?

Editable grids have certainly been one of the most requested features within the Dynamics CRM community for years, and we are very excited about it now being built in as standard functionality within the latest release of Dynamics 365. Editable grids provide you the ability to edit records from directly within a view without out even having to open the record. Editable grids can also be activated in sub-grids as well. Additionally, this functionality is not exclusive to the web client and works within the phone and tablet interfaces as well.

How Do Editable Grids Work?

Working within editable grids within Dynamics 365 is very easy and takes minimal time for users to learn how to use them. Users who specifically like to manage their records in an “Excel” type environment will have a very high adoption rate to this functionality, as they are now able to work with multiple records in an overview grid format as opposed to having to open records individually. Once, enabled a user simply can click within any given column on a specific record, and make the necessary changes.

Shown below is an example of editable grids enabled on my Account entity, where I am able to quickly and easily update the phone number for a specific account:

How Do I Enable Editable Grids?

Editable grids can be activated very quickly and easily by navigating to the Settings module. Under the Customization section, select Customizations, and then finally click Customize the System. Editable grids are enabled at the entity level. Select the entity you want to enable editable grids for, click the control tab, and add the editable grid control. In my example below, I will enable editable grids for the Opportunity Entity:

Settings > Customization > Customizations

Select Customize the System

Select the entity, then click the Controls tab, and Add Control…

Select Editable Grid and click Add:

Select the interfaces you want editable grids enabled for, and finally click Save, and then Publish

Upon publishing your changes, you should now be able to navigate back to your Opportunity entity and see that the changes have been published and that the Opportunity entity views are now editable.

Want more in-depth information on editable grids in Dynamics 365? Check out this technet article.

Also for a video demonstration on how to enable editable grids, watch the online video.

About Ryan Talsma:
Ryan Talsma is the CRM Product Manager at InterDyn BMI, who has previously spent time as a functional, technical, and support consultant. Ryan has extensive experience in CRM installs, upgrades, IFD/AD FS implementations, JavaScript, workflows, solution architecture, and implementing Microsoft Dynamics CRM Online as well as On Premise. 

Editable Grids in Dynamics 365

Watch this recorded webinar to get a brief overview of the new editable grids feature in Dynamics 365, including how to configure and enable them, as well as a demonstration of how they work after being configured.

Want to learn more about how CRM works within Dynamics 365? Attend our free webinar on December 6! Register now

Please feel free to contact us if you have any questions.

Microsoft Dynamics CRM and the Transition to Dynamics 365

By Brian Dewulf, CRM Practice Manager

Many of you may have already heard about Dynamics 365, the next generation of business applications from Microsoft. If you are like us, you probably have many questions about how this transition will affect your current CRM implementation. As InterDyn BMI’s CRM Practice Manager, I will do my best to answer common questions about this transition and also talk about some of the new features that will be available in this upcoming release.

How will the transition to Microsoft Dynamics 365 affect my current Microsoft Dynamics CRM system?

The answer to that question depends on whether you are running Dynamics CRM on-premises or Dynamics CRM Online.  For those of you currently running an on-premises version of Microsoft Dynamics CRM, the short answer is, you don’t have to do anything.  You can continue to run your existing version of CRM on-premises for as long as you like.  Those of you using Microsoft Dynamics CRM Online will need to transition to one of the new Dynamics 365 licensing plans when you current CRM Online agreement expires.  Most CRM Online subscriptions renew annually.  The renewal date is based on when you first signed up for CRM Online.  Your BMI account manager will be able to assist you with this transition.

How do the Dynamics 365 licensing plans differ from Dynamics CRM Online?

Dynamics CRM Online licensing offered several different license options.  Customers could choose between Enterprise, Professional, Basic, Essential, and Self-Service licenses.  Until the recent addition of the field service and project service modules, these licenses gave users differing levels of access to the Sales, Marketing and Customer Service modules. Those are the modules which have traditionally been part of the core CRM functionality.  Two different versions of Dynamics 365 will be available. Dynamics 365 Enterprise becomes available for purchase on November 1, 2016.   Dynamics 365 Enterprise Edition includes the traditional core CRM functionality, including the field and project service modules.  In Dynamics 365 these CRM modules are now referred to as “apps”.  These apps can be purchased individually or as part of a plan.  If you only need traditional CRM sales and marketing functionality you could purchase just the Dynamics 365 Sales app.  If you need the traditional CRM service functionality you can purchase the Dynamics 365 Customer Service app.   Also available is the Dynamics 365 Operations app.  This app has traditionally been know as Microsoft Dynamics AX.  It offers a wide range of enterprise resource planning functionality.  Customers requiring access to more than one app have the ability to choose between two different plans. Plan 1 includes all of the traditional CRM functionality, including field and project service.  Plan 2 includes everything in Plan 1, plus Dynamics 365 Operations.  All of these apps and plans have 2 types of licenses, as opposed to the 5 licenses available previously.  For users who only need minimal access to the system, for things like knowledge sharing and BI access, customers can purchase the team member license.  Users who need more than this light access, will require a full license.

What are the benefits of transitioning to Dynamics 365?

  • The primary benefit of transitioning to Dynamics 365 is access to all of the latest features available in this new release. Here is a list of just a few of the new features:
  • Enhancements to the project service module including an integration with Microsoft Project client software
  • An all new business process flow and business rule visual designer with drag-and-drop functionality
  • The ability to launch workflows from business process flows
  • All new editable grid functionality which allows the user to perform inline editing of records in both the web and mobile clients
  • New Email Engagement functionality which allows you to see when your email has been opened, a link has been clicked, an attachment viewed or a reply received
  • The ability to set a reminder to follow-up if you don’t receive a reply or if the email is not opened
  • Relationship Insights analyzes your CRM and Exchange data to provide actionable knowledge about the strength of your customer relationships
  • Enhancements to the CRM App for Outlook including improved performance and support for on-line to on-line, on-prem to on-prem, and hybrid scenarios
  • Native integration between Dynamics 365 Enterprise CRM and Operations apps
  • Microsoft PowerApps and FLOW are new tools designed to allow customer to create “no-code” applications which can connect to multiple data sources, including Microsoft Dynamics 365

InterDyn BMI would be happy to answer any other questions that you may have regarding your specific situation.  Please reach out to your account manager or contact me directly by email: brian.dewulf@interdynbmi.com.

Help! I Created a User As My CRMService Account!

deathtostock_creative-community_columbus
By Ryan Talsma, CRM Product Manager

I wanted to take a minute and share a support case I recently had with a customer. Here’s an important thing to know about Microsoft CRM: You should never create the CRMService account as a user in CRM (this is not the same as the CRM Admin Account you used to run the install). When this customer called for help, I was able to witness what happens if you do. When the CRMService account is created as a user in CRM, you will be prompted with a license error and ALL users will be locked out of the organization that the user was added to (other orgs still work), so just deleting the user isn’t an option anymore.

While searching online, I found a couple suggestions that I would consider to be much “higher risk” solutions that I wouldn’t feel comfortable trying in a production environment. After testing a couple ideas, what I found to work best was:

  • Back up all organizations within the CRM environment you are working within.
  • Run a repair on CRM via add/remove programs.
  • Change all services running under CRMService to NT Authority/Network Service (or any other service account that is not a user in CRM).
  • Open CRM after the repair completes (you should be able to access the org again).
  • Delete the user in CRM that was created for CRMService.
  • Run the repair again and change the services back to CRMService.

Hopefully none of you will come across this, but by following these steps, you will be able to correct the situation to allow all users back into CRM.

This article is applicable to all versions of Microsoft CRM on premise.

About Ryan Talsma:
Ryan Talsma is the CRM Product Manager at InterDyn BMI, who has previously spent time as a functional, technical, and support consultant. Ryan has extensive experience in CRM installs, upgrades, IFD/AD FS implementations, JavaScript, workflows, solution architecture, and implementing Microsoft Dynamics CRM Online as well as On Premise. 

Issue Configuring Internet Facing Deployment in Dynamics CRM 2016

By Ryan Talsma, CRM Product Manager

In this post, and many yet to come, I’ll be blogging about Microsoft Dynamics CRM: technical information, usage, customer success stories and many more aspects of the product. I am the CRM Product Manager at InterDyn BMI and have spent over 4 years as a CRM technical and support consultant. During this time, I have done 20+ CRM installs/upgrades, working with systems all the way back to CRM 3.0.

I wanted to share an issue with deploying Microsoft CRM 2016 that I have come across a few times regarding the configuration of the Internet Facing Deployment (IFD). The issue occurs when you enter your external domain in the configuration wizard but Microsoft CRM does not allow you to click “Next”. As you can see in my screenshot below, the next button is still faded out and I cannot continue.

Since it was just a development environment, I did get this resolved the first time by doing a re-install of CRM (simply repairing CRM doesn’t work), although this is obviously a sub-optimal solution. However, a few weeks later I had it happen again in a production environment and I needed a better option. I was able to bypass the issue by configuring the IFD via PowerShell by simply running the commands below.

NOTE: Make sure you run them one at a time. Copying and pasting the entire block at once does not work. Also “dev” and “auth” are interchangeable with whatever DNS prefixes you are using:

Add-PSSnapin Microsoft.Crm.PowerShell
$ifd = Get-CrmSetting -SettingType “IfdSettings”
$ifd.Enabled = 1
$ifd.DiscoveryWebServiceRootDomain = ‘dev.yourdomainname.com’
$ifd.ExternalDomain = ‘https://auth.yourdomainname.com’
$ifd.OrganizationWebServiceRootDomain = ‘yourdomainname.com’
$ifd.WebApplicationRootDomain = ‘yourdomainname.com’
Set-CrmSetting $ifd

From here, you should be able to re-open your Deployment Manager and see that the IFD is now enabled and that you can navigate the wizard as needed.

This is a known issue by Microsoft. For additional information on how to configure the IFD via PowerShell, check out this TechNet article from Microsoft.

About Ryan Talsma:
Ryan Talsma is the CRM Product Manager at InterDyn BMI, who has previously spent time as a functional, technical, and support consultant. Ryan has extensive experience in CRM installs, upgrades, IFD/AD FS implementations, JavaScript, workflows, solution architecture, and implementing Microsoft Dynamics CRM Online as well as On Premise.