views:

169

answers:

0

Hi folks

I have a problem with windows UAC, scheduled tasks and a executable named "dbupdate.exe". I have full power over source code, manifests and so on, but not over user systems (short: normal software engineer ;-). Language is Delphi, but shouldn't be important I think.

I have a problem using an application in task scheduler in windows vista and windows 7. The program is named dbUpdate.exe. It has built in a xp/vista manifest, which configures that the program should be started "asInvoker".

Now, in vista and windows 7 I can start the program without any problem, but I have to be logged in to the system. If I am not logged in, the program is not executed (I use windows task scheduler, but I know the problem exists with other scheduling-programs too). But: If I rename the program to "dbBlaBla.exe" it is executed. Leads me to the point, that the UAC Installer Detection is thinking my program is an installer (which it's not, but I know it looks at filenames like update, setup and so on).

I searched the web, I could not find many helpful things. So I ask here

Do I have to create a special manifest to be able to execute it in a scheduled job? Or is there a way to disable UAC for scheduled jobs or just for my executables? Or do I realy have to choose another name (then it would work, like mentioned before) and take the risk that the costumers and my colleagues are not very satisfied about this?$

Thanks for any help, greetings