Archive

Archive for the ‘Microsoft Office’ Category

Microsoft Word – Remove Document Template

If you need to remove a document template embedded into your Microsoft Word document, then follow the quick steps below (written for MS Word 2016):

  • Go to File > Options
  • Select Add-ins

MSWordManageOptions

  • In the Manage option set, select Templates, click Go

Now you will be shown the following screen:

MSWordTemplatesAndAdd-ins

 

Remove/Clear the Document template text area (020140918.dotx as shown in my example above) and click OK.

Hope that helps?

Greg Olsen
YellowDuckGuy

Advertisements

Microsoft Dynamics CRM – Outlook Tracking Emails Warning

August 18, 2015 Leave a comment

You can use Microsoft Dynamics CRM for Outlook (add-on to Microsoft Outlook) to track email, contacts, tasks, and appointments. When you use the track option in Microsoft Outlook to track an email message, contact, task, or appointment record, a copy of that record is saved as an activity in Microsoft Dynamics CRM and synchronised with the Outlook record. They are now linked. You can now view and edit that record in Outlook or CRM. If you have Outlook on your laptop or tablet etc, you can view that same tracked record.

Tracking records in CRM for Outlook is a manual process.  Therefore, CRM gives you the ability to keep your personal Outlook records separate from your CRM records. You don’t want your email to your wife about what’s for tea tonight ending up in your CRM system!

So tracking emails in CRM from Outlook is a great feature. However if not set up correctly, you could run into issues. Some of us have multiple email addresses or CRM organisations we manage or maintain, therefore keeping these all separate at times on one device can be a challenge, especially if you perform demos or testing multiple CRM systems.

So what do you do when you receive the following warning when setting up Outlook, possibly from an existing configuration? Keep reading.

To track emails and perform synchronization, your Outlook email address should be the same as your email address in Microsoft Dynamics CRM

The error message will be displayed as:

Outlook Message - Track Email

 

The scenario I am normally faced with is because the email address I am using is different from the email address of my CRM organisation.  The simple fix is to update your associated email address in CRM on the user record and Approve the email address.  You may find if your tracking of email is not working, approving the email may fix your tracking issue as well. Once your email address is updated in CRM, use the Approve Email (found on the command bar in CRM 2013 and 2015) to accept the email change and allow CRM to process emails using this address.

To note, you may also see this error message if you are configuring Microsoft Dynamics CRM for Outlook, but you don’t have an Outlook email address, or you haven’t set the primary email address field in CRM.

Microsoft Dynamics CRM–Support with Windows 10, Edge and Office 2016

August 15, 2015 Leave a comment

A lot of us now have moved onto Windows 10 and enjoying the new operating system, well personally I can say I am. This blog post will reference another blog post on the Microsoft Dynamics CRM Support Blog regarding CRM support with Windows 10, the new Edge Browser and Office 2016.

In summary:

All Dynamics CRM releases including CRM 2011, CRM 2013, and CRM 2015 currently support Windows 10 for use with the web client. The supported browser is Internet Explorer 11.

Support of Microsoft Dynamics CRM 2015 on Edge browser will be available for CRM 2015 with Update 0.2 (7.0.2) and Update 1.1 (7.1.1) in September.

Support with Microsoft Dynamics CRM 2013 will be introduced in Update Rollup 4 for Service Pack 1 (6.1.4)

For more information, head along to the URL below:

https://community.dynamics.com/crm/b/dynamicscrmsupportblog/archive/2015/07/10/dynamics-crm-support-with-windows-10-edge-browser-and-office-2016

Greg Olsen
YellowDuckGuy

Office 365 – Clean up your AD with IdFix before Migrating

September 16, 2014 Leave a comment

There is a handy tool from Microsoft called IdFix, which helps you clean up your On-Premises Active Directory (AD) before you synchronise or migrate it to Office 365 i.e. into the cloud. IdFix will cleverly identify errors such as duplicates and formatting problems in your On-Premises Active Directory before you begin the migration to Office 365. I recommend you run this as a prerequisite step before you start your migration to Office 365.

You can download the tool directly from Microsoft: IdFix DirSync Error Remediation Tool.  I have put a copy of this for future purposes here.

 

