Moving on to CRM 2015 online this fall 2015 with Ping Federation and Mobile capabilities.
CRM Dynamics Unlimited covers all parts in development, deployment, new release, patch ups, rollups, current News and events.
Friday, July 17, 2015
Saturday, May 16, 2015
Moved from CRM 2011 to CRM 2013 May 2015
We are Onpremise CRM 2013 now Plans to go CRM Online soon.....
Monday, March 16, 2015
Thursday, January 15, 2015
Register for Convergence 2015 in Atlanta
Register for Convergence 2015 in Atlanta
http://www.microsoft.com/en/convergence/atlanta15/#fbid=fkiSo22thk-
http://www.microsoft.com/en/convergence/atlanta15/#fbid=fkiSo22thk-
DR (Diaster Recovery) Environment set up for Production CRM 2011 System
Cloning the production servers and changing the names of the CRM servers is not
going to be the best method for creating a DR environment for CRM
deployment as the CRM servers cannot be cloned under different names.
There are two options, one is to
create a completely separate CRM environment at which point databases are
restore and CRM can be reinstalled to if needed. The other is a standby
environment where CRM is already installed to the DR app servers and you’d only
need to move SQL server. This blog post discusses both opotions: http://social.technet.microsoft.com/wiki/contents/articles/6404.dynamics-crm-4-0-disaster-recovery.aspx
Our option was to Restore Database onto a stand-by environment Here the DR CRM app servers
are ready to go, to use it the SQL databases would need to be restored and the
Database Connection would need to be updated.
The Restore Databases and Join
servers to existing organization option, this creates an entirely separate DR
CRM Deployment. When the time comes to switch to DR, the databases would
need to be restore, edited, and CRM installed to existing databases.
Subscribe to:
Posts (Atom)
