Category: SCOM

Migrating Notifications from SCOM 2012 R2 to 2016

June 14, 2017June 13, 2017 · 1 Comment ·

When upgrading a SCOM environment from 2012R2 (or 2012) to 2016, one of the most time demanding tasks can be replicating the notifications settings. In my case, I had to do a brand new install, and needed some way to migrate the notifications configuration from the old SCOM environment to the new. Luckily there is a pretty quick way to achieve this. Let’s begin!

Log in to the 2012R2 environment, go to the Administrations pane, and locate and export the Notifications Internal Library (Microsoft.SystemCenter.Notifications.Internal). Export this MP somewhere locally.

Open the MP/XML file with some editing tool, Notepad, Notepad++, Visual Studio, etc….

As you can see, this MP version is version 7.1.10226.0.

If you quickly hop over to the SCOM 2016 environment, and locate the same MP (same name, Microsoft.SystemCenter.Notifications.Internal), you will notice it is a different version. What we will need to do here is, update the OLD MP to a version number just slightly higher than the one in the 2016 environment.

So, in my case, I will change 7.1.10226.0 to 7.2.11719.1. Save the XML file, and copy it over to the SCOM 2016 environment.

Next we have two options:

we can either import the updated MP, or,
alternatively we can delete the MP from SCOM 2016 (v7.2.11719.0)

Before doing that, it is recommended to export the MP, and save it for “just in case“. In my case, I deleted the MP.

Now if you go into Notifications settings, you will see an exact copy of the configurations from your SCOM 2012R2 environment. To enable all the notifications, or disable, execute the following cmdlet in the OperationsManager console.

Get-SCOMNotificationSubscription | Enable-SCOMNotificationSubscription

Get-SCOMNotificationSubscription | Disable-SCOMNotificationSubscription

As an FYI, I forgot to disable the subscriptions beforehand. This would have been ideal to do before saving the XML file before importing into SCOM 2016. You can edit this by replacing the following text. Run a Control+H (Replace), and Replace All, Enabled=”true” to Enabled=”false”.

There you go! Notifications have been replaced from SCOM 2012R2 to SCOM 2016.

Monitoring Domain Controllers in SCOM 2016 – Event ID 1102

June 2, 2017June 2, 2017 · 4 Comments ·

So you deploy a SCOM 2016 agent to a Windows 2016 Domain Controller, only problem is, after the agent push, discovery doesn’t work. Well, the agent isn’t corrupted… Ports are open… SCOM agent is being deployed using the System Local account… etc. etc. So, now what?

Taking a look at the Windows 2016 domain controller and its event log, the domain controller OpsMgr log is getting bombarded with Event IDs 1102….

After some investigation, seems to be this has been an issue in SCOM 2012 (and 2012R2) as well. Well, here’s the fix…

Taking a look at the HSLockdown, the Local System account is being denied access.. Browse to the following folder “%windir%\Program Files\Microsoft Monitoring Agent\Agent “and run the following command (elevated access…), “HSLockdown.exe /L“

Now that we can see the Local System account is being denied access, let’s give it access… Running the following command, “HSLockdown /A “NT AUTHORITY\SYSTEM“. Restart the SCOM Agent (net stop HealthService.exe & net start HealthService.exe) and you should be good to go now!

Cheers!

Microsoft System Center 2016 Management Pack for Hyper-V

March 15, 2017March 15, 2017 · Leave a comment ·

Finally, Microsoft/System Center team published the much awaited Management Pack for SCOM 2016 and Hyper-V 2016.

Here is the link to download and get Hyper-V 2016 monitored in your environment. LINK.

SCOM Agent Version Addendum Management Pack

March 1, 2017 · Leave a comment ·

Earlier this week, Microsoft’s Kevin Holman published an excellent article and SCOM Management Pack that addresses the issue with SCOM 2012 and agent updates. Please have a read, and consider installing this MP to help alleviate the issues SCOM 2012 has created when it comes to understanding which version your SCOM agent is on….

BLOG POST HERE.

Step-by-Step – SCOM 2012 R2 Update Rollup 12 (UR12) Install Procedure

