|
We are using the updater component and 99% of the process is running smoothly, its that 1% thats killing me, here is our issue. Our operations team runs the installer on the client machine, the operations team has "admin" privs, the ops team then opens the application so it can check for downloads, no downloads are found (which is what is expected) and a "UpdateVersion.xml" file is created in the client directory. The install is created in a sub folder off of "program files", the "program files" security says "admins & power users" (also subs are flagged to inherit), all of the files and subfolders in the application folder have these permissions EXCEPT the "UpdateVersion.xml", it doesnt include "power users", so when the end user (who is in power users, but not in admin) runs the application (and in the mean time a new version is set to be downloaded) the download doesnt work (because they cant access the file), we must manually add "power users" to the "updateversion.xml" for it to start working.
Now if we have the ops team install the application WITHOUT running it and allow the end user (power user) to run the application, it creates the "UpdateVersion.xml" and the file's permissions includes "power user", the client is informed of the update and all is well.
Under the "debugging" section of the documentation that comes with the Component it says "If your app is installed in the program files directory, and you are NOT a admin or power user it will not update", allow of our users are power users.
If i create any files manually in the subfolders when im logged in as an admin it creates the file with "power users" included in the security.
Any help would be greatly appreciated
Subman |