SCOM 2019 agent communication error in workgroup due to certificate issue
Any help to fix the above will be appreciated: Background: SCOM 2016 was successfully upgraded to SCOM 2019. Newly connected client require approval on SCOM Manager The workgroup clients were manually upgraded to the provided SCOM 2019 agent but there is communication error due to certificate error. Certificates were re-imported without any error (MOMCertImport.exe /SubjectName) but the error still exists. The root CA certificate was imported into the Trusted Root Certification Authorities folder Also, a new Client was installed on a new workgroup server but experienced the same error. Questions: Any idea how to fix the above on SCOM 2019 Is there a MOMCertImport64.exe Error on SCOM Manager The OpsMgr Connector negotiated the use of mutual authentication with x.x.x.x:64332, but Active Directory is not available and no certificate is installed. A connection cannot be established. Error on Client OpsMgr was unable to set up a communications channel to xx.domain.com and there are no failover hosts. Communication will resume when xx.domain.com is available and communication from this computer is allowed.System Center 2019 – What’s new
Microsoft just launched Windows Server 2019 and Windows Admin Center, which also raised the interest in System Center 2019. At Microsoft Ignite, Microsoft was talking about what is new in System Center 2019, the future of System Center, and how it fits in with Windows Admin Center and other management tools. Check out what is new in System Center 2019 here: https://www.thomasmaurer.ch/2018/12/system-center-2019/
SSRS Reporting Services HTTP Error 503
In an attempt to repair a broken SSRS installation for Operations Manager, I have attempted a fresh install using SQL Reporting Services 2017 (14.0.600.1669). When running OM 2019 RTM Report Server (Setup version 10.19.10050.0) it changes the SRS extension in the rsreportserver.config, the ReportServer web service stops working with 503 error. Other discussions I have seen with similar issue suggested a newer version of SSRS (done) and others suggest turning off AV (done) and I am still seeing this issue. Does anyone else know how to troubleshoot why the OM Extension would be giving the ReportServer a 503 error? I am wondering if some other aspect of the server hardening could be impacting it? OPSMGRSETUPWIZARD.LOG [12:24:01]: Always: :Adding WebConfigAppSetting to WebConfigFile [12:24:02]: Debug: :Setting retry count to:5 [12:24:02]: Debug: :More: 5 rety to go.. [12:24:02]: Debug: :AddWebConfigAppSettingToWebConfigFile: Added AppSetting with a GroupId of 209e08e0-0bb9-516b-5c3c-256e32c99e8f in the C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\web.config config file. [12:24:02]: Always: :Adding WebConfigAppSetting to ReportingService config file [12:24:02]: Debug: :Setting retry count to:5 [12:24:02]: Debug: :More: 5 rety to go.. [12:24:02]: Debug: :AddWebConfigAppSettingToWebConfigFile: Added AppSetting with a GroupId of 209e08e0-0bb9-516b-5c3c-256e32c99e8f in the C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\bin\ReportingServicesService.exe.config config file. [12:24:02]: Always: :Replacing SRS extensions. [12:24:02]: Debug: :ReplaceSRSExtensionsWithOMExtensions: full SRS URL is : http://VSCOMSQL:80/ReportServer/ReportService2005.asmx [12:24:02]: Debug: :ReplaceSRSExtensionsWithOMExtensions: MOM Server is: vscom.greenfieldsavings.com [12:24:02]: Debug: :ReplaceSRSExtensionsWithOMExtensions: SRS Report Server Folder is: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\ [12:24:02]: Debug: :ReplaceSRSExtensionsWithOMExtensions: RSSrvPolicy.Config File: C:\Program Files\Microsoft SQL Server Reporting Services\SSRS\ReportServer\rsreportserver.config [12:24:02]: Debug: :Setting retry count to:5 [12:24:02]: Debug: :More: 5 rety to go.. [12:24:02]: Debug: :Setting retry count to:5 [12:24:02]: Debug: :More: 5 rety to go.. [12:24:03]: Debug: :ReplaceSRSExtensionsWithOMExtensions: Restarted the service: ReportServer [12:24:03]: Debug: :Setting retry count to:5 [12:24:03]: Debug: :More: 5 rety to go.. [12:24:04]: Warn: :Message:SRSPolicySetter WebException Exception: The request failed with HTTP status 503: Service Unavailable.. Will retry.. [12:24:04]: Debug: :Now Sleeping for : 60000 milliseconds [12:25:04]: Debug: :More: 4 rety to go.. [12:25:16]: Warn: :Message:SRSPolicySetter InvalidOperationException Exception: Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.. Will retry..
Web API for SCOM
Hi, To meet internal goals and intentions as to integrate existing monitoring in to third party systems and in house developed applications, I created a web api for SCOM. The api let's you easily surface data like alerts, and health states on computers and other monitoring objects. Maintenance mode and scheduling in scom 2016 is also implemented. If you want to try it out the full source is available on github https://github.com/ehrnst/System-Center-Operations-Manager-API And on technet https://gallery.technet.microsoft.com/System-Center-Operations-5d88527c If you happen to try it out, I appreciate any feedback you have Martin EhrnstSCOM 2019 Reporting Error - "Cannot execute report"
Running SCOM 2019 with UR4 on a single DB server with 2 management servers. A bit baffled - I have a logical disk space report that has been running in my SCOM environment since SCOM 2016 and I've never had a problem with it. This is a 3rd party report that I found in the community and added to SCOM. I've used it to create daily logical disk space reports for 4 different groups of servers. These are schedule reports that run every morning ~6:00. This worked normally until last week - on Tuesday morning all 4 reports showed normal data, on Wednesday all 4 reports were empty. I tried to run the report from the console and this error pops up: Application: Operations Manager Application Version: 10.19.10569.0 Severity: Error Message: Cannot execute report. System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ReportForm.RunReportJob(Object sender, ConsoleJobEventArgs args) As far as I know there were no changes made to the environment last week and certainly not between Tuesday 6:00 AM and Wednesday 6:00 AM. The server was updated the week before but ran reports for 5 days successfully after that. Also, all of the out-of-the-box reports appear to run normally. Even reports that come with the Veeam Management Pack for VMware still work properly. It's just this one report that seems to be broken. Any thoughts? TIA ~DGM~
SCOM low disk space alert don't work
I created a low disk space alarm for Windows 10 client , but neither the console nor the mail received a warning. My configuration steps are as follows: 1. In the "rules" of the authoring interface, search for "logical Disk" see the screenshot below. 2. In the "Monitor" of the authoring interface, search for "logical Disk" see the screenshot below. 3. To trigger this alert in a POC environment, I do the following for a client (using Disk Manager to compress disk space). With the above configuration, I did not receive any alerts as I expected, but in the SCOM monitoring panel, I could see a chart of disk space. I hope you master can help me, thank you very much!Preview of first System Center semi-annual channel release now available
In June, we announced that System Center was moving to a faster release cadence with new semi-annual channel releases coming this year. At Ignite, I shared with you that the first public preview would be available in November. I’m excited to announce that you can now try the System Center preview, version 1711, to take advantage of the new features and updates across the System Center family. Blog PostDifferent ways of SCOM Integration with Third Party Applications
Hello, We have a application which needs to be integrated with SCOM. We were using various methods from management group for getting different data. But as per documentation : https://docs.microsoft.com/en-us/dotnet/api/microsoft.enterprisemanagement.managementgroup.getmonitoringperformancedata?view=sc-om-dotnet-2016 GetMonitoringPerformanceData() and some other similar performance API are now obsolete. Now we are exploring alternatives to using this. Can you help with below questions: 1) Should we change the entire data collection mechanism from SCOM SDK to something else or just find a workaround for obsolete api's and wouldn't it break the consistency? 2) What are the possibilities of using SQL Query approach instead of SCOM SDK, and what are performance issues based on this approach? What are the resources where in detail i can get idea about using SQL query approach. Here i can see a mention of using sql as a way https://docs.microsoft.com/en-us/system-center/scom/plan-thirdparty-integration?view=sc-om-2019 3) How can connectors and orchestrators be used here for getting data from SCOM. Where can i get detailed documentation for using this approach? 4) What are possibilites of using REST API approach, as mentioned here https://docs.microsoft.com/en-us/rest/operationsmanager/. But there are no API's for getting events data and similarly many other data. Also response of API does not contain detailed data for example in case of alerts very limited data is given compared to SCOM SDK. Thanks a lot. System-Center-Team NehaGarg RobYork EricStarker Dean_Gross Trevor Seward dloder
Cannot get SNMP Traps to work in SCOM 2019
Hi. I can't get SNMP traps to work with SCOM 2019. I had it working in SCOM 2016, but when I set up a new server with SCOM 2019, I just can't figure out as to why it does not work... I have followed Kevin's guide: https://kevinholman.com/2015/02/03/snmp-trap-monitoring-with-scom-2012-r2/ I'm using a solaris server to test SNMP Traps, and it looks like the wireshark gets the packet, but SCOM never shows anything in event view or alert view (i set up rules to handle both) I have exported the management pack I created and removed the VERSION so it can find v1 and v2 (also in Kevin's guide). Can it be that I have some other management pack installed that messes with my rule to catch all traps? Does SNMP Traps work in SCOM 2019? If anyone have the SNMP Traps working in SCOM 2019, can you please provide a list of your management packs, so I can compare? Any help would be greatly appreciated!
