I have a file \\server\share\myApp\app.exe that a handful of people run directly from the share. I need to update that file occasionally, but it is usually locked due to the open SMB sessions.
My normal procedure for similar SMB locked files is to close the files and sessions locking them like:
$openAppFiles = Get-SmbOpenFile | Where Path -like 'D:\Shares\myApp\*'
$appSessions = $openAppFiles | Select SessionID -Unique
Close-SmbOpenFile -FileID $openAppFiles.FileID -Force
Close-SmbSession -SessionID $appSessions.SessionID -Force
Extract-Archive $newZip -Destination 'D:\Shares\myApp\' -Force
But lately, I have run into issues where a client is able to reconnect and lock one or more of the files I'm updating within that tiny window. I can test trying to just rename a file for example:
Rename-Item .\app.exe .\app.exe.bak
[Error] Rename-Item : The process cannot access the file because it is being used by another process.
Is there a way for me to temporarily block clients from accessing these files?
I've considered turning off the share temporarily, but I would have to do it after-hours. I can also just keep re-running it until it works, but that doesn't necessarily solve the issue either. What other options can I try?
