A couple of weeks ago I went to a three-hour-deep dive on VMware ThinApp. ThinApp is a really cool technology that allows users to virtualize applications and makes applications more portable. This portability makes it so the application does not rely on the underlying operating system. For example, if you need to run Internet Explorer 6 for some legacy application, it's possible to do this using ThinApp and it will be an isolated (more secure) environment and can be run on Windows 7. Many applications can be run using ThinApp and it's especially useful if you have VMware View or the new VMware Horizon, but ThinApp can be used outside those solutions as well.
VMware has recently come out with ThinApp Factory, which is a virtual appliance you can deploy on vSphere or VMware Workstation that simplifies the implementation of ThinApps. It will automate the packaging of applications, while also centralizing administration, and provide recipes to help administrators package even more applications. VMware has also teamed up with a company called Ninite that will be providing recipes in a feed. In this post I'll take you through the initial install of ThinApp Factory and an example of how to use it.
- Download ThinApp Factory from http://labs.vmware.com/flings/thinapp-factory
- Extract the zip file into a folder
- On your vSphere Client, go to File>>Deploy OVF Template and browse to the AppFactory.ovf file
- Click Next through the wizard (while choosing the appropriate settings for your environment)
- Fill in the entire first section and all of the required fields of the network settings under the Properties tab at the end of the wizard (I recommend giving it a static IP so that you can easily navigate to it, and you must use a standard switch instead of a distributed switch)
- Access the management portal by browsing to the IP you assigned it. I noticed that even though I had a default gateway, I still had to be on the same subnet.
- Accept the EULA
- Right now there is no password configured, so you can just login with the username "admin"
There is a flowchart that shows you how to get started creating your builds, a system data chart, and an alert window that can be pulled up manually. Now you must create a workpool, which is a pool of Windows machines that you've configured that will be managed by the ThinApp Factory. You need at least one workpool to create ThinApp packages. The role of the workpool will become clearer later.
- Click on Settings in the upper right corner and make sure the workpool tab is selected
- Fill in the Name and select to use either an existing VM or an .iso for creating the templates that will be used as "clean slates" for creating ThinApps
- Enter the necessary information (see Figure B for example using .iso) and click Save. Make sure you pick the proper install Type (ex: Windows 7 Enterprise). This may take several minutes, but if it completes successfully the status bar will be all green.
- Go back to the dashboard and select the Add Application Source icon from the workflow picture
- Browse for the installer file (ex: Java) and then fill in the name and version, select a datastore, and click Save
- Go back to the Dashboard and click on Select Application. The installer you just added should now be listed there
- Put a checkmark by it and select Capture
- Here you can select which workpool you'd like it to use, which ThinApp version and the project location.
- Click on Auto Capture (there is a Manual Capture option as well, if you'd like to make changes). After clicking Auto Capture, it will show you that the task is running as shown in Figure C. You will also see a VM appear in your vSphere client as it is being created from the workpool. This will automatically be deleted when the task is complete.
- When done, you can click on the Projects tab to see your finished ThinApp. From here you can publish your App to the ThinApp store (found at http://ThinAppFactoryIPAddress/store) where you can select the applications they want and then click on Get Applications.
Right now ThinApp Factory is just a fling, which means it's not officially supported by VMware. However, I highly suggest trying it out if you're looking for a good way to centralize and virtualize application deployment.
Lauren Malhoit is a VMware vExpert '12, '13 and a member of the EMC Elect. She works as a Solutions Implementation Engineer at Network Storage Inc., where her main concentrations are on VMware, EMC, and Cisco. She has a degree in Computational Mathematics from Hillsdale College and has worked on several certifications, including CCNP, MCSE: Security, and VCP 5.