Why doesn't the authentication module retain its configuration settings?  I have a feeling that this is behind my issue of the two accounts being created depending on how you login (WindowsSignin.aspx or "Windows Login" tab of the login control).  It's like the login control completely ignores the domain name when creating the user account.

I configured the module with the following settings:

• Enabled:  checked
• Hide Login Controls?:  unchecked
• Synchronize Role?:  checked
• Do Not Automatically Create Users?:  unchecked
• Provider:  ADSIAuthenticationProvider
• Authentication Type:  Delegation
• Root Domain:  dc=mysubdomain,dc=mydomain,dc=biz
• User Name:  mysubdomain\domainuser
• Password:  mypassword
• Confirm Password:  mypassword
• Email Domain:  blank
• Default Domain:  mysubdomain

If I go back into the configuration page, it's changed to this:

• Enabled:  checked
• Hide Login Controls?:  unchecked
• Synchronize Role?:  checked
• Do Not Automatically Create Users?:  unchecked
• Provider:  ADSIAuthenticationProvider
• Authentication Type:  Delegation
• Root Domain:  dc=mysubdomain,dc=mydomain,dc=biz
• User Name:  blank
• Password:  blank
• Confirm Password:  blank
• Email Domain:  @change.me
• Default Domain:  blank

Shouldn't it at least retain the email domain and the default domain?

Your method doesn't really work for me.  Some of my users share a computer from time to time, so they need to be able to login to DNN under their own domain accounts instead of the account of the current Windows user.

Also, when I enable automatic login via WindowsSignin.aspx, my IE users can't upload avatar pictures.  For some reason, putting my site in the "Local Intranet" or "Trusted Sites" zones reduces functionality instead of increasing it.

My real problem is that the automatic login and the manual login create two different accounts when they should be the same.  I wonder if this is by design, or if it was missed during testing.