You use Microsoft Application Virtualization for Desktops to virtualize applications for client computers. A virtual application that was installed by using a Windows Installer Package (.msi) file…

Question

Options

• AReinstall the virtual application package.
• BUse the Repair function in the Windows Installer Package.
• CUse the Microsoft Application Virtualization (App-V) Sequencer to edit the virtual application
• DReload the virtual application package.

• A
  84% (31)
• B
  11% (4)
• C
  5% (2)

Explanation

1: RE-LOAD PACKAGE FROM Application Virtualization Client Management Console: How to Load or Unload an Application You can use the following procedures to load or unload an application from the cache, directly from the Results pane of the Application node in the Application Virtualization Client Management Console. When you select this node, the Results pane displays a list of applications. When you load or unload a package, all the applications in the package are loaded into or removed from cache When loading a package, if you do not have adequate space in cache to load the applications, increase your cache size. For more information about cache size, see How to Change the Cache Size and the Drive Letter Designation. ------ OR ------ 2: Remove and Install an MSI-PACKAGE (which automatically re-load app-v package) Stand- Alone Mode with MSI The App-V 4.5 Sequencer supports creating an MSI during the sequencing process. This process does not have a formal publishing or streaming procedure. This MSI will contain the ICO, OSD, and Manifest.xml files that are necessary for publishing the application on the machine it is run from and how to import the SFT file into the App-V client cache. The package file (SFT) is not part of the MSI that is generated during sequencing and will need to be in the same directory as the MSI to successfully complete by default. In some scenarios it may be necessary to place the SFT files at an alternate location like a file server. In this scenario the administrator could use the SFTPATH parameter to specify an alternate location of the SFT file. This would not require the SFT file to be in the same directory as the MSI. In Standalone mode the package will be published and the SFT file contents will be loaded into the client cache completely. The following command shows how to install an MSI based package when the SFTFILE is located on a file server. Msiexec.exe /i \PathToMsi\packagename.msi SFTPATH=\server\share\package.sft /q Streaming Mode with MSI Another option is to use MSI based packages but choose to stream the SFT file contents from an App-V Server, file server, or local file location. In this scenario the package will be published, but the SFT file will be streamed to the App-V client cache. The process of streaming the SFT will be done by default as part of the installation of the MSI, but could optionally be configured to happen when the user launches the application the first time. c 2008 MICROSOFT Source: App-V Application Publishing and Client Interaction Copyright○ Use the Repair function in the Windows Installer Package. Use the Microsoft Application Virtualization (App-V) to re-sequence the application. - it is WRONG. Repair function of MSI- package not reload SFT-package. But you can choose Repair function of Client Management How to Repair an Application To repair a selected application, you can perform the following procedure directly from the Results pane of the Application node in the Application Virtualization Client Management Console. When you repair an application, you remove any custom user settings and restore the default settings. This action does not change or delete shortcuts or file type associations, and it does not remove the application from cache. Use the Microsoft Application Virtualization (App-V) Sequencer to edit the virtual application package. - it is WRONG. Question about user's side, not server's side.

No community discussion yet for this question.