We are delighted to share our new EIC Delivery Methodology for efficiently managing Saviynt Implementations and delivering quick time to value. CLICK HERE.

AD Account Attribute LASTLOGONDATE is not getting updated

Siva
Regular Contributor
Regular Contributor

Hi Experts,

We are  facing an issue in updating AD ACCOUNT ATTRIBUTE  i.e. LASTLONGONDATE::lastLogon#millisec  as LASTLOGONDATE::lastLogonTimestamp#millisec,
we have updated firstly in ADSI connection & it is successful.

Then, we ran ADSI full ACCOUNTS Import job & Job also ran successfully, but  LASTLOGONDATE value is not getting updated .
we have tried for users who has LASTLOGONDATE in DEV environment.

Siva_0-1668161987525.png

[NAME::samaccountname#String,
ACCOUNTID::distinguishedname#String,
LASTLOGONDATE::lastLogonTimestamp#millisec,
LASTPASSWORDCHANGE::pwdlastset#millisec,
DISPLAYNAME::displayname#String,
CUSTOMPROPERTY1::employeeid#String,
CUSTOMPROPERTY2::mail#String,
CUSTOMPROPERTY3::sn#String,
CUSTOMPROPERTY4::givenname#String,
CUSTOMPROPERTY5::cn#String,
CUSTOMPROPERTY6::userprincipalname#String,
CUSTOMPROPERTY7::useraccountcontrol#number,
CUSTOMPROPERTY8::department#String,
CUSTOMPROPERTY9::title#String,
CUSTOMPROPERTY10::lastlogondate#millisec,
CUSTOMPROPERTY11::co#String,
CUSTOMPROPERTY12::c#String,
CUSTOMPROPERTY13::countrycode#String,
CUSTOMPROPERTY14::employeetype#String,
CUSTOMPROPERTY15::mobile#String,
CUSTOMPROPERTY16::division#String,
CUSTOMPROPERTY17::name#String,
CUSTOMPROPERTY20::manager#String,
CUSTOMPROPERTY26::objectguid#String,
CUSTOMPROPERTY28::company#String,
CUSTOMPROPERTY30::extensionattribute8#String,
CUSTOMPROPERTY19::employeenumber#String,
STATUS::useraccountcontrol#number,
CUSTOMPROPERTY21::homedrive#String,
CUSTOMPROPERTY22::homedirectory#String,
RECONCILATION_FIELD::CUSTOMPROPERTY26]

It will be really much help if anyone have worked on this one pls let me know the solution 

Kind regards 

Siva Avula

 

 

 

Saviynt 2021.0

 

 

13 REPLIES 13

rushikeshvartak
All-Star
All-Star

Does LASTPASSWORDCHANGE getting updated ?


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Siva
Regular Contributor
Regular Contributor

Hi Rushikeshvartak

apologies for delayed response,

No, LASTPASSWORDCHNAGE is also not getting updated.
We are unable get exactly what we are missing,

It will be really much help if you have worked on this one pls let me know the solution

Best regards
Siva Avula

can you try making all customproperty to lower case


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

Siva
Regular Contributor
Regular Contributor

For other connections also its in upper case only,
Its updating other CP values , So I think it wont make change.


just a thought, could you specify the type as String and map it to a custom property ?

Regards,
Avinash Chhetri

Siva
Regular Contributor
Regular Contributor

Hi Avinash
I had already tried by doing so, but it's not updated with new timestamp

Siva
Regular Contributor
Regular Contributor

I tried by making them to lower case, nothing chnaged,

whatever the last login date was also disappeared

Siva_0-1668781023575.png

try below

[CUSTOMPROPERTY1::CN#String,CUSTOMPROPERTY2::userPrincipalName#String,LASTLOGONDATE::lastLogon#millisec,DISPLAYNAME::displayName#String,CUSTOMPROPERTY25::company#String,CUSTOMPROPERTY3::sn#String,COMMENTS::distinguishedName#String,CUSTOMPROPERTY4::homeDirectory#String,LASTPASSWORDCHANGE::pwdLastSet#millisec,CUSTOMPROPERTY5::co#String,CUSTOMPROPERTY6::cn#String,CUSTOMPROPERTY7::givenName#String,CUSTOMPROPERTY8::title#String,CUSTOMPROPERTY9::telephoneNumber#String,CUSTOMPROPERTY10::c#String,DESCRIPTION::description#String,CUSTOMPROPERTY11::uSNCreated#String,VALIDTHROUGH::accountExpires#millisec,CUSTOMPROPERTY12::logonCount#String,CUSTOMPROPERTY13::physicalDeliveryOfficeName#String,UPDATEDATE::whenChanged#date,CUSTOMPROPERTY14::extensionAttribute1#String,CUSTOMPROPERTY15::extensionAttribute2#String,CUSTOMPROPERTY16::streetAddress#String,CUSTOMPROPERTY17::mailNickname#String,CUSTOMPROPERTY18::department#String,CUSTOMPROPERTY19::countryCode#String,NAME::name#String,CUSTOMPROPERTY21::manager#String,CUSTOMPROPERTY22::homePhone#String,CUSTOMPROPERTY23::mobile#String,CREATED_ON::whenCreated#date,ACCOUNTCLASS::objectClass#String,ACCOUNTID::distinguishedName#String,CUSTOMPROPERTY24::userAccountControl#String,STATUS::userAccountControl#Number,CUSTOMPROPERTY26::objectGUID#Binary,CUSTOMPROPERTY27::objectSid#Binary]


Regards,
Rushikesh Vartak
If you find the response useful, kindly consider selecting Accept As Solution and clicking on the kudos button.

sundas7
Regular Contributor II
Regular Contributor II

Hi Siva,

Were you able to resolve the issue?  We are seeing the similar issue in our environment.

The lastlogon date field is either blank for most of the user accounts or they are not getting synced correctly.

We see there is one other parameter in ADSI editor of AD :lastlogon Timestamp.

Should we be mapping (in account attribute) that to lastlogondate in Saviynt.

 

Thanks

Shyam

Siva
Regular Contributor
Regular Contributor

Hi Shyam, we have raised a ticket for this requirements , unfortunatelySaviynt is unable to manager this  lastlogon Timestamp attribute. so we are using lastlogondate

sundas7
Regular Contributor II
Regular Contributor II

Thank you Siva for your immediate response.

So which configuration is currently working in your environment.

Regards

Shyam

Siva
Regular Contributor
Regular Contributor

 we are using lastlogondate

Falcon
Saviynt Employee
Saviynt Employee

Here's a good explanation of lastlogontimestamp and why the information may not be accurate across DCs

https://social.technet.microsoft.com/wiki/contents/articles/22461.understanding-the-ad-account-attri...

Additionally, the lastlogondata or lastlogontimestamp may be updated but the connectors typically work based on the modifytimestamps which will have its own lifecycle which may further delay the information in Saviynt. Overall life cycle of these attributes needs to be checked before relying on the information in Saviynt.