I am a developer of an educational software product, and I have noticed a large number of support calls from customers that use ZenWorks. Our application automatically updates itself when a new version is published, and this code has been working flawlessly for 10 years. It appears that some interaction with ZenWorks is causing our update to silently fail, and I would like to verify this.
At install, the installer gives full control to Everyone as an administrator, then is usually run with a low privilege (i.e. student) account. When an update occurs, files can be downloaded and updated in the %PROGRAMFILES%\app directory, and these all appear to succeed. File creation and writes all appear to work, EXCEPT for the .exe file. During update, the running file is renamed, and the new file is written to the old file.
When the executable is run again, it is obvious that the old version is still being run. This behavior is somewhat similar to Vista's virtualization of program files, but it also occurs on Windows XP. All of the environments that report this issue seem to be running ZenWorks, even if they did not use ZenWorks to install or package the application.
Can anyone verify that ZenWorks can cause this behavior, and even better, tell me how to fix it with a configuration setting. I would like to avoid having to reinstall thousands of desktops.