>I succeeded to have this running by changing the application Identify account to one with the privilege. However, when this runs, it stops the entire Web services on the server. I have to issue a iisreset /restart to have them back running. So, obviously, someone doesn't like us to play with that under an ASP.NET application.

If you think about it this has to be the case - all the permissions being used before the change are potentially invalid.

It would be *less* dangerous to grant the neccessary registry permissions to the identity account, But it would be safer to temporarily impersonate a user with the required permssions. Example here: http://support.microsoft.com/kb/306158#4

>
>If the default would be to have a new Web site to use the ASP.NET version v2.0.50727 version, we wouldn't have to do that. Or, is there an option somewhere to let IIS know that every new Web site we configure should be under v2.0.50727?