Yes you will need the source files (which can be found here) and I'd also setup a local development install of DNN if you don't have one already. It doesn't need to be the source version, the install version will work fine.

Setup your local DotNetNuke install and install the source version of the AD provider on it. Go to your <DNN Install> directory and browse to DesktopModules\AuthenticationServices\ActiveDirectory and launch the .sln file. Once it's open you'll probably have to fix the references to DotNetNuke.dll and DotNetNuke.Membership.DataProvider.dll. Once the references are fixed you should be able to do a build of the project. At this point it'll put a new DotNetNuke.Authentication.ActiveDirectory.dll in the project's bin directory.

1. Once your project is setup open the login.ascx file and also open up the standard DotNetNuke login.ascx (DesktopModules\AuthenticationServices\DNN\Login.asxc). 
2. Copy everything starting with <div class="dnnForm dnnLoginService dnnClear"> right down to the closing </div>.  
3. Remove the verification items <div class="dnnFormItem" id="divVerify"...> to the closing </div> tag for that section.
4. Rename divCatpcha1 and divCaptcha2 to trCaptcha1 and trCaptcha2
5. Build the project and make sure it succeeds.
6. Copy the freshly compiled DotNetNuke.Authentication.ActiveDirectory.dll from the project's bin\Providers directory to your development install's bin\Providers directory.
7. Launch your development install in your browser and verify that Standard and Windows Login look the same (got the Funk out).

If all is good you should be able to now copy the login.acx file and the DotNetNuke.Authentication.ActiveDirectory.dll to their respective locations on your production install (make backups of the files before copying).

If you run into any problems let me know. I'm going to try to get some bug fixes in this week if I can free some time up and may do a quick release. My hands are a little tied as I still want to support DotNetNuke 5 and these changes make it the provider look funky in that version. I could do multiple releases but I've done that before when DotNetNuke went from version 4 to 5 and it was a real pain in the butt to having multiple sources and releases.

Mike,

I made the changes, but when Trying to build, it seems that the project is not recognizing my, local DNN install, I get a bunch of errors saying DNN items not being recognized:

Could not locate the assembly "DotNetNuke". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

I changed the MyProject IIS path to match my local one but this didn't seem to help.

Chris

Mike,

I had not changed the references, after doing so I got a bunch of warnings about timezone and then some errors about unable to copy file "install.css" (for example) to D:\Websites\DNNDev... The Device is not ready

Is there something else that might be referencing the incorrect local DNN? my file path should be C:\DotNetNuke\Website....

Chris