Skip to main content

Determine what Clients a User has Logged into when the Client is Offline

This one was a bit tricky.  The idea is to match a logon event of a user to one of a client via a common piece of data.  That data is the IP address.

This code is not thoroughly tested.  It utilizes the Security logs from a Domain controller.  It looks for event  4768.  Both the user login and the client login will contain an IP address inside the message portion.  It then looks through the records to match User Name and Client Name using the IP Address.  A few things to consider:

1) This will need to be executed against each Domain Controller.  Since you do not know which DC the client is bound to, your will need to check all of them.

2) In a large environment with large security logs, this will take some time.

3) The code is not optimized.  I’ll leave that fun up to you.

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

90

91

92

93

94

95

96

# Creates the object that will be used to store information from the event logs.

Function New-LogObject

{

    $Obj = New-Object -TypeName PSObject -Property @{

        "UserName" = $Null

        "IPAddress" = $Null

        "Record" = $Null

        "Client" = $Null

        "TimeGenerated" = $Null

 

    }

    Write-Output $Obj

}

 

# Creates an object that will be the final product of this code.

Function New-MatchObject

{

    $Obj = New-Object -TypeName PSObject -Property @{

        "UserName" = $Null

        "Client" = $Null

        "TimeGenerated" = $Null

 

    }

    Write-Output $Obj

}

 

# Retrieve the first 100 events of event ID 4768

$Events = Get-EventLog -LogName Security -InstanceId 4768 -Newest 100

 

# Allocates dynamic memory.

$Data = @()

 

 

# Loop through each event and identify the key parts.

ForEach ($E in $Events)

{

  

   # User Record.

   If ((($E.Message).Split("`n"))[3] -notlike "*$*")

   {

        $Obj = New-LogObject

 

        # Extract the username.

        $Obj.UserName = (($E.Message).Split("`n"))[3].Replace("Account Name:",$Null).Trim()

 

  

        # Extract the IP Address.

        If ((($E.Message).Split("`n"))[12] -match "\d+.\d+.\d+.\d+")

        {

            $Obj."IPAddress" = $Matches.Values

        }

 

        $Obj.Record = "User"

        $Obj.TimeGenerated = $E.TimeGenerated

   }

   ElseIf ((($E.Message).Split("`n"))[3] -like "*$*")

   {

        $Obj = New-LogObject

 

        # Extract the username.

        $Obj.Client = (($E.Message).Split("`n"))[3].Replace("Account Name:",$Null).Trim()

 

  

        # Extract the IP Address.

        If ((($E.Message).Split("`n"))[12] -match "\d+.\d+.\d+.\d+")

        {

            $Obj."IPAddress" = $Matches.Values

        }

 

        $Obj.Record = "Client"

   }

 

   # Record the object in the Dynamic memory.

   $Data += $Obj

} # END: ForEach ($E in $Events)

 

# Compare records and match users to clients.

$Data2 = @()

For ($X=0 ;$X -lt $Data.count; $X++)

{

    For ($Y = $X+1; $Y -lt $Data.count; $Y++)

    {

        If (($Data[$X].IPAddress -eq $Data[$Y].IPAddress) -and ($Data[$X].Record -eq "User") -and  ($Data[$Y].Record -eq "Client"))

        {

            $Obj = New-MatchObject

            $Obj.UserName = $Data[$X].UserName

            $Obj.Client = $Data[$Y].Client

            $Obj.TimeGenerated = $Data[$X].TimeGenerated

 

            $Data2 += $Obj

        }

    }

}

 

$Data2 | Sort-Object -Property TimeGenerated -Unique -Descending

Comments

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

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 .

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?

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

Where did a User’s Account Get Locked Out?

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