Welcome Guest |
Join Now!
|
Help
|
Sign in
Site Search:
Home
Profile
Product
Microsoft Dynamics AX
Microsoft Dynamics CRM
Microsoft Dynamics GP
Microsoft Dynamics NAV
Microsoft Dynamics RMS
Microsoft Dynamics SL
Networking
Organization
Resources
CustomerSource
PartnerSource
Marketplace
Microsoft Dynamics
Product Suggestions
Convergence
Microsoft Dynamics CRM Home
Blogs
Video
Forums
Executive Insights
MVP's
Related Communites
Community Home
»
Microsoft Dynamics CRM
»
Blogs
»
BillOnCRM, CRM Tips, Tricks, and Traps
» setting up a 8220 mirror 8221 of a production envi...
Related Content
Tag Cloud
CRM 4.0
Setting up a “mirror” of a production environment for dev/testing
BillOnCRM, CRM Tips, Tricks, and Traps
Bill Owens is the CRM Practice Manager for Affiliated Resource Group. His company focuses on Microsoft Dynamics CRM, and is a leading implementation partner in the Ohio area. He has been implementing Microsoft Dynamics CRM since the early CRM 1.2 days.
RSS for Posts
Tweet
Setting up a “mirror” of a production environment for dev/testing
Anonymous
4 Aug 2008 10:44 AM
Comments
1
mscrmguy wrote this on Thursday, July 31, 2008
I recently needed to set up a “mirror” of a production system for use in development and testing. I had worked with the Redeployment tool in CRM v3 and I was interested to see how v4 worked. I was very happy when the v4 tool was *very* easy to use, and here are the steps I followed.
1. Used SQL 2005 to do a backup of the CRM v4 production databases
2. Using the VPC image distributed by Microsoft, I copied the .bak file to the VPC. I then did a restore of the database files to the VPC SQL instance. For some reason the SQL GUI did not work, so I used the following command (Names changed):
restore database OrgName_MSCRM from disk='C:\Temp\OrgName_MSCRM.bak' WITH MOVE 'OrgName_MSCRM' TO 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ OrgName _MSCRM.mdf', MOVE ' OrgName _MSCRM_log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data\ OrgName _MSCRM_log.LDF'
3. Once the DB was successfully restored on the VPC image, I fired up the CRM Deployment Manager, right-clicked on the “Organizations” item, and selected “Import Organization”
4. The next step asked me to specify the SQL server, and as soon as I did that the deployment manager found the organization I wanted to import
5. The next screen asked me for a name and a display name
6. Next input was the report server URL
7. The next steps involved the mapping of users. There are several options for this tep, I chose to simply “Manually Map Users”, and the only user I mapped was the Administrator which was mapped to the Litwareinc Administrator on the VPC. I got a warning that “All users are not mapped. Do you wish to continue?” and just clicked “Yes”
8. The next screen was simply the tasks verification screen, so I clicked “Next” and then on the next screen “Import”
9. And that was it! It took a bit of time and at the end I am able to access the org via
http://moss:5555/orgname/loader.aspx
You can see the screens here but please note names are hidden:
http://www.mscrmguy.com/redeploy/redeploy.html
1 Comments
Read the complete post at
http://blog.aresgrp.com/crm/post/Setting-up-a-e2809cmirrore2809d-of-a-production-environment-for-devtesting.aspx
CRM 4.0
Most Viewed Posts From This Author
Send Emails and Attachments in CRM 2011 using the SDK
Posted by
Bill Owens
on
Posted
7-7-2011
0
Comments
CRM 4.0 Plug-in Registration Tool Walkthrough
Posted by
Anonymous
on
Posted
10-30-2009
0
Comments
SQL Server: The instance name must be the same as computer name
Posted by
Anonymous
on
Posted
10-30-2009
0
Comments
Creating a Dashboard using MOSS, Excel Web Services, Excel 2007 and Microsoft CRM
Posted by
Anonymous
on
Posted
10-30-2009
0
Comments
Workflow Best Practices – Reduce Wait time
Posted by
Anonymous
on
Posted
5-28-2010
0
Comments