SCOM 2016 Step by Step– Part 18 – Operations Manager Shell PowerShell Error When Launched as Administrator

You wll probably get this error when you start SCOM powershell console as administrator.

“.\OperationsManager\Functions.ps1 : The term ‘.\OperationsManager\Functions.ps1’ is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again.
At line:1 char:34
+ … t-Module OperationsManager; .\OperationsManager\Functions.ps1; .\Oper …
+                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (.\OperationsManager\Functions.ps1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

.\OperationsManager\Startup.ps1 : The term ‘.\OperationsManager\Startup.ps1’ is not recognized as the name of a
cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify
that the path is correct and try again.
At line:1 char:69
+ … r; .\OperationsManager\Functions.ps1; .\OperationsManager\Startup.ps1
+                                           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : ObjectNotFound: (.\OperationsManager\Startup.ps1:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Windows\system32>

To resolve it once and for all run this code


$CMD = '$SCOMInstallPath = (Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Setup" -Name "InstallDirectory").InstallDirectory; Set-Location $SCOMInstallPath\..\PowerShell'
Add-Content -Path $profile.AllUsersAllHosts -Value $CMD -verbose -Force

If you don’t belive me reference is here

And now It is fine



Install SCOM Reporting role again on the same SSRS server aka FileNotFoundException: Could not load file or assembly ‘Microsoft.EnterpriseManagement.Reporting.Security’

SCOM reporting and me!? We are lately on the war path. I decided yesterday to remove SCOM 1711 technical preview and install SCOM 1801 final release. When I started to install reporting role I get this error screen


I checked everything and everything was fine. Next steps were logs. Error in logs was: ERROR: Exception caught instantiating Windows report server extension: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. See the report server log files for more information. —> System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.EnterpriseManagement.Reporting.Security’ or one of its dependencies. The system cannot find the file specified.

What is the problem? Problem is that SCOM modifies the configuration files of the SQL Reporting Service with its own configuration. It makes copies of original configuration files as RSReportServer.config.0, RSReportServer.config.1 and web.config.0


So what to do when you try to reinstall?

Method 1

Rename one of these configuration files back to RSReportServer.config and web.config.  Restart ReportServer Windows Service and IIS.

Method 2

Run ResetSRS.exe tool you can find on SCOM installation media under Support Tools folder . It will reset configuration of SRS. After you run it restart SSRS services. Tool is used in command prompt in this manner c:\resetSRS.exe <SQLINSTANCENAME>



I constantly forget  things. I hope this helps somebody not to scratch its head for a day and try different things.

System Center Operations Manager 2016 Step by Step– Part 17 – Cannot create a connection to data source “DB_Audit”

Let assume that you installed Audit Collection and gave some users Report Operators role. After they run some reports from Audit Report folders they get error

An error has occurred during report processing. (rsProccesingAborted).
Cannot create a connection to data source ‘DB_Audit’. (rsErrorOpeningConnection)


What is the problem? When you are running other reports (not AC Reports)  from SCOM console they are run in context of Operations Manager Data Reader you created. Because ACS is not part of SCOM reporting role it does not share same security context. Account you use to run Audit reports will not have any rights to read from SCOM audit database. The best explanation (old one but good one) I read is written on this blog .

To solve this we need to give account access to OperationsManagerAC database. Just log in to you SQL instance and give it db_datareader access. Best practice would be to create group with name for example ACReports users, and give this group db_datareader access. All users inside group will have access to Audit reports, regardless of they SCOM Reports Operator role.


This is also very specific written on SCOM 2016 documentation link

The installation procedures for ACS Reporting do not differ, but the application of access control is different. By deploying ACS Reporting on the same SQL Server Reporting Services instance as your Operations Manager Reporting, the same role-based security applies to all reports. This means that ACS Reporting users need to be assigned to the Operations Manager Report Operator Role to access the ACS reports.

In addition to membership in the Operations Manager Reporting Role, ACS report users must also be assigned db_datareader role on the ACS database (OperationsManagerAC) to run ACS reports. This requirement is independent of the presence of Operations Manager Reporting

I hope this helped you in getting your Reports utilized, because it is very important part of SCOM software.  

System Center Operations Manager 2016 Step by Step– Part 16 – Installing Reporting role on remote SQL installation? Missing SQL instance!?

The other day I was trying to install test SCOM 1801 environment and when I wanted to do reporting role installation I was stuck at this page. SQL Server instance for Reporting Services had empty SQL Server instance list. I scratched my had a little bit, but finally come to solution that is very obvious but somehow hidden and not enough explained. That is why some people doesn’t like SCOM because they can not get answers when they need it. Please if you have some piece of blog or Microsoft article that explain this comment. (I would like to have some reference) Closest one is article from Cameron Fuller. Even he had the same problem there.




So let me explain. When people are starting with SCOM or making test environments they take one big server and put everything there. SCOM installation, SQL database, SSRS and everything else needed for SCOM to work. IT works fine if you have enough resources. When it comes to production you usually take one server for SCOM roles and another one for SQL workloads. You start with installation and suddenly you come to this screen and there is no SQL Server instance available, even you know that everything is setup fine on SQL Server. You can even get remotely http://server/reports and http://server/reportserver pages. So what is the catch. 


There is no other way. You can try but it doesn’t work and you will always get the same problem. You can manage to use remote SQL Reports database for examle, but SSRS service and Reporting role SCOM installation need to be on the same computer. There is also a catch for using reporting in web console but you can read it on another one of my  blogs 

In any case to repeat


Like addition I will give you link to short Reporting book from Savision team “SCOM Reporting Guide – Tips and best practices”.

HP ILO2 2.31 released?! :-)


Yesterday I needed to do some update and I was trying to get ILO running on one server (DL 360 G5). I checked latest firmware version I had in my repository and saw it was not updated. Ok I said let go check if there is something newer on HP (sorry HPE) site. I was surprised. They released by the end of 2017 new firmware for ILO2 that is deprecated. They addressed some Java and SSL issues that probably everybody has these days . So upgrade you repository and download latest firmware for old stuff

System Center Operations Manager Ignite Announcements


Ignite is behind us, and lots of new things are happening in and around Microsoft. Things change, and SCOM also. If you are SCOM user and follow SCOM team blog, you will see that they announced survey regarding changes they implement in System Center products. One of them is new release cadence that will resemble Windows. It means that update for System  Center will be aligned with Windows updates. On November 8th Microsoft will release preview version of System Center 1801. If you don’t understand the numbers of version, first two numbers are the year of release, and two last ones are the month. System Center will be released semi-annual with new future addressing issues and new feature. you will be able to update you system if you have eligible Software Assurance for that product.


When we talk about what is coming for SCOM 2016 here it is

  • System Center 1801 prieview early November. Release Q1 2018
  • Service Map integration is now in public preview but it will relased probably with new version. you can download MP here
  • Windows Server 2016 SDDC monitoring

Improved Unix/Linux support

    • “setup improvements” hopefully a better way to deploy “manually”
    • Kerberos support
    • Log file monitoring with FluentD. Essentially this enables us to create monitors etc. based on logfiles as we can with Windows (This is huge)


SCOM 2016 HTML5 console

  • Improved diagnostics and drill down – this is huge for those who haven’t invested in third-party software
  • Custom widget support. Display other charts on your dashboard.


  • MP updates and recommendations (introduced in 2016) now supports 3rd party MPs. 56 partners with certified MPs are available.
  • Visual Studio Authoring Extension for VS 2017

If you want to find out more details about all of this please watch Ignite session System Center for the modern datacenter: First look at advancements coming this year

System Center Operations Manager 2016 Step by Step– Part 15 – Installing inbox MP hotfix for WMI health monitor issue and more

After almost 2 months I remembered that I have blog to write.Lot of things happened in between, but couple of days ago Microsoft released fix for WMI health monitoring issues. I will not go to much in detail what happened there, but symptoms you have look like on the picture below and error you see in alerts is WMI is unhealthy. Error can be true in some cases! Bu if you have installed this fix and error is still there something is for sure wrong. There was discussion about this error already on Technet forum and colleague from SquaredUp company wrote new management pack you can download that was removing this issue until Microsoft relase fix. If you don’t know SquaredUp has nice community page where you can found post about it and lot of other SCOM related things.


Microsoft released fixed MPs and announced it on SCOM Team blog here.  New feature in SCOM 2016 for Nano servers caused trouble.  Fix is called Microsoft System Center Operations Manager 2016 inbox MP hotfix for WMI health monitor issue and you can download it here . It is just simple new management pack. Lets deploy it.

Run installation you downloaded






In Windows Explorer you will se two new MPs


Go to Import Management pack and navigate to folder you “installed” MPs. Chose them and you should see next windows. Version of currently installed System Center Core Monitoring MP is 7.2.11878.0 (fixed 7.2.11907.0) and version of System Center Internal Library is 7.0.8437.7 (fixed 7.0.8437.10).


Click Yes on Security risk question. and that is it. You fixed problem your boss was nagging you for. Easy.-)


