crm Chapter 10 –Maintaining Organizations through Depl.pdf

Configuration Customization in Microsoft Dynamics CRM 4.0 Chapter 10 – Maintaining Organizations through Deployment Manager Overview • Creating Multiple Organizations • Review the following Deployment Manager utilities: • Deployment Administrators • Organizations • Servers • License Lesson: Creating Multiple Organizations • Multiple organizations are supported on a single Microsoft CRM Server • The CRM Server is no longer restricted to a given organization • Maintaining multiple organizations (known as multi-tenancy) is only available in the Enterprise Edition • Provides hardware optimization (multiple organizations serviced by less Microsoft CRM Servers) and potential reduction of Total Cost of Ownership Creating Multiple Organizations • A site-wide configuration database (MSCRM_CONFIG) drives this multi-tenancy design • All organization-wide settings from the local registry, the IIS metabase, and all other server dependent locations are stored here Creating Multiple Organizations • What happens when upgrading from Microsoft Dynamics CRM 3.0 to 4.0? • The application’s registry and IIS metabase settings are migrated away from the Microsoft CRM Server and stored in the configuration database • The organization entered during Server Setup is added to the configuration database regardless of the edition of Microsoft Dynamics CRM that you install. Creating Multiple Organizations • In the Enterprise Edition, you add additional organizations through Deployment Manager • When adding a new organization, the New Organization Wizard performs the following tasks: • It creates a new CRM database for the organization • It registers the new organization in the Configuration and SQL Report