January 30, 2017February 22, 2017 · 6 Comments ·

My personal notes for installing SCOM 2012 R2 Update Rollup 12, Step-by-Step. UR12 (Update Rollup) has a lot improvements, please see below the many updates being provided in this UR. One thing to mention, UR12 also has resolved an issue with respect to Reporting — please see notes below. Also, it is rather nice to see updates (still) being pushed out for SCOM 2012R2 along with other System Center 2012 products.

It is highly recommended to upgrade your lab/Dev environments first before upgrading your Production environment(s). The step by step procedures below are the steps I took and in no way shape or form do I accept responsibility for any data loss, and/or issues within your environment. It is advised to always take a backup of your SQL databases and/or snapshots of your SCOM environment(s). Please take these notes as suggestions. Always refer to Microsoft’s KB (posted below) for full documentation steps.

Here are the key updates for UR12 (source Microsoft):

Issues that are fixed in Operations Manager Update Rollup 12

When you try to upgrade System Center 2012 R2 Operations Manager Reporting Server to System Center 2016 Operations Manager reporting server, the upgrade fails for the following configuration:

Recovery tasks on “Computer Not Reachable” messages in the System Center Operations Manager Monitor generate failed logons for System Center Operations Manager Agents that are not part of the same domain as the Management Groups.
When a Management Server is removed from the All Management Servers Resource Pool, the monitoring host process do not update the Type Space Cache.
SHA1 is deprecated for the System Center 2012 R2 Operations Manager Agent and SHA2 is now supported.
Because of incorrect computations of configuration and overrides, some managed entities go into an unmonitored state. This behavior is accompanied by event 1215 errors that are logged in the Operations Manager log.
IntelliTrace Profiling workflows fail on certain Windows operating system versions. The workflow cannot resolve Shell32 interface issues correctly.
There is a character limitation of 50 characters on the custom fields in the notification subscription criteria. This update increases the size of the limitation to 255 characters.
You cannot add Windows Client computers for Operational Insights (OMS) monitoring. This update fixes the OMS Managed Computers wizard in the System Center Operations Manager Administration pane to let you search or add Windows Client computers.
When you use the Unix Process Monitoring Template wizard to add a new template to the monitor processes on UNIX servers, the monitored data is not inserted into the database. This issue occurs until the Monitoring Host is restarted

Install Procedure

Once you are ready to begin your upgrade, it is recommend you do the following server/roles in the order below:

Install the update rollup package on the following server infrastructure:

Management server or servers
Audit Collection Services
Gateway servers
Web console server role computers
Operations console role computers
Reporting Services
Agent Updates

Apply SQL scripts.
Manually import the management packs.
Apply the agent update to manually installed agents, or push the installation from the Pending view in the Operations console.

Once you have downloaded the rollup files, I like to extract and only keep the language I need, in this case, ENU (English). You will need to install these with Administrative rights, I like to use PowerShell as Local Administrator. It really does frustrate me, as there is no indication that the rollup installed correctly, (other than looking at the file version number change via File Explorer).

Personally, I prefer to execute the MSP files via PowerShell (RunAs Administrator) console.

Again, the order needs to be:

Management Servers
Audit Collection Services
Gateway Servers
Web Console Role Servers
Operations console role computers
Reporting Services
Agent Updates

Once the updates are installed, server(s) are rebooted, etc., you will now need to apply the SQL scripts. First update the Data Warehouse, then followed by the OpsMgr DB.

The scripts can be found here, “%SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\SQL Script for Update Rollups”

Please note, the user executing these scripts needs to have read and write permissions to the database(s).

Execute the SQL queries in the following order:

UR_Datawarehouse.sql
update_rollup_mom_db

Once you have successfully executed the SQL scripts, you will now need to import the updated Management Packs (MP). These MPs can be found here, “%SystemDrive%\Program Files\System Center 2012 R2\Operations Manager\Server\Management Packs for Update Rollups“.

You will need to import the following MPs, please see below:

