Skip to main content

Use the difference between event log time stamps to decide if you need to take action

Today I am on a long flight back to Indianapolis after a week of training at Microsoft. Being the geek that I am I decided to take a quick look at PowerShell.org to see if anybody in the community was having issues that I could help with before we took off. One community member needed to be able to tell if two events were being recorded more than 2 hours apart. If so, she wanted an action to take place.

I used the Subtract Method of the System.DateTime object that is given to you in the TimeCreated property of an individual event log to resolve this. In the below function, I have it extract the first two events that match the criteria in $EventHash. I then take the first returned event and subtract the second events time from the first and then look for the TotalHours property. If it is greater than the number of hours specified when the function was called, it returns True. If not, it returns False.  It also has a built in safety.  If 1 or less events are returned, the function defaults to False.

 
Function Get-EventTimeSpan
{
Param (
[Parameter(Mandatory
=$True)]$Hours
)
# Specify the criteria for your event here.
$EventHash = @{LogName = "System"; ID = 1014}

# Recover the first two events from the event log that matches
# the criteria in the $EventHash data.
$EventData = Get-WinEvent -FilterHashtable $EventHash -MaxEvents 2

# Verify that at least two events were recovered from the log.
# If there are less than 2 events recovered, Execute the ELSE
# Statement. The Else statement should execute code if only one
# or less events are found.
If ($EventData.Count -eq 2)
{
If ((($EventData[0].TimeCreated).Subtract(($EventData[1].TimeCreated)).TotalHours) -lt $Hours)
{
# Return $False if the time between events is less than the
# number of hours specified in $Hours.
Write-Output $False
}
Else
{
# Return $False if the time between events is greater than the
# number of hours specified in $Hours.
Write-Output $True
}
}
# End: If ($EventData.Count -lt 2)
Else
{
#If there are less than 2 events in the event log, return $False
Write-Output $False
}
# End: Else Statement for If ($EventData.Count -lt 2)



}
# ---- End Function Get-EventTimeSpan ---------------------------------------


9

Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

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.