windows-itpro-docs/windows/deploy/provisioning-create-package.md
jdeckerMS 5b91586ba7 Squashed commit of the following:
commit 9f95be92f864acf6a9cef8121e9d7c5b02f18da6
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 13:28:40 2017 -0800

    fix table

commit eaaf7927d163b4fb3eb89f2e9e3b2de367be8ea0
Merge: c53bbe2 cf11083
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 13:19:19 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit c53bbe240c88573cacdbfd424b2549ff895b2263
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 09:06:46 2017 -0800

    sync

commit 2db82b374821d5e57224f3492c4fdcf68a8d7c36
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 08:57:23 2017 -0800

    sync

commit a3fd8ad3d9d909e98332252e702e31496bb53cf0
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 08:49:41 2017 -0800

    sync

commit de0b46958e5783d0edb31c916f45f45118f9cd2f
Merge: c80779f deb778a
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 08:49:00 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit c80779f75b34ccd0c6772b695332f667d90aa760
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 08:48:10 2017 -0800

    fix code block

commit 24a001bff7cf3c0451195a094f063a80f61450e0
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 08:44:48 2017 -0800

    fix link

commit 574411a38d113a974a5c406746a06f629cdb50c0
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 08:38:57 2017 -0800

    fix links, format

commit 5e106b72f679243b0c601146277b66f9045c26f9
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 08:25:17 2017 -0800

    fix format

commit 6c693cee1a305955fcb3b711f393ed695e51e96f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 08:11:09 2017 -0800

    tweak apply

commit 501e1100d08b21a107a6d55f335edad08620250d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 07:44:01 2017 -0800

    moved apply procs, learn more links

commit 17c18a8970ccff5f11239031188a9f7a4f59f8f7
Merge: 3c80075 37bf478
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 18 07:38:50 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 3c80075ab12e4ced0134c3ad02f7de7e0ec0c24d
Merge: 4b77100 a4496a2
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 15:37:33 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 4b771007b71692959676a4290492af0ea7375c2d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 15:35:26 2017 -0800

    missing intro

commit 7c5406e213c5a84497352fb76ef491d53a1ecf74
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 15:30:05 2017 -0800

    add related links

commit deacc390e081365fc4be0509fc4a4b016fbe3734
Merge: d62ca20 a3fba4c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 14:29:29 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit d62ca20830be9ce1afae4deba12c6688c591554c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 14:27:56 2017 -0800

    escaped < >

commit dd2e558fd6e9cb38ecba49cb0d2d4ea08d5a53ae
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 14:14:01 2017 -0800

    multivariant

commit 668cdc313f47565f1275261496db748975d2b5b1
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 13:23:41 2017 -0800

    update change deploy

commit 1b5070b0f8bdbbe2e8d53c84173d0f0818bc1b30
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 13:21:51 2017 -0800

    resolve conflict change history manage

commit 8e342df4125216b4fa802204cb26441b1ecf63df
Merge: 031f50b 9793669
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 13:20:28 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 031f50b5ee684a048c34e6cf297149343585ec69
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 13:17:33 2017 -0800

    tweak

commit 54e2eb787d78c3a680e4c54e63b99e06a293fc39
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 11:15:51 2017 -0800

    tweak table

commit 4dc33fb1898f168b1bf59a127f7317e1df5ab4ef
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 11:02:33 2017 -0800

    cli

commit 755758d424f92bb0e8f42281310d9855aaaba4d6
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 10:56:38 2017 -0800

    new topics

commit 0711e5571a34788a5402c3e35a522341f1bf68b5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 10:08:03 2017 -0800

    update how it works

commit 210680ebf086e973ab06b9d7cf35768efa3fd6c4
Merge: eeec810 a171f82
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 09:17:08 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit eeec8100536b249aec154852d0879a81e9d07dda
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 17 09:16:38 2017 -0800

    reorder how it works

commit ed862463fc83d9f46ed8081cc3166d3bf123aa21
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 14:26:43 2017 -0800

    sync

