0

0

Forums: Thx for the reply Maybe I did not explain it right. We not trying to manually close or Ack the Alerts.If that was the case , its a no brainer.Its part of the automatic workflow that a new alert goes through.All new alerts are acted upon by the ALert Update Connector to enable them to go to a third party monitoring product. So, the issue, we having is that in cases where the issue is...

0

0

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

0

0

Forums: 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 to do triple homing?  Is this even suggested?  Nothing set in stone yet, just looking for input to help planning.  Thanks.

0

0

Forums: 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 Alert Update connector kicks in & changes the status from Closed\Resolved  to "Ack by Connector".This results in the Alerts staying Ope...

0

0

Forums: :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 search for. Well if you leave it out make an educated guess what will happen... it won't know in which Management Pack it has to search for. Add a...

0

0

Forums: $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 charm! Second script is still problem. Even I create/change to "System.Entity" - $MPElement[Name="System.Entity"]$  $MPElement[Name="Mic...

0

0

Blog: 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 into one database server with two instances running in a virtual on my HyperV systems controlled by SCVMM. The host that I put this database on was...

0

0

Forums: 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.