I am using Get-SmbOpenFile, But surprisingly, it looses its connection and I can see that there is no lock even after couple of seconds later on the file any more, even it is still opened. I safely can remove that file on my server or can rename the file.
Why, this can be? I have to check opened .VHDX disk file connected with user and need to close them if they are still opened.
Get-SmbOpenFile | Where-Object { $._Path -match '\apvdp100\Profile\TestP1088\100.txt' } returns nothing even the file is opened remotely.
Get-SmbOpenFile | Where-Object { $._Path -match '100.txt' } returns the object if i open the file remotely and check within a second.
Even immediately after opening on remote machine from shared networked path, switched to file server and executed Get-SmbOpenFile it stops outputting anything and returns nothing.
It should in ideal case must return the information of opened file if it is opened otherwise nothing. But that's not the case as I explained earlier.
So, I have two questions :-)
**1. So, what is the right way to search the file ? ( above Fully qualified path doesnt returns the search result )
2. Why the lock gets lost after couple of seconds later**