title: IIS - Custom Application Pool identity not being used
body: <p>I have an ASP.NET web application that uses an Application Pool with a custom identity set to connect to DB via Trusted Authentication.</p>
  
  <p>I have this working correctly on a dozen servers, yet I am having an issue with one: IIS is not using the custom identity and is instead attempting to impersonate the user when initiating the DB connection.</p>
  
  <p>I verified I have the app pool configured to use the custom account and my web.config has <code>&lt;identity impersonate="false"/&gt;</code>. In fact I'm using an exact copy of the code and web.config from another properly working box.</p>
  
  <p>I do have Windows Authentication enabled for the app to get the user login, but not for impersonation, and this is working correctly on 12 of 13 servers. If I disable Windows Authentication on the impacted box, I get <code>Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON</code> when accessing the site.</p>
  
  <p>I tried recreating the application pool and the the IIS Application to no avail.</p>
  
  <p>Anyone seen this behavior before? I'm running out of ideas. Thanks!</p>
  
  <ul>
  <li>ASP.NET MVC4</li>
  <li>IIS 7.5</li>
  <li>Server 2008 R2 64bit</li>
  </ul>