![]() No one, with the exception oft the person who's trying to open it legitimately, has opend the file -> we've all file audit policies enabled, no according entries in the event logs ![]() It's not the temporary ownership file “~$ myfile.doc” If a user tries to open a file (word or excel) he's getting the well know message saying the file is “locked for editing by 'user XYZ'” -> the user who is allegedly "locking" the files (user XYZ) is always the same one and it's a simple domain user, no domain admin or such.įurthermore: "user XYZ" has never opened these files, since, according to the ACLs, he's not allowed to do so. Sometimes we are experiencing a strange effect on our file servers and all the usual/known reasons cannot explain it:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |