OpsMgr 2016 Agent Crashes SharePoint 2016 Site

Today I pushed the SCOM 2016 agent to my newly installed SharePoint 2016 server via the SCOM console. My SCOM management group is on 2016 RTM UR 3. Once the SCOM agent was installed, I could not launch SharePoint Central Admin site after a reboot. After turned off the custom error in web.config, I could see the exception: This is caused by the known issue with SCOM 2016 agent APM component (Application Performance Monitoring). My good friend Kevin Greene has already blogged this: http://kevingreeneitblog.blogspot.com.au/2017/03/scom-2016-agent-crashing-legacy-iis.html So to fix my issue, I followed Kevin’s instruction – reinstalled the SCOM agent using MOMAgent.msi

Free PowerShell OpsMgr Management Pack from Squared Up

Squared Up is releasing a new free management pack that provides several PowerShell related templates that allows SCOM administrators to create the following workflows: Name Type Description Run a PowerShell Script Diagnostic Runs a script as a diagnostic, returning text PowerShell Script Three State Monitor Monitor Runs a script and reports Healthy, Warning, or Critical based on the script output PowerShell Script Two State Monitor Monitor Runs a script and reports Healthy or Warning/Critical based on the script output Run a PowerShell Script Recovery Runs a script as a recovery, returning text PowerShell Script Alert Generating Rule Rule Raises Alerts

Azure Functions Demo: Voting App

Back in April this year, Pete Zerger (@pzerger) and I delivered two sessions in Experts Live Australia. One of which is titled “Cloud Automation Overview”. During this session, we have showed off a pretty cool voting demo app that is made up with Azure Functions, Key Vault, Azure SQL DB and Power BI. As shown above, this demo app allows attendees in our session to vote on a topic that we have chosen by scanning QR codes using mobile devices. In this case, since we were delivering the session in Melbourne Australia, we have decided to let people to vote

Preventing Azure Automation Concurrent Jobs In the Runbook

Recently when I was writing an Azure Automation PowerShell runbook, I had an requirement that I need to make sure there should be only one job running at any given time. Since this runbook will be triggered by a webhook from external systems, there was no way for me to control when and how the webhook would be triggered. So I had to add some logic in the runbook that only execute the core code block if there are no other jobs running. The key for this technique is to use the built-in variable that is available in any Azure

%d bloggers like this: