How to Update an Existing Virtual Application Package
Updated: November 1, 2013
Applies To: System Center 2012 - Virtual Machine Manager, System Center 2012 R2 Virtual Machine Manager, System Center 2012 SP1 - Virtual Machine Manager
You must have the Server App-V Sequencer installed to change a server virtual application package. For more information about how to install the App-V Sequencer see How to Install the Server Application Virtualization Sequencer.
To update an application in an existing server virtual application package
To start the Server App-V Sequencer, on the computer that is running the Server App-V Sequencer, select Start / All Programs / Microsoft Application Virtualization / Microsoft Application Virtualization Sequencer.
In the App-V Sequencer, click Modify an Existing Virtual Application Package and then click Next.
On the Select Task page, click Update Existing Package. Click Next.
On the Select Package page, click Browse and locate the virtual application package (.sprj file) that contains the virtual package that you want to update. Click Next.
On the Prepare Computer page, review the issues that could cause the package update to fail, or for the package update to contain unnecessary data. It is strongly recommend that you resolve all potential problems before you continue. After you have fixed the conflicts, to update the information displayed, click Refresh. After you have resolved all potential issues, click Next.
Important If you have to disable virus-scanning software, you should scan the computer that is running the Sequencer to make ensure there are no unwanted or malicious files that might be added to the package.
On the Upgrade Configuration page confirm whether any further configuration is required. Click Next.
On the Select Installer page, click Browse and specify the update installation file for the package. If the update does not have an associated installer file and you plan to run all installation steps manually, select Perform a custom installation. Click Next.
On the Installation page, when the Sequencer and application installer are ready, install the application to the package root you selected (typically Q:\) so that the Sequencer can monitor the installation process. Perform the installation by using the application’s installation process.
If there are additional installation files that must be run as part of the installation, click Run and locate and run the additional installation files. When you are finished with the installation, select I am finished installing. Click Next.
Tip Instead of clicking the Run button, you can minimize the Sequencer and perform any additional required installation steps directly on the computer running the Sequencer. This is because the Sequencer is monitoring all system activity, whether or not it originates from within the Sequencer user interface (UI).
On the Installation Report page, you can review information about the virtual application that you just sequenced. For a more detailed explanation about the information displayed in Additional Information, double-click the event. After you have reviewed the information, click Next.
On the Create Package page, add Comments that will be associated with the package. Comments are useful for identifying version and other information about the package. The default Save Location is also displayed. To change the default location, click Browse and specify the new location. Click Create.
On the Completion page, to exit the wizard, click Close. The package is now available in the Sequencer.
In the Sequencer console, to save the package select Package / Save. Assign a name to the package and also specify where the package should be saved.
Important Virtual application packages can contain sensitive information, for example usernames and passwords. You should always save virtual application packages in a secure location.
For additional resources, see Information and Support for System Center 2012.
Tip: Use this query to find online documentation in the TechNet Library for System Center 2012. For instructions and examples, see Search the System Center 2012 Documentation Library.