Policy Based Management Syndication

EPM Framework v4 Released!

The Enterprise Policy Management Framework (EPMF) team is proud to announce the updated release of “Enterprise Policy Management Framework 4.0 for project EPMFramework. This is a major release with lots of performance tweaks and

The EPM Framework 4.0 includes the following updates:

  • For enhanced support of large environments
    • Reviewed database design, including views and indexing
    • Redesigned data load procedure
  • PowerShell execution now deletes XML files as soon as load is done – improves space usage on temp folder
  • Redesigned reports
  • Tested/verified against SQL Server 2005-2014

Note: an upgrade script for all the relevant database objects is provided, supporting direct upgrade from v3. Please check the documentation for further information.

HUGE thanks to the hard work from Pedro Azevedo (Twitter | Blog) who developed and tested this new version. Do you use Policy-Based Management (PBM) at work? Give this new version of EPMFramework a spin and let us know what you think.

5 replies on “EPM Framework v4 Released!”

Can the documentation please be updated as well? The document I followed from but copying this SL “F:\MSSQL\”
.\EPM_EnterpriseEvaluation_412.ps1 -ConfigurationGroup “” -PolicyCategoryFilter “” –EvalMode “Check” into a powershell windows started from SQL gives me an error saying the drive does not exists. Browsing through native powershell using the same command (SL “F:\MSSQL\”) does work. This doc needs to be updated to the syntax that SQL Powershell can use. Running the PS script as a job allows with the same command allows it to be found but still fails to a syntax error. The error, if (-not (Get-PSSnapin | ?{$ -eq ‘SqlServerProviderSnapin100’}))etc… The term ‘Get-PSSnapin’ is not recognized as the name of a cmdlet, I have done exactly as the document says so I feel it should be updated or these errors with resolution should be included. Thanks!

You need to replace the drive letter with that of your system. The F:\ is only there as an example. We’ll update the documentation to better reflect this, thanks.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.