Microsoft.SystemCenter.TFSWISynchronization.mpb, which has the following dependencies:
- Microsoft.SystemCenter.AlertAttachment.mpb, which should be installed from the System Center Operations Manager 2012 R2 media.
- Microsoft.SystemCenter.Visualization.Library.mpb
Microsoft.SystemCenter.Visualization.Component.Library.mpb
Microsoft.SystemCenter.ClientMonitoring.Library.mp
Microsoft.SystemCenter.DataWarehouse.Report.Library.mp
Microsoft.SystemCenter.ClientMonitoring.Views.Internal.mp
Microsoft.SystemCenter.Apm.Infrastructure.mpb
Microsoft.SystemCenter.Apm.Library.mpb
Microsoft.SystemCenter.Apm.Library.Resources.(LANGUAGECODE_3LTR).mpb
Microsoft.Windows.InternetInformationServices.2016.mp (this MP has to be downloaded separately from the Microsoft Update Catalog) which has the following dependency:
- Microsoft.Windows.Server.2016.Discovery.mp (this MP has to be downloaded separately from the Microsoft Update Catalog)
Microsoft.SystemCenter.Visualization.Library.mpb
Microsoft.SystemCenter.Advisor.mpb
Microsoft.SystemCenter.Advisor.Internal.mpb
Microsoft.SystemCenter.2007.mp
Microsoft.SystemCenter.Advisor.Resources.(LANGUAGECODE_3LTR).mpb
Microsoft.SystemCenter.SyntheticTransactions.Library.mp
Microsoft.SystemCenter.OperationsManager.Library.mp
Microsoft.SystemCenter.OperationsManager.Internal.mp
Microsoft.SystemCenter.Apm.Web.IIS10.mp, which has the following dependencies:
Microsoft.SystemCenter.ClientMonitoring.Internal.mp, which has the following dependency:
Microsoft.SystemCenter.OperationsManager.AM.DR.2007.mp

Once the MPs have been imported, you should now go back to your Pending Management view, under the Administrations pane, and update all servers.

And that is that! You are now on the latest and greatest System Center release for SCOM 2012 R2 Update Rollup 12!

Installing SCOM 2016 License Key

January 27, 2017January 27, 2017 · Leave a comment ·

Launch the PowerShell console, and Run as Administrator:

Import-Module OperationsManager
Set-SCOMLicense -ProductId "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
Start-Sleep -s 10
Restart-Service healthservice, omsdk, cshost

Don’t forget, in order for the Product Key to be applied, you will need to restart all SCOM Services, (or you can run the code above (there is a 10 second delay after the key is applied before the services are restarted)):

Microsoft Monitoring Agent (healthservice)
System Center Data Access Service (OMSDK)
System Center Management Configuration (cshost)

Cheers!

System Center Operations Manager (SCOM) 2016 – Requirements for Windows Server 2016 via PowerShell

December 27, 2016October 13, 2017 · 2 Comments ·

The following PowerShell code is to install all the necessary IIS components for System Center Operations Manager (SCOM) 2016 Web Console on Windows Server 2016.

Import-Module ServerManager
Add-WindowsFeature Web-Server, Web-WebServer, Web-Common-Http, Web-Default-Doc, Web-Dir-Browsing, Web-Http-Errors, Web-Static-Content, Web-Health, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Performance, Web-Stat-Compression, Web-Security, Web-Filtering, Web-Windows-Auth, Web-App-Dev, Web-Net-Ext45, Web-Asp-Net45, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Mgmt-Tools, Web-Mgmt-Console, Web-Mgmt-Compat, Web-Metabase, NET-Framework-45-Features, NET-Framework-45-Core, NET-Framework-45-ASPNET, NET-WCF-Services45, NET-WCF-HTTP-Activation45, NET-WCF-TCP-PortSharing45, WAS, WAS-Process-Model, WAS-Config-APIs, web-asp-net -restart

You can also find this in Microsoft’s TechNet Gallery, HERE.

SCOM & Other Geeky Stuff

A series of blog posts around Microsoft Cloud and Datacenter technologies, specifically Azure Cloud, System Center and other various Microsoft technologies.