Skip to main content

When did a client last start?

By

This is a question that I often have to ask a user.  The problem is that our users answers cannot always be considered…shall we say “reliable.”  Below is a PowerShell function that you can use to to determine when the client in question was last started.  Here is what you get when you run this function.

PS C:\windows\system32> Get-LastStartTime -ComputerName Work-PC

Last Startup Time: 12/31/2012 1:44:43 PM

I’m using this as part of the HelpDesk module that I creating for my up coming book and also I’ll be demonstrating the full module at the Cincinnati PowerShell users group meet up on Thursday, February 21, 2013.  Here is a link to the event.  Our focus will be on using PowerShell with your Help Desk.

# .............................................................................

# Function Get-LastStartTime

# Retrieves the last start time on the client machine.

Function Get-LastStartTime

{

Param ($ComputerName = ".",

    [Switch]$PassThru

    )

   

   

    If (!$Quiet)

    {

        Write-Host "Last Startup Time: " `

         -ForegroundColor Cyan `

         -BackgroundColor DarkBlue `

         -NoNewline

    }

 

 

    $Events = Invoke-Command -ScriptBlock {

        Try

        {

            $LogHash = @{LogName = 'System'; ID = 6005}

            Get-WinEvent -FilterHashtable $LogHash `

             -MaxEvents 1 `

             -ErrorAction Stop

 

        }

        Catch

        {

           

        }

      

     

        } -ComputerName $ComputerName

   

    If (!$Quiet)

    {

        If ($Events -ne $Null)

        {Write-Host ($Events.TimeCreated).ToString() `

         -ForegroundColor Green `

         -BackgroundColor DarkBlue}

        Else

        {Write-Host "Could not determine the last start time." `

         -ForegroundColor Red `

         -BackgroundColor DarkRed}

    }

 

 

    # If $Passthru is enabled, then return the results of this test

    # to the PowerShell pipeline.

    If($PassThru) {Write-Output $Events}

 

 

 

<#

.SYNOPSIS

Returns the time the client was last started.

 

.DESCRIPTION

Returns the time the client was last started.

 

.PARAMETER ComputerName

the name of a client to connect to.

 

.PARAMETER PassThru

Returns the test result from this cmdlet.

 

.EXAMPLE

Get-LastStartTime -ComputerName Work-PC

Last Startup Time: 12/31/2012 1:44:43 PM

 

.EXAMPLE

Get-LastStartTime -ComputerName Work-PC -PassThru

Last Startup Time: 12/31/2012 1:44:43 PM

 

   ProviderName: EventLog

 

TimeCreated           Id   LevelDisplayName Message                                                          

-----------           --   ---------------- -------                                                         

12/31/2012 1:44:43 PM 6005 Information      The Event log service was started.    

#>

 

} # End Function: Get-LastStartTime -------------------------------------------

Labels:

Comments

Post a Comment

Popular posts from this blog

Adding a Comment to a GPO with PowerShell

By
As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th
Post a Comment
Read more

Return duplicate values from a collection with PowerShell

By
If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe
Post a Comment
Read more

How to list all the AD LDS instances on a server

By
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.
Post a Comment
Read more