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 […]
– Nagios + SCOM – Uninstall Nagios Agent remotely using Powershell
Posted on Author stefanroth
I don’t like to clean up very much, but there are certain cases where it really makes fun to clean up. Especially if there a Non-Microsoft product, Powershell and SCOM involved. In my case a customer decided to replace his Nagios system through SCOM 2012. Cool!!! Because Nagios also uses an agent for monitoring, one […]
SCOM 2012 Agent Failover – An Event Log Check
Posted on Author stefanroth
Sometimes we need a sign to check that some things happen . For me I wanted to visualize and verify if a SCOM agent failed over properly or not. As you might know the Windows agents do not report to a SCOM 2012 resource pool. If you install an agent on a Windows server the […]