We use MS SCCM to deploy all our thinapped applications via their MSI files. This works just fine... apps are installed silently in the background (to shared folder C:\ThinApps) and are available for all users.
All users are regular domain users, i.e. they don't have any administrative or power user rights.
Our problem occours when we deploy an update. This is done by putting the update thinapps on a file share, and having the corresponding AppSyncURL in the packages.
Upon launch it creates the .ASL file (which I presume is the file to see when it last checked for an update) and begins to download an .ASE (which I guess is the new .EXE).
However, since they are regular users ThinApp seems to not be able to replace the original .EXE and we are left with a duplicate .1 file. Which means redundant data storage...
Any way to fix this?
Another issue... if an administrator happens to start an app on these machines the admin created .ASE is unavailable to users, meaning they'll never check for updates(?). Additionally, when run as an admin the files won't be renamed to either .EXE or .1, just leaving the .ASE there.
Any fix to this apart from manually resetting file security information and making any user able to delete any application?