During my last assignment I worked with the SCOM to SCSM Alert connector. This connector is syncing alerts from System Center Operations Manager to System Center Service Manager. This is a two-way connector, information from SCSM is synced back to Operations Manager. During the configuration of this connector we ran into an issue with Secure Vantage Audit Manager ACS Optimizer.
Authoring
SCOM: Service Monitoring – Part 3
StandardIn the first part of my blog series about Service Monitoring I’ve described how Service Monitoring could be implemented en what parts of Service Monitoring are important. In the second part I’ve described the structure of Distributed Applications and how you can make your Distributed Applications dynamic. You can find Part 1 and Part 2 here. In this blogpost I want to focus on creating a distributed application and discovering monitoring objects using an external source. In my case the external source is an XML file.
SCOM 2012: Process Monitoring on Session Hosted Servers
StandardThis week I received a question about process monitoring. The question was about monitoring CPU and Memory usage of processes on RDS or Citrix XenApp Session Host servers. Process monitoring is one of the standard capabilities so I started with configuring process monitoring through the template which you can find in the Authoring section. But the results were not what I wanted to see. Check this blog to see why!
SCOM 2012: ACS Forwarder Security Log Retention Monitor
StandardIn an OpsMgr Audit Collection Services implementation the local security logs on the forwarders are the queue when the collector is not available. So the retention time of the Security Log is a very important, but out-of-the-box not monitored by OpsMgr. Today I decided to create a PowerShell monitor which monitors the retention time of the security event log. This PowerShell monitor uses the following script to define the retention of the Security event log of an ACS forwarder.
SCOM 2012: ACS automatic failover (update)
StandardA couple of weeks ago I posted my ACS collector automatic failover script. I have implemented this solution in my current ACS implementation and based on that implementation I have 2 tips which avoids two active controllers.
SCOM 2012: ACS Collector automatic failover v2
StandardLast month I created an OpsMgr ACS Collector failover script. This script worked but was not able to failover the ACS Collector role in all scenarios. This was mainly based on the fact that I used the existing ACS collector service monitor. This monitor checks the AdtServer service and alert when this service fails. Only when the complete server is down this monitor goes into a gray state instead of critical state. So I decided to add some additional components to the failover script. An updated version of the failover script (management pack) can be at the end of this blogpost.
Continue reading
Speaker at Experts Live 2014
Standard
I’m honored that I can present a System Center Operation Manager session at the Dutch community event of the year! Experts Live is a great event with session about Microsoft different technologies like Azure, Hyper-V, System Center, PowerShell, SQL and Office365. My session at Experts Live is about how to transform your OpsMgr environment from component monitoring to Service Monitoring. Continue reading
SCOM 2012: SCOM Groups based on AD Groups (PowerShell)
StandardBased on an article of Boris Yanushpolsky I was inspired to build a PowerShell equivalent. Boris described how you could populate an SCOM group with members of an Active Directory group. His example was using VBScript. Since I’m trying to avoid VBScript I have created a PowerShell one.
SCOM 2012: ACS Alert on logons at Servers
StandardThis week I received a nice question when working on a ACS project. The question was to get an alert when an interactive logon event occurs on a group of servers.
With this question the following requirements were asked:
- The alert should only be sent if the user account is member of an Active Directory group;
- The alert should only be generated for servers is which are member of a specific OU;
- The alert should be logged almost real-time. Continue reading
SCOM 2012: Dependency Monitor not working after re-import of an Management Pack
StandardLast week I discovered a problem with the Dependency Rollup monitors inside one of my management packs. After a re-import of the management pack the dependency rollup monitors didn’t work anymore. The monitors would not initialize after the re-import. When I updated the management pack anything was fine but with a re-import of the Management Pack I ended with broken dependency roll-up monitors.