As per Kevin Holman’s article entitled ‘OpsMgr 2012: What should the SPN’s look like?’ (i.e. https://kevinholman.com/2011/08/08/opsmgr-2012-what-should-the-spns-look-like/), please correct the following erroneous event log entries that are logged when the SDK service is restarted (and configured with an AD account):
Event Log: Operations Manager
Event ID: 26371
Event Source: OpsMgr SDK Service
Event Level: Warning
The System Center Data Access service failed to register an SPN. A domain admin needs to add MSOMSdkSvc/MS1 and MSOMSdkSvc/MS1.contoso.com to the servicePrincipalName of CN=MS1,CN=Computers,DC=contoso,DC=com
The events are still being logged, even in SCOM 2019.
Thank you,125 votes
HI, Brian Wren had mentioned that Microsoft would always have a Management Pack for every Microsoft product. Currently Microsoft does NOT have an MP to monitor ADFS49 votes
If you, for instance, put several Windows Computers in maintenance via the scheduler and one of them was already put in maintenance manually, that one will get out of maintenance when the scheduler ends.
Same deal for hosted objects that were put in maintenance manually.
Also check here: https://social.technet.microsoft.com/Forums/systemcenter/en-US/e2af78b9-70b2-4282-b647-71f41dc0b476/scom-20162019-maintenance-schedules-stop-manually-configured-maintenance?forum=operationsmanagergeneral9 votes
This feature is planned for 2019 UR2. The furthest end time on the object will be honored with 2019 UR2.
would love to see you making adjustments to O365 management pack with the ability to monitor the status of Microsoft Teams. Currently o365 management pack is really not transparent and its based on ticket system. It would be great to have something like it is for SfB on premise where you can use synthetic transactions. I would love to see synthetic tests checking if PSTN and Peer-to-Peer calls are working from/to Teams.11 votes
I'm using a Mac and open the web console of SCOM 1807 in Chrome or Safari. Clicking on a result in Results pane, I get only a couple of lines in the Details pane. Although I can drag and drop the grey line between the Results and Details pane, it constantly reverts to it's former position.20 votes
Planned for SCOM 2019 UR1
We generally check the catalog regularly for updated Management Packs in SCOM 2012 R2. The catalog is currently showing what appear to be incorrect versions of the MPs for the customers still on 2012 R2:
It might be a good idea to correct this, since these versions will break UNIX/Linux monitoring in SCOM 2012 R2, at the very least agent deployment will be broken.1 vote
We have fixed this, please verify and comment
There is no management pack to monitor message queue running on server 201623 votes
Using the Maintenance Mode Scheduler that came with SCOM 2016 is pretty cool but there is no mechanism to detect if a server is already in MM. If we put a server in maintenance mode e. g. for 48 hours and someone else doesn't know this and schedules another MM let's say for 2 hours then the ealier scheduled MM of 48 hours will be overwritten and the MM ends after the 2 hours. So there should be a logic which checks if a MM is already set and how long. If the newly scheduled time period is shorter than the one already scheduled then it will be ignored.
Using the Maintenance Mode Scheduler that came with SCOM 2016 is pretty cool but there is no mechanism to detect if a server is already in MM. If we put a server in maintenance mode e. g. for 48 hours and someone else doesn't know this and schedules another MM let's say for 2 hours then the ealier scheduled MM of 48 hours will be overwritten and the MM ends after the 2 hours. So there should be a logic which checks if a MM is already set and how long. If the newly scheduled time period is shorter than…14 votes
With SCOM 2019 UR2, maintenance schedule will end at furthest end time. if there is a conflict in maintenance schedule on an object , then the furthest end time will be honored.
The SCOMpercentageCPUTimeCounter (vbs or ps1) used by Agent processor utilization rule and monitor runs on each agent every 5 minutes (321 sec) and with a sync time set to 00:00.
This causes CPU spike on virtualization hosts.135 votes
Please leave your email id in comments if you would like to test this fix.
When using the Edge browser to view the web console, you are unable to resize any of the sections. When you click on a border, you will get a error icon (red circle with red line).9 votes
Release planned for SCOM 2019 UR1
Make a bool setting on each Management Server object to check mark, that this MS cannot be accidentally put into Maintenenance Mode. This would avoid a lot of Problems for customers who put servers into Maintenance Mode.105 votes
- Don't see your idea?