Related Articles
SCOM 2016 – System.Data.SqlClient. SqlException, Exception Error Code: 0x80131904 Login failed for user
Posted on Author stefanroth
Sometimes there are things you won’t understand. I tried to install a new SCOM 2016 management server in a virgin Azure VM (Windows Server 2016). The necessary SQL Server 2016 was placed on another Azure VM (Windows Server 2016). Well this is nothing special and I have installed SCOM a gazillion times, BUT now I […]
SCOM 2012 – Find SCOM Object for “Unknown” ID in Alert
Posted on Author stefanroth
There are sometimes alerts which might contain some strange id’s which are not as informational as you might would like have. One way to find out what is hiding behind this id is to use a SCOM Powershell command. As an example, today I received an alert that looked like this…
SCOM 2016 – Upgrade Notes from the Field
Posted on Author stefanroth
Upgrading from SCOM 2012 R2 to SCOM 2016 is theoretically no such big deal. BUT sometimes you could face issues at the customer’s infrastructure, which force you to take some extra hurdle. This post should give you a high level overview of different migration scenarios and additionally some pitfalls you could meet upgrading to SCOM […]