While I was working for one of my clients project, I needed to query some cnames for Crm IFD configurations.

After searching a while , I meet this powerfull tool . DnsPedia.Com

Hope this will help you too.

Microsoft Dynamics CRM SDK Version 5.0.8 released. You can download from MSDN library or  MSDN downloads

Updates in the SDK :

·         Updated binaries for the Portal developer toolkit and developer extensions. New features include support for authenticating portal users through the Windows Azure Access Control Service.

·         A new section describing developer integration and access to Microsoft Office 365.

·         Updated helper code for authentication to support more scenarios.

·         A new topic providing guidance for creating solution components that support multiple languages.

·         New samples for auditing, entity serialization, bulk delete and more.

·         See the complete list of new and updated samples and links to all  the new topics in the Release History on the first page.

You may have noted that Microsoft Dynamics CRM Sustained Engineering has released fixes for Internet Explorer-related memory leaks affecting our Microsoft CRM 2011 web client.  I’ve noticed that occasionally IE clients may still leak memory, eventually resulting in slower page load times or Out Of Memory errors, even though the latest CRM 2011 Update Rollup has been installed on your CRM servers.

Please note: Windows client servicing, via Windows Update or WSUS (Windows Server Update Services) + SCCM (System Center Configuration Manager) is also vital.  We’ve identified a fix that can potentially help with Internet Explorer memory leaks.  This fix was pushed through Windows Update via MS10-090: Cumulative security update for Internet Explorer.  It was released earlier this year and is likely already on your client machines.  HOWEVER: the fix I’m referencing here is registry enabled, so to receive the benefits of this fix, you need to add the registry keys mentioned in the associated Microsoft Knowledge Base article:

KB 975736: A memory leak occurs when you open a Web page that contains a circular reference in an iframe

The registry changes needed to activate the fix are described in this Knowledge Base article, and for large enterprises, these registry keys are generally pushed by GPO (Group Policy Objects) or other means.

In any case, I heartily recommend that you assure MS 10-090 is installed on your client machines and the KB 975736 fix enabled if you are still experiencing Internet Explorer-related memory leaks when the latest CRM 2011 Server Update Rollup (as of this writing, Update Rollup 5) is installed.

http://blogs.msdn.com/b/crminthefield/archive/2011/11/11/microsoft-dynamics-crm-2011-related-microsoft-windows-internet-explorer-memory-leaks-and-windows-microsoft-update.aspx

While I was importing one crm db from 4.0 in 2011 , I was getting error while publishing the reports and import progress stops itself.

After some investigation in error details , I realized there are custom reports in crm 4.0 db.

I had to take the backup the reports ( I assume you know how to do it by editing report in crm)

and ran the query below in crm 4.0 organization db. ( myorgname_MSCRM )

DELETE FROM [enterkon_MSCRM].[dbo].[ReportBase]      WHERE SignatureId is null  GO

So , this query deletes all custom reports and versions.

And finally you can import the db from 4.0 in to 2011 successfuly.

PS : the query is an UNSUPPORTED SOLUTION. Never forget to backup your db and reports.

Open a Windows PowerShell window with Administrative Rights.

PS > Add-PSSnapin Microsoft.Adfs.PowerShell

PS > Get-ADFSRelyingPartyTrust -Name:”relying_party“

PS > Set-ADFSRelyingPartyTrust -TargetName “your_relying_party_name” -TokenLifetime 7200

So this code set the session timeout as 12 Hours (7200 minutes )

Don’t forget to replace your_relying_party_name with the real name in your AD FS 2 Manager –>Relying Party Trusts

SQL server reporting services can be configured in two modes

• Native mode
• SharePoint Integration mode

When reporting services are running in native mode, the reports will store on SQL server reporting server. When user sends a request for report the response comes from Report Server in SQL Server.

When reporting services running in SharePoint integration mode, SharePoint gets the reports from server via web service to end users.

Installation Instructions

SQL Server 2008 R2 Installation instructions to enable reporting services in SharePoint integration mode.

1. Select the SQL Server Feature Installation option from SQL Server 2008 R2 setup page

2. On the features selection page, Select Database Engine Services,Reporting Services then click Next

3. In Server Configuration page enter appropriate credentials and click Next

Note: SharePoint 2010 products in farm configuration require domain accounts     for service configurations.

4. On Reporting Services Configuration page, select Install SharePoint integrated mode default configuration and say finish.

Configuration steps on Report Server

After Setup is finished, you can verify that installation by connecting to the report server. You can test by browsing to /reportserver”>http://<your server name>/reportserver

1. Open the Reporting Services Configuration Manager from Configuration tools

2. Select the report server instance that you installed in SharePoint Integration mode

3. Configure the web service URL and test whether it is running fine or not. We are going to use this url in SharePoint Administration tool

4. Make sure your database is using SharePoint Integration Mode

Configuration Steps on SharePoint Server

if the reporting service for sharepoint add-in is not installed on your server ,plz download and install it here ( http://www.microsoft.com/download/en/details.aspx?id=622 )

1. Open the SharePoint Central Administration toll and the click General Application Settings

2. Click on Reporting Services Integration link under Reporting Services.

Enter the Reporting server web services URL that you configured earlier in the  Web Services URL box. Enter the authentication mode that you are using and credentials in the respective box then click ok

3. Upload the rdl files (SQL report files) to document library in SharePoint. If the configuration is successful then you should be able to see the SQL server Report in SharePoint 2010 as follows

resource

I am sure you can find lats of good things in here

Cheers,

While configuring Claims-based authentication in Deployment Manager , error message box appeared.It may because of the length of SSL Cetificate name.If it’s longer than 128 chars , the Deployment Manager can not write it to the MSCRM_Config database.
Here is the solution and worked for me.But you should know that the solution is unsupported :
Run the query for MSCRM_CONFIG database .This query updates the Certificates table and its schema:

ALTER TABLE Certificates ALTER COLUMN Name NVARCHAR(256);
UPDATE   MSCRM_CONFIG.dbo.ConfigurationMetadata

SET   ConfigurationMetadataXml =     REPLACE(      CAST(ConfigurationMetadataXml AS NVARCHAR(MAX)),

‘<Column Name=”Name”><Description>Name of the Certificate</Description><Type>nvarchar</Type><Length>128</Length>’,

‘<Column Name=”Name”><Description>Name of the Certificate</Description><Type>nvarchar</Type><Length>256</Length>’     );