Skip to main content

PowerShell: Parse the events of the last 24 hours and color code them.



The following script demonstrates how to read events for an event log that have occured over the past 24 hours and to color code them. Now, use your imagination. With a little enginuity, you could parse for events that you are interested in and have this script exercise some procedures as opposed to just displaying colored text on your monitor. PowerShell is desighed for you to be able to create the tools that you need.

# ==================================================================
# EventColors.PS1
# Author: Jason A. Yoder, MCT
# WWW.MCTExpert.com
#
# Demonstrates how to list events from an event log written
# in the last 24 hours and also adding color to denote the event
# type.
# ==================================================================

# Get the current date and subtract 1 day. This is used to determine if
# an event is less the 24 hours old.
$Date = (get-date).adddays(-1)

# Gather the details of all event from the "System" log that are
# less then 24 hours old.
$Events = Get-EventLog -LogName "System" | where {$_.TimeWritten -gt $Date}

# Sent a number to represent which record we are looking at.
# This will be used in the DO WHILE loop to determine when to
# terminate the loop.
$EventNumber = 1

Do{
# The Switch statement is similar to the "case" statements
# in other programing languages. In this switch
# statement, we are evaluating what type of
# event has been recorded so we can give the event
# the correct color. Event Types include: Critical,
# Error, Wrning, and Information. Verbose is also
# a valid event type, but not included in this script.
Switch ($Events[$EventNumber].EntryType)
{
"Critical"
# The parameters of -ForgroundColor and -BackgroundColor will help
# distinguish each event type. Only the first line will have color
# attributes set. The remaining line of data for each event will
# go back to the values set as default for that user.
{ Write-Host -ForegroundColor Red -BackgroundColor DarkRed "Critical Messages"
Write-Host $Events[$EventNumber].EventID
Write-Host $Events[$EventNumber].TimeGenerated
Write-Host $Events[$EventNumber].MachineName
Write-Host $Events[$EventNumber].Message }
"Error"
{ Write-Host -ForegroundColor Red -BackgroundColor DarkYellow "Error Messages"
Write-Host $Events[$EventNumber].EventID
Write-Host $Events[$EventNumber].TimeGenerated
Write-Host $Events[$EventNumber].MachineName
Write-Host $Events[$EventNumber].Message }
"Waring"
{ Write-Host -ForegroundColor Yellow -BackgroundColor DarkYellow "Warning Messages"
Write-Host $Events[$EventNumber].EventID
Write-Host $Events[$EventNumber].TimeGenerated
Write-Host $Events[$EventNumber].MachineName
Write-Host $Events[$EventNumber].Message }
"Information"
{ Write-Host -ForegroundColor Green -BackgroundColor DarkGreen "Informtion Messages"
Write-Host $Events[$EventNumber].EventID
Write-Host $Events[$EventNumber].TimeGenerated
Write-Host $Events[$EventNumber].MachineName
Write-Host $Events[$EventNumber].Message }
}
# Incriment the record number pointer.
$EventNumber ++
# Conintue looping until the Record pointer is equal
# to the number of events in the event log.
} While ($EventNumber -le $Events.Count)

Comments

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Set up your Environment to utilize Invoke-GPUpdate

I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...