http://crm.dynamics.com/en-us/roadmap
Link to the CRM 2011 Q2 Release preview Guide
http://crmpublish.blob.core.windows.net/docs/ReleasePreviewGuide.pdf
http://crm.dynamics.com/en-us/roadmap
Link to the CRM 2011 Q2 Release preview Guide
http://crmpublish.blob.core.windows.net/docs/ReleasePreviewGuide.pdf
I have run into several customers having internally users loginning each time using the companies external crm address. This can cause a bit of anger with your CRM users.
Each ADFS system has an internal URL. This URL can be found by openning up the ADFS Management Console or Using the CRM deployment manager. Using the CRM deployment manager, right click on CRM and hit properties, and navigate to the web tab. This is the internal URL.
The internal URL will pass the domain credentials (Kerboros) and not force the user to login each time. The CRM users will love you!
We see a ton of requests to get an email notification when an item (email, case etc) enters a CRM queue. CRM 2011 can handle this out of the box, no special tools required. The first thing to note is that we want to capture the creation of or the on change event for the queue item depending on your needs.
Inside a workflow, you can create a queue item. This will create the item in the queue from a workflow.
Queue Item is the record that is created when something is “moved” into a queue. This queue item record is actually a pointer to the item now in the queue. So, under set properties, select the queue the item is in, then select the queue item. Here’s I am referencing the queue GP and the actual case.
Next, I have another workflow called Queue Email Notification. This was created on the Entity Queue Item and is running under the option: Record fields change, on the field Queue (which is the name of the queue). This will capture the name of change of the Queue Item Record ( Hence inserting it into a queue).
Now you can send a user or team (direct) , email address (using a contact under a record, could be a distribution list as well). The workflow will have a send-email which will send something like “A new case has been created in the queue!” to the address created.
Also of note in CRM 2011, the new feature Record Dynamic URL. This gives you the URL for any entity! This used to be a plugin or ISV solution in past CRM versions. Now, by simply adding the Record Dynamics URL from the left the screen, the email will contain the complete URL Hyperlink to record.
We had a report that the CRM 2011 Outlook Client was returning more than 250 rows even though being limited by the CRM Administrator. It turns out that new pinning behavior in CRM 2011 Outlook client will override that settings. Let’s take a look..
In Outlook client, to the left of the view name, there is a small “Pushpin.” This pushpin controls whether the view “obeys” the User Setting for the number of records to be shown per view. Pushpin shown below in the un-pinned position:
When the pushpin is in the up position, it shows all available records that are based on the Users credentials regardless of the settings limitation. This allows the user to scroll thru all the records at one time. 
Although this can be handy when looking for a record lower in the alphabet, it there are ten’s of thousands of records, it could cause a real performance problem.
A customer had cleaned-up their user accounts in a effort to reduce their CRM Online license counts. They were experiencing random errors with scripts and onloads. The error message was:
Turns out CRM Online will let you disable the installing users (known as the billing administrator) account.
Simply re-enabling the deactivated user record returned system functionality to normal.
Once you deploy ADFS in a functional environment, the users will generally receive timeout requests, or requests to log back in, which can quickly become an issue within an 8 hour shift (480 minutes).
The solution is to set the ADFS Timeout. The ADFS timeout determines how long the claims token will live in the system before requiring a re-authentication or signin from the user. This can be set on the internal and external sides of ADFS. You will need to know the names of your ADFS relying party trusts.
To begin, open the ADFS Management Console:
Open the left hand navigation, expand relying parting trusts to find the display names:
Now, run the Windows Powershell from the machine with ADFS installed.
Now from the powershell, start the PSSnapin for ADFS:
Using the internal relying party trust name from the ADFS wizard above, enter this command where the dev.mydomain.com is the name of your internalcrm ADFS relying party trust. 
The last line of the results specific TokenLifetime will say how long the current time out is set.
Set the timeout to 480 for 8 hours ( minute increments). Example below is (240).
Now, set the timeout is set. You can follow the same steps to review or set your external timeout as well. It’s not a good security practice to set your external lifetime greater than 1 hour, as somebody who logins in remotely and forgets to logout, the session will be active until that timeout period is reached.
Troubleshooting a customer’s CRM 2011 setup failure, we almost were thinking it was machine account issue, so we rejoined the machine to domain last night. Sorry to say, that didn’t help.. So a little more digging…
It turns out that whomever installed SQL on that box (might be a VM image copy), failed to enter the service accounts when configuring SQL during the install, and decided to change the SQL services after the install.
The big issue with this approach is that SQL install creates the specific SPN’s for these accounts. So changing them after will work on the local box, but anything connecting via kerboros (not GP), will have issues trying to pass on the authentication.
The fix was:
setspn –A http/HostName Domain\Reporting Services Sevice Account
setspn –A http/HostName.domain.com Domain\Reporting Services Sevice Account
A quick restart of IIS, and now the CRM server installation can proceed. Enjoy!
When importing solutions from other systems (particularly advanced systems with tons of custom entities) you will receive an error message not allowing the import of the solution. If you download and open the error message, in the XML you will see that optionset values (picklists) fail. Even more specifically, left over optionsets from CRM 1.0/1.2 releases as well failing due to NULL labels.
The fix for this issue was a manually workaround deleting the values from the XML and reimporting the XML for the option set minus only. Thanks to Microsoft Support, we now have a hotfix available for those who cannot wait for the upcoming CRM 2011 Rollup 7. The KB Article #is 2651616 and has not yet been published at this time.
You will have to request this download from Microsoft support directly.