I'm working with a client/server application that places entries in Component Services/Dcom Config. I'd give you more info on DCOM, but I don't know much about how this program works with it. When I run the client install on a Windows Vista client, I right click on the setup and select Run as administrator. The install works great, but the first time I run the program I get an error. I am logged in as a user that belongs to the clients local admin group. The error isn't important because it's specific to the app, not Vista. I can avoid the error by Running as administrator the first time I click the app's shortcut on the client. I have an easy fix to the problem, but I wonder why I'm not prompted to run as administrator. I know why I have to Run as admin thanks to processmon. I need to create a string in the HKEY_CLASSES_ROOT\TypeLib key but I can't unless I Run as administrator. I have an easy workaround, but I still have two questions:1)Why aren't I prompted to elevate my permissions when I click on my programs .exe?2)Why should I have to Run as administrator if my user account is a member of the Local Admin group. One other note. If I run the install and click on my client app shortcut for the first time logged in as the builtin admin, I don't have any problems. Thanks in advance.

1) Because Vista isn't psychic. There is a whole bunch of application compatability heuristics designed to detect applications that will fail without admin rights but they are by no means comprehensive. You can flag in the shortcut properties that the application requires admin rights (it's on the compatability tab), in which case it will always give you the prompt. 2) This is due to User Account Control. All processes are launched with the permissions of a Standard User by default, unless the application either identifies itself as requiring admin rights or the heuristics detect the need. Only Administrators can respond to this prompt, either by clicking yes in the consent dialog or by entering credentials into an over-the-shoulder elevation prompt. 3) The built in Administrator account isn't subject to UAC, neither are Domain Administrators if you are on Active Directory.

Thanks Andy. I agree with what your saying. I may need to make use of the Run as admin checkbox in the compatability tab in the future. For now I just need to Run as admin once to create the key. Thanks.