I am sure Microsoft has had many complaints regarding the length of time to complete a redeployment, infact I posted earlier that they can take up to 1 hour per gig or more. Apparently Microsoft has listened and refined the redeployment process with Rollup 10, see the link below for more information.
Share on Facebook
Occasionally during testing you need to force the install of CRM and may not be concerned with with the installation pre-checks, the following registry setting will allow the Next buttons to be active although there may be stop issues within the pre-check window. However, I only use this on test environments and would never us this for a production system.
Add the IgnoreChecks registry key to the computer that is running Microsoft Dynamics CRM 4.0 so the installation can proceed when an error is shown in the Environmental Diagnostic Wizard (EDW):
- Click Start, click Run, type regedit, and then click OK.
- In the registry, locate the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRM
- Right-click MSCRM, point to New, click DWORD Value, and then type IgnoreChecks.
- Double-click IgnoreChecks, and then type 1 in the Value data field.
Share on Facebook
http://support.microsoft.com/default.aspx?scid=kb;en-US;2003564
Redeploying large databases can take a lot of time, I generally estimate 1 hour per gig of database size which has turned out to be a reasonable number. For example the most recent redeployment was 10 gig and took between 9 and 12 hours over the course of 3 re-deployments for testing and otherwise. However, with the larger databases you can run into server limitation which has resulted in KB 2003564. Its important to note that once the database has been redeployed some of the settings within the KB will need to be reversed, this is outlined within the article.
KB 2003564 Description
When you import a Microsoft Dynamics CRM 4.0 organization, you may experience a timeout or a hang in the MMC console window hosting the Microsoft Dynamics CRM Deployment Manager.
The Microsoft CRM Deployment Manager window may show up as a white screen during this time and Windows Task Manager will show the program “Deployment Manager” as “Not Responding”. This may even happen if you have increased the OLEDBTimeout setting for Microsoft Dynamics CRM 4.0 to a value greater than when the error was experienced.
If you enable platform tracing, using the steps in KB 907490, How to enable tracing in Microsoft Dynamics CRM, http://support.microsoft.com/default.aspx?scid=kb;EN-US;907490 , you will see an error like the following in the platform trace files (Note that the default log for Importing an organization will be located by default in the %appdata%\Microsoft\MSCRM\Logs\Import.log file for the user who installed Microsoft Dynamics CRM 4.0.
Share on Facebook