commit 8abd729805cb0719104a118529f037effa197457
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 13:44:26 2017 -0800

    moved sections between topics

commit fad95aa31de0a9e621338751671c499779fb362e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 13:21:36 2017 -0800

    sync

commit efb848b257da63dd7b84e2e8edb12139f54e3dc1
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 12:53:53 2017 -0800

    reorg apply

commit 1a98b619c49c4cda9ab673247ba80771c9519251
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 12:42:00 2017 -0800

    finish create

commit 0ec9ade931ab3b74fddf0bbc25cd1d986ad382ed
Merge: f169e92 44e62eb
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 12:41:30 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit f169e92adea1d42a21c0844a6f109d5e632cdc08
Merge: 0f182c8 110241e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 12:06:04 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 0f182c8e9af068d65b29851b8569c5518707d773
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 11:25:52 2017 -0800

    switch

commit 351ab3a2b1d81481a4b760c65fbd33d36e7c9089
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 09:55:25 2017 -0800

    updates to install

commit 5b01085b0b961512fa891a171330967c9f4f7657
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 09:36:06 2017 -0800

    sync

commit 837f0a902fa66cc07f83b93b3f66cbc160d09fc6
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Fri Jan 13 08:58:22 2017 -0800

    sync

commit 2d8a29cb97b3f16dd0bb2d664ad9cdd11123b5ae
Merge: ad8151c c564f3e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 12:51:13 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit ad8151c775a18bcec03d41631c6c43d1b2fabb28
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 12:50:30 2017 -0800

    sync

commit 514161581723808a2ed5c29b24a3dcfd28901b78
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 12:03:30 2017 -0800

    remove graphic

commit 8d4ab1471d1f8d2c5d3a28cab73e860dd0e25e7c
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 11:58:23 2017 -0800

    sync

commit 3147720b7edc492b93aa8def7ca94bec4f54b74b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 11:45:07 2017 -0800

    fix format

commit 67fa6473648c45b4b9ff31d506bd9485b67a9760
Merge: 9995503 24803cd
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 11:43:21 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 9995503434d09fcbae73510ee0aec6123bc1a6f8
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 10:36:33 2017 -0800

    add links

commit 3e725b83f60c2ce06e043f704d4dbb86e7064ec8
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 10:34:16 2017 -0800

    sync

commit d40be4b40ecff550e9ccf0f022609e81142fc923
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 09:02:52 2017 -0800

    add topic

commit 010b2f64320a02857b189493e7e71934f8030c11
Merge: 639e54e 7519b87
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Thu Jan 12 08:26:45 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 639e54e4525c4cc0b79b770e8e81b07574e032cc
Merge: 79a7ee0 97b8484
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 11 14:33:39 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 79a7ee0597a4198a5be098cafe960c23b5f2f88b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 11 14:33:08 2017 -0800

    sync

commit ca313243bfc7cd9ac81c623eeafbe60fc2e6ce1d
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 11 13:17:04 2017 -0800

    add art

commit 938e50ca5db8304e7e44d040fd9e6c25ef3d402f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 11 12:40:47 2017 -0800

    mobile

commit 0552360320664f8f61a73eed5212a8f476d27f2f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 11 11:38:56 2017 -0800

    complete desktop

commit b3cea45101b03d0a8ba79b916a3b8c2de0ad09b1
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 11 11:10:09 2017 -0800

    format check

commit 2271bd9206316c752d0634c3df93ff23c6a80abd
Merge: 6a3478d 8ef9050
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 11 10:44:20 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 6a3478d8ab1f113150de7dd5df89118c4915b947
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 11 10:43:42 2017 -0800

    sync changes

commit 12964dabbbea4f1084d0396c956a23784a900f48
Merge: affb590 ec7b776
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Wed Jan 11 08:17:43 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit affb590262719ce7500292070c218d4b4f518c62
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 10 14:22:43 2017 -0800

    related topics

commit 0fb18bddbc1ec4c83f72b6d38159ed1d552d709f
Merge: 58555e2 2cad77f
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 10 14:12:50 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 58555e2dac6e8ca95b9110436b4c601b6727e7d0
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 10 12:00:52 2017 -0800

    sync

