ThinApp is an application virtualization (Agent-Less) solution.
Application virtualization, therefore, the use of ThinApp, allows us to:
- Coexist different versions of the same application on the same Operating System
- Use Windows 7 and Windows XP applications on Windows 10 and Windows 11 systems and thus simplify the migration from outdated operating systems to a modern OS
- Reduce IT support and related Help Desk costs
- Increase user mobility
- Stream applications
In detail, ThinApp captures the installation of one or more applications (including files and registry keys that are modified) in an ecosystem that looks like a single executable file.
The executable file is portable on other systems (of the same version or different) and we can control the level of interaction with the operating system on which we are going to run the application and with other applications in our system.
ThinApp allows various ways of isolation using a sandbox:
- FULL
- MERGED
- WRITE
During the creation of the virtualized package, we can choose only two of the previous options (MERGE and WRITECOPY) the third (FULL) we can activate by modifying an INI file post-capture of the installation
In the following diagrams, we find the three modes



The Sandbox is our box where changes to the ThinApp package that the end user performs during use can (depending on the isolation mode chosen) be saved.
The sandbox is:
- Customizable the path where it resides
- Editable in .ini file that generates application capture
- Can reside in the same directory as the ThinApp EXE
- Can be on a network share
- By default is %appdata%\thinstall\application
- Each user has his own sandbox
- Resetting application configurations is executable by deleting the sandbox
The distribution of a ThinApp is feasible in several ways:
- Using a network share and running application streaming
- Using it from a USB device
- Copying it to your computer
The use of the network share for the distribution of ThinApp packages allows an easy updating of the packages themselves.
























![Notepad
File Edit Format
[General]
netlnternet=
View
Help
ipø=192.168.247.54
diskMode=
ip1=192,168,246.54
defaultGateway=192.168.247.1
target=
ds=
routes
2.168.246.1,192.168.4.0/24 192.168.246.1,172.25.2.0/23 192.168.246.1,172.25.6
netmaskØ=255.255.255. or
netManagement etwor
net3ackendNetwork
• pØA110cationMode=STATICV4
name=
deploymentOption=twonic
forceNetmaskØ=255.255.255. or
forceNetmask1=255.255.255. or](https://vmvirtual.blog/wp-content/uploads/2022/05/notepad-file-edit-format-general-netlnternet.png)

![Notepad
File Edit Format View Help
l[Generate1]
net Internet—DPG - EXT•4Zjjj)
ipe=192.168.247.55
diskMode—thick
source—E : - unified - access - gateway- 22.03. 1955Ø 91_OVFI Ø. Ova
ip1=192,168,246.55
default-Gateway=192.168.247.1
target—vi : / /vcaØ7
ds=vsanDatastore
routes1=172.16.e.Ø/16 192.168.246.1,192.168.4.0/24 192.168.246.1,172.25.2.0/23 192.168.246.1,172
netmaskØ=255.255.255. and
netManagementUetwork
net8ackendNetwork=DPG - INT - C*IZ
ipeA110cationMode=STATICV4
name-VilJAGØ3-22Ø3
deploymentOption=twonic
forceNetmaskØ=255.255.255. and
forceNetmask1-255.255.255. and
ip1A110cationMode=STATICV4
net-maski=255,255,255. and
authenticationT imeout—3ØØØØe
fipsEnab1ed—fa1se
sys L ogType=UDP
uagName=viuage3
clockSkewT01erance=6Øe](https://vmvirtual.blog/wp-content/uploads/2022/05/notepad-file-edit-format-view-help-lgenerate1.png)

















