If you want to deliver the App Volumes application package in the .vhd format following your own delivery mechanism, then you can use PowerShell Cmdlets that allow you to perform operations such as install, swap, uninstall, and launch applications.
App Volumes applications can be directly delivered to Windows endpoints using device management tools.
For more information about this delivery scenario, see Deliver App Volumes Applications to Windows Endpoints.
Enhance end user experience during application uninstall and application swap
To enhance end user experience, notifications can be presented to the end user before the application gets uninstalled or swapped from the Windows endpoint. You can choose to use this capability by adding an svservice parameter EnableAppChangeNotification of type REG_DWORD at HKLM\SYSTEM\CurrentControlSet\Services\svservice\Parameters in the Windows endpoint. Prior to uninstall or swap, the value of this parameter must be configured to 1.
Note: The notifications are displayed only when the application remains launched at the time of uninstall or swap. If the application is not actively used, then no notifications are displayed even when the parameter is enabled.
To understand how the parameter helps in end user experience during uninstall or swap, see the descriptions for Uninstall-AppVolumesPackage and Swap-AppVolumesPackage in the table listing the PowerShell Cmdlets in this page.
PowerShell Cmdlets
| Command line Argument | Task |
|---|---|
Install-AppVolumesPackage -Path VHD path -ClassicDelivery -StoreOffline | Installs the application on the Windows endpoint, using the .vhd package from the path specified in the command. The .vhd and .json files must be at the same location and have the same file name. The following are optional parameters:
|
Uninstall-AppVolumesPackage -Path VHD path | Uninstalls the application from the Windows endpoint. Depending on the EnableAppChangeNotification parameter value, the uninstall behavior varies.
For more information about EnableAppChangeNotification, see the Enhance end user experience during application uninstall and application swap section earlier in this page. |
Swap-AppVolumesPackage -OldPath Old VHD path -NewPath New VHD path -ClassicDelivery -StoreOffline | This command swaps or replaces an existing application package with a new application package. An existing package can be swapped with another version of the application package or a different application package. Depending on the EnableAppChangeNotification parameter value, the swap behavior varies.
For more information about EnableAppChangeNotification, see the Enhance end user experience during application uninstall and application swap section earlier in this page.-ClassicDelivery and -StoreOffline are optional parameters. When these optional parameters are used, the swap occurs immediately, the delivery mode of the swapped package is classic, and the .vhd and .json files of the new application package are locally stored on the Windows endpoint. For information about these parameters, see the other rows in this table. |
Get-AppVolumesPackages -OutputFile path of the file where the json output must be stored | Use this command to list application packages which are assigned to a particular session. Application details such as package name, package version, and other package identifier details are retrieved and displayed on the command line. With this command, you can use the -OutputFile file path parameter. File path indicates where the json output must be stored. When this parameter is used, in addition to the output getting displayed on the command line, the output also gets stored in the json format in a file at the location as mentioned in the parameter. Example: In the following example, application package details such as package name, package version, volume ID, App Product ID, path from where the .vhd package is virtualized, and so on are fetched for Adobe Reader XI and Mozilla. At the Windows PowerShell prompt, the command and output are as follows:
Package Name : Adobe Reader XI (11.0.23)For more information about App Product ID (upgradecode), see Windows Command-Line Arguments for the App Volumes Application Capture Command-Line Program. |
Extract-AppVolumesPackageShortcuts -Path VHD file path/json file path -IncludeIcons -IconFormat ico|png -IconSize Size -IconExtractPath folder path -OutputFile file path | Use this command to list all the shortcuts of an application package and retrieve information related to the shortcut. To enhance user experience, Note: The following parameters can be used with this command: -OutputFile file path parameter. File path indicates where the json output must be stored. When this parameter is used, in addition to the output getting displayed on the command line, the output also gets stored in the json format in a file at the location as mentioned in the parameter. -IncludeIconsThis is an optional parameter which can be used to extract the application icon. When this parameter is used, an icon is extracted to the current working directory by default. If a location is specified using the -IconExtractPath parameter, then the icon is extracted to the location specified in the parameter. If the -IncludeIcons parameter is not used, then no icon is extracted. Other icon-related, optional parameters which can be used only with -IncludeIcons are as follows:
Example: At the Windows PowerShell prompt, the command and output are as follows: C:\Users\Administrator\Desktop> Extract-AppVolumesPackageShortcuts -Path "C:\Users\Administrator\Desktop\Office2016.vhd" -IncludeIcons -IconFormat png -IconSize 256x256 -IconExtractPath "C:\Users\Administrator\Desktop\temp" -OutputFile "C:\Users\Administrator\Desktop\temp\Outputfile.txt" |
Run-AppVolumesApp -Path VHD path -LaunchID Launch ID | -LaunchID: A unique GUID identifier which represents an application shortcut in a package.When this command is run, an application is delivered and the application shortcut is launched. When an end user clicks the shortcut, the application is launched. Each application shortcut is associated with a unique launch ID (GUID), which is captured at the time of application packaging. As the application is delivered only for that user session, this application is not available for the user after reboot. Prerequisites:
|
¿Le resultó útil esta página?