Much has shifted in recent years in the world of endpoint management and there are specific tools designed to address the unique scenarios now associated with modern work. Distinguishing the pros and cons of each tool can be a challenge. The SQL configuration is outlined in the SQL recommendations for MECM – White Paper to provide guidance to Microsoft Endpoint Configuration Manager (MECM) administrators and IT professionals on how to configure and administrate the SQL Server instances related to Microsoft Endpoint Configuration Manager.Over the years, Microsoft has released several iterations of technology aimed at streamlining the security and management of enterprise endpoints.

IMPORTANT!! Customers should test and adjust these settings according to their environment. It’s was also written based on field experience and customer feedback. This document is not intended to replace the official guidance produced by the Product Group but provides additional information not already in this document. So, let’s look at these recommendations from a SQL Server perspective, applied specifically to a Microsoft Endpoint Configuration Manager (MECM) environment. The SQL recommendations for MECM – White Paper is available on GitHub and includes general best practices for SQL Server configuration and management, but also a recommendation applied in Microsoft Endpoint Configuration Manager context. Questions are often along the lines of “How should I properly configure SQL database settings in a Configuration Manager environment for the best performance?”, “What maintenance should I be running on SQL”, or “How often should I be running this maintenance?” Kudos to Ryad Ben Salah / Benjamin Reynolds and Stephane SereroĪs a Premier field engineer at Microsoft, we field many questions about SQL configuration for Configuration Manager environments, so we’re writing this to address some of them here. Updated : G ITHUB is now the new repository that hosts the new release of the document (2.6)

Microsoft mecm