deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 13:27:23 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
windows-itpro-docs/windows/configuration/provisioning-packages/provisioning-command-line.md
Nick Schonning 2ed412cef0 fix: MD033/no-inline-html 
- Escape elements being swallowed as HTML
- Remove Head/Style that don't render on docs.ms
- Use backticks where there is no formatting
- Espace inside pre blocks
- Remove non-docfx xref with text
2019-06-21 02:42:25 -04:00

4.0 KiB
Raw Blame History

title, description, ms.prod, ms.mktglfcycl, ms.sitesec, author, ms.author, ms.topic, ms.localizationpriority, ms.date, ms.reviewer, manager
title description ms.prod ms.mktglfcycl ms.sitesec author ms.author ms.topic ms.localizationpriority ms.date ms.reviewer manager
Windows Configuration Designer command-line interface (Windows 10) w10 deploy library dansimp dansimp article medium 07/27/2017 dansimp

Windows Configuration Designer command-line interface (reference)

Applies to

  • Windows 10
  • Windows 10 Mobile

You can use the Windows Configuration Designer command-line interface (CLI) to automate the building of provisioning packages.

  • IT pros can use the Windows Configuration Designer CLI to require less re-tooling of existing processes. You must run the Windows Configuration Designer CLI from a command window with administrator privileges.

  • You must use the Windows Configuration Designer CLI and edit the customizations.xml sources to create a provisioning package with multivariant support. You need the customizations.xml file as one of the inputs to the Windows Configuration Designer CLI to build a provisioning package. For more information, see Create a provisioning package with multivariant settings.

Syntax

icd.exe /Build-ProvisioningPackage /CustomizationXML:<path_to_xml> /PackagePath:<path_to_ppkg> 
[/StoreFile:<path_to_storefile>]  [/MSPackageRoot:<path_to_mspackage_directory>]  [/OEMInputXML:<path_to_xml>]
[/ProductName:<product_name>]  [/Variables:<name>:<value>] [[+|-]Encrypted] [[+|-]Overwrite] [/?]

Switches and arguments

Switch Required? Arguments
/CustomizationXML No Specifies the path to a Windows provisioning XML file that contains the customization assets and settings. For more information, see Windows provisioning answer file.
/PackagePath Yes Specifies the path and the package name where the built provisioning package will be saved.
/StoreFile No


See Important note.		 For partners using a settings store other than the default store(s) used by Windows Configuration Designer, use this parameter to specify the path to one or more comma-separated Windows settings store file. By default, if you don't specify a settings store file, the settings store that's common to all Windows editions will be loaded by Windows Configuration Designer.


Important If you use this parameter, you must not use /MSPackageRoot or /OEMInputXML.
/Variables No Specifies a semicolon separated <name> and <value> macro pair. The format for the argument must be <name>=<value>.
Encrypted No Denotes whether the provisioning package should be built with encryption. Windows Configuration Designer auto-generates the decryption password and includes this information in the output.


Precede with + for encryption or - for no encryption. The default is no encryption.
Overwrite No Denotes whether to overwrite an existing provisioning package.


Precede with + to overwrite an existing package or - if you don't want to overwrite an existing package. The default is false (don't overwrite).
/? No Lists the switches and their descriptions for the command-line tool or for certain commands.

Related topics