|
Posted by Roger Abell [MVP] on December 17, 2006, 12:21 pm
Please log in for more thread options I think you have been given some correct information.
Consider, JoeApp, a previously unseen application, always checks
for a temp file on disk in same location as a file it attempts to open,
and if found determines from the temp if the instance of JoeApp that
opened the file did so for exclusive access.
Such is totally application specific. OS based lock examination
would not help, unless locking at OS level is also being used.
In either case one might feasibly use a tool like filemon or PsFile
( http://www.microsoft.com/technet/sysinternals/fileanddiskutilities.mspx )
to determine what accesses are being made to the file.
If the file locking is done via the OS, instead of application internal,
then the file locking is probably being handled by the SMB redirector,
and info on these locks is in memory stuctures.
One could try to get at the desired info by examination of the existing
file object handles. See the Handles utility
http://www.microsoft.com/technet/sysinternals/ProcessesAndThreads/Handle.mspx
> In this instance that might work but try to pretend for a moment the
> following scenario:
>
> User is using an application you have never heard of (I mean you
> specifically, for this example, I want you to avoid thinking of
> products that can provide the information I want) - call it Joe's
> application.
>
> Using Joe's application, trying to open a file called ABC.XYZ
> Joe's application tells you that the file is "in use" or "locked by
> another user" - whatever.
>
> Assuming no MS Word or Excel is involved, assuming you have no idea by
> whom or with what application the file is in use...
>
> Can you suggest a third party program or a security policy for Windows
> that will allow this user to determine what network user has the file
> open?
>
> While I appreciate your previous answers and advice, they all avoided
> the issue - I need to assume nothing is known, except that the file I
> am trying to open is definitely open and locked by someone else on
> this network.
>
> In computer management on the server, for example, I can see open
> files and sessions. Is there a policy setting perhaps that I can
> assign to users that they have the rights to see this specific
> information, but not other administrative items in computer
> management?
>
> I appreciate any advice you could offer.
>
>
>
> On Tue, 5 Dec 2006 10:34:51 -0000, "Edwin vMierlo"
>
>>Well it does matter, as "file locking" is partially the responsibility of
>>the software which opens it.
>>
>>Example, Notepad.exe does not lock it, but MS-Word does.
>>
>>As far as I remember, Microsoft Office applications do actually lists who
>>has the file open (just tested it with XL, and it actually does list the
>>domain username on who has the file open)
>>
>>As you are using MS-Word, it might be best to post your question to an
>>office newsgroup, experts there might be able to handle your specific
>>question
>>
>>rgds,
>>Edwin.
>>
>>
>>
>>
>>> On Mon, 4 Dec 2006 17:32:39 -0000, "Edwin vMierlo"
>>>
>>> >
>>> >> Dear all,
>>> >>
>>> >> I have a specific request on a network for a user to be able to see
>>> >> who has any specific file open. For example, user wants to access a
>>> >> file but software says file is open -
>>> >
>>> >what software ?
>>>
>>> Doesn't matter what software. In this specific case, it is MS Word,
>>> but I don't want it to matter. Regardless of the software, assume a
>>> program tells the user a file is already in use, and assume that
>>> software cannot determine by whom.
>>>
>>> >
>>> >
>>> >
>>> >> I want this user to be able to
>>> >> see who has the file open. I DO NOT want this user to have any other
>>> >> more-than-normal priviliedges - ie: administrative, etc. - it is an
>>> >> ordinary user, who needs to be able to see just this information.
>>> >>
>>> >> I cannot find any policy or plugin, perhaps I have not looked in the
>>> >> appropriate place.
>>> >>
>>> >> Please advise.
>>> >>
>>> >> Thank you
>>> >>
>>> >>
>>> >> ---Atreju---
>>> >
>>>
>>>
>>>
>>> ---Atreju---
>>
>
>
>
> ---Atreju---
| 
XML Sitemap