1
Vote

Deploying Sample Database

description

After the sample database is restored per the deployment guide included in the 1.0 download package, the users in the sample data need to be mapped to users in the CRM deployment that the sample database was restored to. What is the best way to do so?

comments

wanlizhu wrote Apr 25, 2007 at 9:14 PM

Use the Microsoft CRM Redeployment Wizard to map sample data users to users of the target CRM deployment. See attached instructions, which is also included on the Microsoft CRM 3.0 CD (under the folder \RedeploymentTool).

wanlizhu wrote Apr 25, 2007 at 9:14 PM

Here are the exact steps (as outlined for the redeployment tool):
  1. Install the Microsoft CRM Redeployment Wizard on the computer which will be used as MSCRM Server (The Microsoft CRM Redeployment Wizard is available on the Microsoft CRM Server CD. The Wizard is located in the \RedeploymentTool folder.) For installing the MS CRM Redeployment Wizard, navigate to the RedeploymentTool folder, double-click RedeployImport.msi and follow the installation instructions. 2. Restore the copy of the MS CRM databases provided in the solution pack to the computer running SQL Server in the new system. While restoring the databases, ensure thet athe restored databases are named as follows -MS CRM Demo Metabase - Adventure_Works_Cycle_METABASEMS CRM Demo Database - Adventure_Works_Cycle_MSCRM 3. Start the Redeployment Wizard from Start menu --> Programs --> Microsoft CRM --> Microsoft CRM Redeployment Wizard. 4. On the Welcome to the Microsoft CRM Redeployment Wizard opening page, click Next. 5. On the Database Information page, type the name of the Microsoft SQL Server and then select the name of the restored Microsoft CRM database - Adventure_Works_Cycle_MSCRM. 6. On the Organization Information page, leave the name as "Adventure Works Cycle". 7. On the Active Directory Information page, Browse Active Directory to choose an Organizational Unit where the Microsoft CRM security groups will be created. 8. On the User Mapping page, choose the method to be used as Manually Map Users and click Next. 9. On the Edit User Mapping page, map users from the demo Microsoft CRM system to your new system. After the users are mapped, click Next. 10. On The Confirm Database Transformation page, click Start for the wizard to start the transformation. 11. The Performing Database Transformation page appears showing the transformation progress. When the process is complete, click Next. 12. Click Finish to complete the wizard. 13. Install Microsoft CRM on the computer in the new system and make sure to select the Connect to existing database option during setup. Connect to the above database that has been transformed using the Redeployment Wizard. 14. Now import the customizations provided in the solution pack.

ifgood wrote Apr 25, 2007 at 9:14 PM

The above process did not work as when I try to install Microsoft CRM (step 13) is failed during the System Requirements step phase with "Setup detected a version mismatch between the specified database and the current product". I've tried the installed using a purchased CRM V3 media and a MSDN version downloaded 2 days ago. Do I need a specific version of CRM V3 and if so how can I get it? The server is running W2K3 Ent Rc2 and Sql 2005 Ent (without Sp1).

ifgood wrote Apr 25, 2007 at 9:14 PM

Found a resolution on Google groups to the version mismatch error. See below:

I encountered the same issue, inorder to resolve this I had to go into the 'Company_Name'_MSCRM database on the SQL server, open the tables, and open the BuildVersion table. I then changed the "Revision" from 0 to 106. The installation was then able to conitune. It does give you a warning but my installation went over without issues.

dawidy wrote May 4, 2007 at 2:45 PM

About Sql version mismatch...I checked the Revision field in BuildVersion table in a database that was created by the CRM installer. It was 1232. I set the Revision field in the Adventure_Works_Cycle_MSCRM database to 1232 and I was able to continue the installation.

wrote Feb 13, 2013 at 9:47 PM