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

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
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

Backup and Restore AD LDS with DSDBUTIL.exe

By
Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services.  The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database.  Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet.  Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS.  You may want to make sure the database is being backed up and also have a restore plan in place.  Should the database become corrupt, the application that uses that database will fail.  This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...
6 comments
Read more