Since I upgraded to the last couple of versions of DNN, I can no longer define an AD user as a SuperUser.  It used to be that I could locate the username in the database, and set the issuperuser flag to 1, and that particular user would have host-level access from then on.  With the last few versions of DNN though, everytime I set this flag it resets to 0.

This makes it extremely difficult to manage my system that has 139 AD-Authenticated portals now because I cannot log into those portals except via AD login.  Is there any chance of getting this working again or do I need to go through each of my 139 portals to reconfigure them to allow DNN logins?

I am in the same boat except I had a 6.0.2 installation with AD already setup and 2 AD users set as SuperUsers.  After upgrading to 6.1.1 in internet explorer i noticed single sign on did not work.   In my case i had default authentication disabled which meant I could not login to manage.  I had to revert to 6.0.2.

 After reverting I enabled default authentication and then tried the update again. this time i was able to login as a standard superuser but my ad superuser account does not work.  If I remove the website from trusted or intranet security group it prompts me for the ad username and password which it accepts and then gives me the DNN login prompt which fails.  There is no indication in the event log of a login failure or an error.  Actually nothing shows up at all.  

 So it was working in 6.0.2 but failed when going to 6.1.1.