Vmware thinapp 4 release notes

Топ 100

Air Explorer Pro 2.6.0 Rus

FolderSizes 9.0.248 Rus Enterprise Edition Portable

Total Commander 7.04a

ABBYY FineReader 12.0.101.264

KMSAUTO NET 1.5.4 (2019) (РАБОЧИЙ АКТИВАТОР WINDOWS 10, 8.1, 8, 7, OFFICE)

iZotope RX 7 Advanced Audio Editor 7.00.218

BitTorrent Pro 7.9.9 Build 43296 Stable RePack

Корректор зрения (Полная версия)

Smith Micro Moho (Anime Studio) Pro 12.2 Build 21774

Adguard Премиум 6.0.224.1092

Autodesk 3D Studio Max Design 2010 DVD (x86/x64)

Apache OpenOffice 4.1.0 Stable (RUS)

Punto Switcher 3.4

Kaspersky Internet Security 2015

Djvu Reader

Качаем с µTorrent

AIMP 3.60

AllReader 2.5 (эмулятор книги)

IrfanView (просмотр фото)

CCleaner 5 (очистка мусора)

K-Lite Codec Pack 10.9.0 FULL

The KMPlayer 3.9.0.125

FolderSizes 7.5.24 Enterprise Edition + Rus

Microsoft Office 2007 Enterprise RUS

XFastLAN (cFosSpeed v9.05) — бесплатная версия

ESET Smart Security 7.0.302.32

WinRAR 4-5 (x86x64)

Nero Burning Rom (писалка)

Tipard Video Converter 6.1.32

Adobe Photoshop CS3 (Автоустановка)

What’s New

New: The 4.0.3 release adds support for specifying environment variables in the VirtualComputerName
parameter of the Package.ini file. The GetComputerName and GetComputerNameEx API functions
return the value of the VirtualComputerName parameter in a captured application.

The 4.0.3 release adds the ObjectTypes parameter
to the Package.ini file. You can use this parameter to specify a list of virtual COM objects that are visible
to other applications in the physical environment.

The 4.0.3 release changed the name of the VMware ThinApp User’s Manual to ThinApp User’s Guide.

ThinApp 4.0.3 is also a maintenance bug fix release. See .

What’s New

The ThinApp 4.7.3 release adds support for packaging and execution of virtualized applications on Windows 8 operating system. The Windows 8 support enables cross-platform capability for many applications regardless of the operating system of capture. The cross-platform capability is an important component of supporting the latest Microsoft Windows releases for both managed and unmanaged endpoints.

New Package.ini parameter — You can use the PreventDllInjection=1 parameter to prevent ThinApp runtime from loading a DLL when another external
application calls the SetWindowHook to set a global hook. This parameter should be used only when the hook is in conflict with a virtualized application. For example, if a virtualized application is unable to start because the other application NxPowerLite calls SetWindowsHook to set a global hook
oehook.dll, modifying the package.ini with PreventDllInjection entry allows the virtualized application to start.

For additional information about ThinApp 4.7.3, visit the following Web sites:

  • http://www.vmware.com/products/thinapp/
  • http://www.vmware.com/go/thinappsdk/

