We are currently using a script file (cmd) to kill some process when the UPS trigger a power loss. The problem we currently have is that the script is started by the UPS service properly, but it looks like it is running in a limited command environment. Some basic functions like SET or "echo test>c:\info.txt" works, but we cannot start or call another application, bat file, cmd file, taskkill.exe, etc. When using the SET command we can notice that it is effectively NOT running under the user account the service is set on. When we execute the cmd file manually, using the same account the service is set on, everything goes as expected. Anyone have an idea how to correct this behavior ? We suspect it is related to security, UAC or something close but no solutions worked yet. We already tried : Disabling UAC Modifying secpol to allow administrators to run any applications without questions Using Built-in administrator account for the service Using Local Service account for the service Using current user account (with administrative role) for the service. Thank you.

1. Perhaps the user context play the role. 2. Give try to UPS vendor's forum or support. Regards Milos

What do you mean by the user context ? Is it the user account used by the service ? We already contact the UPS manufacturer and they do not have a clue...