We are currently using Persona and will be moving over to UEM very soon. We are currently setting up UEM 9.5 and have over 100 thinapps that we plan on continuing to use. I know that we will need to rebuild anything created before Thinapp 5.2. What is the best way to make sure that each users Thinapp settings are retained? Do I have to profile each Thinapp in order to allow them to sync within the user's profile?
Hi rmunson95,
For integration with UEM's DirectFlex feature, we require ThinApp 5.2 packages. In such a scenario, UEM performs it actions within the ThinApp virtual environment. That means that you can reference "real" profile locations like <LocalAppData>\YourApp\Something.json and HKCU\SOFTWARE\YourApp\SomethingElse, and UEM will read those from (and restore them back into) ThinApp's bubble.
Without upgrading your packages, I think you can still use UEM to persist your users' ThinApp settings (but I definitely don't have much ThinApp experience...) In that case, you would be working with the ThinApp settings "from the outside", i.e. where they live in the "physical" profile. I think that's in %APPDATA%\Thinstall\ApplicationName?
In that case, you would create Flex config files in UEM for your packages, each just capturing the corresponding "real" <AppData>\Thinstall\ApplicationName folder.
Hi rmunson95,
For integration with UEM's DirectFlex feature, we require ThinApp 5.2 packages. In such a scenario, UEM performs it actions within the ThinApp virtual environment. That means that you can reference "real" profile locations like <LocalAppData>\YourApp\Something.json and HKCU\SOFTWARE\YourApp\SomethingElse, and UEM will read those from (and restore them back into) ThinApp's bubble.
Without upgrading your packages, I think you can still use UEM to persist your users' ThinApp settings (but I definitely don't have much ThinApp experience...) In that case, you would be working with the ThinApp settings "from the outside", i.e. where they live in the "physical" profile. I think that's in %APPDATA%\Thinstall\ApplicationName?
In that case, you would create Flex config files in UEM for your packages, each just capturing the corresponding "real" <AppData>\Thinstall\ApplicationName folder.
I had previously attempted to do what I think is exactly what you stated.
I created a custom config file then named it the name of the Thinapp in this case CDBurnerXP.
import/export tab:
[IncludeFolderTrees]
<AppData>\Thinstall\CDBurnerXP
Direct Flex Tab
CDBurnerXP.exe (Thinapp exe)
Turned out that it was not working because I had the whole path to the exe. Thank you for your help.