Add-AppxProvisionedPackage

NAME
Add-AppxProvisionedPackage

SYNOPSIS
Adds an app package (.appx) that will install for each new user to a Windows image.

SYNTAX

    Add-AppxProvisionedPackage [-CustomDataPath [<String>]]
	[-DependencyPackagePath [<String[]>]] [-FolderPath [<String>]]
	[-LicensePath [<String>]] [-LogLevel {Errors | Warnings | WarningsInfo}] 
    [-LogPath [<String>]] [-PackagePath [<String>]] 
	[-ScratchDirectory [<String>]] [-SkipLicense] [-SystemDrive [<String>]] 
	[-WindowsDirectory [<String>]] -Online [<CommonParameters>]
    


    Add-AppxProvisionedPackage [-CustomDataPath [<String>]] 
	[-DependencyPackagePath [<String[]>]] [-FolderPath [<String>]] 
	[-LicensePath [<String>]] [-LogLevel {Errors | Warnings | WarningsInfo}] 
    [-LogPath [<String>]] [-PackagePath [<String>]] 
	[-ScratchDirectory [<String>]] [-SkipLicense] [-SystemDrive [<String>]] 
	[-WindowsDirectory [<String>]] -Path <String> [<CommonParameters>]
	


DESCRIPTION
The Add-AppxProvisionedPackage cmdlet adds an app package (.appx) that will install for each new
user to a Windows image. If the package has dependencies that are architecture-specific, you must
install the applicable architectures for the dependency on the target image. For example, you must
install the x86 dependency on the x86 image.

You cannot install an app package (.appx) on an operating system that does not support Windowsr 8
apps. Apps are not supported on Server Core installations of Windows Serverr 2012, Windowsr
Preinstallation Environment (Windows PE) 4.0, or on any versions of Windows older than Windows 8
and Windows Server 2012.

To install and run apps on Windows Server 2012, you must install the Desktop Experience.

Use the Online parameter to specify the running operating system on your local computer, or use
the Path parameter to specify the location of a mounted Windows image.

Use the PackagePath, DependencyPackagePath, and LicensePath parameters to specify the location of
all the files that are needed to add the provisioned app package (.appx). Use these parameters to
provision line-of-business apps.

Use the FolderPath parameter to specify the location of a folder of unpacked app package (.appx)
files that includes any dependency packages and a license file.

To add an app package (.appx) for a particular user, or to test a package while developing your
app, use the Add-AppxPackage cmdlet instead.

For more information, including requirements for app package provisioning, see Sideload Apps with
DISM (http://go.microsoft.com/fwlink/?LinkID=231020) and How to develop an OEM app that uses a
custom file (http://go.microsoft.com/fwlink/?LinkID=279989) in the TechNet Library..

RELATED LINKS
Online Version: http://go.microsoft.com/fwlink/p/?linkid=289347
Add-AppxPackage
Get-AppxProvisionedPackage
Remove-AppxProvisionedPackage
Set-AppXProvisionedDataFile

REMARKS
To see the examples, type: "get-help Add-AppxProvisionedPackage -examples".
For more information, type: "get-help Add-AppxProvisionedPackage -detailed".
For technical information, type: "get-help Add-AppxProvisionedPackage -full".
For online help, type: "get-help Add-AppxProvisionedPackage -online"