Known Issues

  • Virtual IE11 fails during shutdown after IE11 security patch KB 4056568 has been applied.

    Workaround: Add the following parameter in the General Purpose Parameters section in the Package.ini file and rebuild the package: ForceTerminateThread=1

  • LibreOffice does not shut down correctly on the 64-bit version of Windows 8.1. 

    Workaround: Add the following parameter in the General Purpose Parameters section in the Package.ini file and rebuild the package: ReleaseShutdownLocksEarly=1

  • Unable to insert Office objects in certain Microsoft Office applications such as Excel charts in Excel, Word document in Word, PowerPoint, and so on. 

    Workaround: None

  • Internet Explorer 11 does not start on Windows 8 and Windows 8.1.

    Workaround: None.

  • Internet Explorer 6.0 does not open some specific URLs.

    Workaround: Add the following parameters to Package.ini and rebuild the package: NotificationDLLs=T2embed.dll

  • If Protected View is enabled in Microsoft Excel 2013, Excel fails to open files from a network share.

    Workaround: Disable protected view from File > Options > Trust Center > Trust Center Settings > Protected View > Enable Protected View for files located in potentially unsafe locations.

  • Microsoft Office 2010 and Microsoft Office 2013 fail to start when deployed to a system with Microsoft Office natively installed.

    Workaround: For more information, see KB article .

  • Not able to start Google Chrome from a network share.

    Workaround: Add SetVirtualModuleFileNameInPeb=1 to Package.ini and rebuild the package.

  • Microsoft Visio 2010 help files are not displayed on 64-bit versions of Windows. 

    Workaround: Apply the workaround in KB article .  

  • 32-bit Internet Explorer 10 does not work on Windows 8.1; both 32-bit and 64-bit versions.

    Workaround: None.

  • If you attempt to start two instances of Microsoft Word 2013 or Microsoft Power Point 2013, these applications become unresponsive.

    Workaround: None.

  • If you replace the Outdir parameter in Package.ini with any of the following language characters, ThinApp fails to build packages on the 32-bit versions of Windows 7:

    • Simplified Chinese
    • Traditional Chinese
    • Japanese
    • Korean

    Workaround: None.

  • ThinApp does not support any 16-bit applications on Windows 8, Windows 8.1, and Windows 10 machines.

    Workaround: None

  • When you start AutoCAD on 64-bit versions of Windows 7, the following error message is displayed:PresentationFontCache.exe - Application Error

    Workaround: None.

  • Visual Studio 2010 displays the following error message:Invalid license data. Reinstall is required on launch.  For more information, see KB article .

    Workaround: None

  • Unable to open web pages by using Internet Explorer 8 or later on Windows 10.

    Workaround: For information about the workaround, see the knowledge base article .

  • When a website is marked as favorite in Internet Explorer, the website is not seen immediately in the Favorites Bar.

    Workaround: Create ##Attributes.ini file in the %Common Favorites% folder with the following content and rebuild the package: DirectoryIsolationMode=WriteCopy

  • When 64-bit version of Microsoft PowerPoint 2010 or Microsoft Word 2010 on Windows 10 is started, a «Fatal Application Exit» error occurs.

    Workaround: Add the ChildProcessEnvironmentException=msiexec.exe in Package.ini and build the project.

  • A COMDLG32.dll error appears when applications are run from a network share.

    Workaround: Add ProcessExternalNameBehavior=Original and SetVirtualModuleFileNameInPeb=1 to the General Parameters section of the Package.ini and rebuild the package.

  • Microsoft Visio 2010 fails to start when deployed to Windows 10 1803

    Workaround: None

  • ThinApp cannot change registry key names on 32-bit versions of Windows.

    Workaround: None

What’s New

The following features have been added for this release:

  • The thinreg.exe utility has been enhanced, facilitating file type association. It also includes support for DDE, extra verbs, and MIME type registration.
  • Enhanced support for double-byte applications and double-byte locales.
  • Enhanced support for 16-bit MSDOS programs.
  • Support for control panel extensions. Some applications, such as QuickTime or the mail applet for Microsoft Outlook 2007, have control panel extensions that you can now see in a ThinApp environment.
  • Ability to register files other than .exe files. For example, if you install an application that installed a README file or has another link to documentation, you can access those files.
  • Protocol registration. If an application invokes SMTP or HTTP, ThinApp starts any virtual applications that can handle the tasks. If ThinApp cannot locate virtual applications, ThinApp invokes native applications to handle the tasks.
  • ThinApp includes the RequiredAppLinks parameter in the Package.ini file. Previously, the user had to manually add this parameter.
  • ThinApp makes the MSI build template accessible to users to customize the MSI database.
  • User documentation has been restructured to start with basic functionality targeted at the novice user, building towards advanced functionality regarding deployment and customizations.
  • Log Monitor now supports the ability to pause and resume trace file capture.
  • Application link now supports multi-level links, such that application A links to application B, which links to application C, and so on.
  • Special entry points cmd, regedit and iexplore are marked with an asterisk (*) to denote these are not virtual applications. Rather, they load respective native EXEs in virtual environment.
  • Isolation mode can now be specified at the root of registry (for example, for HKCU, HKLM).
  • Stub executables changed to improve security and interaction with roaming profiles and system-installed applications.
  • Support for creating MSI distribution larger than 2GB (requires separate CAB file to be distributed).
  • Support for creation of compressed trace files.
  • Support for running ThinApp application on GoGlobal platform.
  • Support packaging application wrapped with the «Shrinker» packer.

New Parameters in thinreg.exe

