Post client pc "SbClientLog.txt" and user and machine audit logs, so we can have a meaningful discussion here.
If you tie user accounts to AD (there is connector app for that), then you can automatically delete EEPC user account once it is deleted from AD.
If there's no recent audit for a user, then any machine they have been using has not synced - it's the machines which upload the audit after all?
There is a canned report called Users Not Assigned to Machines Report which might help you. Unless the user is simply using the EEM with their userID, what is the point of having a userID if it's not assigned to a machine? You could probably safely delete any users this report finds unless they are using EEM and you should already know who that is.
This doesn't answer your entire question but should help clean up your database.
I managed to receive the logs from the user...
the user is using mostly the hibernate mode... but was definitely also rebooting his client from time to time.. but these events are not logged in the audits... whats wrong? what can i do?
nothing - there's nothing in any log to indicate there's a problem, and also nothing to indicate user savignac has logged on since 18th January. My guess is they are using a different user ID.
I'm guessing (since this is an older version) that there's a problem with the audit system which is so subtle as to not be reported as an error - eBoot the machine to clean everything up, that should reset everything to user audit gets captured again.
EEPC 5.2.3 is not that old! and should work properly.
I would try to reconcile user and machine ID's using pre-boot Option/Recovery features. Before one applies heavier procedure of Emergency Boot.
what if a simple machine recovery does not help? the machine recovery was followed by user-deletion and a recreation of the user on the server, synchronising the changes onto the client. also creating a new user, called temp and syncing this one also onto the client.
this did not help, both users (temp and regular one) could not login, since a message saying, that parameters are incorrect appeared.
how can i fix such problems? may it be, that the local DB is broken or corrupt?
i did a emergency boot on a computer with the same problem last week and the computer got stuck within the safetech cd during the emergency boot process.
so what can i do instead? mount the sbfs and execute chkdsk? or is there another option like deleting ALL users from the affected client on the server, synch this onto the client, and then recreate the user?
eBoot is the only thing which will rebuild SBFS, other than disable/enable. There's not much else you can do - you could mount SBFS and chkdisk it I guess, it's not guaranteed to fix everything though, only things which Chkdsk can find.
okay, thank you!
and what would you recommend to do in case the emboot procedure will be stuck again?
last time when this happened, i got a 92h error after the next reboot.
so i want to be 100% sure, that it will fix my problem.