title: How to allow to allow admins to edit my app's config files without UAC elevation?
body: <p>My company produces a cross-platform server application which loads its configuration from user-editable configuration files. On Windows, config file ACLs are locked down by our Setup program to allow reading by all users but restrict editing to Administrators and Local System only. </p>
  
  <p>Unfortunately, on Windows Server 2008, even local administrators no longer have admin privileges (because of UAC) unless they're running an elevated app.  This has caused complaints from users who cannot use their favorite text editor to open and save config files changes-- they can open the files (since anyone can read) but can't save. </p>
  
  <p>Anyone have recommendations for what we can do (if anything) in our app's Setup to make editing easier for admins on Windows Server 2008?</p>
  
  <p>Related questions: if a Windows Server 2008 admin wants to edit an admins-only config file, how does he normally do it?  Is he forced to use a text editor which is smart enough to auto-elevate when elevation is needed, like Windows Explorer does in response to access denied errors?  Does he launch the editor from an elevated command-prompt window? Something else?</p>