The Guide

 

Before I get any further, I would like to mention that you also get a guide with the tool download. It is called the IdFix – Directory Error Remediation Guide. You can download version 1.07 of the guide directly from here. Therefore I won’t mention the software and hardware requirements of the tool, I recommend you read the guide for this information. The tool is aimed at IT Administrators.

SupportDocTitle

 

Using IdFix

 

Once you launch the tool (I am currently using version 1.07), IdFix will search your On-Premises Active Directory for any objects which do not conform to Office 365. 

IdFixTool

After IdFix completes the query, you will get an object count in the status bar at the bottom, as shown below.

IdFixTool2

Like my example, if there are no errors in your directory (cool, I’m good to go), you can go ahead and synchronise your On-Premises Active Directory with Office 365. If there are errors in your directory, it is recommended that you go through each one and fix them before you synchronise to Office 365. You can fix them directory into your On-Premises Active Directory first and then do another query in IdFix to see your issue has gone.  It’s not mandatory to fix the errors before migrating to Office 365, but I would recommend you do. This allows for your Office 365 tenant to be a clean one from day 1.  If you are to fix an error, you will need to agree with the suggested change in the UPDATE column (check this to see what the issue is first), and then in the ACTION column select what you want IdFix to do to implement the change and then click Apply. Note: Once you hit Apply, IdFix will update your Active Directory immediately. So make sure you are aware of what changes are going to take place. 

The IdFix – Directory Error Remediation Guide has the following ACTION options documented. These are available from the ACTION drop down list:

·COMPLETE – The original value is acceptable and should not be changed despite being identified as being in an error state. For example, two users may have a proxy Address identified as duplicate. Only one can use the value for mail delivery. The user with the correct value should be marked as COMPLETE, while the other user is marked as REMOVE.

·REMOVE – The attribute value will be cleared from the source object. In the case of a multi-valued attribute; e.g. proxy Addresses, only the individual value shown will be cleared.

·EDIT – The information in the UPDATE column will be used to modify the attribute value for the selected object. In many cases, a valid update value has been predetermined. In these cases, you can mark the ACTION as EDIT and go on to the next error. If the predetermined update value is not desired, you can manually input the new value.

·UNDO – This value is only shown if the user has loaded a previously saved Update file. The sole operation that can be executed is to restore the original value.

·FAIL – This value is only shown if an update value has an unknown conflict with the directory rules. In this case, you may attempt to edit the value again. It may be necessary to analyse the values in the object using ADSIEDIT.

Note: on empty ACTION – Only errors with a customer selected Action will be considered for update. To reiterate; unless a specific choice is made IdFix will not perform any operation on the error.

If you would like to know more about the tool IdFix, I suggest you read the guide first before running the tool. The guide has everything you need to know. You should find the tool straight-forward to use.

If you have any comments or feedback on the tool IdFix, I would be keen to hear them. Simply add a comment below.

Greg Olsen
YellowDuckGuy

Microsoft Office 365 & Yammer – Leaders in Social Enterprise

A recent report published from Forrester has recognised Microsoft Office 365 + Yammer as Forrester Wave Leaders within the Enterprise Social Platforms. You can find the full report from the Forrester site here.

Microsoft Office 365 and Yammer can be clearly shown within the ‘Leaders’ area of this Forrester Wave illustration.

Office365 & Yammer Graph 2014

Another Key Takeaway from the report published by Forrester:

Enterprise social has become increasingly integrated with adjacent technologies, such
as document collaboration, portals, and line-of-business applications like customer
relationship management. To that end, vendors with significant leverage like IBM,
Microsoft, and salesforce.com will become more dominant on customers’ shortlists.

For more information, you can read the report here.

Greg Olsen
YellowDuckGuy

Microsoft Dynamics CRM 2011 – Compatible with Office 2013 Preview

September 17, 2012 Leave a comment

There is a brief article which outlines the compatibility of CRM 2011 with Office 2013 Preview at the URL specified below.

Support with Microsoft Dynamics CRM 2011 and Microsoft Office 2013 Preview

URL: http://support.microsoft.com/kb/2744957

Microsoft Dynamics CRM 2011 with Update Rollup 10 is compatible with Microsoft Office 2013 Preview. See the full compatibility list here for CRM.

