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 […]
In part 1 we installed LINUX and now it is time to get SCOM 2012 ready for LINUX monitoring. There are several steps we need to do: Set up a Resource Pool Import the management packs Setup name resolution Configure the RunAs accounts Assign the RunAs accounts to profiles.
In this post here on possible cause why the discovery wizard could run forever. Last week I faced a situation where the discovery wizard for deploying Linux agents and for deploying windows agents didn’t work. The setup topology was 2 management servers SCOM 2012 and one dedicated SQL Server 2008 R2 SP1 for the SCOM databases.