System Center Operations Manager Ignite Announcements

 

Ignite is behind us, and lots of new things are happening in and around Microsoft. Things change, and SCOM also. If you are SCOM user and follow SCOM team blog, you will see that they announced survey regarding changes they implement in System Center products. One of them is new release cadence that will resemble Windows. It means that update for System  Center will be aligned with Windows updates. On November 8th Microsoft will release preview version of System Center 1801. If you don’t understand the numbers of version, first two numbers are the year of release, and two last ones are the month. System Center will be released semi-annual with new future addressing issues and new feature. you will be able to update you system if you have eligible Software Assurance for that product.

systemcentercadence

When we talk about what is coming for SCOM 2016 here it is

  • System Center 1801 prieview early November. Release Q1 2018
  • Service Map integration is now in public preview but it will relased probably with new version. you can download MP here
  • Windows Server 2016 SDDC monitoring

Improved Unix/Linux support

    • “setup improvements” hopefully a better way to deploy “manually”
    • Kerberos support
    • Log file monitoring with FluentD. Essentially this enables us to create monitors etc. based on logfiles as we can with Windows (This is huge)

image

SCOM 2016 HTML5 console

  • Improved diagnostics and drill down – this is huge for those who haven’t invested in third-party software
  • Custom widget support. Display other charts on your dashboard.

image

  • MP updates and recommendations (introduced in 2016) now supports 3rd party MPs. 56 partners with certified MPs are available.
  • Visual Studio Authoring Extension for VS 2017

If you want to find out more details about all of this please watch Ignite session System Center for the modern datacenter: First look at advancements coming this year

Advertisements

How to remove OMS from SCOM

I am sometimes so annoyed that once you connect your SCOM to OMS it is hard to get rid of it. You even delete workspace, but only thing you get is some errors in SCOM console. Ok how to get it out if you temporary doesn’t want it there?

I started with Kevin Holman post about it but I had some trouble doing it so here is full  story. Lets first copy paste some things.

First of all we need to stop download of intelligence  management packs from OMS and all others related. To do that,  create override with name “override OMS temporary disable” , and disable two rules. Go to Authoring > Rules, and set your scope only to “Operations Manager Management Group”

Disable the following two rules:

image

It will disable automatic download of OMS MPs.

Now lets delete some MP

Open PowerShell and do next commands

Get-SCOMManagementPack -name “*advisor*” | Remove-SCOMManagementPack

Get-SCOMManagementPack -name “*IntelligencePack*” | Remove-SCOMManagementPack

get-SCOMManagementPack -name “Microsoft.EnterpriseManagement.Mom.Modules.AggregationModuleLibrary” | Remove-SCOMManagementPack

First command will probably fail. you will delete only one management pack but rest of it will not be possible because of dependency. This two you will have problems with

image

They have dependency on this management pack and you can not delete them. So what to do?

image

If you added run as account for System Center Advisor Run As Profile Proxy, and probably you did,  remove it from there. After that we need to edit this management pack. Go to PowerShell again and do this (don’t run it read first).

$MP = Get-SCOMManagementpack -Name Microsoft.SystemCenter.SecureReferenceOverride
$MP.References
$MP.References.Remove(“SystemCenter6“)
$MP.References.Remove(“SystemCenter5“)
$MP.Verify()
$MP.AcceptChanges()

To explain.

  1. With $MP.References you will show all reference inside this MP including Advisor ones.image
  2. After that you will remove references using right Key names listed for Advisor MPs
  3. With MP.Verify() you check everything to ensure there are no orphaned overrides, etc.
  4. If everything is OK do $MP.AcceptChanges() to save everything

After that you can easily delete first override mp “override oms temporary disable”  and both  left over Advisor MPs.

image

If I missed some step please comment