The final output files are isolated one from each other and from the operating system, so any installation conflicts (if they exist) are eliminated. The result can also be compressed, which decreases the file size and therefore makes it easier to share and use on multiple devices. Once the virtualized bundle is finished you can export it as an EXE or MSI and run it on multiple versions of Microsoft Windows without repackaging it. This operation should be done with a clean operating system, in order to avoid compatibility problems. Configuration of the project settings is also available.īefore starting the virtualization procedure VMware ThinApp scans your hard-drive and file registry to create a baseline of your system. Using this program you can create an initial baseline of your system, deploy or package software, check for specific differences. I noticed the "vmw.lic" file in "C:\Program Files (x86)\VMware\VMware ThinApp" but copying that over from a 1709 to the 1803 machine does not help either.VMware ThinApp is designed to deliver virtualized instances of applications in order to help IT administrators with software migration to a newer operating system and eliminate specific conflicts and compatibility issues. If I go back to Windthe same license key I enter during setup does not cause me to get prompted to enter the key again, it just works(tm). The error message I get is "The license key entered does not match any licenses.", the same message I'd get if I banged my head on the keyboard enough times to get to the 25 characters it expects. The same happens with 5.2.2 on the same machine, Windows 10 1803. I installed the 5.2.3 ThinApp tool, entered the serial during setup and when I started the capture program, right when the program starts, it will ask me for a license again. Everything seems to work just fine.Įxcept when I wanted to build my ThinApps.
I didn't want to wait for the release of the 7.5 Horizon View Agent, so I went ahead with testing Windwith the 7.4 version.
0 kommentar(er)
