title: IIS 7 Windows authentication with default app pool setup problems
body: <p>I have IIS 7.5 site:</p>
  
  <ol>
  <li>Authentication = Windows Aythentication enabled</li>
  <li>Application Pool = DefaultAppPool</li>
  <li>DefaultAppPool Identity = ApplicationPoolIdentity</li>
  <li>Load User Profile = True</li>
  </ol>
  
  <p>On the filesystem, </p>
  
  <ol>
  <li>DefaultAppPool has Read and Execute privileges to the entire site.</li>
  <li>Also added a security group with Read and Execute privileges to the entire site.</li>
  </ol>
  
  <p>With these settings, only users in the security group are able to access the site. All others get a AD login window, which has no affect. I'm not understanding this behaviour.</p>
  
  <p>From research, it looks like I don't need to add the DefaultAppPool to the filesystem, if users are only executing, but still doesn't explain why they get the login challenge.</p>
  
  <p>I'm also unclear if i need to set the AuthenticatedUserOverride (in Config Editor) from UseAuthenticatedUser to UseWorkerProcessUser if i want to use the filesystem security of DefaultAppPool. When i set this, i get an access error, not even the login challenge.</p>
  
  <p>Note: site is not in the Default Web Site, but on a specific port number.</p>
  
  <p>I'm unclear why i seem to need users listed in an ACL rather than using the generic DefaultAppPool.</p>