I suggest you ...

support maintenance schedules which targets a SCOM group with a lot of members

When a maintenance schedule targets a SCOM group with 500+ members/objects to put into maintenance mode, each object is put into maintenance mode simultaneously. This means each object will exit maintenance mode simultaneously as well. This results in a very large MaintenanceModeStage table in the data warehouse. The rule which processes this table has a 30 second timeout, while it takes several minutes to process all entries, and raises multiple 31551 events. The timeout value cannot be changed.
Would it be possible to either not put each group object in maintenance mode simultaneously, or to allow the timeout value to be changed?

7 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
Dennis shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Signed in as (Sign out)
Submitting...

Feedback and Knowledge Base