In AD my domain is listed as domain.com. What I am saying is that users should have the option to type their name in any format they want and it should just work. When I connect to a network resource or say outlook web access I can log in using user@domain.com domain.com/user domain/user they all just work. Even if i just type my username and no domain it still works because in iis i have a default domain configured and users dont really have to type it in. DotNetNuke should not treat windows authentication any different that windows does. Windows accepts all formats and so should DNN. So like I said in my previous post, I think you should store it in the database in which ever way it needs to be to make it work. Then when a user logs in you simply manipulate what they typed to make it match the format in which you have it stored as. i.e if they typed user@domain.com, take the value of the textbox before you do anything else with it change it to domain.com/user and proceed with authenticating. As i finished writing that, I think I finally understand the problem. Are you not able to manipulate what the user has typed in the login box because dnn handles the event and not the auth provider? OK OK, now I get it. In that case what if you did a check on the dnn table to see if the alternate format of the user name exists and if so prevent DNN from creating two users? At the very least reject the authentication? I am answering my own questions as i go. That would be because you can not add your own stored procedures. But you dont necessarily need a stored procedure to access the database.

How do you promote an AD user to host admin?  I can make one an Administrator, which allows access to the Admin menu, but don't see a way to promote to host admin.

I did see that, but I was assuming there was also a way to do it before you turn off Standard authentication through the host or admin interface.

Is there some program that is similar to phpmyadmin but for sql express 2005?