Hello, We are using the Windows Service template to create monitor for a particular service. As a result, we have noticed the creation of 2 underlying monitors, which leads us to the following questions: Q1: The monitor targeting the service is automatically configured with a frequency of 60...but the question is 60 what...seconds or minutes?!? It is based on the Win32ServiceInformationProviderWithClassSnapshotDataMapper module. Q2: Why does the template create a second monitor that is disabled? I understand that the monitor is inherited from Windows Service, but why does it exist in the first place? Thanks, Larry

Hi Larry, For Q1, The frequency should be 60 seconds. For Q2, the following article described the situation: http://oopsmgr.wordpress.com/2008/12/12/scom-2007-r2-day-three/ It should a by designed feature.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Good morning Vivian, Q1 - I should have mentioned “Discovery” instead of “Monitor” in the original question. In your response, you mention "should", which has left some doubt in my mind. If this is correct, then I am to understand that each and every server targeted (i.e. in target group) runs the discovery every 60 seconds! This seems a little excessive, no? Can someone confirm with certainty? Q2 - The referenced URL only states the following in regards to the second monitor: “So now we are waiting for an alert to show up. In our case it should pop up in 10 minutes time. Let’s review what we have in inside MP. First of all there are two monitors for Windows Service Running State (?). First one is created within new MP and can be modified in whatever way, second one is inherited from Windows Service library and can only be overriden. Moreover, the second has already been disabled by override, while first one is enabled by default.” It unfortunately does not explain its existence. Larry

Hi, no activity for a long time. will mark as answer now. feel free to re-open. thanksAnders Bengtsson | Microsoft PFE | blog at http://www.contoso.se

Hi! Q1 Regarding the discovery, once every 60 seconds is indeed excessive. Once every 24 hours should be more appropriate for a discovery targeting Windows Computer. However, an override (or directly editing the MP) easily fixes that. Q2 The Monitoring template actually creates three Monitors. Whether the last two are enabled or disabled depends on what you configured when running the Wizard. The three are "Service Running State", "Windows Service CPU Usage Monitor" and "Windows Service Memory Usage Monitor". Note! The monitors get created regardless what you enter in the Wizard. You also get a number of rules, which are harder to spot (since they are targeted at the ClassType that your service inherits from). An easy way to see this is to go to Authoring->Management Pack Templates->Windows Service Select your service template, Right-Click and View ManagementPack Objects->Whatever your interested in. (sorry, if you know all this, I'm not trying to patronize) /Roger ps Read the authoring guide and do this in the Authoring Console. It's actually not very difficult and you will get much more control.This posting is provided "AS IS" with no warranties, and confers no rights.