Its been a little while since I’ve posted on my blog…it’s been a very hectic few months but I’m back and hopefully will be able to provide you guys with some more useful SCOM related things.

Today though its Windows PowerShell as I was required to perform the equivalent of touching a file on a Windows Server. PowerShell doesn’t have a cmdlet specifically for this (that I’m aware of anyway) but we can use the Set-ItemProperty cmdlet and have it update the LastWriteTime property using the current date and time (well actually you could pass it any date and time if you like).

Turns out its pretty easy, just like this…

Set-ItemProperty -Path C:\TestFile.txt -Name LastWriteTime -Value (Get-Date)

 

Hope it helps you.

Today I was asked if there is any way of getting emailed if a particular Windows Event Log Event was generated on a server.
“Of course” I said, “SCOM can easily do that!”
“Oh we don’t have SCOM” was the reply.
“What? You don’t have SCOM? Why are you even talking to me?”.

Sadly this person was not in the position to use SCOM so he needed a different solution.

Read more

If you want to find out what objects are currently in Maintenance Mode, here’s a nice bit of SQL Code you can use for just that. I’ve added a more useful English Reason than just the code because SCOM stores the code itself in the Database. It’s a lot easier in my opinion to identify the reason as server was put into maintenance that just code 8 or 9.

Here it is, enjoy.

Read more

I’ve had so much positive feedback about my original SCOM Health Check Script and also the updated v2 one which a lot of people thanked me for updating it with the fresh new style. However I also got some great feedback asking if I could turn it into a SCOM Report that could be run, scheduled and emailed from SCOM itself. Then you’ll be pleased to know that I’ve been working on it and soon plan to release my version 1.0 SCOM Health Check Report. So this new report will be like the previous one as far as content goes, giving you the same sort of information, except instead of being written in Windows PowerShell I wrote this using SQL Queries and SQL Report Builder. I’ve then taken that and populated it into a SCOM Management Pack so you guys can simply import it straight into SCOM and schedule it to email you…how easy is that!

It has a slightly different look to my previous reports and I’m still playing around with styles so I haven’t actually settled on a final one but it will most likely look something like this..

SCOM Report v1.0

 

 

 

 

 

 

 

Read more

There’s a lot of ways we can retrieve a list of alerts from SCOM, but nothings quicker than going to the Database directly. So here’s a bit of SQL that can grab all alerts from a Management Server, but formats the output a bit nicer. So for example rather than outputting the severity as a 0, 1 or 2…it outputs the english word, Informational, Warning or Critical. Same with the Monitor or Rule. Just a bit easier to read than working out if a 0 or a 1 is a monitor or rule.

Read more

Merry Christmas!

Categories: Other
Comments: No

Hello everyone,

Thanks for your fantastic support and feedback this year, I really do appreciate it.

I just wanted to say Merry Christmas and have a Happy and Safe New Year! I’ll take a very short break and I’ll see you early next year with some great new SCOM Posts and Training Videos!

– Tim 🙂

 

In the previous video I ended with a short lecture on why it’s so important that you ensure that your agents work properly…in this video I pretty much start with the same lecture (haha). After that we begin to see how we can troubleshoot SCOM Agents. I talk about problems you might experience with manually installed agents versus discovery based installations. I discuss things like Gray agents, agents appearing in Pending Management, Certificates, the Health Service, Restarting the service, flushing the cache and how to read the windows event log.

13-troubleshooting-scom-agents