Archive for November, 2010

Regular Checks of OpsMgr

November 8, 2010 Leave a comment

A recent question on the Technet Forums was how to best do regular health checks of OpsMgr – here is a reliability worksheet to get started (along with the usual collection of articles that Kevin Holman has on his blog).


ACS Forwarder Connects and Disconnects

November 8, 2010 Leave a comment

I came across this problem on a customer site recently:

Thanks to the blog article all was resolved quickly and relatively painlessly!

Troubleshooting Greyed Agents

November 4, 2010 Leave a comment

A great place to start:

If it is the agent on a Domain Controller that is greyed out then you might want to check these out first:

Categories: Troubleshooting

CU3 and PRO tips

November 2, 2010 2 comments

Just thought it might be useful to stress this if you are looking to apply Cumulative Update 3 – “PRO Integration: PRO Tips do not function correctly after CU3 is installed. Event ID 26319 is thrown in the Operations Manager Event Log, and PRO Tips are not shown. If you are leveraging PRO Tips, we advise skipping CU3 and applying CU4 when it is released. Please contact your CSS representative if you have already applied CU3 and are experiencing this issue.”

There is a hot fix available from PSS but it is very much ” .. use at your own risk”.

Self Tuning Thresholds

November 1, 2010 Leave a comment

Sadly they haven’t quite lived up to the hype and expectation. Hopefully work will continue on them as the underlying principal is undoubtedly very useful. It is just the actual implementation in the current version hasn’t hit the mark:

Just in case the links get groomed over time, here is a summary of some of the limitations as stated by Kevin Holman:
1) “If the healthservice is ever restarted on the agent, the learning process must begin again before you will get an alert.”

2) “These dont always work well for all counters especially counters that vary widely or are ever at zero. You will find the STT to create many alerts when there is not an actionable situation. Also – the STT will not alert until the learning period is set. The learning period is reset on each Health service restart…. so if your learning period is 1 week, and you reboot your server monthly for patching – you only get monitoring 3 weeks out of the month.

In general, as Ake points out in one of the threads – “An alternative could be a consecutive samples over threshold monitor.”


November 1, 2010 Leave a comment