Contact Info

Crumbtrail » Administration » Powershell » Powershell 3.0 » Add-AppxProvisionedPackage

Add-AppxProvisionedPackage - Powershell 3.0 CmdLet

ActiveXperts Network Monitor ships with integrated Powershell scripts to monitor complex network. The scripts run out of the box
Download the ActiveXperts Network Monitor FREE version now »


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

Add-AppxProvisionedPackage [-CustomDataPath <String>] [-DependencyPackagePath <String[]>] [-FolderPath <String>] [-Lice
nsePath <String>] [-LogLevel <LogLevel>] [-LogPath <String>] [-PackagePath <String>] [-ScratchDirectory <String>] [-Ski
pLicense [<SwitchParameter>]] [-SystemDrive <String>] [-WindowsDirectory <String>] -Online [<SwitchParameter>] [<Common
Add-AppxProvisionedPackage [-CustomDataPath <String>] [-DependencyPackagePath <String[]>] [-FolderPath <String>] [-Lice
nsePath <String>] [-LogLevel <LogLevel>] [-LogPath <String>] [-PackagePath <String>] [-ScratchDirectory <String>] [-Ski
pLicense [<SwitchParameter>]] [-SystemDrive <String>] [-WindowsDirectory <String>] -Path <String> [<CommonParameters>]

The Add-AppxProvisionedPackage cmdlet adds an app package (.appx) that will install for each new user to a Windows imag
e. If the package has dependencies that are architecture-specific, you must install the applicable architectures for th
e 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 Windows® 8 apps. Apps are not su
pported on Server Core installations of Windows Server® 2012, Windows® 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 s
pecify the location of a mounted Windows image.

Use the PackagePath, DependencyPackagePath, and LicensePath parameters to specify the location of all the files that ar
e 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 an
y 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-AppxPa
ckage cmdlet instead.

For more information, including requirements for app package provisioning, see How to Add and Remove Apps.