Not really. If a file is locked, it's locked and unless the process that holds the lock releases it or the network share connection for that user is disconnected, you can't do much with the file.
You should switch to ClickOnce deployment instead of running the executables from a network share. Aside from the updating issue you describe, running from network share has implications on the code access security, and has a perf impact on the initial load of the application.
我们的问题原来是由于 Windows 文件共享中的一项名为“机会锁定”的新功能造成的。 ”当两台服务器都是 2008 年时，目前不可能关闭此功能。
我们目前正在与 Microsoft 合作，寻找其他解决方案并进行一轮工作。目前倾向于使用DFS。
Our problem turned out to be because of a new feature in windows file sharing called "Opportunistic Locking." It's currently impossible to turn this feature off when both servers are 2008.
We currently have a case open with Microsoft looking for other solutions and work a rounds. Leaning towards using DFS at the moment.
In general you should have no problem to rename locked file on windows 2008 terminal servers exactly as on all previous versions of Windows NT starting with first one Windows NT 3.1.
Probably you have problem with the program which you use for file renaming. You could do this in the old operation systems directly in Explorer, later no more. But it is possible to rename files in CMD.EXE. Just start cmd.exe and try rename command.
发布评论
评论（3）
并不真地。如果文件被锁定，它就被锁定，除非持有锁的进程将其释放或该用户的网络共享连接已断开，否则您无法对该文件执行太多操作。
您应该切换到 ClickOnce 部署而不是运行来自网络共享的可执行文件。除了您描述的更新问题之外，从网络共享运行还会对代码访问安全性产生影响，并对应用程序的初始负载产生性能影响。
Not really. If a file is locked, it's locked and unless the process that holds the lock releases it or the network share connection for that user is disconnected, you can't do much with the file.
You should switch to ClickOnce deployment instead of running the executables from a network share. Aside from the updating issue you describe, running from network share has implications on the code access security, and has a perf impact on the initial load of the application.
我们的问题原来是由于 Windows 文件共享中的一项名为“机会锁定”的新功能造成的。 ”当两台服务器都是 2008 年时，目前不可能关闭此功能。
我们目前正在与 Microsoft 合作，寻找其他解决方案并进行一轮工作。目前倾向于使用DFS。
Our problem turned out to be because of a new feature in windows file sharing called "Opportunistic Locking." It's currently impossible to turn this feature off when both servers are 2008.
We currently have a case open with Microsoft looking for other solutions and work a rounds. Leaning towards using DFS at the moment.
一般来说，在 Windows 2008 终端服务器上重命名锁定文件应该没有问题，就像在从第一个 Windows NT 3.1 开始的所有以前版本的 Windows NT 上一样。
可能您用于文件重命名的程序有问题。您可以在旧操作系统中直接在资源管理器中执行此操作，以后就不再这样了。但可以在
CMD.EXE中重命名文件。只需启动cmd.exe并尝试rename命令。In general you should have no problem to rename locked file on windows 2008 terminal servers exactly as on all previous versions of Windows NT starting with first one Windows NT 3.1.
Probably you have problem with the program which you use for file renaming. You could do this in the old operation systems directly in Explorer, later no more. But it is possible to rename files in
CMD.EXE. Just startcmd.exeand tryrenamecommand.