Skip to main content

Finding the Last Logon Time of a Client

By
So it is a beautiful evening here in Phoenix and I’m sitting behind my computer working.  It’s all good.  Especially when I get to do a little PowerShell and I get to help someone on the side.  So I’m on PowerShell.com and I see that someone needs a little help getting the last logon time for their clients from Active Directory.  He is doing everything right with pulling the correct information from AD.  His goal is to be able to look for all computer objects that have not logged in in the past 60 days. 
This is actually a good example of how to start the creation of a PowerShell tool.  I am going to expand this tool to make it more flexible and to allow the user to ask for a variety of days as opposed to one.  Also, we will output the information in a reusable format.
This command essentially filters the output of Get-ADComputer as long as you include the –Properties LastLogonDate parameter when using Get-ADComputer. The output is unaltered from Get-ADComputer so you can then pipe it to what ever other command that you need.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
100
101
102
103
104

Function Get-StaleClients
{
[CmdletBinding()]
Param (

    [parameter(Mandatory=$true,
                ValueFromPipeline=$true)]
    [Microsoft.ActiveDirectory.Management.ADComputer[]]
    $Computer,

    [parameter(Mandatory=$true)]
    [INT]
    $Days

)

BEGIN
{
    # Create a .NET object with the cutoff
    # date in the past
    $DaysPast = (Get-Date -hour 0 -Minute 0).AddDays(-$Days)
} # END: BEGIN Block

PROCESS
{
    Foreach ($C in $Computer)
    {
        # Verify that the object has a LastLogonDate property.
        If ($C.LastLogonDate -ne [System.DateTime])
        {
            Write-Warning "LastLogonDate property not in the object."
        }
        Else
        {
            $C |
            Where-Object {$_.LastLogonDate -le $DaysPast}
        }
    } # END: Foreach ($C in $ComputerName)
} # END: PROCESS BLOCK

END {} # END: END Block

<#
.SYNOPSIS
Filters all Active Directory computer objects that are past to it and determines
if those clients have logged in within a specific number of days.

.DESCRIPTION
Filters all Active Directory computer objects that are past to it and determines
if those clients have logged in within a specific number of days.

.PARAMETER Computer
The Computer object from Active Directory to examine.

.PARAMETER Days
The number of days since the last logon.

.INPUTS
Microsoft.ActiveDirectory.Management.ADComputer

.EXAMPLE
Get-ADComputer -Filter * -Properties LastLogonDate | Get-StaleClients -Days 15

Filters all computer objects that have not logged in in the past 15 days.

.NOTES
===============================================================================
== Cmdlet: Get-StaleClients                                                  ==
== Author: Jason A. Yoder                                                    ==
== Company: MCTExpert of Arizona                                             ==
== Date: 2015APR06                                                           ==
== Copyright: All rights reserved.                                           ==
== Version: 1.0.0.0                                                          ==
== Legal: The user assumes all responsibility and liability for the usage of ==
== this PowerShell code.  MCTExpert of Arizona, Its officers, shareholders,  ==
== owners, and their relatives are not liable for any damages.  As with all  ==
== code, review it and understand it prior to usage.  It is recommended that ==
== this code be fully tested and validated in a test environment prior to    ==
== usage in a production environment.                                        ==
==                                                                           ==
== Does this code make changes: NO                                           ==
===============================================================================
#>

} # END: Function Get-StaleClients

#Get-ADComputer -Filter * -Properties LastLogonDate|
#    Get-StaleClients -Days 15

#Get-ADComputer -Filter * |
#    Get-StaleClients -Days 15

Get-Help Get-StaleClients -Full



Labels:

Comments

Post a Comment

Popular posts from this blog

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

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more

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