I have added the attribute lastlogondate to our account schema along with other attributes like lastlogon etc and all of them show up after aggregation except for lastlogondate.
Does anyone know why this attribute refuses to aggregate? Is it something to do with it being a date time ?
Turns out i was confused as usual. If you use Powershell you will see an attribute called lastLogonDate but it’s a PowerShell-calculated attribute from lastLogonTimeStamp.
It’s not an attribute that actually exists on the AD object if that makes sense - it’s PowerShell-specific.
No worries - like others have done, I can add it as a “custom” attribute and add logic in a rule somewhere to populate the value from lastLogonTimeStamp