I'm in the process of testing an upgrade to DNN 6.2 and also the AD Provider 5.0.4.

Once I upgrade to 6.2 the autologin no longer works. It is as though the AD httpmodule is not being loaded at all. When a user visits a portal that requires authentication, they are redirected to the normal login page & not the windowssignin.aspx

Is anyone else having this problem? 

A possible work around for us is to make it so that our standard login page redirects to the windowssignin page, but this means that the page the user was trying to access is lost and they are redirected to the home page.

 Cheers Wayne

BTW - A side effect of this is that it does eliminate the 302 redirect loop for search engine bots that happens when using the AD provider on sites available to the public.