Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a question on how to best deploy/update a software package on a Windows server that is used by several users across the network.

We are in charge of updating a software package on a regular basis. This package is installed in a shared folder on machine A.

Users log into machine B via terminal client. The shared folder is accessible from machine B.

Now when we try to update the software, we often face the situation where someone is still running the software, meaning that the EXE/DLL files are locked and we cannot update them.

We cannot tell who is locking the files, since we do not have access to machine B. We basically have to call the other office every time and ask everyone to please quit the software.

What would be a saner way to implement this kind of setup? Or do we have to resort to breaking the locks?

share|improve this question

You can see the current network connections in Control Panel > Administrative Tools > Computer management > Shared folders > Sessions.

You can also close a connection by Right clicking it and selecting "Close session", but I won't do for updating DLL's of a running program:

share|improve this answer
this is exactly right. This is a design choice to improve stability, not something you want to workaround. – Jim B Nov 10 '10 at 22:38

try to use unlocker (

share|improve this answer
I'm aware of this possibility, but I'd rather find a way to do this "right", instead of hacking around a design feature using a 3rd party tool. There HAS to be a better way :-) – hmn Nov 10 '10 at 14:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.