0

0

Well you don't need to update the alert, that "Ack by Connector" is redundant. You only have to acknowledge the alert.

0

0

We are considering System Center Advisor, which would require dual homing agents.  We are also planning on SCOM 2012 migration, one option would to dual home to the new 2012 Management Group.  So this brings me to this question- Is it possible t...

0

0

We have an Alert Update Connector, which updates Custom Fields on Alerts. Have been noticing that when a Critical  alert comes in from a monitor(say a SQl Agent monitor) , & the state changes immediately back to resolved(ex SQL Agent hiccup), the...

0

0

:D what are you doing? Of course it won't find System.Entity, you have to tell it in which Management Pack that class is. Ever wondered what this is for: MicrosoftSystemCenterInstanceGroupLibrary6172210! <- it tells it in which Management Pack it has to s...

0

0

$ComputerName='FQDN' $MC = Get-MonitoringClass -Name System.Entity $MOS = $MC | Get-MonitoringObject foreach ($MO in $MOS) {  if ($MO.Path -eq $ComputerName) { write-host $MO.GetLeastDerivedNonAbstractMonitoringClass().name }  } Working like a...

0

0

When I was building my System Center 2012 testing lab I installed SQL server in a virtual running on my HyperV systems I was controlling with SCVMM 2012 RC. I’ll admit it, it seemed like a good idea at the time. I put all of the System Center products in...

0

0

Because the VMM installer tries to install an agent on the server running WSUS, I suspect only way this is going to work is if you install WSUS before you install VMM on your server. Not even sure that would do it, but would be worth a try in the lab.

0

0

Ooops, well the method Getmonitoringclass() doesn't exist, there's GetMonitoringClasses() but that's not what you need. What you need is: $MO.GetLeastDerivedNonAbstractMonitoringClass().name And, I already explained to you that have to target System.Enti...

0

0

This is not working from some reason: $ComputerName='FQDN' $MC = Get-MonitoringClass -Name System.Entity $MOS = $MC | Get-MonitoringObject foreach ($MO in $MOS) { if ($MO.Path -eq $ComputerName) { write-host $MO.GetMonitoringClass().Name  } }...

0

0

Thanks again, this works! I got email, and alert in console. Is there any way to get this with monitors, in order to get alerts auto-closed (what I can't get with rules)?

0

0

Hi I dont have SCOM 2012 RC in lab environment. I add the following property: $Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$ and it works fine. I think there is problem with ipaddress property. Yes i have edit the alerting i...

0

0

Thanks! It means if I create rule for this event, I can get email only if it is alerting rule? In that case, I have to close alert manually.

0

0

Subscriptions are only available for alerts, not for collections.

0

0

Hey SteveO, I tracked this down with Microsoft and blogged on the results here: http://blogs.catapultsystems.com/cfuller/archive/2012/02/02/opsmgr-2012-scom-overriding-the-default-autosignout-value-for-the-web-console.aspx. I hope it helps / it worked wel...

0

0

For me is important to get email, alert is not necessary. Target of collection rule is ''Monitoring Cluster Service'', and I don't get mail.

0

0

What is the target of the collection rule? Use that one for your alerting rule and see if that works out for you.

0

0

The issue you have is that you target the DBEngine class, change that to System.Entity otherwise you can't get anything but DB Engine instances. The relationship is just fine. Regarding "all classes": You have to have a parent (reference point) for which...