Jul 12, 2018 Stardock, your competitive edge in corporate solutions, entertainment and consumer software for Windows 10. DreamScenes, Themes, skins, icons, desktop enhancements and strategy games! Software Object Desktop Your complete Windows customization suite. Start10 The first Windows 10 Start menu alternative. Indicates that this cmdlet registers an existing app package installation that has been disabled, did not register, or has become corrupted. Use the current parameter to specify that the manifest is from an existing installation, and not from a collection of files in development mode.
-->Important
The App-V 5.0 Sequencer does not grant any license rights to the software application that you use to create the Package Accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a Package Accelerator with the App-V 5.0 Sequencer.
The App-V 5.0 Sequencer does not grant any license rights to the software application that you use to create the Package Accelerator. You must abide by all end user license terms for the application that you use. It is your responsibility to make sure that the software application’s license terms allow you to create a Package Accelerator with the App-V 5.0 Sequencer.
Use the following procedure to create a virtual application package with the App-V 5.0 Package Accelerator.
Note
Before you start this procedure, copy the required Package Accelerator locally to the computer that runs the App-V 5.0 Sequencer. You should also copy all required installation files for the package to a local directory on the computer that runs the Sequencer. This is the directory that you have to specify in step 5 of this procedure.
Before you start this procedure, copy the required Package Accelerator locally to the computer that runs the App-V 5.0 Sequencer. You should also copy all required installation files for the package to a local directory on the computer that runs the Sequencer. This is the directory that you have to specify in step 5 of this procedure.
To create a virtual application package with an App-V 5.0 Package Accelerator
- To start the App-V Sequencer, on the computer that runs the App-V 5.0 Sequencer, click Start / All Programs / Microsoft Application Virtualization / Microsoft Application Virtualization Sequencer.
- To start the Create New Package Wizard, click Create a New Virtual Application Package. To create the package, select the Create Package using a Package Accelerator check box, and then click Next.
- To specify the package accelerator that will be used to create the new virtual application package, click Browse on the Select Package Accelerator page. Click Next.Important
If the publisher of the package accelerator cannot be verified and does not contain a valid digital signature, then before you click Run, you must confirm that you trust the source of the package accelerator. Confirm your choice in the Security Warning dialog box. - On the Guidance page, review the publishing guidance information that is displayed in the information pane. This information was added when the Package Accelerator was created and it contains guidance about how to create and publish the package. To export the guidance information to a text (.txt) file, click Export and specify the location where the file should be saved, and then click Next.
- On the Select Installation Files page, click Make New Folder to create a local folder that contains all required installation files for the package, and specify where the folder should be saved. You must also specify a name to be assigned to the folder. You must then copy all required installation files to the location that you specified. If the folder that contains the installation files already exists on the computer that runs the Sequencer, click Browse to select the folder.Alternatively, if you have already copied the installation files to a directory on this computer, click Make New Folder, browse to the folder that contains the installation files, and then click Next.Note
You can specify the following types of supported installation files:- Windows Installer files (.msi)
- Cabinet files (.cab)
- Compressed files with a .zip file name extension
- The actual application files
The following file types are not supported: .msp and .exe files. If you specify an .exe file, you must extract the installation files manually.
- On the Package Name page, specify a name that will be associated with the package. The name that you specify identifies the package in the App-V Management Console. Click Next.
- On the Create Package page, provide comments that will be associated with the package. The comments should contain identifying information about the package that you are creating. To confirm the location where the package is created, review the information that is displayed in Save Location. To compress the package, select Compress Package. Select the Compress Package check box if the package will be streamed across the network, or when the package size exceeds 4 GB.To create the package, click Create. After the package is created, click Next.
- On the Configure Software page, to enable the Sequencer to configure the applications that are contained in the package, select Configure Software. In this step you can configure any associated tasks that must be completed in order to run the application on the target computers. For example, you can configure any associated license agreements.If you select Configure Software, the following items can be configured using the Sequencer as part of this step:
- Load Package. The Sequencer loads the files that are associated with the package. It can take several seconds to an hour to decode the package.
- Run Each Program. Optionally run the programs that are contained in the package. This step is helpful to complete any associated license or configuration tasks that are required to run the application before you deploy and run the package on target computers. To run all the programs at once, select at least one program, and then click Run All. To run specific programs, select the program or programs that you want to run, and then click Run Selected. Complete the required configuration tasks, and then close the applications. It can take several minutes for all programs to run. Click Next.
- Save Package. The Sequencer saves the package.
- Primary Feature Block. The Sequencer optimizes the package for streaming by rebuilding the primary feature block.
If you do not want to configure the applications, click Skip this step, and to go to step 9 of this procedure, and then click Next. - On the Completion page, after you review the information that is displayed in the Virtual Application Package Report pane, click Close.The package is now available in the Sequencer. To edit the package properties, click Edit [Package Name]. For more information about how to modify a package, see How to Modify an Existing Virtual Application Package.Got a suggestion for App-V? Add or vote on suggestions here. Got an App-V issue? Use the App-V TechNet Forum.
Related topics
-->Syntax
Description
The Add-AppxPackage cmdlet adds a signed app package to a user account.An app package has an .msix or .appx file name extension.Use the DependencyPath parameter to add all other packages that are required for the installation of the app package.
You can use the Register parameter to install from a folder of unpackaged files during development of Windows速 Store apps.
To update an already installed package, the new package must have the same package family name.
Examples
Example 1: Add an app package
This command adds an app package that the package contains.
Example 2: Add a disabled app package in development mode
This command gets the full path of the package manifest file of an installed Windows Store app, and then registers that package.You can use DisableDevelopmentMode to register an application that is staged by the StagePackageAsync API, has been disabled, or has become corrupted during testing.
Example 3: Add an app along with its optional packages
![Soundpackager Soundpackager](http://cdn.rainbowresource.netdna-cdn.com/products/051018i1.jpg)
This command adds an app package along with its optional packages. It is an atomic operation which means that if the app or its optional packages fail to install, the deployment operation will be aborted
Example 4: Install only the required section of a streaming app
This command adds an app package but only installs the required section of a streaming app. Calling this command again without the RequiredContentGroupOnly flag proceeds to install the rest of the application in the order defined by the AppxContentGroupMap.xml
Parameters
-AppInstallerFile
Runs an appinstaller file and allows the user to install all of the defined packages with a single click.For more information, see Create an App Installer file manually.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Prompts you for confirmation before running the cmdlet.
Type: | SwitchParameter |
Aliases: | cf |
Position: | Named |
Default value: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Specifies the dependency package full name or dependency package bundle full name to be registered.
Type: | String[] |
Position: | Named |
Default value: | None |
Accept pipeline input: | True (ByValue) |
Accept wildcard characters: | False |
Specifies an array of file paths of dependency packages that are required for the installation of the app package.The app package has an .msix, .appx, .msixbundle, or .appxbundle file name extension. You can specify the paths to more than one dependency package.If a package is already installed for a user, you can skip adding it to the DependencyPath.
Type: | String[] |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Indicates that this cmdlet registers an existing app package installation that has been disabled, did not register, or has become corrupted.Use the current parameter to specify that the manifest is from an existing installation, and not from a collection of files in development mode.You can also use this parameter to register an application that the Package Manager API has staged.Use the Register parameter to specify the location of the app package manifest .xml file from the installation location.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Specifies an array of optional packages that must be installed along with the app package. It is an atomic operation which means that if the app or its optional packages fail to install, the deployment operation will be aborted
Type: | String[] |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Indicates that this cmdlet forces all active processes that are associated with the package or its dependencies to shut down.If you specify this parameter, do not specify the ForceTargetApplicationShutdown parameter.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Indicates that this cmdlet forces all active processes that are associated with the package to shut down.If you specify this parameter, do not specify the ForceApplicationShutdown parameter.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
This parameter is used to force a specific version of a package to be staged/registered, regardless of whether a higher version is already staged/registered.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Indicates that this cmdlet forces the deployment of all resource packages specified from a bundle argument.This overrides the resource applicability check of the deployment engine and forces staging of all resource packages, registration of all resource packages, or staging and registration of all resource packages.This parameter can only be used when specifying a resource bundle or resource bundle manifest.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
This parameter is used to prevent missing referenced packages to be downloaded.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
![Appnee Appnee](http://www.dobrehry.estranky.cz/archiv/inahled/47.jpg)
Specifies the main package full name or bundle full name to register.
Type: | String |
Position: | Named |
Default value: | None |
Accept pipeline input: | True (ByValue) |
Accept wildcard characters: | False |
Specifies the PackageFamilyName of the optional packages that are in a related set that need to be installed along with the app. Unlike the external packages flag, you do not need to pass in a path to the optional package(s). It is an atomic operation which means that if the app or its optional packages fail to install, the deployment operation will be aborted
Type: | String[] |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Specifies the file path of the app package.An app package has an .msix, .appx, .msixbundle, or .appxbundle file name extension.
Type: | String |
Aliases: | PSPath |
Position: | 1 |
Default value: | None |
Accept pipeline input: | True (ByValue) |
Accept wildcard characters: | False |
Indicates that this cmdlet registers an application in development mode.You can use development mode to install applications from a folder of unpackaged files.You can use the current parameter to test your Windows速 Store apps before you deploy them as app packages.To register an existing app package installation, you must specify the DisableDevelopmentMode parameter and the Register parameter.In order to specify dependency packages, specify the DependencyPath parameter and the DisableDevelopmentMode parameter.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Specifies the parameter -MainPackage that defines the family name or full name to be registered.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
This is an optional element that is used to specify the other optional packages that are specified in the main app package. These packages will not be installed as part of the deployment operation.
Type: | String[] |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Specifies that only the required content group that is specified in the AppxContentGroupMap.xml must be installed. At this point the app can be launched. Calling add-appxpackage specifying the path to the app, triggers the rest of the app to be installed in the order defined in the AppxContentGroupMap.xml.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
In the case of a failed deployment, if this switch is set to $true, files that have been created on the target machine during the installation process are not removed.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Stages a package to the system without registering it.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Specifies that the package being added is a dependency package update.A dependency package is removed from the user account when the parent app is removed.If you do not use this parameter, the package being added is a primary package and is not removed from the user account if the parent app is removed.To update an already installed package, the new package must have the same package family name.
Type: | SwitchParameter |
Position: | Named |
Default value: | None |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Specifies the AppxVolume object to which to stage the package.The volume also specifies the default location for user AppData.
Type: | AppxVolume |
Position: | Named |
Default value: | None |
Accept pipeline input: | True (ByPropertyName, ByValue) |
Accept wildcard characters: | False |
Shows what would happen if the cmdlet runs.The cmdlet is not run.
Type: | SwitchParameter |
Aliases: | wi |
Position: | Named |
Default value: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Inputs
System.String[]
System.IO.FileInfo
Outputs
None