This content has been marked as final. Show 5 replies
post the client log - it will tell you which way the password is flowing.
are you using offline or online install mode?
We only use online for installs. When you say client log, are you referring to the audit log? I am still learning all the whys and wherefores for Safeboot.
The clientlog can be found on the client's installation directory, usually C:\Program Files\SafeBoot\Sbclientlog.txt
Also you can see for yourself, if it says anything regarding "Updating local token data for user SbAdmin with database changes" which indicates an update of the password.
Note that the sbclientlog is only useful if it's from one of the clients that has issues with picking up the 'new' password.
Another tip, make sure timestamps are correct on the machines, if the client's timestamp is newer than the one from the server, it wouldn't wanna update any passwords as it thinks it's newer then.. There's an option on the Sync tab from the machineproperties, to ensure the times are synced along with the server.
Ok. Thank you for the clarification. I have looked at a client that should've picked up on the new password and I can see entries for updating local token data, but I can still log into Safeboot with the old password.
It was back around August when this happened, so all my clients should've picked up the new password.
It's like something reverted back to the old password.
It's really weird.
if someone got the (old) password wrong on a machine which had not yet synced, then got it right and synced, then the old password would be reflected back up to the db and across everywhere.. The code tries to keep the password of the last successful login current everywhere, not necessarily the last changed password. (think about it - it makes sense once you work the logic through).