Skip to main content

When did a client last start?

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 -------------------------------------------

Comments

Popular posts from this blog

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.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the