System Requirements for installing Microsoft Office 2013

  • 1GHZ or greater x86/x64 processor
  • 1GB RAM for 32bit and 2GB for 64bit
  • 3.0Gb free hard disk space.
  • Supported O.S: Windows 7, Windows 8, Windows Server 2008 R2 or Windows Server 2012.
  • Browser: Microsoft Internet Explorer 8, 9, or 10; Mozilla Firefox 10.x or a later version; Apple Safari 5; or Google Chrome 17.x.
  • Graphics: Directx10 graphics card /1024×576 resolution

Office2013

Greg Olsen
YellowDuckGuy

Microsoft Dynamics CRM 2011 – Error When Browsing Discovery.svc Service

February 3, 2012 4 comments

Today I had to resolve a customer issue where the Dynamics CRM 2011 for Outlook Configuration Wizard could not find the CRM 2011 server and the CRM server did exist on the domain.

outlook_crm_error

I was connecting Microsoft Outlook 2007 to CRM 2011 via the installed add-in Microsoft Dynamics CRM 2011 for Outlook.

My list of areas to troubleshoot this issue was as follows:

  • Check CRM 2011 server is running ok. Can I browse it from the CRM Server?
  • Check I can ping the CRM server from the Outlook client PC
  • Check I can browse to CRM from the web browser on the Outlook client PC
  • Check I can resolve the Discovery.svc service. CRM for Outlook Configuration tool uses this.
  • Check the registry settings for the Configuration settings of CRM for Outlook

The Issue

Going through this list I found I could not resolve the Discovery.svc service from the Outlook client PC. You should be able to resolve the Discovery.svc service using the following URL. http://%5Byourcrmserver%5D/XRMServices/2011/Discovery.svc

You should see a page similar to below when you can successfully render the Discovery Service.

Discovery.svc - Now Renders

So I thought I had a possible IIS issue as I couldn’t render the service on the CRM server as well. I decided to check the Event Viewer first for any clues. Below is the error message I received.

WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/63835064
Exception: System.ServiceModel.ServiceActivationException: The service ‘/XRMServices/2011/Discovery.svc’ cannot be activated due to an exception during compilation.  The exception message is: This collection already contains an address with scheme http.  There can be at most one address per scheme in this collection. If your service is being hosted in IIS you can fix the problem by setting ‘system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled’ to true or specifying ‘system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters’.
Parameter name: item. —> System.ArgumentException: This collection already contains an address with scheme http.  There can be at most one address per scheme in this collection. If your service is being hosted in IIS you can fix the problem by setting ‘system.serviceModel/serviceHostingEnvironment/multipleSiteBindingsEnabled’ to true or specifying ‘system.serviceModel/serviceHostingEnvironment/baseAddressPrefixFilters’.
Parameter name: item
at System.ServiceModel.UriSchemeKeyedCollection.InsertItem(Int32 index, Uri item)
at System.Collections.Generic.SynchronizedCollection`1.Add(T item)
at System.ServiceModel.UriSchemeKeyedCollection..ctor(Uri[] addresses)
at System.ServiceModel.ServiceHost..ctor(Type serviceType, Uri[] baseAddresses)
at Microsoft.Crm.Sdk.V5.DiscoveryServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService(String normalizedVirtualPath)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
— End of inner exception stack trace —
at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
Process Name: w3wp
Process ID: 4116

    From this error message it seems their is a http bindings issue within IIS. Then it came to me! One of our infrastructure guys had created another port binding for CRM to be on port 80 for some other unrelated testing.

Resolution

Therefore to resolve this I had to remove the extra http binding in the Microsoft Dynamics CRM website within IIS.

To change or investigate your site bindings, click on Bindings… under Edit Site in IIS as shown below.

Discovery.svc - IIS Bindings

You should only have one http binding in the list as shown below. Note: I have removed the binding which was causing the problem in the image below.

Discovery.svc - IIS Bindings - Only 1

Its possible to have multiple http bindings, but you will need to change some web.config values which contain multipleSiteBindingsEnabled and set it to true. See the error message earlier for more information.

Hope that helps!

Greg Olsen
Yellow Duck Guy