There have been many posts about this over the years, and this is nothing new nor groundbreaking. However, I still run into customers who don’t fully understand how this works, how to configure it, and some of the good resources documenting this in the past have disappeared. So, this article…
Just publishing a little script I find handy when I need to free up space on my Hyper-V server. I have a home lab I use from time to time as well as my VMs hosted in Azure. These are hosted on Hyper-V. The VM disks in my lab grow…
One common issue I see regularly, is when customers upgrade their OS in place on Agent monitored systems, or replace and older OS with a new VM and a new OS, but keep the same server name. This practice causes issues for SCOM. You might see duplicate discovered instances across…
There are times when you may wish to automate deleting objects in SCOM. The safest method is always using the Console, or the SDK to delete objects in SCOM, in a manner they were designed to be deleted. There is an option in the SCOM Console to delete discovered Network…
This is based on the SQL MP Version 7.0.20.0. https://www.microsoft.com/en-us/download/details.aspx?id=56203 This new MP supports discovery and monitoring of SQL 2012, 2014, 2016, 2017, 2019, and later versions of SQL Server. It is completely different than all previously released SQL Management Packs, the older ones I will refer to as “Legacy”…
KB Article for OpsMgr: https://support.microsoft.com/en-us/help/4492182/update-rollup-7-for-system-center-2016-operations-manager Download catalog site: http://www.catalog.update.microsoft.com/Search.aspx?q=4492182 Updated UNIX/Linux Management Packs: https://www.microsoft.com/en-us/download/details.aspx?id=29696 Recommended hotfix page: https://kevinholman.com/2009/01/27/which-scom-hotfixes-should-i-apply/ Key fixes: Improved the performance of SCOM console in listing the groups. Users of a scoped group are not able to use the Console. (this resolves the bug introduced in UR6) Fix:…
One of the changes in SCOM 2019 is that RunAs accounts now require Log on as a service, instead of Log on locally, which I previously discussed here: https://kevinholman.com/2019/03/14/security-changes-in-scom-2019-log-on-as-a-service/ If you deploy SCOM 2019 agents, and use RunAs accounts, you might see these events: Log Name: Operations ManagerSource: HealthServiceEvent ID: …
In the SCOM Console you will see some new views in the Administration panel: These actually aren’t new for SCOM 2019, they existed in 1801/1807 as well. These are driven by a Management Pack discovery, in the MP: Microsoft.SystemCenter.OperationsManager.Internal (Operations Manager Internal Library). The new discovery is Microsoft.SystemCenter.OM.Products.Discovery (Discovery of…
You need to know about this. Yes, there will be a test later. One of the changes in SCOM 2019 is increasing the out of the box security configuration. Previous versions of SCOM not only allowed, but *required* the “Log on Locally” user right for SCOM service accounts and RunAs…
There is already a very good deployment guide posted on Microsoft Docs here: https://docs.microsoft.com/en-us/system-center/scom/deploy-overview The following article will cover a basic install of System Center Operations Manager 2019. The concept is to perform a limited deployment of OpsMgr, only utilizing as few servers as possible, but enough to demonstrate the…