1) Does the AD solution work best on asp.net 2.0?

2) If it doesnt matter, does it matter if I have version 3.3.4 or 3.3.5?

3)Since I have thousands of users that I will need to match up with AD accounts, is there a bulk way of handling this?

So far I've had great success with running it under 3.3.5 and .NET 1.1. I haven't tried under 2.0 except with DNN4.

As far as question 3 goes, there's nothing that you have to bulk do. As your users hit the site and login (or get automatically logged in) and are authenticated against the AD their accounts are created automatically in DNN. The hardest part is getting Security Roles synced. If the roles are already there they'll be added when their DNN account is created. If not then you need the 3.3.5 AD Fix.

You mean a user who has already has an account on the site and is also a domain user? They'll get a new account created with their domain credentials (Domain\Username). How you reconcile that I'm not sure.

I think if you don't uncomment the Authentication line in your web.config they won't be prompted to login but I'm not sure if that affects automatic logins. I thought I was good to go on that count but found out last night that if I hit the site externally it prompts for a login. Everytime I'd tried before from home it was on my work laptop and I thought the "Page Not Found" was related to something else not that it was trying to authenticate me and last night I happened to use my home computer.