Importing SCOM management packs after update rollup installation

So you installed new SCOM Update rollup. As you know procedure is to install new versions of management packs from folder “Management Packs for Update Rollups”. You can check procedure on this post. This is usually repeating task and sometimes we install management packs we don’t need. to make it easier I wrote script that will firstly check for installed MPs on local server and than look for new versions in  “Management Packs for Update Rollups” folders. If there is a new version it will install management packs. You can modify script easily and change to make it more suitable for you. It is maybe not SCOM friendly script but usually there is no much changes in management packs for update rollup besides new versions of files.

To download it visit TechNet Gallery link

Enjoy time you gain and use it wisely

System Center Operations Manager 2016 Step by Step– Part 14 – Installing ACS reports

Hi it was long time ago I wrote something so lets continue. you installed and configured ACS but you want to see reports. How to do it.

Log in to your SSRS server where you already have deployed SCOM reports and make sure that everything is working properly first.


After that copy ACS folder from installation media in ReportsModel folder to you server for example to C:\ drive


Run PowerShell or cmd and run next command

.\UploadAuditReports "myAuditDbServer\Instance1" "http://myReportServer/ReportServer$instance1" "C:\acs"

Result will look something like this. Ignore warnings


After that open Reports web page. Usually http://server:80/reports and open Audit Reports folder


Select show hidden items if it is not already checked


Click DBAudit source. Setting should be looking like this


Open one report in console and try to test it


It should be working Smile


System Center Operations Manager 2016 Step by Step– Part 13 – Manually installing agents on server

Recently I had problem with SCOM agent. Shortly it crushed totally SharePoint 2010 frontend server. To find out more you can read about it on this post APM feature in SCOM 2016 Agent may cause a crash for the IIS Application Pool running under .NET 2.0 runtime.

One of the solutions was to install agent manually without installing  APM feature. Before you do anything first copy installation of MOM agent or complete SCOM installation locally on PC. I copied everything in C:\SC 2016 RTM SCOM  folder. This is the short description of command use to do it. It is used when you don’t have AD integration enabled and you use Local system account as Action account


%WinDir%\System32\msiexec.exe /i "C:\SC 2016 RTM SCOM\agent\AMD64\MOMAgent.msi" /qn USE_SETTINGS_FROM_AD=0 USE_MANUALLY_SPECIFIED_SETTINGS=1 MANAGEMENT_GROUP=scom-hteronet SECURE_PORT=5723 ACTIONS_USE_COMPUTER_ACCOUNT=1 NOAPM=1 AcceptEndUserLicenseAgreement=1

Stay happy