New parameters have been added to the thinreg utility to provide you with additional options when searching for directories and files, or specifying excludes.

  • Setting Recursive Paths to Search Multiple Levels of Directories

    The thinreg utility evaluates all directories and files that it detects and registers the EXE files that match the search criteria.

    You can use wildcards to set recursive paths to search all levels of directories. In the following example, thinreg searches four levels of directory for applications. The thinreg utility registers all applications (EXE files) that it detects in the three-level directory structure. Wildcards (*) are used to specify that all directories at a specific level are to be searched for all EXE files.Example: thinreg /a c:\thinapp\*\*\xyz*\*.exe

    You can also use wildcards to limit a search to specific directories and files. In the following example, thinreg searches for all directory and file names that begin with xyz at the second level, and registers the EXE files that have names beginning with xyz. Example: thinreg c:\thinapp\*\xyz*\*

  • Excluding Directories from a Search and Excluding EXE Files from Registration

    You can use the /e or /exclude command to prevent thinreg from searching specified directories, or from registering specified EXE files.

    • You must use one /e command for each directory or file that you want to exclude.
    • Each exclude must be separated from the next exclude by a space.
    • You can use wildcards.
    • You cannot specify file paths.

    The following example shows three exclude commands (note the spacing).Example: thinreg /e abc /exclude def /e hi*

  • Specifying a Text File of thinreg Commands

    You can use /f <full path name> <filename> to specify a text file of commands that thinreg processes when registering EXE files. This is useful when you have long or numerous commands.

    • Do not specify thinreg at the beginning of the command.
    • You can use hard line breaks (Enter) in the text editor.

    Example: /f c:\xyz\file.txt

Known Issues

The following known issues affect this release:

  • New: The ThinApp User’s Guide states that ThinApp does not support nested Active Directory groups.
    Active Directory Domain Services define security groups and distribution groups. ThinApp can only support nested security groups.
  • ThinApp installation errors might occur with system login names that contain Japanese characters.
  • Adobe Acrobat 8 Professional cannot create a PDF file from a Microsoft Word or Microsoft Excel document.
  • The Application Sync utility fails when the AppSyncURL parameter in the Package.ini file contains Japanese characters.
    To prevent this failure, use ASCII characters in the AppSyncURL parameter.
  • Microsoft Word 2003 stops responding when you open and close the Microsoft Equation Editor.
    The Equation Editor feature creates a COM object. When you close the Equation Editor, the Winword.exe utility tries
    to free the object and causes the Equation Editor to fail.
    To prevent this failure, deselect the Equation Editor option during the Microsoft Office 2003 installation.
  • Internet Explorer 6 and Internet Explorer 7 do not work on Windows Vista.
  • Windows and Google Search do not work with a captured Microsoft Outlook application.
  • Using Microsoft Office 2003 Excel files in Office 2007 compatibility mode causes an error.
  • For backward compatibility reasons, Thinstall appears in the user profile and as the folder in which the sandbox is created.
  • Packaging applications on hard drives with limited space can generate errors during the packaging process.

What’s New

The ThinApp 4.6.1 release adds the following features to improve usability, performance, and updates:

  • Improved support for Microsoft Office 2010 applications.
  • Known issues related to Internet Explorer 7 and Internet Explorer 8 have been addressed.
  • New options have been added to the package.ini file.
  • S x S COM is now supported.
  • More than 160 known issues have been resolved, resulting in improved application support.

For additional information about ThinApp 4.6.1, visit the following Web sites:

  • http://www.vmware.com/products/thinapp/
  • http://www.vmware.com/go/thinappsdk/
  • http://blogs.vmware.com/thinapp/2011/02/vmware-thinapp-461-whats-new.html

What’s New

The ThinApp 4.7 release provides ThinApp integration with Horizon Application Manager, which includes the following features:

  • The ThinApp Setup Capture wizard includes an option to manage with Horizon Application Manager. When the checkbox is selected, ThinApp checks if the Horizon agent is installed natively on the client and is running. If the Horizon agent is found, the ThinApp package reports to the Horizon agent so that it can be controlled by Horizon Application Manager.
  • Horizon Application Manager entitlement allows the delivery of ThinApp packaged applications to specified users and groups. The Horizon agent authorizes a ThinApp package to open, based on entitlements.
  • ThinApp packages are registered by Horizon Application Manager and delivered to end points.
  • The administrator can track usage of ThinApp packages by using Horizon Application Manager monitoring and reporting.
  • The administrator can configure an Organizational URL for end points missing the Horizon agent.

