Hi , recently i recieved 2 warning about failed powershell script and my data access service and service group are not monitpred

my scom scom version 2012 R2.

System.Management.Automation.CmdletInvocationException: The Data Access service
is either not running or not yet initialized. Check the event log for more
information.At line:10 char:19
+ $alertsByObject = Get-SCOMAlert
-ResolutionState 0 | group MonitoringObjectId
+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
at
System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object
input, Hashtable errorResults, Boolean enumerate)
at
System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean
ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[]
pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext
funcContext)
at
System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame
frame)
at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)
at
System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame
frame)

Hello!

On 11.02.2016 my OM server displayed the error stating "DB free space is low". I really was not able to add any information to the OM db. I then - 11.02.2016! - resloved the issue (by enabling the autogrowth) and since then I didn't have any problems with the database. Nevertheless, OM's console still displays the status of my OM server as 'critical' even today, 20.02.2016.

Why hasn't the OM server's status changed back to 'optimal'?

Disk C: free space ~ 25GB.

Thank you in advance,

Michael

Dear all,

From scom if we don't have MP for some application , we can try monitoring that application through service , event log , WMI , with some script . my question here is what else we can consider for set up monitor apart from (service , event log , WMI , with some script).

74KMS

Hello All,

I'm coming across a bunch of SCHANNEL issues on a server I'm configuring only TLS 1.2 on. When I configure TLS 1.2 and reboot I immediately get SCHANNEL issues - if I stop the SCOM agent they all go away. If I re-enable TLS 1.0/SCOM it's happy.

Does SCOM 2012 R2 not support TLS 1.2 yet? I can't seem to find any documentation on this and I've ran through the agent config, management server, etc.. I've ensured TLS 1.2 is available on my Management Server.

Any help would be appreciated.

Dear all,

We have a gateway server implemented in our environment it was working fine , when license got expired it( Gateway server) went to  grayed out status , we requested new certificate and imported all , however after new certificate implementation , still GW is in Grayed out status.

Error :

Failed to initialize security context for target MSOMHSvc/XXXXXX.com The error returned is 0x80090303(The specified target is unknown or unreachable).  This error can apply to either the Kerberos or the SChannel package.

The OpsMgr Connector could not connect to MSOMHSvc/XXXXXX.com because mutual authentication failed.  Verify the SPN is properly registered on the server and that, if the server is in a separate domain, there is a full-trust relationship between the two domains.

Any idea pls ?

It's strange just happened in these day. When we tried modify or create the notification, it had the following error:

Date: 2/22/2016 11:27:20 AM
Application: Operations Manager
Application Version: 7.0.9538.1109
Severity: Error
Message: The notification subscription was not valid for the update. See inner exception for details.

