We have a line-of-business app written in VB6. When the app starts, it checks a specific network path to see if there any updates to the application. If there are updates, the program logs in as the domain administrator and copies the new files. Since Windows Vista, this is broken because of UAC. In order for our app to update itself, the user has to right click and select "run as administrator". If the user is not a local admin on their computer, windows will ask for administrator credentials. Is their any way in group policy to specify that a particular executable can run as the administrator without prompting? If not, does any one have any suggestions on how to get around this?
If the app is installed under Program Files and Windows vista/7 UAC will only allow administrators to change those files. There are several possible ways I can see to circumvent this security feature. Be warned - UAC is trying to prevent you from shooting yourself in the foot so be wary.
1) (not tested) reinstall the app in a non-program files directory. Windows is only controlling access to certain special directories
2) turn off UAC. This should return it to pre-Vista function.
3) if the update can be driven from the command-line, schedule a regular task to run as administrator to perform the update
4) Whenever there is a release, package the update and deploy it so that the app never has the need to update.