Recently i had requirements to install rollup updates 17 on CRM 2011 Server and related components. I am sharing my scenario and i hope it will help you to plan or install your rollup updates 17 on Dynamics CRM 2011.

Current Installed Rollup Versions:

1. Microsoft Dynamics CRM 2011 Server VWCRM2011:5555

  • Current installed build version number on CRM Server is 5.0.9690.2839 which is rollup update 11.

CRM 2011 Version number

Read the rest of this entry »

Recently i was applying rollup 17 updates to Dynamics CRM 2011 server and i got this error message while installation of SRS Data Connector for reporting services. “KB2600640 is not installed on this computer in CRM 2011″.

Basically it complains about installing the Update Rollup 6. My rollup update version for SRS data connector was older than Rollup 6 and i have to install rollup updates 6 before to install rollup updates 17.

http://support.microsoft.com/kb/2600640?wa=wsignin1.0

http://www.microsoft.com/en-us/download/details.aspx?id=28712

If you like this post please click LIKE and visit my sponsors thanks !!

Tags: , , ,

admin on April 16th, 2014

Below is a list of Dynamics CRM Build and Version numbers as a quick reference.

Version Build Number Release Date (DD/MM/YYYY) KB Articles: SDK Version
RC 05.00.9688.53 -
RTM 05.00.9688.583 16/02/2011
Update Rollup 1 05.00.9688.1045 07/04/2011 KB2466084
Update Rollup 2 05.00.9688.1155 06/06/2011 KB2466086
Update Rollup 3 05.00.9688.1244 26/07/2011 KB2547347 5.0.5
Update Rollup 4 05.00.9688.1450 19/09/2011 KB2556167
Update Rollup 5 05.00.9688.1533 20/10/2011 KB2567454 5.0.7
5.0.8
Update Rollup 6 05.00.9689.1985
05.00.9690.1992
12/01/2012
20/01/2012
KB2600640 5.0.9
Update Rollup 7 05.00.9690.2165 22/03/2012 KB2600643 5.0.10
Update Rollup 8 05.00.9690.2243 03/05/2012 KB2600644
Update Rollup 9 Cancelled - -
Update Rollup 10 05.00.9690.2730
05.00.9690.2740
16/08/2012
04/10/2012
KB2710577 5.0.12
Update Rollup 11 05.00.9690.2835
05.00.9690.2838
11/10/2012
23/10/2012
KB2739504
Critical Update for Update Rollup 11 05.00.9690.2903 7/26/2013 KB2855319
Update Rollup 12
(OnPremise / v2)
05.00.9690.3218/
05.00.9690.3233/
05.00.9690.3236
07/01/2013
30/01/2013
KB2795627 5.0.14
CRM Online “Polaris” (UR12+) 05.00.9690.3233 13/01/2013 N/A 5.0.14
Update Rollup 13 05.00.9690.3448 03/26/2013 KB2791312 5.0.15
Update Rollup 14 05.00.9690.3557 07/13/2013 KB2849744 5.0.16
Update Rollup 15 05.00.9690.3731 10/08/2013 KB2843571 5.0.17
Update Rollup 15 v2 5.0.9690.3739 10/08/2013 KB2843571 5.0.17
Update Rollup 16 05.00.9690.3911 22/01/2014 KB2872369 5.0.17
Update Rollup 17 5.0.9690.4150 12/05/2014 KB2915687 5.0.17

 

If you like this post please click LIKE and visit my sponsors thanks !!

Tags: , , ,

admin on March 22nd, 2014

Scenario 1 (CRM and ADFS installation on same box)

 

Basic requirements

One Public IP is needed

One SSL Certificate is needed (wild card certificate preferred)

ADFS should use default website port 80 and SSL port 443 on IIS

CRM could use port 5555 and SSL port 444 on IIS

DNS need to be configured on the Domain Controller machine under the public domain lookup zone. Following are the A records for proper CRM URL resolution

  1. ADFS Server URL(External Domain)
  2. Dev URL(CRM Discovery Service end point)
  3. Auth URL(CRM IFD Federation end point)
  4. Org URL(Organization of CRM)
  5. Internal  CRM URL(CRM Claim Federation end point)

Read the rest of this entry »

Tags: , , , ,

admin on February 22nd, 2014

I found this interesting article written by powerobjects, i thought it would worth of sharing with my readers.

Email Tracking
It may not be suggested to keep employees as contacts in a customer-focused implementation of Microsoft Dynamics CRM because of the perceived problem of email tracing from Outlook. When you track an email from Outlook, it will track the email against the CRM record of everybody on the email (either sender or recipients). When you have an employee as a contact in CRM, that contact record will show all the email the employee ever sent or received under Closed Activities.

 

Email Duplication

Database administrators might be looking at this kind of email tracking with concern about how often the same email is being duplicated. When an email is tracked in CRM, it is NOT duplicated for each contact it is tracked against. A single email is merely ‘related’ to each contact. However, there is increased potential for duplicate records when you have employees in CRM. That is because when an employee sends and email to another employee and tracks the email, it may be tracked again when the 2nd employee receives the email.

If You MUST Track Employees in CRM

If you must track employees, there are some options for you to avoid the email tracking conflicts described above.

Option 1 – Use Contacts but Create Email Aliases
Use the contact record for employees, but create an email alias for each employee that is used only for CRM. Since CRM uses an exact match on email address in order to identify which contact to track email against, an alias will fool it. The email will not be tracked against the employee UNLESS it is Set Regarding the employee contact directly.

Option 2 – Use Users
Some organizations are uncomfortable with a single person having two records (Contact and User). To resolve this, they enter all employees (even non-Users) into CRM as users and then deactivate the users who do not need licenses. If choosing this route, employee lookups would need to be modified in order to include inactive records. This may make some tasks difficult, such as updating the employee records, either with workflow or manually. Since they are inactive, then they would be read-only.

Option 3 – Creating a Custom Entity
By creating a custom entity for employees, it gives you the flexibility to edit the records easily, but also to NOT have to create an email alias. Custom entities can be email-enabled so that email notifications can be sent manually or via workflow.

Final Thoughts

In considering how best to store employees in Microsoft Dynamics CRM, don’t forget to consider security. Determine who needs to access (view, edit, and delete) employee records, and who does not need to access. If you repurpose contacts or users for employees, you will have less control over security because your security model must support multiple uses of the same entity. By creating a custom entity for employees, you can control the rights separately.

 

Reference:

http://www.powerobjects.com/blog/2013/04/03/options-storing-employees-in-crm-2011/

If you like this post please click LIKE and visit my sponsors thanks !!!

Tags: , , ,