For additional information about ThinApp 4.7, visit the following Web sites:

  • http://www.vmware.com/products/thinapp/
  • http://www.vmware.com/go/thinappsdk/
  • http://blogs.vmware.com/thinapp/2011/11/vmware-thinapp-47-whats-new.html
  • http://blogs.vmware.com/thinapp
  • http://pubs.vmware.com/thinapp4/help/

What’s New

VMware ThinApp 5.1 is the latest version of ThinApp. This release has the following enhancements.

ThinApp Package Management

In earlier versions of ThinApp, to change some specific Package.ini parameters, you had to first
make those changes in the configuration file, save the file, and rebuild the package. Using the new ThinApp package management feature, you can dynamically reconfigure the attributes of deployed
ThinApp packages at runtime. ThinApp Package management helps IT administrators manage
ThinApp packages and define group policy for each package. Each package to be managed must have an associated group policy defined using its inventory
name.

When you install ThinApp 5.1, a new folder named Policy is created in the installation directory. This
folder contains tools and templates for managing ThinApp packages and contains the following files:

  • AppPolicy.exe
  • README.TXT
  • ThinAppBase.adml
  • ThinAppBase.admx
  • ThinAppGeneric.adml
  • ThinAppGeneric.admx

ThinApp selects the policy precedence when you rebuild a package and deploy it. If a package is managed by a group policy, ThinApp gives precedence to the policy over its Package.ini configuration.

Group Policy Administrative Templates

(ADMX/ADML)

  • Windows Server 2008
  • Windows Server 2008 R2
  • Windows Server 2012

Administrative Template files contain markup language that is used to describe a registry-based Group Policy. The administrative files are divided into language-neutral (.admx files) and language-specific resources (.adml files), available to all Group Policy administrators. These factors allow Group Policy tools to adjust the user interface according to the administrator’s configured language.

Reconfiguring Attributes of Deployed ThinApp Packages

  • AppSync
  • AppLink
  • Entry-Point Shortcuts

Note: To know how to reconfigure these package attributes, see the ThinApp 5.1 User’s Guide.

ThinDirect

In ThinApp 5.1, the following enhancements have been made to the ThinDirect plug-in:

  • Support for the update of ThinDirect settings at specified time intervals

In ThinApp 5.1, the ThinDirect functionality has been enhanced to periodically poll for the ThinDirect setting changes. Since, the ThinDirect settings are now detected dynamically, the user need not restart the browser to view the updated changes.

Support for dynamic changes to ThinDirect via ADM

In ThinApp 5.1, you can use ThinDirect.ADM file to manage the ThinDirect enabled firefox.

Support for overriding the ThinDirect settings through GPO

In ThinApp installation directory, locate the ThinDirect.admx and ThinDirect.adml files. Use these files to manage the settings for ThinDirect feature by defining a group policy object. If the ThinDirect feature is defined through the GPO, these settings would override the text file (ThinDirect.txt) based redirection.

Support for redirection between two virtual browsers

ThinApp 5.1 supports redirection between two virtual browsers.

Support for ThinDirect in Mozilla Firefox

In ThinApp 5.1, ThinDirect has been enhanced to work with Mozilla Firefox version 22 and later. In earlier versions of ThinApp, ThinDirect was limited to Internet Explorer.

Extracting an existing ThinApp project to a system

snapshot.exesnapshot64.exePre-requisites

  • Verify that the architecture and type of the captured operating system is the same as that of the deployed operating system.
  • Perform the extraction of an existing ThinApp project on a clean capture and build machine.
  • Ensure that the user profile in the existing virtual project is the same as that of the capture and build machine.
  • snapshot.exe is used to extract an existing ThinApp project to a capture and build 32-bit operating system
  • snapshot64.exe is used to extract an existing ThinApp project to a capture and build 64-bit operating system

NoteThinApp 5.1 User’s Guide

MAPI Support

ThinApp 5.1 supports the Messaging Application Programming Interface (MAPI) on the following Microsoft Windows platforms:

  • Windows 7
  • Windows 8 32-bit
  • Windows 8 64-bit
  • Windows 8.1 32-bit
  • Windows 8.1 64-bit

Support for Windows 8.1

ThinApp 5.1 works on the Windows 8.1 August update (Update 2).

For additional information about ThinApp 5.1, visit the following Web site:

http://www.vmware.com/products/thinapp/

Resolved Issues

