Upgrade the Capacity trending reports from version 1.0.3

Applies to: upgrades from OpsLogix Capacity trending reports 1.0.3 to 1.0.13 or later · SCOM 2019, 2022, 2025
Last updated: October 2026 · Reading time: 6 minutes

Version 1.0.13 replaces the 12 reports of version 1.0.3 with nine reports: seven new ones and the two redesigned Multi instance reports, and installs a new forecasting engine in the data warehouse. The upgrade is a normal management pack import, but a few things need attention before and after it.

What changes

• Ten reports are removed. SCOM deletes them during the upgrade, together with the e-mail subscriptions, linked reports and favourites that use them. See the table below for their replacements.
• New reports: Capacity overview, Top N at risk and Capacity heat map (each in a Percentage and an Absolute value version), and Capacity profile.
• The forecasts now use several models, detect level shifts and give a date range, an act-by date and the capacity to add. See Reading the capacity forecast.
• The default report period is 90 days back and 90 days ahead.
• The report folder in the console is named OpsLogix IMP - Capacity trending reports. The folder on the report server stays /OpsLogix.IMP.Capacity.
• Your licence stays: the upgrade does not change the licence table. You do not need a new licence pack.

Removed reports and their replacements

Before the upgrade

1. Write down the e-mail subscriptions, linked reports and favourites on the removed reports: who receives them, how often, and with which parameters. You recreate them on the replacement reports afterwards.
2. On SQL Server 2017 and later: the new version installs a new build of the forecasting assembly, which SQL Server does not trust yet. If clr strict security is on, switch it off for the upgrade:

   EXEC sp_configure 'show advanced options', 1;
   RECONFIGURE;
   EXEC sp_configure 'clr strict security', 0;
   RECONFIGURE;

   If you followed our older advice and left it off with the database set to TRUSTWORTHY, the upgrade works as is; we recommend moving to a trusted assembly afterwards (step 4 below).
3. On Reporting Services 2019 and later: check that the SCOM resource extensions are allowed for upload; see Capacity reports are missing from the SCOM console after import.

Upgrade

1. Import the new reports pack (OpsLogix.IMP.Capacity) in Administration > Management Packs > Import Management Packs. Leave the licence pack as it is.
2. Wait until the management server has deployed it, usually a few minutes. Event 31565 or 31567 in the Operations Manager log means that the data warehouse or Reporting Services step failed.
3. Check the result: the folder OpsLogix IMP - Capacity trending reports in the Reporting workspace lists nine reports, and Capacity overview - Percentage value shows a row per disk for the Logical Disk Free Space (%) rule.
4. Trust the new assembly and switch clr strict security back on: steps 4 and 5 in Capacity reports show rsErrorExecutingCommand or "Forecast failed". Repeat this after every later upgrade, because each version has a new assembly hash.

After the upgrade

• Recreate the subscriptions and favourites from step 1 on the replacement reports. For a weekly e-mail, Top N at risk is usually the best fit.
• Open each subscription on the reports that remain (the two Multi instance reports) and check its parameters, because these reports have new parameters with defaults.
• If you had your own logo, it is kept.

Related articles

• Capacity trending reports release notes
• Which capacity report to use
• Install the Capacity trending reports