We are getting an increasing number of calls from users where they complain about their ThinApps are launching without their settings/configurations. In these cases, we have found that a new folder was created in the "%appdata%/Thinstall" folder with the thinapp name appended by the computer name. Example: "%appdata%\thinstall\netbioscomputername".
The problem is fixed by deleting the extra folder with the appended computer name.
This behavior seems become more prevalent since we upgraded from View 5.3 to View 6.1.
Our basic understanding of this is that the folder gets created because it thinks the ThinApp is already running.
What causes this scenario and how we can address it? Are there options in a ThinApp with regard to how this scenario is handled?
Could this happen if the user has the application running and it is forced to refresh without a normal logoff?
Any help/411 would be great. thanks...