The ThinApp 4.6.2 release resolves these issues:

  • When ThinDirect is used to redirect a URL from Internet Explorer 8 to a virtualized Internet Explorer 6 URL, the Internet Explorer 6 window might be hidden behind the Internet Explorer 8 window. In addition, the redirection message might appear in a second Internet Explorer 8 tab, adjacent to the original Internet Explorer 8 tab.
  • When you use the Application Link utility, you must build the base package and linked packages using the
    same version of ThinApp.
    To upgrade older packages to include the latest version of the ThinApp runtime, use the relink.exe utility.
  • The Application Sync utility fails when the AppSyncURL parameter in the Package.ini file contains Japanese characters.
    To prevent this failure, use ASCII characters in the AppSyncURL parameter.
  • When you use the Application Sync utility to update a virtual browser that has ThinDirect implemented, changes that have been made to the ThinDirect.txt file are not detected.
  • To ensure that non-English versions of virtual applications that are captured by ThinApp display the correct language user interface, during the ThinApp capture you must open the natively installed version on the capture machine before you start the post scan operation.
  • When use of a proxy is enabled in virtual Microsoft Excel 2007 running on Windows XP SP2 32-bit, you cannot perform Web queries or import data.
  • When attempting to search for something using the Research pane in virtual Microsoft Excel 2003 running on Windows Vista and Windows 7 unexpected behavior is encountered. Windows Installer opens and the following error message appears Error 1719: The Windows Installer Service Could not be accessed. This can occur if the Installer is not correctly installed. Contact your support personnel for assistance. Click OK each of the three times that the error message is displayed. The Research pane shows the result for the searched keyword.
  • When running ThinApp Converter on Workstation virtual machines, ensure that the Workstation virtual machines are using bridged networking.
  • When running more than one instance of ThinApp Converter, ensure that the INI files are configured so that the Converters do not use the same virtual machines.
  • For optimal performance, use Windows 2003 or Windows 2008 as a file server for network share. The file server requires sufficient system resources to handle a high volume of file operations. Do not use the host that runs the ThinAppConverter.exe as the file server for the network share.
  • RTF files in a ThinApp project cannot be opened by a natively installed Microsoft Office 2010.
  • The case in which virtualized Microsoft Windows Live Messenger returns a failed to create process default activation context message when attempting startup has been resolved.
  • Virtual Internet Explorer 6 no longer generates new browser instances on Windows Vista x64 operating systems.

Known Issues

The following are known issues for this release:

  • When you use Application Sync to upgrade Adobe Reader 6 to Adobe Reader 7, it might seem that the application did not upgrade correctly if the previous version of the virtual application is running. Workaround: After you have upgraded the application using Application Sync, close the Adobe Reader 6 virtual application that you have running and then relaunch it. It should open the upgraded version.
  • When you double-click on a document, some applications (like Microsoft Excel) will open the document in an already-running copy of the application. When using a virtual package and ThinReg, documents will always be opened in a new copy of the application.
  • You cannot insert a Powerpoint object from a file into a Microsoft Excel document.
  • When you try to launch a Firefox 2.0.3 virtual application, Application Sync does not work properly if Firefox 2.0.3 is natively installed and a webpage is open on the client machine.
  • Internet Explorer 6 does not run on Windows Vista.
  • Windows Office XP activation is not supported on Windows 2003 and XP.
  • Thinreg currently does not support any customization of the file-type association commands when registering packages. For example, if an application registers a file type association as «viewer.exe /f %1,» it will be registered as «viewer.exe %1.»
  • Application Link will not recursively import dependencies. It only imports dependencies from those directly specified in the RequiredAppLinks and OptionalAppLinks fields of the package.ini file.
  • In-place updates do not work with Application Link packages. For example, you cannot place a .1, .2, etc., in the same directory as an Application Link package and have that version override the version request by the application.
  • If Application Sync is used to update an application that is being imported by another application through Application Link, the import operation will use the original application and not the updated version.
  • Single sign-on service does not work on captured Lotus Notes applications.
  • Child processes are created with a random path stub exe.
  • Windows Live Messenger opens up redundant processes when Outlook is launched.
  • After the installer is updated to a different version of the Adobe Acrobat Reader, the icon name still displays an older version of the application.
  • When you run Microsoft Outlook 2003 with a Word 2007 package, the File > Send E-mail option fails.
  • Adobe Acrobat 8 Professional cannot create a PDF file from a Word or Excel document.
Оцените статью
Рейтинг автора
5
Материал подготовил
Андрей Измаилов
Наш эксперт
Написано статей
116
Добавить комментарий