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?