11/11/2022 02:27 AM
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.
[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
11/16/2022 06:22 PM
Does LASTPASSWORDCHANGE getting updated ?
11/17/2022 09:30 PM
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
11/17/2022 09:32 PM
can you try making all customproperty to lower case
11/17/2022 09:38 PM
For other connections also its in upper case only,
Its updating other CP values , So I think it wont make change.
11/18/2022 05:25 AM
just a thought, could you specify the type as String and map it to a custom property ?
11/18/2022 06:22 AM
Hi Avinash
I had already tried by doing so, but it's not updated with new timestamp
11/18/2022 06:17 AM
I tried by making them to lower case, nothing chnaged,
whatever the last login date was also disappeared
11/18/2022 09:35 AM
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]
03/31/2023 06:19 AM
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
03/31/2023 06:27 AM
Hi Shyam, we have raised a ticket for this requirements , unfortunatelySaviynt is unable to manager this lastlogon Timestamp attribute. so we are using lastlogondate
03/31/2023 06:35 AM
Thank you Siva for your immediate response.
So which configuration is currently working in your environment.
Regards
Shyam
03/31/2023 06:37 AM
we are using lastlogondate
03/31/2023 12:46 PM
Here's a good explanation of lastlogontimestamp and why the information may not be accurate across DCs
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.