Select the product you need help with

Important changes in the App-V v5 Sequencer

Article ID: 2777777 - View products that this article applies to.

Summary

This article contains the following information:

- Important changes in the Microsoft Application Virtualization (App-V) v5 Sequencer
- Unsupported scenarios with the App-V v5 Sequencer
- Known issues with the App-V v5 Sequencer at RTM

Back to the top | Give Feedback

More information

Important changes in the App-V v5 Sequencer:

When an application installer requests a restart of the Sequencer system an actual restart will occur. After the system restart the Sequencer will launch itself into monitoring mode. Complete any remaining installer tasks and click next.
In the “Package Name” dialog field “Primary Virtual Application Directory (required)”, enter a path to the system drive where the virtual application will be installed.
To specify full package download, in the Streaming dialog select “Force application(s) to be fully downloaded before launching (recommended for low/WAN networks)."
If no programs were launched during the optimization phase, the primary feature block (FB1) will be empty. Applications with empty feature blocks will be streamed on-demand until it can be launched and then background streamed.
For information on using App-V v5 with Microsoft Office see http://support.microsoft.com/kb/2772509
(http://support.microsoft.com/kb/2772509)

Unsupported scenarios with the App-V v5 Sequencer:

Creating an Office 2013 package using the App-V v5 Sequencer
Opening an Office 2013 .appv package with the App-V v5 Sequencer
Creating an Office 2010 package using the App-V v5 Sequencer
Converting existing App-V v4.6 Office 2010 packages to App-V v5
Entering package names that are longer than 1024 characters
Saving an App-V v5 package to a path longer than 256 characters
Installing virtual applications to a drive other than %SystemDrive%
The use of “piping” between Sequencer Powershell commands
Forcing shortcuts to a profile other than current user (Public, All Users)

Known issues with the App-V v5 Sequencer at RTM:

Customizatons made to File Type Association (FTA) properties using the App-V v5 Sequencer might not be saved properly when the package is subsequently updated. Workaround: After package update, verify and if necessary re-enter any customized FTAs.
Existing App-V v5 Packages lose description text when opened for update by the v5 Sequencer. Workaround: After package update re-enter the packge descriptiion if necessary. The package description can be copied from the App-V v5 Server console.
When an AutoCad 2012 package is devirtualized, the FlexNet Licensing Service may not be installed. The workaround for AutoCad 2012 is to restart the Sequencer system & launch the Sequencer after devirtualization.

Back to the top | Give Feedback

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use

(http://go.microsoft.com/fwlink/?LinkId=151500)

for other considerations.

Back to the top | Give Feedback