asked on

CRM 2011 Upgrade: splitting full server environment to front-end/back-end servers

I am in the process of upgrading CRM 2011 to CRM 2016 and want to know the feasibility/issues encountered of splitting a full server environment into front-end/back-end servers

The common wisdom has been that this is very difficult and not worth the time. I would like some up to date information on this, however, since I have not encountered a full-server installation during the last five years.

This is not a highly customized or really large installation. There are managed solutions from PowerObjects and a limited number of Jscript web resources and plugins.

I would like some advice from someone that has done this process recently and what they encountered, positive or negative.

Thanks

ASKER CERTIFIED SOLUTION

Feridun Kadir

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

apollo7

ASKER

Thanks, my reasons are with past installations I have extreme problems with the asynch service taking over all the memory of a full server especially when running deployments of new solutions, complex workflows and so on. In the middle of the night I would check on an automated deployment and stay up closing services to let the process complete. Almost always, the deployment process would crash and we would need to start over.

By remaining in Full Server mode until Dynamics 365, I should be aware of any potential plugins/workflows that could bring down the server.
Sounds very feasible and I appreciate the advice.

apollo7

ASKER

Thanks, this answers my question.