Operational monitoring tools including System Center, Azure Monitor
Ever wonder when a SQL MP is published?
Wonder no longer, look for the SQL Engineering Blog!
New https://techcommunity.microsoft.com/t5/SQL-Server/bg-p/SQLServer/label-name/SQLReleases
Old – redirect in effect https://blogs.msdn.microsoft.com/sqlreleaseservices/
This is a series of blog posts to help with SCOM best practices, and things that make SCOM easier to administer.
Associate MPX files in Notepad++ blog
Backup management packs via PowerShell blog
Get to know your monitor blog
Load Test MP with Report blog
Load Test MP Fragments blog
Maintenance Mode PowerShell blog
Manage DB storage with DWdataRP blog
Managing Subscriptions blog
PowerShell Rule/Monitor/PerfCounter MP and Fragments blog
Registry Key discovery MP Fragment clarification blog
Run As PowerShell monitor fragment blog
Sealing Management packs with 2012R2 and 2016 blog
Subscriptions blog
Subscription Set up Guide blog
Uncommon MP Fragments blog
Verifying Overrides blog
Agent Management pack KH Blog
Enable proxy as a default KH blog
How to be heard blog
Manage alerts/events/performance KH Blog
Office Analytics (find where all the time goes) blog
Optimize SQL blog
Recommended Registry tweaks KH blog
SCOM Agent Version Addendum KH blog
Set SCOM Agent to remotely managed KH Blog
SQL Engineering Blog
SYSTEM CENTER 2016 Operations Manager – Anti-Virus Exclusions blog
Update VMM MP’s for SCOM when SCVMM patched blog
MP Viewer blog
Download Notepad++ here
Kevin Holman blog on extracting scripts from MP’s using Transform tool from codeplex
Test fire events using EventLog Explorer here
Alternate tool to fire any events here
I will raise my hand when asked if I prefer Notepad++ for looking at XML (because I can shrink the sections I’m not concerned about).
Using Notepad++ (works best for color and concatenation of XML or quotes in case of syntax errors when editing)
Open Overrides management pack (XML)
Click on the (-) for Manifest
Click on the dash (-) for RelationshipTypes
Click on the dash (-) for each Discovery (if it exists)
Verify targets exist in MP’s to be updated
Scroll to the right to view the Targets of your Override management pack
If changes were overrides, look at the Monitor or Rule and verify this is in the pack to be updated
To understand which MP is being referenced, look at the example – Windows3!
Scroll to the top of your MP and click on the (+) plus sign to expand manifest
NOTE Windows3 is the server 2016 Monitoring MP
Verify your monitor/rule name still exists, and your Override should still apply
In Server Overrides MP, look at the Monitor= section for the Monitor name
Go to the Windows Server 2008 Monitoring MP and look for that monitor
There is no monitor for 2008
Alternatively, you can look at the SCOM console as well (if MP is installed)
There is NO 2008 Memory Pages per second monitor
Now to remove the override in our MP
In Notepad++, highlight the MonitorConfigurationOverride section, and delete
Rinse and Repeat
Increment the version number and import MP when finished validating overrides.
The Office 365 Run As account is used for Proxy access for an HTTPS connection from SCOM MS to Office 365 portal endpoint.
Must be a domain account, not an Azure account (particularly if they ‘re not the same tenant or AAD associated
Service Accounts are recommended to prevent impact should an employee leave
SCOM uses a domain account (example scom_action ID)
Verify that ID is in Azure tenant (contact your Azure Administrator if you don’t have access )
To follow best practice, update the Run As account with the service account
Verify Run As account
On SCOM console that there are no Operations Manager event log 7000 events for the ‘run as’ configured ID
Remote Desktop to SCOM MS Server
Verify if the ‘run as’ ID has a valid password
Look in the Operations Manager Event Log for Event ID 7000
Click on Find
Type in the user’s ID from the ‘run as’ account in SCOM
If no entries found, then ID is successfully authenticating against the domain
If errors found, correct ID/Password
NOTE New subscription may take 5-10 minutes to populate health data
From SCOM console
Click on Administration
Click on the Office 365 wizard
Click Add Subscription
Add Subscription Name
Click Next
SCOM UI will prompt for Azure login
Enter ID and password
Click Sign in to authenticate
Click on Monitoring Tab
Click on Office 365 folder
Click on Office 365 Monitoring Dashboard
Verify state on the subscription in question
In Azure Portal
Verify the Application exists ( Azure tenant shows as SCOM O365MP )
NOTE In the right hand pane the Office 365 Management API’s has Application Permissions, and cannot be selected
Click Back to the Settings window
Click on Owners
NOTE NO owners show in this view
Click Add +
In the Add owner window, type the ID
Hit Select to add the user account (This example is the SCOM Service account)
Have user test
Yes this can leave you stumped, and wondering “why?”
This can be many parts, so choose carefully
Verify SCOM ID used in o365 subscription in Azure portal
Create a new subscription in SCOM to use the auto credentials option
Office 365 SCOM Run As Account
In the SCOM console
Click on Monitoring Tab
Click on the O365 dashboard
Look at the health state
Error showed ‘endpoint not found’
Working with Azure Admin, we found the SCOM O365MP application did NOT have a service account assigned.
Verify ‘run as’ ID (originally employee ID, not service account )
Remote Desktop to SCOM MS Server
Verify if the ‘run as’ ID has a valid password
Look in the Operations Manager Event Log for Event ID 7000
Click on Find
Type in the user’s ID from the ‘run as’ account in SCOM
If no entries found, then ID is successfully authenticating against the domain
If errors found, correct ID/Password in SCOM Console
In the SCOM console
Click on Administration
Click on the O365 Wizard
Highlight the subscription
Choose Edit Subscription
Test ID (tested the Service Account)
With the radio button selected at ‘Use auto-created Azure Service Principal’
NOTE Name here is for SCOM purposes and does not have to match Azure Portal Application Name
Click Next
SCOM UI will prompt for Azure login
Enter ID and password
Click Sign in to authenticate
If error is ‘Authentication Fails’, contact your Azure Administrator for assistance
References
Verify SCOM ID used in o365 subscription in Azure portal
Create a new subscription in SCOM to use the auto credentials option