commit 4d107c68d6bbc27bc75ec714b844650a5eb1f678
Merge: 5d52165 60611e5
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Tue Jan 10 08:59:51 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 5d521654f1ae9233d7857fbde2ac0afb95f93f1e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Jan 9 14:06:10 2017 -0800

    sync

commit f21d6c41af1ef019cfe757b181fb757adee90ac3
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Jan 9 13:01:41 2017 -0800

    metadata and uninstall content

commit 81f8976b6e3a2306220948800541a413d866041b
Merge: 9654e2b f81dbd0
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Jan 9 12:26:40 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 9654e2b3886249d4a6235b209c20bca4596fbf18
Merge: 47d6aa6 310c015
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Jan 9 11:04:24 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit 47d6aa6ec8ebaaffa529066320c84635dd5a991e
Merge: a9bc13c f33df1b
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Jan 9 09:59:28 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov

commit a9bc13c733bb231306bc75512fae0c5882fd713e
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Jan 9 09:58:57 2017 -0800

    add topics

commit 8797ae2c0a04bb776811701c2d0672ab457b2bba
Merge: c053cb6 88cf4ee
Author: jdeckerMS <jdecker@microsoft.com>
Date:   Mon Jan 9 09:47:39 2017 -0800

    Merge remote-tracking branch 'refs/remotes/origin/master' into jdprov
2017-01-18 13:34:06 -08:00

12 KiB

title, description, ms.prod, ms.mktglfcycl, ms.sitesec, author, localizationpriority
title description ms.prod ms.mktglfcycl ms.sitesec author localizationpriority
Create a provisioning package (Windows 10) With Windows 10, you can create provisioning packages that let you quickly and efficiently configure a device without having to install a new image. w10 deploy library jdeckerMS high

Create a provisioning package for Windows 10

Applies to

  • Windows 10
  • Windows 10 Mobile

You use Windows Imaging and Configuration Designer (ICD) to create a provisioning package (.ppkg) that contains customization settings. You can apply the provisioning package to a device running Windows 10.

Learn how to install Windows ICD.

Start a new project

  1. Open Windows ICD:

    • From either the Start screen or Start menu search, type 'Imaging and Configuration Designer' and click on the Windows ICD shortcut,

    or

    • Navigate to C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86 (on an x64 computer) or C:\Program Files\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\ICD.exe (on an x86 computer), and then double-click ICD.exe.
  2. Select your desired option on the Start page, which offers three options for creating a provisioning package, as shown in the following image:

    Simple provisioning or provision school devices or advanced provisioning

    • The Simple provisioning and Provision school devices options provide wizard-style walkthroughs for creating a provisioning package based on a set of common settings.
    • The Advanced provisioning option opens a new project with all Runtime settings available.

    Tip

    You can start a project in the simple editor and then switch the project to the advanced editor.

    Switch to advanced editor

  3. Enter a name for your project, and then click Next.

  4. Select the settings you want to configure, based on the type of device, and then click Next. The following table describes the options.

    Windows edition Settings available for customization Provisioning package can apply to
    All Windows editions Common settings All Windows 10 devices
    All Windows desktop editions Common settings and settings specific to desktop devices All Windows 10 desktop editions (Home, Pro, Enterprise, Pro Education, Enterprise Education)
    All Windows mobile editions Common settings and settings specific to mobile devices All Windows 10 Mobile devices
    Windows 10 IoT Core Common settings and settings specific to Windows 10 IoT Core All Windows 10 IoT Core devices
    Windows 10 Holographic Common settings and settings specific to Windows 10 Holographic Microsoft HoloLens
    Common to Windows 10 Team edition Common settings and settings specific to Windows 10 Team Microsoft Surface Hub
  5. On the Import a provisioning package (optional) page, you can click Finish to create your project, or browse to and select an existing provisioning packge to import to your project, and then click Finish.

Tip

