Running into an issue that I've been banging my head against for a while now. We use a shared executable located on a network share. It's an in house system and we occasionally update it. Recently we started running into issues where the EXE is locked and so we cant rename and replace it. Our standard release procedure has always been just to rename, and replace the file. Maybe not the most elegant but it has always worked pretty well.
Migrated to Server 2012 R2 about 6 months ago and it has been working fine apart from this.
I think I'm running into opportunistic locking https://support.microsoft.com/en-us/kb/296264 but I'm not sure of a way around it. Anyone have any thoughts?
Thanks