System.InvalidOperationException: The notification subscription was not valid for the update. See inner exception for details. ---> System.ArgumentException: The notification subscription is not valid for insert. See inner exception for details. ---> Microsoft.EnterpriseManagement.Common.ManagementPackException: Verification failed with 5 errors:
-------------------------------------------------------
Error 1:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 2:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 3:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 4:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 5:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
 ---> Microsoft.EnterpriseManagement.Common.ManagementPackException: Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
   at Microsoft.EnterpriseManagement.Common.Internal.MonitoringNotificationServiceProxy.UpsertNotificationSubscription(String conditionDetectionConfiguration, String dataSourceConfiguration, IList`1 endpoints, String name, String internalName, String displayName, String description, String languageCode, String targetString, String targetManagementPackId, String targetManagementPackVersion, String targetManagementPackPublicKey, String targetManagementPackAlias, Int32 subscriptionType, Boolean enabled, Boolean resetStateOnEnabled, Boolean isUpdate)
   at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.UpsertNotificationSubscription(NotificationSubscription notificationSubscription, ManagementGroup managementGroup, Boolean resetState, Boolean isUpdate)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.UpsertNotificationSubscription(NotificationSubscription notificationSubscription, ManagementGroup managementGroup, Boolean resetState, Boolean isUpdate)
   at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.UpdateNotificationSubscription(NotificationSubscription notificationSubscription, Boolean withTimeReset)
   at Microsoft.EnterpriseManagement.Administration.NotificationSubscription.Update(Boolean withTimeReset)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.Administration.NotificationSubscription.Update(Boolean withTimeReset)
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Notification.SubscriptionCompletionPage.SaveChanges()
   at Microsoft.EnterpriseManagement.Mom.Internal.UI.Notification.SubscriptionCompletionPage.CommitChangesJob()
System.ArgumentException: The notification subscription is not valid for insert. See inner exception for details. ---> Microsoft.EnterpriseManagement.Common.ManagementPackException: Verification failed with 5 errors:
-------------------------------------------------------
Error 1:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 2:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 3:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 4:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 5:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
 ---> Microsoft.EnterpriseManagement.Common.ManagementPackException: Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.Common.Internal.ServiceProxy.HandleFault(String methodName, Message message)
   at Microsoft.EnterpriseManagement.Common.Internal.MonitoringNotificationServiceProxy.UpsertNotificationSubscription(String conditionDetectionConfiguration, String dataSourceConfiguration, IList`1 endpoints, String name, String internalName, String displayName, String description, String languageCode, String targetString, String targetManagementPackId, String targetManagementPackVersion, String targetManagementPackPublicKey, String targetManagementPackAlias, Int32 subscriptionType, Boolean enabled, Boolean resetStateOnEnabled, Boolean isUpdate)
   at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.UpsertNotificationSubscription(NotificationSubscription notificationSubscription, ManagementGroup managementGroup, Boolean resetState, Boolean isUpdate)
   --- End of inner exception stack trace ---
   at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.UpsertNotificationSubscription(NotificationSubscription notificationSubscription, ManagementGroup managementGroup, Boolean resetState, Boolean isUpdate)
   at Microsoft.EnterpriseManagement.MonitoringNotificationManagement.UpdateNotificationSubscription(NotificationSubscription notificationSubscription, Boolean withTimeReset)
   at Microsoft.EnterpriseManagement.Administration.NotificationSubscription.Update(Boolean withTimeReset)
