Optimizing and Maintaining a Microsoft Dynamics CRM 2. Server Infrastructure. Contributors: Brian Bakke, Grant Geiszler, Martijn Bronkhorst Technical Reviewers: Gus Apostol, Ramani Jagadeba, Mahesh Vijayaraghavan, Chandra Akkiraju. Published: August 2. Updated: December 2. Summary. Performance tuning and optimization is a continuous balancing act between design decisions and resource availability. This white paper provides tips, tricks, and guidance for optimizing and maintaining the performance of a Microsoft Dynamics CRM 2. Applies To. Microsoft Dynamics CRM 2. In this White Paper. Introduction. This section introduces the purpose, scope, and applicability of the information provided in this paper. Purpose. This white paper complements, rather than replaces, existing resources that are specific to optimizing and maintaining the various components that make up a Microsoft Dynamics CRM 2. To that end, this document provides relevant context for each component, information on maintaining and optimizing that component specifically within the Microsoft Dynamics CRM implementation, and links to related resources that may offer additional guidance for particular environments. Scope. This paper focuses on optimization and maintenance of the server infrastructure associated with a business solution based on an on- premises or hosted deployment of Microsoft Dynamics CRM 2. For information focused specifically on optimizing and maintaining the Microsoft Dynamics CRM clients that connect to an instance of Microsoft Dynamics CRM 2. Microsoft Dynamics CRM Online, see the white paper Optimizing and Maintaining Client Performance for Microsoft Dynamics CRM 2. CRM Online. Applicability. When considering the applicability of the information in this white paper to any specific solution based on Microsoft Dynamics CRM 2.
What Support Expert can do: 1. Virus Removal and protection 2. PC Tune-up & Maintenance 3. Fix slow computer 4. Clean your computer 5. Download tools to clean, optimize, backup or compress your registry. Microsoft Dynamics CRM solution. As a result, be sure to verify the functionality and performance impact associated with any specific optimization technique in a test environment prior to making any change in a production environment. Why Registry Utilities Professional? The registry is the nerve center of your PC and is used to store information and settings for software, hardware, user. Important. For Microsoft Dynamics CRM 2. Download. This paper can be downloaded from the Microsoft Download Center: Optimizing and Maintaining a Microsoft Dynamics CRM 2. Server Infrastructure. Overview of Optimizing a Server Infrastructure. Microsoft Dynamics CRM 2. In addition, the product supports a variety of server topologies. For example, you can deploy Microsoft Dynamics CRM 2. Single- server configuration, with Microsoft Dynamics CRM Server 2. SQL Server, SQL Server Reporting Services, and optionally, Microsoft Exchange Server installed and running on the same computer. Consider taking the following high- level approach when devoting efforts to optimizing and maintaining a connected system such as Microsoft Dynamics CRM 2. Important. Regularly downloading and installing the latest hot fixes and update roll- ups is a critical first step to enhancing and maintaining the performance of an overall deployment. For a listing of current resources, updates, and hot fixes available for Microsoft Dynamics CRM 2. Microsoft Support site, see the Support for Dynamics CRM page. After the system is configured for optimal performance, be sure to establish a performance baseline by recording the optimized levels of performance. Monitoring and Maintaining Performance. Over the course of time, routine, daily use of a connected system such as Microsoft Dynamics CRM 2. After deploying a solution based on Microsoft Dynamics CRM 2. Windows Reliability and Performance Monitor to collect and analyze performance data that you can use to monitor the overall health of the system. Logical Architecture for Microsoft Dynamics CRM 2. Understanding the unique aspects and system components that are generally associated with the logical architecture for implementing a Microsoft Dynamics CRM 2. While there are a variety of specific hardware and software requirements for implementing a solution based on Microsoft Dynamics CRM 2. Important. The graphic shows one example of the architecture for implementing Microsoft Dynamics CRM 2. Planning an implementation to address a specific business environment may indicate that one of many alternate structures would be more appropriate in a particular situation. The Client Tier. The client tier provides for interactions between the Microsoft Dynamics CRM 2. The system components that typically fall within the client tier include the following. Microsoft Dynamics CRM for Outlook. Web Client. Mobile Express Client. Potential performance issues affecting the client tier include network link issues (ping time, cache size and expiration time, compression technology) or relate to offline synchronization. The Application Tier. The application tier centralizes and performs all business logic processing, as well as providing the Web server responsibilities, for a Microsoft Dynamics CRM 2. Note. Because of the need to balance the differing server resource requirements of the Web server components and the business processing components, configuring and tuning the application tier can more difficult than optimizing the client tier. The system components that typically fall within the application tier include the following. Windows Server 2. R2. Microsoft . NET Framework and Microsoft . NET Applications. Internet Information Services. Microsoft Dynamics CRM Server 2. Front End Server. Back End Server (CRM Async Service). Deployment Administration Server. Microsoft Dynamics CRM Reporting Services. Potential performance issues that commonly affect the application tier include resource bottlenecks (processor, memory) or relate to plug- ins, SDK code, or workflow. The Data Tier. The data tier maintains solution data and serves up that data to address requests from the application tier. The database architecture of a Microsoft Dynamics CRM 2. Microsoft SQL Server and the databases containing the records and information unique to an organization. Depending on the implementation, the data tier can also include the Microsoft Dynamics CRM E- mail Router, as well as the E- mail server and database. The system components that typically fall within the data tier include. Microsoft SQL Server. Microsoft Dynamics CRM Database. Microsoft Dynamics CRM E- mail Router or Microsoft Exchange Server. Potential performance issues that commonly affect the data tier relate to physical data layout, the storage subsystem, or indexes. Server- Side Techniques for Optimizing the Client Tier. While there are a variety of techniques available for configuring and customizing the clients connecting to a deployment of Microsoft Dynamics CRM 2. Microsoft Dynamics CRM Online for optimal performance, there are also server- side settings that can help to enhance the performance of Microsoft Dynamics CRM clients. Using Compression Techniques. Compression techniques designed to optimize network performance directly affect the size of the data files transmitted over the network. Configuring HTTP Compression. By using bandwidth more effectively, enabling compression can provide faster transmission times between IIS and compression- enabled browsers. If your network bandwidth is restricted, as it is, for example, with mobile phones, compression can improve performance. IIS can be configured to compress only static files, only dynamic application responses, or both static files and dynamic application responses. Important. HTTP compression is usually available in a default installation of IIS 7. However, only static compression is installed by default. For information about how to install static or dynamic compression, see Setup in the article HTTP Compression < http. Compression>. To configure HTTP compression. On the Microsoft Dynamics CRM Server, in the Internet Information Services (IIS) Manager administrative tool, expand Sites, and then click Microsoft Dynamics CRM. After a static file is compressed, it is cached in this temporary directory until it expires, or until the content changes. The temporary directory must be on a local drive on an NTFS- formatted partition. The directory cannot be compressed and should not be shared. For example, if there are 2. Disk space limit is set to 1. GB. If you click the Per application pool disk space limit (in MB) option and type a number in the text box under it, IIS automatically cleans up the temporary directory according to a least recently used rule when the set limit is reached; the default is 1. MB per application pool. However, Microsoft Dynamics CRM 2. HTTP responses sent to SDK clients because this is an IIS- wide setting that can’t be configured at the Microsoft Dynamics CRM site level. Regardless, enabling HTTP compression can have a great impact on the performance of Microsoft Dynamics CRM for Outlook, which is an SDK client. An example of the impact compression can have on network resource utilization for a vanilla, out of box CRM server with sample data is shown in the following table, which provides a comparison of the bytes transferred when switching to Accounts View. No Compression. Compression Enabled on HTTP. Compression Enabled on HTTPS. Bytes Sent. 10. 50. Bytes Received. 21. Note that using HTTPS with compression shows an even more significant improvement in network resource utilization over than does using HTTP with compression. To configure Microsoft Dynamics CRM Server 2. HTTP responses that are sent to SDK clients, turn on IIS dynamic compression for the SOAP responses that are returned by Microsoft Dynamics CRM server by creating a batch file named IIS7- Enable. SOAPXML- Dynamics. Compression. cmd and adding to it the following line (one line): %SYSTEMROOT%\system. Server/http. Compression /+. Several Microsoft Dynamics CRM customers have implemented WAN acceleration appliances with encouraging results.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |