-
mike S
- PowerServer
- Monday, 6 July 2026 02:09 PM UTC
The app launcher stores itself on localappdata (non-roaming), whereas the application itself stores itself in appdata (roaming). This is configurable and is great that we have that option.
I don't see what benefit there is in storing the application in a roaming profile. if someone goes to another machine, or is using a terminal server farm, then yes it will already have downloaded stuff - but it would downloaded app again anyway.
There isn't any user specific settings/configurations in these downloads (unless the application itself was written to use an ini file that gets written to and downloaded).
Plus, this is a cloud application so users could be on machines outside the corporate domain as well as inside the domain.
To this point, i've kept everything at the appeon defaults, but i may just move everything to be at localappdata and not have it in roaming. What does everyone else do? Any reason this is a bad idea? I assume that the permissions on both locations would be the same.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.