!! Please note: This only applies to CTI Versions 5.30 and below !! 
!! Since Microsoft has changed the EULA of their WIF SDK we are now allowed to include all required files into our setups !!

All of our client products (Telephone Integration and DocumentsCorePack Client) need the WindowsIdentityFoundation Framework to be able to connect to CRM 2011.

Unfortunately the WIF Framework is not officially supported on WindowsXP by Microsoft, but there are 2 ways to make this work on a WindowsXP OS. 

When using per User licensing, it is mandatory to enable all users that should be licensed within CRM. It often occurs, that after installing the license via the License Manager, the below screen appears:

Figure 1: License Manager - Preview License

This is due to the fact, that the user (usually an admin), who is running the license-manager is not a licensed user at this point.

To enable this, specific users you will have to follow the below steps. 

This article explains the security roles that must be assigned to users that should be allowed to use our Add-Ons.  

When ordering licenses, you will be asked for the organisation unit name of your CRM system. This information is mandatory in order to create a license. Below, you can find a short description about how to get the necessary information for CRM 4.0 / CRM 2011.

Check the log textbox if the following statement is present (might be accomodated by a 401 exception).

Receiving a service unavailable response on a website usually indicates, that the application pool of the site is not running.

To solve this issue, open your InternetInformation Management and verify all required app pools are started.

Before you can upgrade your CRM 4 to 2011, you will need to uninstall all 3rd party addons and check that all buttons have been deleted. After the migration you can then install the latest version of each addon.
 
Should you have not done this, then it will be more complicated to get rid of the buttons and icons before you can install the CRM 2011 addons.

On a migrated organization, make sure the dcp/gc/ti security role migrated from CRM 4 is deleted.

This migrated role might interfere with the new setup and block the user from installing, because rights are checked wrongly.

That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com.

Basically there are two ways to activate debugging:

Solution 1: Activating debugging via the TI-Setup

Solution 2: Activating debugging on your Client via the Registry

This article contains a detailed guide on how to find out the version number for each mscrm-addons product in CRM 4.0.