Microsoft App-V 4.6 Packaging
Microsoft Application Virtualization (App-V) can make applications available tend user computers without having tinstall the applications directly on those computers. This is made possible through a process known as sequencing the application , which enables each application trun in its own self-contained virtual environment on the client computer. The sequenced applications are isolated from each other. This eliminates application conflicts, but the applications can still interact with the client computer.
The App-V client is the feature that lets the end user interact with the applications after they have been published tthe computer. The client manages the virtual environment in which the virtualized applications run on each computer. After the client has been installed on a computer, the applications must be made available tthe computer through a process known as publishing , which enables the end user trun the virtual applications. The publishing process copies the virtual application icons and shortcuts tthe computer—typically on the Windows desktop or on the Start menu—and alscopies the package definition and file type association information tthe computer. Publishing alsmakes the application package content available tthe end user’s computer.
The virtual application package content can be copied ontone or more Application Virtualization servers sthat it can be streamed down tthe clients on demand and cached locally. File servers and Web servers can alsbe used as streaming servers, or the content can be copied directly tthe end user’s computer—for example, if you are using an electronic software distribution system, such as Microsoft System Center Configuration Manager 2007. In a multi-server implementation, maintaining the package content and keeping it up tdate on all the streaming servers requires a comprehensive package management solution. Depending on the size of your organization, you might need thave many virtual applications available tend users located all over the world. Managing the packages tensure that the appropriate applications are available tall users where and when they need access tthem is therefore an important requirement.
Microsoft Application Virtualization (App-V) 4.6 provides the following enhancements and new features for the App-V Desktop Client, Client for Remote Desktop Services and App-V Sequencer:
- Support for 64-bit applications—provides the ability tsequence and run 32-bit and 64-bit applications on 64-bit versions of Windows 7, Windows Vista, Windows XP, Windows Server 2008, Windows Server 2008 R2, Windows Server 2003 and Windows Server 2003 R2. For more information about supported operating systems, see Application Virtualization Deployment Requirements.
- Support for Windows 7 and Windows Server 2008 R2—provides support for Windows 7 and Windows Server 2008 R2, including support for Windows 7 features such as the taskbar, Jump Lists, AppLocker, BranchCache, and BitLocker TG.
- Expands globalization and localization—provides support for 12 additional languages.
- Support for Virtual Desktop Infrastructure (VDI) systems—provides the capability for the read-only shared cache thelp optimize server disk storage in VDI scenarios.
- Improved sequencing experience—provides improvements tthe sequencing wizard and support for sequencing 32-bit and 64-bit applications.
Application Virtualization (App-V) 4.6 SP1 provides the following enhancements and new features:
- Improved App-V sequencer – the App-V 4.6 SP1 sequencer has been updated thelp improve the sequencing process. The enhancements include a more predictable packaging experience, and help at each step of the sequencing process. Click any of the following links for more information about the new version of the App-V sequencer.
- App-V Package Accelerators can be used tautomatically sequence large, complex applications. Additionally, when you apply an App-V Package Accelerator, you are not always required tmanually install an application tcreate the virtual application package. For more information about App-V package accelerators, see About App-V Package Accelerators (App-V 4.6 SP1).
- Enhanced support for sequencing different types of applications. For more information about the different types of applications, see How tDetermine Which Type of Application tSequence (App-V 4.6 SP1).
- Enhanced support for using App-V project templates. For more information about App-V project templates, see How tCreate an App-V Project Template (App-V 4.6 SP1).
- Step-by-step help during sequencing. For an example of the new step-by-step see Type of Application Page (Learn More).
- Enhanced reporting thelp identify sequencing issues. For an example of the new reporting, see Files Excluded Page Dialog Box (App-V 4.6 SP1).
- Support for using a read-only cache on RDS – App-V 4.6 SP1 now supports using a shared, read-only cache in both VDI and RDS environments. For more information about sharing a read-only cache on RDS, see How to Configure a Read-only Cache on the App-V Client (RDS).
- Support for sequencing the Microsoft .NET Framework 4 – App-V 4.6 SP1 now supports sequencing the Microsoft .NET Framework 4.
- Customer Feedback and Hotfix Rollup – App-V 4.6 SP1 also includes a rollup up of fixes to address issues found since the App-V 4.6 release.
Microsoft Application Virtualization (App-V) 4.6 SP2 provides several enhancements and new features, which are described in this topic.
Support for Windows 8 and Windows Server 2012
App-V 4.6 SP2 adds support for Windows 8 and Windows Server 2012 Remote Desktop Services.
Support for coexistence with App-V 5.0 client
App-V 4.6 SP2 provides support for coexistence with the Microsoft Application Virtualization 5.0 client. Review the App-V 5.0 documentation for instructions on how to configure the App-V 5.0 client for coexistence with the App-V 4.6 SP2 client. For more information about App-V 5.0, see Application Virtualization 5 on TechNet.
New Sequencer command-line parameter
When you create a Package Accelerator (PA) through the Sequencer GUI, you can select an RTF or TXT file that provides packaging and deployment guidance to the administrators who will apply the Package Accelerator. This functionality is now available using the Sequencer CLI.
Specify a path to an RTF or TXT file that provides packaging and deployment guidance when creating a Package Accelerator.
Microsoft Application Error Reporting no longer needs to be installed
When you are installing the App-V 4.6 SP2 client by using setup.msi, you no longer need to install Microsoft Application Error Reporting (dw20shared.msi). App-V 4.6 SP2 now uses Microsoft Error Reporting. For more information, see How to Install the App-V Client by Using Setup.msi.
Customer feedback and hotfix rollup
App-V 4.6 SP2 includes a rollup of fixes to address issues found since the App-V 4.6 SP1 release. App-V 4.6 SP2 contains the latest fixes up to and including Microsoft Application Virtualization 4.6 SP1 Hotfix 6.