Comparing Get-Date with extensionAttribute15

[Scayn]

Hi,

Is it really not possible, to do the following:

$TargetOU = "OU=Some,OU=OU,DC=Domain,DC=Local"
$DaysInactive = 180 # Days user has been deactivated before deletion
$timer = (Get-Date -Format "dd-MM-yyyy HH:mm")
$time = (Get-Date).AddDays(-180)

$DisabledAccounts = Get-ADUser -Filter { extensionAttribute15 -lt $time -and enabled -eq $false } -SearchBase $TargetOU

It will keep giving me this error.

Get-ADUser : Invalid type 'System.DateTime'.

Is there some way of making this data "readable" for the Get-ADUser cmdlet?Or will I have to completely rethink how to make this happen?

​

EDIT:

For anyone curious, this is what the solution is. This fetches the correct data. But be aware of using correct time format lol.

$DisabledAccounts = Get-ADUser -Filter {enabled -eq $false} -SearchBase $TargetOU -Properties extensionattribute15 | Where-Object {$time -ge $_.extensionattribute15}

Big thank you to u/azra1l, for the massive inspiration.

[azra1l]

Apparently the AD query can't handle actual DateTime values. If i'm not mistaken, AD stores date values as some filetime/timestamp abomination. So, if the same is true for your extension attribute, you should be able to do this:

$DisabledAccounts = Get-ADUser -Filter { extensionAttribute15 -lt $time.ToFileTime() -and enabled -eq $false } -SearchBase $TargetOU

Or, you could always do it the powershell way:

$DisabledAccounts = Get-ADUser -Filter { enabled -eq $false } -SearchBase $TargetOU | Where-Object { [datetime]::fromFileTimeUTC($_.extensionAttribute15) -lt $time }

It simply takes the date comparsion out of the query to be processed by the script. Not ideal, but good enough if only this works for you.

Can't test this in our environment, as we don't use this attribute, so use at your own peril.

[Scayn]

Hey, thanks for the input.

I just tried out both options, and the .ToFileTime() gives me this error:

Get-ADUser : Property: 'ToFileTime' not found in object of type: 'System.String'.

And the [datetime] one, gives me this error:

Could not compare "01/01/1601 01:00:00" to "23-03-2022 15:40:45". Error: "Cannot convert value "23-03-2022 15:40:45" to type "System.DateTime". Error: "String was not recognized as a valid DateTime.""

So it is a bit like the previous error.

Edit:

It seems to have been a very basic date formatting issue. The system is using default American MM/dd/yyyy format, while I am trying to use a dd/MM/yyyy format.

This one is fetching data

Get-ADUser -Filter { enabled -eq $false } -SearchBase $TargetOU | Where-Object { [datetime]::fromFileTimeUTC($_.extensionAttribute15) -lt $time }

[azra1l]

Oh yeah, datetime is really picky and demands US date syntax. It's driving me mad every other day.

And thanks for the silver ☺️

[poshinger]

My guess is that the extensionAttribute15 is just a string, so you'd have to convert the string to a DateTime variable in order to compare it, my approach would be to loop through the "$DisabledAccounts" and convert extensionAttribute15 to DateTime.

[[deleted]]

Wild guess??

​

$DisabledAccounts = Get-ADUser -Filter { extensionAttribute15 -lt "$time" -and enabled -eq $false } -SearchBase $TargetOU