realscom

Notes on using the health service SID to monitor SQL instead of Run As accounts. I had to do this for my Commvault mp because using Run As account/profile wasn't an option. I followed the article in the link below called SCOM 2016 doco . Appendix Links Kevin Holman article SCOM 2016 doco SQL Server 2016 doco

Disclaimer Use this management pack at your own risk. I accept no responsibility if it causes damage. Intro A simple little management pack to monitor Commvault infrastructure. This management pack has a good example of using a Run As Account/Profile for a rule and a monitor using cookdown. Products Not applicable. Management pack components Type Name Class Commvault.Class.Service Discovery Commvault.Discovery.AllServices Discovery Commvault.Discovery.CommServes Discovery Commvault.Discovery.MediaAgents Group Commvault.Group.CommServes Group Commvault.Group.MediaAgents Monitor Commvault.Monitor.AllServices

Disclaimer Use this management pack at your own risk. I accept no responsibility if it causes damage. Intro A simple little management pack to monitor Trellix infrastructure. Products Software versions used for testing: Product Version Trellix ePolicy Orchestrator 5.10.0 Trellix Agent Handler 5.10.0 Trellix Agent 5.7.8.262 5.7.6.251 5.6.3.157 5.5.0.447 Management pack components Type Name Class Trellix.Class.ePolicyOrchestrator Class Trellix.Class.AgentHandler Class Trellix.Class.Agent Discovery Trellix.Discovery.AgentHandlerRegistry Discovery Trellix.Discovery.AgentRegistry Discovery Trellix.Discovery.ePolicyOrchestratorRegistry Discovery Trellix.Discovery.Service Monitor Trellix.

I had to use a Run As Account/Profile for my monitor Commvault.Monitor.BackupStatus  so it could access the commserv database. I created an account and when I went to hook up the profile I got this error: The mp was sealed and I had this line in it for the Run As profile: <SecureReferences> <SecureReference ID="Commvault.RunAsProfile.CommvaultDb" Accessibility=" Internal "/> </SecureReferences> The problem is the highlighted bit. I took a look at the  Microsoft.Windows.Cluster.Library mp and it had this: <SecureReferences> <SecureReference ID="Microsoft.Windows.Cluster.PrivilegedAccount" Accessibility=" Public " Context="System!System.Entity" /> </SecureReferences> I changed it to this, re-sealed and was able to save it: <SecureReferences> <SecureReference ID="Commvault.RunAsProfile.CommvaultDb" Accessibility=" Public "/> </SecureReferences>

If you have CLS in a PowerShell script that's in an mp you can get this error. Remove it to fix. FailedJobs.ps1 executed in 0m 0s 190ms :  Running as: NT AUTHORITY\SYSTEM Workflow Name: SQL.Monitor.FailedJobs Management Pack: SQL.Monitoring (2023.7.18.0) PowerShell Version:  Output: Exception setting "CursorPosition": "set_CursorPosition"