A system administrator is deploying a legacy line-of-business application to corporate workstations. Standard users can launch the program, but receive runtime write errors whenever the application attempts to save configuration preferences. Investigation reveals that the software was originally designed to write user configuration files directly to its installation folder inside C:\Program Files\, which standard accounts cannot modify due to default system protection settings. Which of the following is the best long-term solution to resolve this issue while adhering to the principle of least privilege?
- Apply an application compatibility fix shim to virtualize and redirect directory writes to the logged-in user profile.Cevap
- BGrant standard domain user accounts Full Control permissions on the application folder in C:\Program Files.
- CRe-run the setup package from the command line using the /quiet and /norestart switches.
- DAdd standard users to the local Power Users group using the Local Users and Groups snap-in.
Cevap
The optimal resolution is to apply an application compatibility fix shim to virtualize and redirect directory writes to the logged-in user profile.
Applying an Application Compatibility Shim (or leveraging UAC file virtualization) allows legacy applications designed for older operating systems to run properly under standard user accounts. The shim redirects file write operations directed at protected system directories like C:\Program Files to user-accessible locations such as %LOCALAPPDATA%, maintaining system security while ensuring application functionality.
Adım Adım Çözüm
Anahtar Kavram
Application Compatibility Shims and User Account Control (UAC) File Virtualization