I have been going rounds with the AD suff myself. I not only configured the DNN settings for active directory authentication, I also turned off the anonymous user access to the site and removed all but authenticated and required service users from the site folders. I found that ASP.NET takes the path of least permissions, so if the user can authenticate without AD it uses those credentials. As it requires the user credentials to get to the page, that is what ASP.NET uses. In mixed mode, the users get created and being that the site requires AD credentials to access site resources. You also want to be sure, if your site is being access via IP, the address is listed in your internal DNS server. Otherwise, your users will be required to log into the site (http://10.0.0.1 translates to http://myinternalsite).

I agree that the AD team should address the issue of new users not getting created when fully AD configured, however I had to find a work around in the mean time. I hope this helps.

 

I was experiencing the same issues with AD not creating users.  I removed the identity impersonate="true" from the web.config and now it is working.  I am using a user with network access as the Annonymous user for the site and to run the App Pool instead of a local account.

This is what I did to sort this. Hope it helps someone. I am using DNN v455 (but hope to go up to v484 sometime soon):

1) Edit your web.config file to have forms authentication rather than windows authentication i.e.

 
 
     
   
     

also comment out the authentication entry under httpmodules i.e.

     

 also ensure the following entry is present in the main section of the web.config file:

     
       
       
     
   

 2)   Copy the windowsSignin.aspx files from the admin\security folder to the dotnetnuke root folder.

3)  Amend the document properties in IIS for the dotnenuke virtual directory to have windowssignin.aspx as the default document (it will pick it up from the root directory so that is why step 2 is required)

4) Make sure AD authentication is enabled and functioning properly under Admin / Authentication of the portal.

That should be it. Existing users will be logged in. New users will have a DNN user created in the database and will be logged in. The AD information should be used to create the information within DNN.