If you were not able to attend Convergence 2007 last week in San Diego, sit back and watch the Satya's keynote....

http://metahost.origindigital.com/microsoft/20070312/convergence_20070312_500.asx

Microsoft have posted a new version (Rev. 1.1) of the Microsoft Dynamics CRM 3.0 Remediation Instructions for 2007 Daylight Saving Time Changes to the Microsoft Download Center.  THIS IS A DOCUMENTATION UPDATE ONLY.  Please note these changes:

 

Summary of updates:

1.       OLEDB TimeOut registry setting marked with increased importance as we have seen this be our number one support issue.

2.       Local Admin rights necessary and you must be logged in as the actual CRM client user  when installing client-side 925874

3.       Information on if you need to install DST updates if users, resources, sites, computers are in a time zone not affected.

4.       Unmarking Tasks and Appointments when you run 932984 if you have already moved them manually, or with the Outlook or Exchange tool called out with more importance.

5.       Addition of stored procs and tables installed with server-side 925874.

6.       CRM Connector issue identified in the 1 hr before DST start goes into effect.

7.       4 known reasons why you may receive error message “Failure : SDK*Exception An unexpected error occurred.” in the log file after you run wizard.

8.       More information on how the Wizard identifies records for possible DST updates.

9.       Section on ways to verify  925874 and 932984 worked.

10.   Steps on how to verify users are in the correct PrivUserGroup when they run or install the wizard or update.

Excitement is growing, with less than a week to go for the annual Microsoft Dynamics conference.

I will be there - so be sure to say Hi if you see me.

Microsoft CRM can provide a great capability to formally record user requests/issues in a structured way.

Create a custom entity - 'Change Request'; 'Suggestion'; 'Feedback'; etc. add some attributes to categorise the way you want users to provide you with their requests/issues.

Now you have a great way to capture and analyse feedback in a structured way - and provide direct feedback to the users so they can view the responses/actions.

Much better than having 'unstructured' data via emails - or overloading the helpdesk with non technical issues.....