CRM 4 is a multi tenent plateform. You can have morethan organization in one crm server deployement. You have the option to import and export organizations. (Organization = one full crm3 deployement)

So keep in mind the multitenancy diff. Rest of all is fine.

One more consideration is: you have to keep the Web route directory with you in crm3 and any changes to ISV/Sitemap needs to be manually backup. While in crm 4 ISV and Sitemap are also a part of organization database.

Any custom code (Workflows/Plugin) needs to be backed up and moved during rollout.

CRM Webservice Accesspoint needs to be reconfigured/updated after rollout.

Any custom report developed needs to be rolled out.

Hope this helps,

Regards,

Ayaz

I´ve seen some sample scenarios for MSCRM 4.0 dev env deployment on MSDN (http://msdn.microsoft.com/en-us/library/ee294457.aspx)

In your oppinion, are these scenarios applicable to CRM 3.0 ? Is there any additional considerations regarding CRM 3.0 ? Any CRM 4.0 characteristic not applicable to 3.0 ?

Once we setup the developmemnt environment. Is just a matter of importing the customizarions XML and backup-restoring the SQL database from production to dev environment ?

Thanks in advance !

Alberto

//#1
FileInfo pointer = new FileInfo( “c:/test.pdf”);
FileStream fileStream = pointer.OpenRead();
byte[] byteData = new byte[(int)fileStream.Length];
fileStream.Read(byteData, 0, (int)fileStream.Length);
string encodedData = System.Convert.ToBase64String(byteData);

//#2
fileStream.Flush();
fileStream.Close();

//#3
UploadFromBase64DataAnnotationRequest upload =
new UploadFromBase64DataAnnotationRequest();
upload.AnnotationId = newNoteID;
upload.FileName = “test.pdf”;

//#4
upload.MimeType = “application/pdf”;

//#5
upload.Base64Data = encodedData;

//#6
UploadFromBase64DataAnnotationResponse uploaded =
(UploadFromBase64DataAnnotationResponse)myCRMService.Execute(upload);

The MS VPC expires yearly so its not a good idea to use that VPC as Dev or Test Environment.

You have to build a new VPC/Server for test/dev environment. If you are a Microsoft Partner then you will have licences for Microsoft CRM to use in test and dev environemnt otherwise you need lisence and need to talk to your regional Mcirosoft Contact to find out licence prices.

You can use Same or Different AD.. no effect. Different ADs is always good … Managemability.

You need to use diferent Databases and do not use same database server as of production as it will harm the performance of prod server. CRM uses SQL a lot so always install test or dev on different Servers.

For Dev environemnt you can use Standalone Installation. Means all(CRM/AD/SQL/Exchange) in one machine.

Licensing is always complex and depends on regions so always call Local MS agent or MS partner to find out licencing issues.

Hope this helps

We have a running MSCRM 3.0 and need to setup an isolated environment to develop and test some customizations and in the process to train new people to maintain them in the future.

We have ASP/.Net trained programmers but the initial CRM deployment was made by some other company.

We would like to start a new development setup, import current customizations and start from there our develoment. Later, when changes are aproved, deploy them to the production environment.

Ready-to-run VPC solutions we could find around there seem outdated and are set to expire last year´s end.

We suppose we´ll have to deploy a new server (perhaps on a VPC) but we´re no t sure about the impact it could have on the current setup. We´re not sure about AD, SQL Databases, Exchange and licensing issues we may encounter on the road ahead.

Is there any hint you could give us ?

Thanks a lot in advance !!

Alberto