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

How to run GPResult on a remote client with PowerShell

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

Set up your Environment to utilize Invoke-GPUpdate

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

Sticky Key problem between Windows Server 2012 and LogMeIn

By
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 .
6 comments
Read more