Author: Stoyan Chalakov

 

SCOM 2016 UR6 console crashes with “Incorrect syntax near the keyword ‘CREATE’.”

Today’s blog article will not be very long, but I hope very helpful for all of you (and spare you some headaches), who already installed SCOM 2016 Update Rollup 6 and are experiencing this particular issue.   Who is affected: The actual problem occurs only for SCOM operators, who have scoped views (are member of […]

Operations Manager Linux/UNIX agent failover and Resource Pools

While answering questions on the Microsoft Technet Forums, I noticed that are lots of questions on topics, which are repeating, or which often are not that well understood. So I had a discussion with Sam (Sameer Mhaisekar) and we decided that it would be very beneficial if we write short blog posts on those topics. […]

System Center Operations Manager and the syptoms of the disabled SQL Server Service Broker

Working with SCOM on an everyday basis means you face some of the so called “known” issues and as such it is very helpful if you are able to identify and resolve them in a quick manner. Today’s post will be all about some of the faulty behaviour that could arise, because of one particular […]

System Center Operations Manager, “Out of memory” and the failing MSSQL workflows

Today’s post will be pretty short, however hopefully very informative and helpful. Actually, the content of it is not mine, but I am sharing it, because I would like this information to reach as many people as possible. If you have been working with the SQL management pack for System Center Operations Manager, then you […]

Automating SQL operations with Invoke-Sqlcmd – challenges and solutions

I’ve been working on some automation tasks with SMA 2016 lately, which involved quite heavy data transactions to a SQL database in the backend. Doing this, I have faced some really interesting challenges that I would like to share now with you and of course their respective solutions/workarounds. Reading and writing data to a SQL […]

Using Optional Parameters in Service Management Automation (SMA) runbooks

In this post, I would like to share an interesting observation I have made when working with optional parameters in SMA runbooks. The requirement is pretty basic – pass an optional [datetime] parameter to an SMA runbook and trigger an action, depending on the whether a value has been passed or not. The error message […]

The mysterious case of the queued Service Management Automation (SMA) runbook jobs (a bit more on Sandbox process separation)

It is weekend again and I have decided to take some time and share some interesting findings in regards to Service Management Automation (SMA) 2012 R2 – an issue I’ve experienced and its possible workarounds. The Problem Random SMA runbook jobs were intermittently getting stuck and remained in a “Queued” job status. The only thing, […]

Forcing a SCOM discovery with PowerShell (the easy way)

While working on customer’s site I noticed on couple of occasions that triggering a specific discovery in SCOM costs too much time to the guys from the Operations Team. What they were basically doing is following a procedure, found in a blog post, describing how to manually trigger a SCOM discovery: SCOM 2012 – Manually […]

Update Rollup 7 (UR7) for SCOM 2012R2 – Now it is possible to see the version number directly in the console

Original Version in German: Update Rollup 7 (UR7) für SCOM 2012 R2 – Die Produktversion in der Konsole ist da! https://blog.pohn.ch/update-rollup-7-ur7-fuer-scom-2012-r2-die-produktversion-in-der-konsole-ist-da/   How to check whether a SCOM Update Rollup (UR) has been installed properly? How to obtain the current product version of SCOM 2012 R2? Until UR6, you had to check various library files […]

Automating the SCOM 2012 R2 agent deletion using PowerShell

In my last project I was given the task to automate the deletion of SCOM agents (both UNIX/Linux and Windows SCOM agents) using a PowerShell script, which then would be executed as part of the deprovisioning process of a specific virtual machine. This was necessary, because after decommissioning virtual machines their associated monitored objects remained […]