Redeploy the Microsoft Dynamics CRM deployment that includes the Microsoft Dynamics CRM Server within the same domain or to another domain.

  1. Back up the Organization_MSCRM databases. To do this, follow these steps:
    1. On the computer that is running SQL Server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    2. Expand Databases, right-click the Organization_MSCRM database, point to Tasks, and then click Back Up.
    3. Under Destination, add the location to save the backup file, and then click OK.
    4. Repeat steps 1b and 1c for any other Organization_MSCRM database that must be moved.
  2. Install Microsoft Dynamics CRM 4.0 on the new computer that will run Microsoft Dynamics CRM Server.

    Note When you are prompted to enter the organization name, use a name that differs from the original organization name. You will import the old organization into the new installation. Therefore, you do not want the installation process to create a new organization that has the same name.
  3. Restore the Organization_MSCRM databases on the new computer that is running SQL Server. To do this, follow these steps:
  4. On the new computer that is running SQL Server, click Start, point to All Programs, point to Microsoft SQL Server 2005, and then click SQL Server Management Studio.
    1. Right-click Databases, and then click Restore Database.
    2. Under Destination to restore, type the name of the Organization_MSCRM database in the To database box.
    3. Under Source for restore, click From device, click the ellipsis button (...), add the Organization_MSCRM database, and then click OK.
    4. Click to select the Restore check box, and then click OK.
    5. Repeat steps 3b-3e for any additional Organization_MSCRM databases.
  5. Apply hotfix 950680.

    For more information about hotfix 950680, click the following article number to view the article in the Microsoft Knowledge Base:

    (http://support.microsoft.com/kb/950680/ ) The workflow rules no longer run when you use the Deployment Manager Import Organization Wizard to import an organization in Microsoft Dynamics CRM 4.0

  6. Import the organization into the new deployment of Microsoft Dynamics CRM 4.0. To do this, follow these steps:
  7. On the new computer that is running Microsoft Dynamics CRM Server, click Start, point to All Programs, point to Microsoft Dynamics CRM, and then click Deployment Manager.
    1. Right-click Organizations, and then click Import Organization.
    2. If you are using the Professional edition of Microsoft Dynamics CRM, you are prompted to delete the existing organization. Click OK to delete the organization that was created during the installation.

      Note This action does not delete the actual Organization_MSCRM database from the computer that is running SQL Server.
    3. In the SQL Server box, click the computer to which you restored the Organization_MSCRM database, click the organization database in the Organization database box, and then click Next.
    4. Type the display name and the name for the organization, and then click Next.
    5. Type the URL in the SQL Server Reporting Services URL box, and then click Next.
    6. Select the method in the Method for the Mapping of the Users list, and then click Next.
    7. Map the users, and then click Next.
    8. In the System Requirements dialog box, click Next, and then click Import.

Notes

  • If you plan to use the same Microsoft Dynamics CRM E-mail Router, you must run the Configuration Wizard to configure the router for the new environment.
  • You must install the Microsoft Dynamics CRM Data Connector for SQL Server Reporting Services to register the components with the new MSCRM_Config database.
  • You must run the Configuration Wizard for the Microsoft Dynamics CRM Client for Outlook to connect to the new Microsoft Dynamics CRM Server.
  • You must reinstall the Data Migration Manager to point to the new Microsoft Dynamics CRM Server.

Comments

Post a Comment

Popular posts from this blog

MS CRM 4.0 Relationship Mappings Error

Image
Whenever relationship is deleted but relationship attribute is used in another relationship mappings. In that case if you click on mappings you will get below error message. Cause: attribute is deleted but attribute is used in attribute mappings. In MS CRM attribute relationship mappings are saved in following tables E ntityMapBase AttributeMapBase Identify the mapping record in EntityMapBase Table. Take the GUID of that record and find the related attribue records in AttributeMapTable select * from dbo . AttributeMapBase where EntityMapId = 'place your relationship record GUID' update the your deleted attribute records DeletionStateCode with 2.
Read more

Open Data Protocol

The open data protocol is a web protocol for querying and updating data.OData does this by applying and building upon web technologies such as HTTP Atom publishing Protocol (AtomPub) JSON to provide access to information from variety of applications,services and stores. OData being used to access information from different sources like Relational Data base File Systems Content management systems Traditional  web sites OData is consistent with the way the Web Works.This Commitment to core Web Principles allow Odata enable a new level of data integration and interoperability across the broad range of clients,server, services and tools. OData provides the uniform way to expose,structure,query and manipulate data using REST practices and JSON or ATOM.OData also provides a way to reprasent metadata about the data,allowing computers to know more about the type system,relationships and structure of the data.
Read more

Using Read-only versus const

There are Two difference versions of constants in C#: the Const keyword is used for compile –time constants read only keyword is used for runtime constants. The main issue with const is that it's evaluated at compile-time, which means if it's changed at a later date; you have to not only recompile that application, but all applications that reference that application. In contrast, read -only is evaluated at run-time providing you a lot more flexibility. An overview of differences between const and read-only in c#      Const Read only Cont be static Can be either instance-level or static Value is evaluated at compile time The value is evaluated at run time. It is initialized at declaration only It can be initialized in declaration or by code in the code constructor .therefore read only fields have difference values depending on constructor used.   So, const should really only be used for logical, real-world constants such as days of week, numeric Constants, etc. as for as perfo...
Read more