Search Our Site


Last week i have been working on monitoring a  business critical application. This application does not write events to the Windows event log but only in it’s own log files. With System Center Operations Manager you have several options on monitoring these log files. In this post some tips and tricks on how to do log file monitoring with System Center Operations Manager. There are some important considerations that must be taken into account when monitoring log files with System Center Operations Manager. The next lines are taken from the Microsoft support site: (

When monitoring a log file, Operations Manager remembers the last line read within the file (a ‘high water mark’). It will not re-read data before this point unless the file is deleted and recreated, or renamed and recreated, which will reset the high water mark. If a logfile is deleted and recreated with the same name within the same minute, the high water mark will not be reset, and log entries will be ignored until the high water mark is exceeded. An implication of this is that log files that are cleared periodically without being renamed and recreated, or deleted and recreated, will not have entries in them processed until the high water mark from before the log is cleared is exceeded. Operations Manager cannot monitor ‘circular log files’ (i.e. log files that get to a certain size or line count, then start writing the newest entries at the beginning of the log) for the same reason. The log file must be deleted or renamed and then recreated, or the application configured to write to a new log once the current log is filled. Example:


Until a few weeks ago I was struggling with exporting and sorting data that I get from PowerShell commands (running against Operations Manager :-)). I could not think of an efficient way to accomplish this. I used the export-csv CmdLet to do an export and after that open the CSV file and sort the data in Excel.

Of course there are many more ways to sort data but I really like the Out-GridView Cmdlet I “discovered” a few weeks ago.
This one is available in PowerShell 2.0. The Out-GridView cmdlet is automatically installed when you install PowerShell 2.0; however, the cmdlet won’t do anything unless you also have .NET Framework 3.0 installed.


My life gets easier every day!!


I had an issue last week when i renamed an Operations Manager group in the console. I had a scheduled task in place for setting maintenance mode which was targeted to this group. After the group has been renamed this stopped working. Further investigation shows that the display name for the group wasn’t changed correctly in the database. When running the Get-SCOMGroup command the old display name showed up.

I know about the older problems with strange display names in the console, but this seems different…or not??

For as far as I know this isn’t a know issue but to make sure I have posted this problem on the TechNet forums:

After some searches on internet I decided to try the solutions used for the “weird display names” which is checking the LanguageCode column in the dbo.__MOMManagementGroupInfo__ table.

-+ Be Aware that Microsoft does not support editing the Operations Manager databases this way +-


Volg ons op: