Apply a provisioning package from a SCCM Task Sequence

Hi Windows 10 lovers!

Today I’m going to explain you how to apply a provisioning package (PPKG) from within a SCCM task sequence (TS).

As a reminder, Configuration Manager 2012 R2 SP1 is a requirement for supported Windows 10 deployment. On the other side, we only support SCCM 2007 for Windows 10 management and not deployment.

I wrote in a previous articles how to

  • create a PPKG (link)
  • apply a PPKG to an offline image using DISM command (link)

And today, I want to show you how easy it is to apply a PPKG from a task sequence. Here is my scenario:

  1. Create a PPKG containing a language pack (Japanese in my case)
  2. Create a package in ConfigMgr containing the PPKG.
  3. Create a TS to deploy Windows 10 Enterprise x64 English and apply the previously created PPKG.

I won’t cover the first point so please refer to my previous article covering the creation of a PPKG.

Creation of a SCCM package containing the PPKG

Copy the PPKG to a shared folder.


From ConfigMgr console, [Software Library] –> [Overview] –> [Application Management] –> [Packages] click on [Create Package] to create a package containing the PPKG. Specify the UNC path where the PPKG has been copied.


Once the package has been created, distribute the content to a distribution point.

Apply PPKG from a Windows 10 deployment Task Sequence

Create a task sequence to deploy Windows 10. Once created, add the “Run Command Line” action at the end of “Install Operating System” group.


In the “Run Command Line” action:

  • Copy the following DISM command line: DISM /Image=C:\ /Add-ProvisioningPackage /PackagePath:JPLanguagePack.ppkg
  • Select the package we created previously.


Test the TS deployment

Now you are ready to deploy that TS containing the PPKG!

While deploying you should see the step where PPKG is applying.


After some time, you should see the language selection screen which proves that the language pack has been successfully added!


If you have any issue during the deployment, think about checking the deployment log (smsts.log).

If successful, you would find a message like this (for a successful language pack addition):