: Verification failed with 5 errors:
-------------------------------------------------------
Error 1:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 2:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 3:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 4:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------
Error 5:
Found error in 2|Microsoft.SystemCenter.Notifications.Internal|7.0.9538.0|Microsoft.SystemCenter.Notifications.Internal|| with message:
Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
-------------------------------------------------------

Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)
: Detected malicious verification code when verifying element of type Microsoft.EnterpriseManagement.Configuration.ManagementPackRule with inner exception: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.VerifyDataTypes(Dictionary`2 moduletypes)
   at Microsoft.EnterpriseManagement.Configuration.ManagementPackRule.Verify(VerificationContext context)
   at Microsoft.EnterpriseManagement.Configuration.Verification.VerificationEngine.VerifyCollectionItems(Object context)

Hi friends,

I want to monitor the ping status for servers , storage device etc , is there is way to create rule or monitor to check the ping status. I mean in case of request timed out , we should get the alert.

I have gone through below forum , is there any other way.

http://www.opslogix.com/download-ping-management-pack

Manju

Evaluating SCOM 2016 TP4 and OPS DB is not listing out during the SCOM installation.I am using SQL Server 2012 Ent Edition. But Microsoft states SQL 2012 supports SCOM 2016 Technical preview... Any specific reason behind it???

Hi!

I have a GW set up recently. I have imported certificates on it and its working fine.

The situation is, the AD team is later going to upgrade the certs (From CA1 to CA2).

For authentication, the certs issued to MS and GW have to be issued from same CA.

Now, when they change the CA from CA1 to CA2, I assume I'll have to upgrade it on both the servers.

Will it need any downtime for my GW clients? Or the GW will "store" some data until the time certificates are upgraded or something?

Thanks,

Sam

I was wondering if there was a "simple" way to back-rev an existing MP in SCOM 2012. I'm working on theCisco UCSM Management Pack. Another Admin upgraded the MP to version 3.1.2.0. I need to get it back to 3.0.1.0.

Of course there are always complications. I can't just delete the MP because it has a dependency on a custom MP for monitoring our Blade Servers. So, I guess what it comes down to, is there a PS Command or Command Line that I can use to "force" it to import the 3.0.1.0 version? Or a relatively easy way to do it?

---

Normal is relative

Hi,

I am monitoring Exchange 2010 from Operations manager 2012 R2, i have imported the required management pack but facing below issue.. i am looking for solution 

1. out of 6 Exchange servers, only 4 Exchange servers are discovered through Exchange 2010 MP.

2. I want to create the custom Dashboard of Exchange server monitoring for this i created one Group with explicit members of all exchange servers, while using the performance widget and choosing the created custom group (including all exchange servers) inGroup or objects no any counters are showing.. i have to show case the dashboard view of All Exchange services, mail queues, Exchange database and exchange server Disk,Network, memory utilizations...

---

Shailendra Dev

Hi

I successfully finish network discovery with event 12008:

Discovery Completed
Devices discovered: 211
Windows computers filtered: 0
Devices in pending list: 8
Devices excluded: 0
Duration Total (sec): 16203
Duration of Probing (sec): 2920
Duration of Processing (sec): 13282 ...

but only part (92) of this devices a can see in Network managment - Network devices, and other (119) i did't see there ( only see in Network monitoring with grey out - not monitoring).

How can i fix this?

State of network discovery server - "2" (and don't change)
Number of Devices Processed - "37" (and don't change)
Discovery rules status - "Processing 31/211" (and don't change)

Clear cache, delete discovery rule and start in again - did't help.

Thanks.

Hi,

Quick question: If no accounts are set up as per the doco for Low Privilege environments i.e.SQLDefaultAction, SQLDiscovery,  SQLMonitor

then will discovery and monitoring still work using the SCOM Action Account as a default or do the above need to be set up?

An alert is generating since 6.6.4

Management Group: MyMgmtGrp. Script: DiscoverSQL2012FileGroups.js : Cannot login to database [MySQLServer.com][MSSQLSERVER:master]

The DBAs have given the SCOM Default Action Account SA access and the alert still keeps coming.

Thx,

John Bradshaw

Hello,

      Is there any way to _only_ enable port monitoring based upon words in the 'Interface Description'?

Hey, 

Has anyone else run across this issue? I am attempting to run the command Remove-SCOMDisabledClassInstance from the Operations Manager Shell and i get the following message.

PS C:\> Remove-SCOMDisabledClassInstance
**WARNING** This operation WILL result in class instances and relationships being permanently deleted.  This operation i
s irreversible and will likely result in a significant amount of activity in the operational database.  Are you sure you
 want to do this? [Y/N]

y

Started.  This operation may take a very long time to complete.

Remove-SCOMDisabledClassInstance : Could not find stored procedure
'dbo.p_DiscoverySourcesEligibleForDeletionDueToOverridesProcedure'.
At line:1 char:1
+ Remove-SCOMDisabledClassInstance
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (Microsoft.Syste...nstancesCommand:RemoveSCDisabledClassInstancesComma
   nd) [Remove-SCOMDisabledClassInstance], UnknownDatabaseException
    + FullyQualifiedErrorId : ExecutionError,Microsoft.SystemCenter.OperationsManagerV10.Commands.RemoveSCDisabledClas
   sInstancesCommand

Hi,

We are monitoring AD servers using MS SCOM 2012 R2.

The performance data for most of the criteria/parameters are successfully collected but we do not find any targets or servers to be selected to view the performance counter for 

• DC Response Time,
• GC Response Time, &
• DC/GC Response Time.

We have set the override value to 'True' for the parameter 'MonitorSSLLDAPBind', as the standard port used is 636. However, no performance data is being collected for any of the monitored AD servers.

Please suggest, how to fix this issue?

SCOM version : 2012 R2

AD Server 2008 & above MP version : 6.0.8321.0.

Thank you.

Thank you.

Hi All,

Need to configure alert for range of Event ID (ex: 2100 - 2200) and it not supposed to generate alert with same event id within next 24hours.

---

Sandoss Kumar N

Hi All,

We are starting to see the below events on one of the SCOM 2012 R2 UR8 Management server.

Event id: 33333
Event Source: DataAccessLayer
Log: Operationsmanager

Data Access Layer rejected retry on SqlError:
 Request: ConsoleTasks -- (LanguageCode1=ENU), (LanguageCode2=), (Category0=f7466c1f-409b-8f70-fa3d-a0211ac98167)
 Class: 16
 Number: 10316
 Message: The app domain with specified version id (191661) was unloaded due to memory pressure and could not be found.

Other one:



Event id: 26319
Event Source: OpsMgr SDK Service
Log: Operationsmanager

An exception was thrown while processing GetConsoleTasksByCriteria for session ID uuid:e1b97eeb-665f-4bbb-8467-0522eb7dc42a;id=313.
 Exception message: The creator of this fault did not specify a Reason.
 Full Exception: System.ServiceModel.FaultException`1[Microsoft.EnterpriseManagement.Common.UnknownDatabaseException]: The creator of this fault did not specify a Reason. (Fault Detail is equal to The app domain with specified version id (191661) was unloaded due to memory pressure and could not be found.).

Anyone experienced this "unloaded due to memory pressure and could not be found" issue on SCOM ?

Does any one have a solution for this ?

---

Gautam.75801

The scenario

We have a 2 server SCOM management group installed in a “Domain A”.

Domain A includes a certificate authority.

We have 100+ Untrusted Customer Domains

I shall use 1 of those domains, “Domain B” as an example for this scenario.

 

As we have such a large number of untrusted domains,  some of which only contain 1 or 2 customer servers, it is not feasible of logical for us to deploy a SCOM Gateway Server to each of these. As a result,  we install these servers in untrusted domains as DMZ servers; making use of PKI Certificates for secure communications.

 

Example

Server Name : Server1.DomainB.Com

A certificate with Client Authentication and Server Authentication is generated for Server1.DomainB.Com by the CA in DomainA. Call it Certificate1

The SCOM Agent is installed on Server1

Certificate1 is installed in the “MY” store / Personal store of Server1

MOMCertImport is run and Certificate1 is selected. An Operations Manager Certificate Store is created and a self signed certificate is created

Comms between Server1.DomainB.Com and SCOMServer.DomainA.Com are activated and all is fine.

 

The Problem

Server Name : Server2.DomainB.Com

Server 2 hosts an applications / feature from an unspecified application that uses a certificate for communication; let’s call that Application1

That certificate has “Client Authentication” and “Server Authentication” capabilities. Let’s call that “Certificate2”

 

A certificate with Client Authentication and Server Authentication is generated for Server2.DomainB.Com by the CA in DomainA. Call it Certificate3

The SCOM Agent is installed on Server2

Certificate3 is installed in the “MY” store / Personal store of Server2

MOMCertImport is run Certificate3 is selected (Certificate2 is also presented as an option, as you would expect).

An Operations Manager Certificate Store is created and a self signed certificate is created

Comms between Server1.DomainB.Com and SCOMServer.DomainA.Com are activated and all is fine.

 

Problem: Application1 stops working.

 

Assumption

 

Application1 has not been configured to intelligently select certificate2 and is selecting the certificate3 from DomainA incorrectly.

 

Attempted Resolution 1

I have removed Certificate3 from the personal store.

 

Result

Application1 begins working again

SCOM Communication continues successfully until the health service is restarted or the server is rebooted

 

Attempted Resolution 2

I have moved Certificate3 from the personal store to a newly created store, call is store1

 

Result

Application1 begins working again

SCOM Communication continues successfully until the health service is restarted or the server is rebooted

Any help would be greatly appreciated!

Thanks,

Mark

Hi All,

I am getting below error during uninstalling the agent. When i select the latest momagent file path it throwing another error.

How to resolve the issue.

---

Sandoss Kumar N