In my experience the server has to be part of the domain. Will adding it to the domain cause problems with IIS or SQL? Unfortunately I can't comfortably answer that question.

Your AD-provider is indeed working nicely. I, however, found out that it's not working correctly with DNN's 'required' profile fields. Normally, when a user registers or logs in and that user has a required profile field not filled in, DNN will enforce that user to first fill in that field, before letting the user actually log in again.

When automatically being logged in via the AD-provider, this check seems to be passed by, causing DNN to not ask the AD-user to first fill in the required fields.

This functionality is somewhat important to the company I set up this system for, though. Is there by any chance a way to fix this myself (perhaps some setting) or is this something that has to be fixed in your AD-provider itself and will you eventually be fixing it?

Thanks in advance for your information! :)

It is important to our company that DotNetNuke's correctly forces users, that automatically get logged in via the AD provider, to fill in required profile fields, that haven't been filled in yet by that user.

Additionally I'd like to add that if a user logs in by hand (via de AD provider's login-screen), everything works as expected :)

Considering the above -and- since it's been some time since my previous posts, you'll surely understand that I'm, by now, getting a little desperate for a fix! Could anyone therefore please say something useful about my pre-previous post?

Thanks in advance!