To optimize your use of the ThinApp Application Sync utility, note these considerations.

Using the Application Sync Utility in a Managed or Unmanaged Environment

If you use virtual applications that update automatically in a managed computer environment, do not use the Application Sync utility because it might clash with other update processes.

If an automatic update feature updates an application, the update exists in the sandbox. If the Application Sync utility attempts to update the application after an automatic application update, the version update stored in the sandbox takes precedence over the files contained in the Application Sync version. The order of precedence for updating files is the files in the sandbox, then the virtual operating system, and finally the physical machine.

If you have an unmanaged environment that does not update applications automatically, use the Application Sync utility to update applications.

Fixing an Incorrect Update Using the Application Sync Utility

If you have multiple Application Sync download updates, such as multiple Microsoft Office updates, and a specific update causes an adverse effect or needs to be withdrawn, you can address the problem by placing the correct update on the server that ThinApp accesses.

The update is applied the next time the application is started on a client machine.

How the Application Sync Utility Affects Entry Point Executables

The Application Sync utility updates entry point executable files. For example, assume you deploy a Microsoft Office 2007 package that does not include Microsoft PowerPoint. A Microsoft Office PowerPoint 2007.exe entry point does not exist for the original package. If you rebuild the Microsoft Office 2007 package to include Microsoft PowerPoint, and you use the Application Sync utility to update client machines, end users can access an entry point executable file for Microsoft PowerPoint.

Updating thinreg.exe Registrations Using the Application Sync Utility

If you register virtual applications on the system using thinreg.exe and update those applications using the Application Sync utility, you can update registrations by placing a copy of thinreg.exe, located in C:\Program Files\VMware\VMware ThinApp, alongside the updated package on the server.

Maintaining the Primary Data Container Name When Using the Application Sync Utility

The Application Sync utility requires that the name of the primary data container, which is the file that stores virtual files and registry information, is the same for the old and new versions of an application. For example, you cannot have an old version with Microsoft Office Excel 2003.exe as the primary data container name and the new version with Microsoft Office 2007.dat as the primary data container name. To verify the name of the primary data container, check the ReadOnlyData parameter in the Package.ini file.

Managing the Application Sync Process When Applications Create Child Processes

When a captured application creates child processes, ThinApp cannot complete the Application Sync process.

For example, you might create Microsoft Office 2003 and Microsoft Office 2007 packages, modify the AppSyncURL parameter in the Package.ini file for both packages, and copy the Microsoft Office 2007 package to a Web server and the Microsoft Office 2003 package to a client machine.

If you start the Microsoft Office 2003 package before the expiration time set in the AppSyncExpirePeriod parameter in the Package.ini file, ThinApp can download the update in the background as you work with the application, but cannot show the updated version the next time that you start the application.

If you start the application after the package expires, ThinApp is unable to download the update in the foreground and restart the application when the download is ready.

Microsoft Office 2003 and Microsoft Office 2007 are examples of applications that create child processes. ThinApp cannot complete Application Sync updates until all child processes stop. You can perform one of the following tasks to resolve the issue:

  • Log out of the machine to stop the child processes, then and log in again.

  • Create a script to end the child processes.

    For example, you can create a script to end the ctfmon.exe and mdm.exe child processes associated with Microsoft Office 2003 and Microsoft Office 2007.

  • Prevent the startup of child processes, such as the ctfmon.exe process associated with Microsoft Office and Internet Explorer applications. See #GUID-65CD168D-939C-4AD1-A083-A86BD4974C9A.