When granting access to resources such as files, it's best practice to apply the principle of least privilege. This means granting the user the minimum access necessary to perform their job and no more. However, this can sometimes lead to unexpected behavior when users attempt to open files. For example, a user may have explicit "Write" permissions on a file, but applications may open the file in read-only mode. Behavior like this will quickly lead to a user creating a help desk ticket.
Overview
A seasoned IT Pro might see this help desk ticket and immediately suspect NTFS permissions as the culprit - and they would be correct to suspect this! However, what they may not immediately realize is why the application is opening the file in read-only mode. Once the IT Pro discovers that the user has "Write" permissions on the file itself, and yet the file still opens in read-only mode, it's time to roll up the sleeves and dig deeper. 🕵️♂️ In this guide, we'll use a tool that should be in every IT Professional's toolbox: Process Monitor (ProcMon). ProcMon can be used to troubleshoot may issues within the Windows OS; however, in this guide, we'll focus on using ProcMon to monitor what's happening under the hood when an application opens a file in read-only mode.