Skip to main content

VMware ThinApp Release Candidate (RC) is shipping!

VMware is pleased to announce the RC revision of ThinApp. This release includes Application Link and Application Sync, as well as many additional improvements to the user interface and the core virtualization engine. We believe that ThinApp represents technology that, when released in final form at General Availability (GA), will provide customers a fundamentally better way to package applications.

With ThinApp technology, IT innovators can prepare their company to better address key application challenges including operating system migrations (to Windows XP, Vista, and others) while reducing application conflicts, deployment costs, and empowering a mobile workforce. ThinApp creates portable applications that can be leveraged across a variety of operating systems (Windows NT, XP, Vista, 2000) and plug into a variety of deployment infrastructures (SMS, LANDesk, Citrix, BMC, and others).


Key Features and Enhancements

The following enhancements were added for RC (Build 3.396):

  • The default isolation mode was changed from WriteCopy to Merged.
  • Application Sync makes fewer web server round-trip queries after bandwidth optimizations were made.
  • User interface enhancements:
    • Added a screen to allow selection of the default file system isolation mode.
    • Removed advanced and less frequently used screens such as Application Sync.
  • To handle larger packages, VMware created a separate .dat data container when the estimated size of a data container is over 200MB. This resolves an issue in which Internet Explorer might not show icons for large executable files.
  • Added the package.ini option, VirtualComputerName. When enabled, this option provides an application with a fixed computer name. This setting is required for some configurations of SQL Server.
  • Added support for the SQL Server SQLWriter service.
  • ThinApp MSIs for package and build tools now install per-machine by default.
  • Added support for the following new file macros: %Temp%, %PrintHood%, %Internet Cache%, %Cookies%, %History%, %Program Files Common%, %Common Templates%, %Common Documents%, %Common AdminTools%, %AdminTools%, %Resources%, %Resources Localized%, %CDBurn Area%, %Profiles%. To prevent any backward compatibility issues, these macros are only available to applications captured using ThinApp 3.393 or higher. You can modify the CapturedUsingVersion parameter in your package.ini file for older captured packages to enable them to use newer macros.

The following new key features and enhancements were added for Beta 2 (Build 3.386):

  • Application Sync - This feature enables you to deploy ThinApp application updates. Application Sync automatically checks for and installs updates to your packaged applications. Updates might include changes such as a new version, service pack updates, or configuration changes in the package.ini file.
  • Application Link - Application Link enables you to establish a link between applications without having to encapsulate them into the same executable package. For example, you can establish a relationship between a deployed instance of Microsoft Office 2003 and a new Microsoft Office plug-in.
  • Support for VMware serial numbers.
  • Added logging support in the runtime environment to assist with troubleshooting.
Check out more here!
Labels:

Comments

Post a Comment

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus
Post a Comment
Read more

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op
Post a Comment
Read more