#Vmware thinapp vs rdp manual
#Vmware thinapp vs rdp portable
#Vmware thinapp vs rdp windows 7

You must design your capture environment to allow flexibility. If you are capturing an add-on to Microsoft Office, then Microsoft Office has to be locally installed in your capturing environment or the add-on installer would fail to run.

#Vmware thinapp vs rdp portable

This will guarantee that all your packages include as many dependencies as possible, making them portable and robust. In general, you should use an environment that is as clean as possible. VMware Workstation, VMware View, Citrix XenDesktop, Microsoft Med-V, and many others offer you the capability to access a virtualized 32-bit operating system on your 64-bit machine.

Your only workaround for those scenarios is whole machine virtualization technologies. 64-bit environments cannot handle 16-bit code. If the application contains 16-bit code, then it’s impossible to make it run on a 64-bit environment. Some applications cannot run on a 64-bit OS, but most applications offer some kind of work around. It just requires a little extra packaging effort. Creating a package supporting many different OS and both 32-bit and 64-bit versions is the hardest. Creating a package supporting multiple operating systems, all being 32-bit systems is a little harder.

#Vmware thinapp vs rdp windows 7

Having these files captured from and installation made on Windows XP rarely conflicts the running of the application on Windows 7 and helps you achieve multiple OS support.Ĭreating a package for one single operating system is of course the easiest task. Installing on a Windows XP with no service pack would force those required files to be installed locally, and therefore captured by the capturing process. They will investigate the targeting platform and if it discovers a Windows 7 operating system, it knows that some files are already present in the same or newer version than required. From ThinApp’s point of view, Windows XP and Windows Server 2003 are of the same generation and Windows 7 and Windows 2008 R2 are of the same generation. Most of the time this would be Windows XP. If you want to support multiple operating systems you should choose the lowest platform you need to support. The package might not be ready for production but it will run on a clean machine not having the application locally installed. This means you have not tweaked the project in any way. Normally you can achieve an out of the box success rate of 60 - 80 percent. The easiest method to package an application is to capture it on the platform where it will run. Most other packaging formats require you to maintain one package per environment. The possibility of running the same package on your Windows XP clients, Windows 7 machines, and your XenApp servers is unique. This is a great feature and really helps in lowering the overall administration of maintaining an application. ThinApp packages are able to support multiple operating systems with one single package. So the general rule is to make sure your environment allows ThinApp to capture all required dependencies of the application. ThinApp will recognize this, investigate which files are related to a component, and mark them as needed to be included in the package. When an installer discovers components already installed, it can register itself to the same components. Snapshotting can be made a little more independent of the capture environment.

#Vmware thinapp vs rdp manual

The other method, monitoring the installer, will be more independent of the capturing environment but will not support all the installer formats and will not support manual tweaking during capture. This means your package would require Java installed or it will fail to run. Since it was already there when you ran the pre-install snapshot, it will not be a part of the captured differences. If your machine already contains the Java Runtime Environment ( JRE ) and the application you are capturing requires Java, then you will not be able to capture the JRE. But, your starting point will decide the outcome. You can copy files and create registry keys manually and it will all be captured. The alternative would be to try to hook into the installer itself. Many packaging products use snapshotting as a method of capturing changes. This should be all the information you need in order to run the application. The differences between the two snapshots represent the changes made by the installer. After modifying the environment, you create another snapshot, the Post-Installation Snapshot.

This means you create a snapshot ( Pre-Installation Snapshot) of the current state of the machine.

ThinApp uses a method of snapshotting when capturing an application installation. The environment you use to capture an installation is of great importance. You cannot write a book about a packaging format without discussing the environment used to create the packages. (For more resources related to this topic, see here.) The capture and build environment