Deployment Automation Tool MS CRM 2011

I want to automate the process of deploying CRM between different environments, such as Envelopment Env, Test Env and UAT. I am wondering if there are existing tools on the market for deployment automation for me? If not, is it possible to automate the deployment of CRM between different environments and what is best suited for this?

thanks

+4
source share
3 answers

Where I work, we are currently working with the same problem. I spend quite a long time, first looking for products that can help us, but I did not find anything promising. Therefore, we ourselves took on this task.

Some guys at Microsoft made a short “technical paper” on this subject, which I found very useful. It can be found here in Deploying Microsoft Dynamics CRM 2011 and CRM Online solutions from development through a test and production environment .

I will not argue that we use the "best" methods, but we decided to try and script everything in PowerShell or through .net based CmdLets in our own PS module. The CRM server comes with PowerShell snap-in, which supports some basic functions for creating / deleting organizations, but you are more or less independent when it comes to "deploying" CRM settings, configuration data, users, etc.

It would be interesting to know which approach you choose (if any)? And if you have any specific question, please feel free to ask!

+6
source

How about this?

The xRM CI Framework is a toolkit that enables you to quickly and easily implement continuous integration for your Dynamics CRM solutions.

+1
source

PowerShell and the XRMCI infrastructure will be well used to deploy solutions, but the disadvantage is that for persistent or configuration data that cannot be added to the solution (or for elements of the solution that currently do not work in CRM 2015, for example, creation rules case, SLA Items, etc.). In this case, my client and I created powershell C # CmdLets that use the SDK and API to create persistent data, such as "Users", "Teams", "Members", "Queue Rules", "Case Creation Rules" (although it support is not supported, the API really allows) and configure mailboxes, etc.

Thus, in combination, the XRMCI infrastructure, C #, and PowerShell can be used to automate the deployment of one environment for the next. The key is to do this slowly, manually run the scripts to begin with and build trust in the process, configure and add additional elements. Once this trust is achieved, move on to integrating with TFS as a CI / CD process.

As for best practice, my own research shows that it’s still “the one who dares” without real “best practice”, over time, players like Chef, Puppet, Octopus and Microsoft (with DSC) will contribute, but presently....

0
source

All Articles