Archive for August, 2016

A while back I wrote a post about turning on agent proxying… you can find that here, but if you need to turn off Agent Proxying you can use the following Windows PowerShell:

$Agents = get-agent | where {$_.ProxyingEnabled -match “True”}
$Agents | foreach {$_.ProxyingEnabled=$false}
$Agents | foreach {$_.ApplyChanges()}

This turns it off for all Windows Agents.

In SCOM 2016 it’s slightly different but the same as you would do for SCOM 2012, again I’d use Windows PowerShell:

Get-SCOMAgent | where {$_.ProxyingEnabled.Value -eq $True} | Disable-SCOMAgentProxy -Confirm

For those of you that have downloaded and use my SCOM 2012 Daily Health Check Script, I thank you for your support and your terrific feedback. Today I’m very pleased to announce that I’ve updated this SCOM Daily Check Script to support SCOM 2016 whilst maintaining backward compatibility with SCOM 2012! So yes it’ll run on either version!

This version also has a couple of minor additions as well…firstly support for the New SCOM 2016 Maintenance Mode Schedules (a great new feature)… those will appear in your report if you have any configured and of course if you are indeed running SCOM 2016. They will look like this:

Maintenance Mode Schedule


Read more

I was chatting to a colleague today (in the elevator of all places) and he was talking about using various websites to find your external IP Address but he wanted to know if there was a command line alternative or something in PowerShell. Given the fact that we spent less than a minute in the elevator my  response was to use a DNS request find out your public IP, just like this…


Read more

When deploying a SCOM Agent to a Domain Controller you might notice the agent going grey. Most likely this is because you have configured the agent to use the default action account which is the LocalSystem account, or in other words: NT AUTHORITY\SYSTEM.

Now we could change this and use a specific domain user account just for our domain controllers, but in my experience going from client to client they simply don’t have it configured that way. So the purpose of this post isn’t to say which I think is better but to show you how to get it working under the default scenario.

So as you can see here’s a new SCOM 2016 build, I’ve just installed the agent on my locked down domain controller and it’s gone grey.

01 - DC Agent is Grey






Read more

I was called this morning to find out why monitoring wasn’t working at one clients site…Thankfully it was a short lived trouble shooting exercise but an important lesson for people that are new to SCOM.

The first thing I noticed was that every single server in the “Windows Computers” view appeared to have a maintenance on. Just to be sure I located all of the Management Servers and yes, they too were in Maintenance Mode.

Read more

Today I was called to help configure SCOM monitoring for some AIX 7 Servers. Ok, not a hard task as such but during the meeting I found out that I was going to have quite a few hurdles to contend with. These AIX Servers were located in a Customers Network behind some chained gateways and the Management Servers were in one network and the only port opened between the two networks was TCP 5723 inbound from the Customer Networks Gateway Server to an Internal Gateway Server on the Management Network where all of the SCOM Servers were located. I also didn’t have an account in the customer network so I can’t push out the agent…oh and I need to get it working today! Sounds like it’s going to be a fun day…

Read more