Moving Active Directory AD to a New Domain Controller DC

Since I don’t have to do this very often, but always seem to forget how to transfer the Schema Masterand Domain Naming Master, I decided to write it down, when it came up again as I transferred all the roles to my Windows 2012 server.

The following three FSMO roles can be migrated from Active Directory Users and Computers. Right mouse click on the domain and select Operations Masters. There is one tab for each of the three FSMO roles:

RID Pool Manager
Infrastructure Master

The following FSMO role can be transfered from Active Directory Domains and Trusts. Right mouse click on Active Directory Domains and Trusts, and select Operations Master.:

Domain Naming Master

For the Schema Master FSMO role, you first need to register a dll by executing the following command (Note: This only needs to be done once from an elevated command prompt.):

c:\> regsvr32 schmmgmt.dll

Then, you can add the Active Directory Schema Snap-In to a Microsoft Management Console (MMC). With the Snap-In added, ensure that the targeted domain controller is the one that you want to transfer the Schema Master role to. To change it, right mouse click on Active Directory Schema, under Console Root, and select Change Active Directory Domain Controller.. to select the domain controler you want to transfer the role to. Once that is done, right mouse click on Active Directory Schema, and select Operations Master to change the role.

If you do not have a different domain controller targeted, you will get the following message:

The current Active Directory Domain Controller is the Operations Master. To transfer the Operations Master to a different DC, you need to target Active Directory Schema to that DC.

And when you switch the target domain controller, you get the following, which is okay for what we want to do.:

Active Directory Schema snap-in is not connected to the schema operations master. You will not be able to permform any changes. Schema modification can only be made on the schema FSMO holder.

Fatal error: Cannot redeclare wpb_getImageBySize() (previously declared in plugins/js_composer/include/helpers/helpers.php

WPBakery Install Receives the Error: fatal error: Cannot redeclare wpb_getImageBySize() 

Fatal error: Cannot redeclare wpb_getImageBySize() (previously declared in /srv/www/vhosts/ in /srv/www/vhosts/ line 111

When installing the WPBakery plugin you receive the above error after trying to activate the plugin. 

The Fix

The issue is easily fixed by installing one of the default themes from WordPress. Activating it. Then returning to the plugins and activating the WPBakery Visual Composer.

DNN (dotnetnuke) Active Forum Module Control Panel a critical error has occurred

Error when opening the DNN Active Forum Module Control Panel

When you attempt to open the forum module Control Panel, you receive load error that says a critical error has occurred. Upon looking at the log files for the website within DNN, you’ll notice that the related error message looks something like this.

DefaultDataProvider:DotNetNuke.Data.SqlDataProvider, DotNetNuke
UserAgent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/600.6.3 (KHTML, like Gecko) Version/8.0.6 Safari/600.6.3
Message:Object reference not set to an instance of an object.
InnerMessage:Object reference not set to an instance of an object.
at DotNetNuke.Modules.ActiveForums.Controls.Callback.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)


The Fix

It is good practice to ensure that you have the latest version of the DotNetNuke forum module on your website. Especially if you are using the later versions of DNN.  Currently the module project has been moved into an open source project on GitHub. The latest version can be found here:


 fixing the error

 you need to ensure that the web.config file also includes the following reference.

        <section name=”cryptography” requirePermission=”false” type=”DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke” />



    <cryptography defaultProvider=”CoreCryptographyProvider”>


        <clear />

        <add name=”CoreCryptographyProvider” type=”DotNetNuke.Services.Cryptography.CoreCryptographyProvider, DotNetNuke” providerPath=”~\Providers\CryptographyProviders\CoreCryptographyProvider\” />



 Take note of where this is found in the web can feed file below.

Screenshot 2015 06 27 17 13 53



Google Analytics API Access V3

Accessing your Google Analytic Data via API

To allow a third party module or application to view and display your Google Analytics data for your website. You need to get a few things organised.

1. You need to have a Google Analytic account with your website registered.

Go to:   and follow their instructions to set up your URL under an account that you can manage and access with Admin permissions. We are not going to go through these steps here as it is a given that you will have this. Seek help from Google if you can’t manage.


2. Set up an API for your Google Analytics Account at the Google Developers Portal.

Go to:  and login with your account.

To get started using Google Analytics API, you need to first create or select a project in the Google Developers Console and enable the API. Using this link guides you through the process and activates the Google Analytics API automatically.

Alternatively, you can activate the Google Analytics API yourself in the Developers Console by doing the following:

  1. Go to the Google Developers Console.
  2. Select a project, or create a new one.
  3. In the sidebar on the left, expand APIs & auth. Next, click APIs. Select the Enabled APIs link in the API section to see a list of all your enabled APIs. Make sure that the Google Analytics API is on the list of enabled APIs. If you have not enabled it, select the API from the list of APIs, then select the Enable API button for the API.
     Screenshot 2015 07 07 00 53 20
  4. In the sidebar on the left, select Credentials.
     Screenshot 2015 07 07 00 54 06

In either case, you end up on the Credentials page and can create your project’s credentials from here.

Create a client ID

From the Credentials page, click Create new Client ID under the OAuth heading to create your OAuth 2.0 credentials.

  1. For the APPLICATION TYPE select Service account.
  2. Click Create Client ID.
  3. For the KEY TYPE select P12 key. (The system will download a .P12 file. You will need this file to upload to the module)
  4. A dialog box appears. To proceed, click Okay, got it.


3. Add service account to Google Analytics account

The newly created service account will have an email address, <projectId>-<uniqueId>; Use this email address to add a user to the Google analytics account you want to access via the API. For this tutorial only Read & Analyzepermissions are needed.

Select User Management (in the Analytics Admin)

Screenshot 2015 07 07 00 49 39

Enter the weird email address from the API credentials step above to give Read & Analyze permissions.

Screenshot 2015 07 07 00 51 16


In Summary

  1. You have created a Google Developer Account.
  2. Created an API and Given Permission to “Analytics API”
  3. You have Downloaded a P12 Credentials file.
  4. You have Authorised the associated weird google email address from the P12 account to have read permissions on your Analytics Account.

If you get all that right, then the module we use, will work to access your Google Analytics data from within your module.


Zendesk to CRM 2015 and Microsoft Dynamics 365 Integration

Installing the Zendesk to CRM 2015 or Dynamics 365 integration

These instruction have been updated from the Zendesk instructions provided here:


They use a combination of the original processes that Zendesk have created originally for CRM 2011 and that worked on Pre SP1 versions of CRM 2013. The packages referenced have been update by InteractiveWebs to work with CRM 2013 Post SP1 and CRM 2015 (technically all versions but we recommend post SP 0.1)


Instillation of the CRM Solution

Install the CRM Managed Solution as you would any other CRM solution.

Download the managed solution for CRM 2015


Click on Import

Screenshot 2015 06 18 17 45 23

Chose File

Screenshot 2015 06 18 17 47 09


Select the Managed CRM package – Click Next

Screenshot 2015 06 18 17 49 51

Click Next

Screenshot 2015 06 18 17 51 30


Leave the Enable any SDK ticked, and click on Import

Screenshot 2015 06 19 23 39 37


Allow the Import to take place

Screenshot 2015 06 19 23 40 43


Click on Close

Screenshot 2015 06 19 23 42 16


On Completion, Click “Publish All Customisations”.

Screenshot 2015 06 19 23 43 04


Update Security Roles

In the CRM menu, select Settings / Security

Screenshot 2015 06 19 23 45 15


Select the User that you wish to use to bring in Zendesk Integration Items. We are using in this example the Administrator account, but it could be anyones account.

Then with the account loaded, select the additional item dropdown menu to the far right of the top level menu, selecting Manage Roles

Screenshot 2015 06 19 23 48 51


Select Zendesk Administrator

Screenshot 2015 06 19 23 50 18

There is also a Zendesk Read configuration setting. The Zendesk support site has details on how this can be used.




Screenshot 2015 06 19 23 47 22

Double Click on that name to load the account.


Configure Entity Mapping

In your browser, click on Refresh to reload the CRM page, and in turn the top level menu that has been updated after import for the Zendesk Solution.

In the CRM system, select Settings / Zen Entity Mappings

Screenshot 2015 06 19 23 54 49


Click + New

Screenshot 2015 06 19 23 55 47


The most typical setups are things like on a “Contact” entity, match the Zendesk ticket requester with the email address on the “Contact” record. But what if you wanted to match of the “Full Name” field instead in both systems?  Now you can by utilizing entity mappings.


  • Select the following items

    • Entity Name – This is the Microsoft Dynamics entity that you want the mapping applied to.
    • Zendesk Object – This is where you can select which object from Zendesk you’d like to pick your field from.
    • Zendesk Field – This will populate with values depending on your selection from Zendesk Object.
    • Entity Field – This is a list of fields associated to the selected Entity Name.  Pick which field you want to match to the Zendesk Field.Click “Save” to store the mapping. 
  • Click the ZD Entity Mapping tile to return to the page. 
  • Repeat steps 1-5 if you wish to add more mappings for additional Entities..


Here’s a list of the most common types of mappings:


  • Account/Organization Entity
    • Entity Name: “Account” or “Organization”
    • Zendesk Object: Organization
    • Zendesk Field: Name
    • Entity Field: Account Name
    • Contact/Lead Entity
      • Entity Name: “Contact” or “Lead”
      • Zendesk Object: User
      • Zendesk Field: EmailAddress
      • Entity Field: EmailAddress 1


Configure Zendesk Settings Page

In CRM Navigate to Settings / ZD Settings (Note that this one is not the ZD Personal Settings Menu Item).

NOTE – This works best in Chrome – We found troubles with IE and Safari (not our work)!


Screenshot 2015 06 20 00 11 05

You now need to set up your Zendesk credentials so that the system can authenticate to the appropriate Zendesk instance.

To do so, navigate to Settings, then locate the Zendesk Settings->Settings title and click the title.

You will be presented with 4 sections:

  • Ticket view defaults  – global default settings for ticket views in the Zendesk ticket panel. 
    This sets the defaults at the account level, but can be overwritten by individual preferences by each user.
  • Filtering – sets the default values for filters in the Zendesk ticket panel.
  • Sorting – sets the default sort order for tickets in the Zendesk ticket panel.
  • Authentication – enter your Zendesk subdomain (make sure you specify HTTP vs. HTTPS if you have SSL enabled) and login credentials (you need administrator credentials). 
    This gives your Microsoft Dynamics CRM users read-only access to available tickets. To create or edit tickets from Microsoft Dynamics CRM, your Dynamics users must have a Zendesk license, and they will need to enter their own credentials (explained later in this article).  
  • Mapped record types – enables you to modify the data elements that display in a Zendesk user profile when a ticket is loaded. 
    You can choose from LeadContact, and Account. All fields are available, including custom fields.
  • Ticket-to-case mapping – identifies data items that should be mapped from standard Zendesk ticket fields into Microsoft Dynamics CRM cases. 
    The three Zendesk fields that are supported are StatusPriority, and Type.


Add Zendesk Ticket Grid

Now you are ready to add the Zendesk ticketing panel to any of the entity pages that you’ve configured mappings for. You need to repeat the steps below for each entity type you want the ticketing grid displayed on.

  1. In Microsoft Dynamics, navigate to the first entity where you want to add the ticketing grid. 
    For this example, we’ll refer to a Contact record.
  2. Select any contact in your list and navigate to the Form Editor.
  • In Dynamics 2015, highlight the More (…) tab(1) and select the option for Form(2) to start the form editor.Form2013-1.png
  • In Dynamics 2011, navigate to the Customize (1) tab and click on Form (2)Form2011-1.png
  • In the Form Editor, click the Insert tab (1), then click the Web Resource button (2).Form2013-2.png
  • In the Add Web Resource page, click the magnifying glass next to Web resource to find the Zendesk ticket grid (zd_/Pages/TicketGrid/TicketGrid.html).Form2013-3.png
  • In the next page, select the check box next to zd_/Pages/TicketGrid/TicketGrid.html, then click OK.
  • Back in the Add Web Resource dialog box you should see zd_/Pages/TicketGrid/TicketGrid.html in the Web resource field. Enter a Name and Label you can easily recognize (consider naming it Zendesk Ticket Panel). Check the box for Pass record object-type code and unique identifier as parameters.  
    Click OK. 
  • ou now have a Zendesk ticket panel in the form layout that you can drag anywhere you’d like on the page. You can even create a special subsection for it if you’d like.
  • After you place the panel, navigate to the Home tab, click Save, then click Publish
  • Refresh the contact page you had open and you should see the new Zendesk ticket panel where you placed it!  Form2013-5.png
  •  Repeat these steps for any other entities you have created mappings for.


Configuring InteractiiveWebs Zendesk to CRM 2015 or Dynamics 365 Web Service

Next you need to enable your CRM instance to use the InteractiveWebs Web Service that will connect Zendesk to your CRM instance either in the cloud, IFD or on premises.

If you have an IFD instance or a Microsoft Hosted Cloud

instance of CRM then go here:

If you have never registered with InteractieWebs then click on “Subscribe Now”

 Screenshot 2015 06 20 19 08 05

Fill in the form with the following details.

Username: Select a user name to use with our website.

Password: Select a password to use on our website

Email: Be sure to use a valid email address. We will not share or spam you, but for services we need this to be accurate.

First Name: Your First Name

Last Name: Your Last Name

CRM Address: This is the address of your CRM server in the following format: e.g..  You type “” (without the  “ “ ).

CRM Organization: You administrator can help with this, but in the example above it is “contoso” and is usually the word before the domain of your hosting environment.

You can contact us on the help link at the bottom of the page if you are not sure what you should type here.

Screenshot 2015 06 20 19 15 01


If you have an on premises CRM solution

you will need a custom version of the web service to host on your own servers. Contact us at our website:

and advise that you are after a custom web service for Zendesk to CRM 2015 integration. Advise us of:

1. The URL you use to access your CRM internally.

2. The Organisation name you use in CRM.

We can then provide you with a custom web service for $200 one off fee with no expiry date on the web service.


Zendesk Setup – Display of CRM Data

It is possible to display the user data from Microsoft CRM in the Zendesk tickets. To do this:

1. In Zendesk select Admin

2. Select Apps / Market Place and search the words – “Microsoft Dynamics”

3. Install the App – Microsoft Dynamics

Screenshot 2015 09 15 04 27 23

Under Manage – you should see the app installed:

Screenshot 2015 09 15 04 28 09

Installing this will allow you to select the “User Data Lookup” Feature that is explained in the next section below.

Screenshot 2015 09 15 04 29 03 – Found in the Extensions / CRM in Zendesk.


Setup Zendesk Settings

Now you will need to set up the Zendesk side of the integration.

To do this, you login to your Zendesk interface and Admin / Extensions 

Screenshot 2015 06 21 09 12 10

In Extensions you select CRM

Select Microsoft Dynamics CRM 2011 (For all versions of CRM including Dynamics 365)

Screenshot 2015 09 15 04 30 17

Select your hosting type

Screenshot 2015 09 15 04 30 36

If you have IFD or Microsoft Cloud Hosted Solution, select Cloud or IFD respectively

FOR CRM versions before Dynamics 365 (up to CRM 2016 pre SP1)

For the Web Service (having subscribed to the service) put in:  (note that this will only work if you have subscribed)

Screenshot 2015 09 15 04 31 03

For Dynamics 365 (or CRM versions after CRM 2016 SP1)

Because the SDK was updated for Dynamics 365 we have created a web service URL unique for later versions of Dynamics 365. Use the

URL: (note that this will only work if you have subscribed)


If you have an on-premise then select that and put in the URL of your web service that was supplied to you after contact InteractiveWebs for a custom solution.

All the other data for that page is per the instructions and help provided by Zendesk in their help pages found here:




If you have problems or questions, please feel free to contact us at: – We have a range of other integration products, including website to CRM integrations for forms, billing, kb, support and more.



DNN Blog Module 404 Error on Reading Post

When using DNN Blog Module you receive 404 page cannot be found error

The symptoms of this are fairly easy. When you click on the Read more link or the title of a blog that would normally take you to the full article of the blog. The page instead displays a 404 error.

DNN Blog 404

 If you explore the URL you will find that the URL references the blog title something like this: 

 take note that the URL does not end with the .aspx


The Cause

The URL of the blog post is being rewritten through the friendly URL settings within the later versions of DNN.

 DNN Friendly URL Settings

 the friendly URL settings can be found within: HOST /  ADVANCED SETTINGS / FRIENDLY URL SETTINGS

 and by default in the later versions of DNN are enabled.  The problem arises when the web.config file is missing a setting for the advanced URL rewriting.


 The Fix

 the fix is very easy and involves editing  the web.config file.

1. Take a backup of the web.config file for your site
2. Open the web.config file, and search for ‘urlformat’. You should find this in the section, like this:

<add name="DNNFriendlyUrl" type="DotNetNuke.Services.Url.FriendlyUrl.DNNFriendlyUrlProvider, DotNetNuke.HttpModules" includePageName="true" regexMatch="[^a-zA-Z0-9 _-]" urlFormat="humanfriendly" />


3. Change the urlFormat value to ‘advanced’, like this:

<add name="DNNFriendlyUrl" type="DotNetNuke.Services.Url.FriendlyUrl.DNNFriendlyUrlProvider, DotNetNuke.HttpModules" includePageName="true" regexMatch="[^a-zA-Z0-9 _-]" urlFormat="advanced" />

Microsoft CRM Solution Import Fields that are not valid were specified for the entity

While importing a solution to CRM 2011, CRM 2013, or CRM 2015 you receive an error 

Fields that are not valid were specified for the entity


The Cause

The cause of this is likely that one of the attributes that you are importing (from a dev environment) already exists in the CRM instance, but with a different attribute.

For Example:

  • In your Live Environment
  • Within Accounts, you create a new attribute called “Friendly Cusomter” and mark it TEXT 
  • Publish and all is well and good.
  • In you Dev Environment
  • Within Accounts, you create a new attribute called “Friendly Customer” and make it a PICK LIST


in other words, the same name for the attribute, but a different kind of field.

Then try to export from DEV and import to LIVE. You get the error.


The solution

You have to remove the conflicting fields from the destination (live in the example above) CRM system.

Microsoft gives you some help here, in the form of an XML dump file. What you need to do is open that file in something like DreamWeaver that has the ability to apply “Source Formatting”. This makes the file pretty to read. 


Ugly XML Dump file from CRM.png


CRM xml dump file in DreamWeaver.png

Then do a search for the text “errortext” and start clicking next / next till you get to some text with an attribute and an error message. 

In our case:

Screenshot 2015 04 29 21 52 24

<Cell ss:StyleID=”s137″ name=”ErrorText”>
<Data ss:Type=”String”>Attribute new_leasecustomer is a Picklist, but a Boolean type was specified.</Data>

This gives the name of the attribute at fault.

<Cell ss:StyleID=”s137″ name=”ErrorText”>
<Data ss:Type=”String”>Attribute new_leasecustomer is a Picklist, but a Boolean type was specified.</Data>

And the error on the import will tell you the Entity that it failed the import on. Again in this case it was the ACCOUNT entity.

So we just removed that attribute from any forms and views, then deleted the attribute (be sure that your live data is not relying on data entered here by users as you will loose it). Publish the entity. Then test the import again. 

CRM 2015 2013 find Dependencies for Managed Solution

How to Delete a Managed Solution in CRM 2013 or CRM 2015

Sometimes when you try to delete a managed Solution, there is an error message about the dependancies of the solution being in use.

CRM Cannot Delete Component

When you download the log file, you see some typical Microsoft Crap that really does nothing to help you.

Screenshot 2015 04 12 16 02 08

The only thing it does is to tell you that you can’t delete the component because it is being used in this case by two other components.

Now the hard part is finding the components that are using it.


Finding the Referenced Dependencies CRM 2015 Components

1. Work out the Solution Name. Navigate to CRM / Settings / Solutions – and read the exact Name of the Solution to be deleted. In this case it was “ZendeskCRM2011Connector

Deleting CRM Managed Solution


2. Login to your CRM Server and open the SQL database that matches the Organisation name being used in CRM.

3. Execute an SQL query against that database that reads.

=’Name of your Solution

(Replacing the Name of Your Solution) with the exact name of your solution, So in our case:


And it executes to give:

CRM Find GUID for Managed Soltuon

This gives you the GUID of the managed solution in the results area. In our example it is the: 3AC85885-F78B-47A3-BAB5-F8DE569B4EDD number at the bottom.

4. Now navigate to the following URL: 

https://YOUR CRM URL/tools/dependency/dependencyviewdialog.aspx?objectid=GUID&objecttype=7100&operationtype=dependenciesforuninstall


Replacing the “YOUR CRM URL” with the URL to your own CRM system.  and replace the GUID with the GUID retrieved from step 3 above. Thus the URL may look like this:


It will show a page that looks like this: 

Show Solution Dependencies CRM 2015


Which you can use to help you work out what to edit to remove the dependencies and delete the solution.

Thanks Microsoft for making something so easy so hard!



Setting up CRM 2015 on Windows 2012 R2 and SQL 2014 Stand Alone

Setting up CRM 2015 on a New Virtual Windows 2012 R2 with SQL 2014

Install the Following Components

  • Services
  1. Indexing Service (Windows Search Service
  2. IIS Admin
  3. World Wide Web Publishing
  • Windows Data Access Components MDAC 6.0
  • Microsoft ASP.NET


Windows Search Service

The following method is use to install the Windows Search Service on Windows 2012 R2. The search feature is launched form the Server Manger (which will start by default as login as an administrator).

Click Add Roles and Features

Windows 2012 Add Roles and Features



Screenshot 2015 03 22 16 15 03



Screenshot 2015 03 22 16 15 42



Screenshot 2015 03 22 16 16 41


Next (without selecting anything)

Screenshot 2015 03 22 16 17 44


With the Features, select Windows Search ServiceNext

Screenshot 2015 03 22 16 19 46


Select Install

Windows Search Service Feature


Select Close

Screenshot 2015 03 22 16 22 15


Run through the process again 

Click Add Roles and Features

Windows 2012 Add Roles and Features



Screenshot 2015 03 22 16 15 03



Screenshot 2015 03 22 16 15 42



Screenshot 2015 03 22 16 16 41


Next (without selecting anything)

Screenshot 2015 03 22 16 17 44


This time select the Web Server (IIS)

Screenshot 2015 03 23 18 09 39

When prompted select Add Features

Screenshot 2015 03 23 18 08 42

Select Next

Screenshot 2015 03 23 18 13 00


Screenshot 2015 03 23 18 13 15


Screenshot 2015 03 23 18 13 19


Screenshot 2015 03 23 18 13 36



Installing SQL Server

When installing the SQL server, the required features are almost the default features with the following two ticks.

1. Database Engine Service

2. Full-Text and Semantic Extractions for Search

 CRM 2013 SQL 2012 Requirements


Additional IIS Feature to Add for IIS

CRM will work much better with IIS Dynamic Compression. The install this you follow the normal Roles and Features install, and find the section for:

Web Server Role (IIS)

Second option: Under Server Manager click Add roles and features       

  • Click Next for Role-based or featured-based installation       
  • Select Server Roles       
  • Expand Web Server (IIS) role     
  •  Under Performance check the option for Dynamic Content Compression

IIS Dynamic Compression Feature

Click Next

This ensures that you can enable dynamic compression after install to ensure that performance is best.







CRM 2015 Extend Auto Logout Time in IFD

CRM 2015 and CRM 2016 IFD will Automatically Logout the user with a Message:

Your session in Microsoft Dynamics CRM is about to expire. To continue working, you must sin in again.

CRM 2015 Auto Logout

By Default this setting is 60 minutes, and the message will pop up around 20 minutes before logout.

Any unsaved changes will be lost as your session ends.


The Fix

To extend the automatic logout time in CRM 2015, we must extend the time set in ADFS 3.0 using the PowerShell command. First we need to know the name that was used to set up the Relying Party Trust in ADFS.

1. Open Server Manager and from the Tools menu select ADFS Management

ADFS Management

2. in AD FS management, open Relying Party Trusts and find the Display name for the CRM IFD Relying Party Trust

Screenshot 2015 04 03 17 30 58

In this case, we have called the Relying Party Trust – “CRM IFD Relying Party” as we keep things simple when we create things. Using the exact name for the title of the trust as we created it. But really it could be anything. One distinguishing feature is that the URL identifier is going to be optioning to the URL that displays in the browser window when you are in the process of login into your IFD CRM.

3. Start PowerShell

Screenshot 2015 04 03 17 35 57

4.  Check you have the correct name of the Relying Party Trust by typing the following command.

Get-ADFSRelyingPartyTrust -Name "relying_party"

Where you replace the “relying_party” with the name you identified in Step 2 above. In our case the command will be: 

Get-ADFSRelyingPartyTrust -Name “CRM IFD Relying Party


The result should look something like this if you get it correct.

Screenshot 2015 04 03 17 40 02

5. Not type the command to set the time you want to set for Auto Logout.

Set-ADFSRelyingPartyTrust -Targetname “CRM IFD Relying Party“ -TokenLifetime 720

(Again replacing the “CRM IFD Relying Party” with the name used on your system.)

Note: The 720 is time in minutes. 12 Hours in this case. You can change the value up and down as liked.

Set-ADFSRelyingPartyTrust -Targetname “CRM IFD Relying Party“ -TokenLifetime 720

Screenshot 2015 04 03 17 43 47

6. Close out the PowerShell and you are done.