miercuri, 23 iunie 2010

Migrate Microsoft Dynamics CRM 3.0 from SQL Server 2000 to SQL Server 2005

I recently had to upgrade a Microsoft Dynamics CRM 3.0 to 4.0. The most easy was to do this, from my point of view is to use the upgrade provided by the Crm installation DVD. But in my case the situation was a bit more complicated. The CRM installation had as a data container Microsoft SQL Server 2000. The goal was to upgrade also the database to Microsoft SQL Server 2008.
But, as we know CRM 3.0 does not support SQL Server 2008 (although i tried to run it and it works. I uninstalled the default instance of Sql 2000, because CRM 3.0 works only with the default instance of the sql server, and installed SQL Server 2008. Before uninstalling Sql Server 2000 i made back-ups of MyOrganization_METABASE and MyOrganization_MSCRM. I restored these databases into SQL Server 2008 and it worked :). But i tested the CRM 3.0 only at surface level with sql server 2008 and i don't know whether is reliable to be used this way, or we should stick to the Microsoft recommendation )
So regarding my problem let's start with the database migration. I installed a fresh copy of Sql Server 2005 on the new machine that will be the CRM DataSource. It is compulsory that the machine is in the same domain as the CRM machine. Let's call the domain MyDomain.com because we will use it later in some steps in the migration process. I set also that the Sql server service will run under the domain admin account (recommended). As options i selected also the reporting services to be installed. On my Crm machine (where Sql Server 2000 was installed) i made back-ups of MyOrganization_METABASE and MyOrganization_MSCRM.

So here are the steps to migrate the databases.

1. Restore MyOrganization_METABASE and MyOrganization_MSCRM. on the new SQL Server
If the CRM jobs were not copied ,go to Crm machine, generate the jobs script and aplly the script to the new SQL Server. Here are the jobs that should have been coppied
  • Organization_Name.Update Contract States
  • MSCRM Identity Reseeding
  • MSCRM Index Reindexing
  • MSCRM Stored Procedures Priming
  • Start_Incremental on Organization_Name_ftcat_documentindex
Organization_Name is your organization name.

2. On the SQL Server Machine open Sql Server Surface Area Configuration (it is found in the configuration tools of Sql Server). Select "Database Engine " and click enable Local and Remote connections

3. On the Sql Server machine
  1. Start SQL Server Management Studio. Then expand the Security folder.
  2. Right-click Logins. Then click New Login.
  3. In the Login dialog box, click General on the left pane, and then click Search.
  4. In the Select User or Group dialog box, click Object Types, make sure that the Groups check box is selected, and then click OK.
  5. Click Locations, click the folder to select all the folder contents, and then click OK.
  6. In the Enter the object name to select field, type SQL, and then click Check Names.
  7. Select the SQLAccessGroup {GUID} record. Then click OK.
  8. In the Login dialog box, click the Windows authentication option, leave all the other default options at their current settings, and then click OK to close all the dialog boxes.


4. On the Crm Machine modify the Microsoft CRM System DSN ODBC Data Source on the Microsoft CRM server to point to the new server that is running Microsoft SQL server. To do this, follow these steps:
  1. Click Start, point to Administrative Tools, and then click Data Sources (ODBC).
  2. In the ODBC Data Source Administrator dialog box, click the System DSN tab, click Microsoft CRM in the System Data Sources list, and then click Configure.
  3. In the first Microsoft SQL Server DSN Configuration window, locate the Server list that contains the names of computers that are running SQL Server. Click the server that you want to connect to.
  4. Click Next three times to configure the data source.
  5. Click Finish.
  6. In the ODBC Microsoft SQL Server Setup window, click Test Data Source to validate the connection to the server.
  7. Click OK two times to complete the configuration.
  8. Click OK to close the ODBC Data Source Administrator dialog box.
5. On the Crm Machine
  1. On the computer on which Microsoft Dynamics CRM is installed, log on as a user who has the domain administrator role.
  2. Install the Windows Support Tools on the Microsoft Dynamics CRM server. The tools are on the Microsoft Windows Server 2003 CD or on the Microsoft Windows 2000 Server CD.
  3. Click Start, point to All Programs, point to Windows Support Tools, and then click Command Prompt.
  4. At the command prompt, run the following commands.

    setspn -A MSSQLSVC/SQL_server_name:1433 Service Account
    setspn -A MSSQLSVC/SQL_server_name.MyDomain.com:1433 Service Account
The Service Account represents the account domain account that is used by the new SQL Server to run.

On the old Sql Server (the CRM machine)

Clean up the contents of the original computer that is running Microsoft SQL Server. To do this, follow these steps:
  1. Delete the old Microsoft CRM SQL databases.
  2. Delete the following login groups:
    • SQLAccessGroup
    • UserGroup
    • ReportingGroup
6. On the CRM Machine

Reconfigure the Microsoft Dynamics CRM server. To do this, follow these steps:
  1. On the Microsoft Dynamics CRM server, click Start, point to All Programs, point to Microsoft CRM, and then click Deployment Manager.
  2. In the left pane, click Server Manager, right-click the Microsoft Dynamics CRM server, and then click Configure SQL Server.
  3. In the Microsoft Dynamics CRM server window, select the new computer that is running Microsoft SQL Server from the SQL Server list, and then click Next.
  4. In the Microsoft CRM database list, click the appropriate Microsoft CRM SQL database. If you have multiple Microsoft CRM servers, click to select the Apply changes to all servers in the deployment check box.
  5. Configure also the new reporting services URL : http://new_sql_machine/reportserver
  6. Click Finish.

So that's it. I my next post i will describe the upgrade process prom crm 3.0 to crm 4.0


References:
http://support.microsoft.com/kb/917948
http://support.microsoft.com/kb/910044/
http://msdn.microsoft.com/en-us/library/ms173748%28SQL.90%29.aspx
http://support.microsoft.com/kb/921393

luni, 14 iunie 2010

Configure Microsoft CRM 4.0 for Outlook to connect to a CRM server that is installed in another domain

Here are the steps to succesfully configure Microsoft Dynamics CRM for Outlook to acces a CRM server that is in a different domain than the computer where Outlook is installed.

Prerequisites:

- Install Microsoft Dynamics CRM for Outlook on your local machine that is outside the domain

- Rollup 11 is installed on the CRM server http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=f84f2bfb-393d-4b90-bf1b-300a82ec6083

- On the computer with Outlook Rollup 7 and Rollup 11 must be installed for MIcrosoft Dynamics CRM Outlook Client

Rollup 7 : http://www.microsoft.com/downloads/details.aspx?FamilyID=a4893988-7804-4e23-ab58-740441cc696e&displayLang=en


Install Steps:

1. Open the organization using internet explorer : http://crm-server:5555/OrgName

2. Add this ip in internet explorer to the Intranet Sites in security settings

3. Modify the security settings for the Intranet zone and set the logging to be automatically (default is prompt for user and password)

4. Close Outlook

4. Start the Crm for Outlook configuration and follow the steps

5. After the configuration is complete start Outlook and enjoy :)

References : http://sundium.wordpress.com/2009/07/12/the-request-failed-with-http-status-401-unauthorized/