[ad_1]
Microsoft Dynamics CRM is becoming the tool of choice for small, medium and even large businesses across USA and even worldwide – and there are strong arguments to support this statement: it is web based, plus it uses Microsoft Outlook replication model and allows you to work offline. However so far we think Microsoft CRM was not popularized in the direction of being transferred to new business owner when old business is sold or want through transformation, resulted in Active Directory reinstallation. Below we would like to offer you highlights, tested with Microsoft CRM 3.0 and we believe that future MS Dynamics CRM releases will be more flexible in the sense of transfer from one domain to another
· New Domain with the same name. Considering you are moving, downsizing, upsizing, for example you have to upgrade from Windows Small Business Server to Windows Enterprise. Install your new server and migrate Exchange users and email from your old domain
· Back Up Microsoft CRM company and metabase databases
· Mount company and metabase databases on your new Windows server SQL server
· Run MS CRM Redeployment tool/wizard. At this time you should be able to map MS Exchange migrated users with your old users. Please be advised to rename users ID after MS Exchange migration – this is required and part of the procedure
· Install MS CRM 3.0 in your new domain with the same name, chose map existing databases, be sure that your are entering the same company name
· Apply your custom reports and MS CRM SDK customizations to new environment
· Additional Tips. SM CRM Redeployment tool resolves Active Directory GUID with human
names, so you can try additional experiments in this direction. Try to avoid Crystal Reports, use MS SQL Reporting Services instead. When doing MS CRM programming, please follow MS CRM SDK (Software Development Kit) rules and conventions, do not do direct SQL Server scripting, or if the last is required – create your development DB and place custom objects there.
[ad_2]
