title: How to test Windows library under different user-security permutations?
body: <p>I am working on a developer library that I want to release later this year and it should work under different user rights and also on different windows platforms. The library can be executed in both a web, windows-service and desktop-app-client context.</p>
  
  <p>What combinations of users should I test the application under? Is it enough to test it using </p>
  
  <ol>
  <li>Normal standard user</li>
  <li>Administrator</li>
  <li>Local system account</li>
  </ol>
  
  <p>Are there any more permutations of users? What kind of typical users/policies do exists out in the enterprises?</p>
  
  <p>Are there any guides about how to Windows "test" software before release so that the number of security/rights gotchas/issues can be addressed before the application hit the customers?</p>