I recently had a customer ask me about ThinApp deployment
options. I figured that it would make a
worthwhile blog post, so here we go.
There’s really three main ways to deploy a ThinApp package
(with differences within each category).
Let me see how well I can explain them.
|
Package location
|
Description
|
Execution Type
|
App Registration
|
Update approach
|
Sandbox location
|
Portability
|
|
Network share
|
Packages stored on central file server
|
Streaming
|
ThinReg utility (usually login script based), pre-configured
shortcuts, or direct execution of package
|
Package replacement or side-by-side updates
|
%AppData% (stored locally, or on network w/roaming profiles or
folder redirection)
|
Online, internal only. Sandbox
changes tied to OS unless redirecting to network.
|
|
Network (predefined network location)
|
Online, internal only. Sandbox
changes move with user.
|
|
USB
|
Take the packages and copy them to a set of thumb drives,
then distribute the thumb drives to the individual users
|
Deployed
|
Direct execution of package or autorun ThinReg script
|
AppSync, manual download or CD/USB distribution
|
%AppData% (stored locally, or on network w/roaming profiles or
folder redirection)
|
Users can take their applications with them to any computer. Sandbox changes will not follow.
|
|
USB (same location as package)
|
Users can take their applications with them to any computer
|
|
Network (predefined network location)
|
Users can take their applications with them to any computer
(sandbox only accessible internally)
|
|
Local
|
MSI package delivery to hard drive of machine
|
Deployed
|
MSI package automatically registers ThinApp package
|
AppSync, manual download or CD/USB distribution
|
%AppData%
|
Apps available offline with mobile machine.
|
More details can be found in the ThinApp Users Guide and the ThinApp Deployment Guide
Make sense? Leave me comments to let me know whether or not this
is clear or useful.