Import a provisioning package can make it easier to create different provisioning packages that all have certain settings in common. For example, you could create a provisioning package that contains the settings for your organization's network, and then import it into other packages you create so you don't have to reconfigure those common settings repeatedly.

After you click Finish, Windows ICD will open the appropriate walkthrough page if you selected Simple provisioning or Provision school devices, or the Available customizations pane if you selected Advanced provisioning. The remainder of this topic will explain the Advanced provisioning scenario.

Configure settings

For an advanced provisioning project, Windows ICD opens the Available customizations pane. The example in the following image is based on All Windows desktop editions settings.

What the ICD interface looks like

The settings in Windows ICD are based on Windows 10 configuration service providers (CSPs). To learn more about CSPs, see Introduction to configuration service providers (CSPs) for IT pros.

The process for configuring settings is similar for all settings. The following table shows an example.

![step one](images/one.png)
Expand a category.
![Expand Certificates category](images/icd-step1.png)
![step two](images/two.png)
Select a setting.
![Select ClientCertificates](images/icd-step2.png)
![step three](images/three.png)
Enter a value for the setting. Click **Add** if the button is displayed.
![Enter a name for the certificate](images/icd-step3.png)
![step four](images/four.png)
Some settings, such as this example, require additional information. In **Available customizations**, select the value you just created, and additional settings are displayed.
![Additional settings for client certificate](images/icd-step4.png)
![step five](images/five.png)
When the setting is configured, it is displayed in the **Selected customizations** pane.
![Selected customizations pane](images/icd-step5.png)

For details on each specific setting, see Windows Provisioning settings reference. The reference topic for a setting is also displayed in Windows ICD when you select the setting, as shown in the following image.

Windows ICD opens the reference topic when you select a setting

Build package

  1. After you're done configuring your customizations, click Export and select Provisioning Package.

    Export on top bar

  2. In the Describe the provisioning package window, enter the following information, and then click Next:

    • Name - This field is pre-populated with the project name. You can change this value by entering a different name in the Name field.
    • Version (in Major.Minor format - - Optional. You can change the default package version by specifying a new value in the Version field.
    • Owner - Select IT Admin. For more information, see Precedence for provisioning packages.
    • Rank (between 0-99) - Optional. You can select a value between 0 and 99, inclusive. The default package rank is 0.
  3. In the Select security details for the provisioning package window, you can select to encrypt and/or sign a provisioning package with a selected certificate. Both selections are optional. Click Next after you make your selections.

    • Encrypt package - If you select this option, an auto-generated password will be shown on the screen.
    • Sign package - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking Select and choosing the certificate you want to use to sign the package.

    Note

    You should only configure provisioning package security when the package is used for device provisioning and the package has contents with sensitive security data such as certificates or credentials that should be prevented from being compromised. When applying an encrypted and/or signed provisioning package, either during OOBE or through the setting UI, the package can be decrypted, and if signed, be trusted without explicit user consent. An IT administrator can set policy on a user device to restrict the removal of required packages from the device, or the provisioning of potentially harmful packages on the device.

    If a provisioning package is signed by a trusted provisioner, it can be installed on a device without a prompt for user consent. In order to enable trusted provider certificates, you must set the TrustedProvisioners setting prior to installing the trusted provisioning package. This is the only way to install a package without user consent. To provide additional security, you can also set RequireProvisioningPackageSignature, which prevents users from installing provisioning packages that are not signed by a trusted provisioner.

  4. In the Select where to save the provisioning package window, specify the output location where you want the provisioning package to go once it's built, and then click Next. By default, Windows ICD uses the project folder as the output location.

  5. In the Build the provisioning package window, click Build. The provisioning package doesn't take long to build. The project information is displayed in the build page and the progress bar indicates the build status.

    If you need to cancel the build, click Cancel. This cancels the current build process, closes the wizard, and takes you back to the Customizations Page.

  6. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.

    If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.

    If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click Back to change the output package name and path, and then click Next to start another build.

  7. When you are done, click Finish to close the wizard and go back to the Customizations page.

Next step: How to apply a provisioning package

Learn more