ConfigMgr SQL Usage Rights

Steve Thompson, ConfigMgr MVP and SQL MVP, has a nice write up on using Ola’s Maintenance Solution with ConfigMgr.  It’s good stuff.  Matthew Teegarden has a follow-up article with more info and some alterations.

There’s only one problem… both are seemingly violating the licensing of the Usage Rights for SQL technology included with ConfigMgr.  Let’ me explain.

Microsoft Docs lists the approved use rights which basically just includes the site database, database replicas for Management Point, WSUS, and SQL Reporting.  An issue was logged to GitHub requesting clarification on on usage rights for other databases / apps / solutions.  In summary, Aaron Czechowski clarified…

  • Ola Hallengren’s Maintenance Solution with a CommandLog database (i.e. CMMonitor), ConfigMgr Client Health DB by Anders Rodland, the MDT database, MBAM, and PowerBI all fall into the category of “additional Microsoft or third-party product” and must have a separate license
  • Adding custom stored procedures, tables, views, database schemas, etc. to a licensed database on the SQL instance is not a licensing question, but a support question.

Thus using Ola Hallengren’s Maintenance Solution without the CommandLog database (by disabling table logging or using the master, CM_xyz, SUSDB, or ReportServer databases) is within the licensing terms.

While Matthew Teegarden states that using the master database isn’t a great idea, it is the best option given the licensing limitations.

So, What To Do?
continue reading on

ConfigMgr Database Maintenance – 2020 edition
Tagged on:                     
%d bloggers like this: