Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, October 19, 2017 8:52 AM
Hi,
I'm trying to build provisioning packages for Windows 10 Version 1703 with Imaging and Configuration Designer in Windows ADK for Windows 10 1703. But, it's failed to build packages. I'd tried to follow procedure. How to fix procedure? Or what is lack of requirement?
1. Install Windows 10 ADK for Windows 10 Version 1703 to Windows 10 Version 1703
2. Create a provisioning setting for desktop device provisioning on Imaging and Configuration Designer GUI
3. Run "Deployment and Imaging Tools Environment"
4. Change folder to the provisioning setting folder
5. Run below command
6. We could get below error message and error log
Versions:
Windows 10 Version: 1703
Build: 15063.674
Windows Imaging and Configuration Designer Version: 10.0.15063.0
Command:
icd.exe /build-ProvisioningPackage /CustomizationXML:customizations.xml /PackagePath:sample.ppk
Error Message:
C:\Users\user1\Documents\Windows Imaging and Configuration Designer (WICD)\Sample_Desktop_Poject_for_TechNet>
Microsoft (C) Windows Imaging and Configuration Designer
ICD.exe : ERROR: The following errors were detected in customizations:
ICD.exe : ERROR: Settings were not found in the store file.
ICD.exe : ERROR: Parse error (0x80070490): 'ComputerAccount' is not a valid child node for /Accounts
ICD.exe : ERROR: C:\Users\user1\Documents\Windows Imaging and Configuration Designer (WICD)\Common\ICDCommon_20171017-131958-249_1296.log
Error Log:
10/17/2017 1:20:46 PM Info ICD Started
10/17/2017 1:20:46 PM Info Command line input: icd.exe /build-ProvisioningPackage /CustomizationXML:customizations.xml /PackagePath:sample.ppk
10/17/2017 1:20:46 PM Info Current directory: C:\Users\user1\Documents\Windows Imaging and Configuration Designer (WICD)\Sample_Desktop_Poject_for_TechNet
10/17/2017 1:20:46 PM Info Attempting to DPAPI decrypt customization XML C:\Users\user1\Documents\Windows Imaging and Configuration Designer (WICD)\Sample_Desktop_Poject_for_TechNet\customizations.xml.
10/17/2017 1:20:46 PM Info Customization XML could not be decrypted as it's most likely not encrypted. The data is invalid.
10/17/2017 1:20:46 PM Info StoreFile path: C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\Microsoft-Common-Provisioning.dat
10/17/2017 1:20:46 PM Info Loaded Knobs schema hive at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\Microsoft-Common-Provisioning.dat
10/17/2017 1:20:46 PM Error WpxGetFileEdition (onecore\base\ntsetup\wpx\core\store.cpp:103) - 0x80070002:
10/17/2017 1:20:46 PM Error No SKU information file C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\Microsoft-Common-Provisioning.sku.xml available for store file C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\Microsoft-Common-Provisioning.dat
10/17/2017 1:20:46 PM Info Loaded settings from Windows Unknown Unknown
10/17/2017 1:20:46 PM Error WpxConfig::FindSchema (onecore\base\ntsetup\wpx\core\config.cpp:162) - 0x80070490:
10/17/2017 1:20:46 PM Error Couldn't find schema path for ComputerAccount under /Accounts
10/17/2017 1:20:46 PM Error WpxSetting::GetChild (onecore\base\ntsetup\wpx\core\setting.cpp:249) - 0x80070490:
10/17/2017 1:20:46 PM Error Couldn't find schema for answer path /Accounts/ComputerAccount
10/17/2017 1:20:46 PM Error WpxWpafReader::ReadSettingsTree (onecore\base\ntsetup\wpx\file\wpafreader.cpp:628) - 0x8007000d:
10/17/2017 1:20:46 PM Error Unrecognized child ComputerAccount specified for tree setting /Accounts
10/17/2017 1:20:46 PM Error WpxWpafReader::ReadSettingsTree (onecore\base\ntsetup\wpx\file\wpafreader.cpp:639) - 0x8007000d:
10/17/2017 1:20:46 PM Error Couldn't read answers under /Accounts
10/17/2017 1:20:46 PM Error WpxWpafReader::ReadCommonSettings (onecore\base\ntsetup\wpx\file\wpafreader.cpp:197) - 0x8007000d:
10/17/2017 1:20:46 PM Error Couldn't read common settings
10/17/2017 1:20:46 PM Error WpxWpafReader::Read (onecore\base\ntsetup\wpx\file\wpafreader.cpp:78) - 0x8007000d:
10/17/2017 1:20:46 PM Error Failed to read common settings node
10/17/2017 1:20:46 PM Error WpxConfig::ReadAnswerFile (onecore\base\ntsetup\wpx\core\config.cpp:598) - 0x8007000d:
10/17/2017 1:20:46 PM Error Failed to load answer file
10/17/2017 1:20:46 PM Error The following errors were detected in customizations:
Settings were not found in the store file.
Parse error (0x80070490): 'ComputerAccount' is not a valid child node for /Accounts
10/17/2017 1:20:47 PM Error Microsoft.Windows.ICD.Common.Exceptions.CustomizationsException: The following errors were detected in customizations:
Settings were not found in the store file.
Parse error (0x80070490): 'ComputerAccount' is not a valid child node for /Accounts
at Microsoft.Windows.ICD.Provisioning.ImageCustomization.ImageCustomizations.ReadAndValidateWPXAnswerFile(Config wpxConfig, XDocument wpxDocument, Boolean ignoreWpxParseErrors)
at Microsoft.Windows.ICD.Provisioning.ImageCustomization.ImageCustomizations.Load(XDocument customizationsXDoc, Boolean onlySettings, Boolean ignoreWpxParseErrors)
at Microsoft.Windows.ICD.Provisioning.ImageCustomization.ImageCustomizations.CreateAndLoadAnswers(XDocument customizationsXDoc, IStoreConfig storeConfig, Boolean ignoreWpxParseErrors, Boolean isMobile)
at Microsoft.Windows.ICD.Core.Common.Project.LoadCustomizations(XDocument customizationsXDoc)
at Microsoft.Windows.ICD.Core.Common.Project.CreateFromStoreFile(IEnumerable`1 storeFilePaths, String location, XDocument customizationsXDoc, InvocationMode invocationMode)
at Microsoft.Windows.ICD.Core.CLI.BuildPackageCmdHandler.Execute()
Thank you for your reading and time.
All replies (13)
Tuesday, November 7, 2017 12:37 PM ✅Answered
Hi Karen,
I've found the solution how to build a desktop profile with icd.exe CLI. We'd not care about "/StoreFile" option of icd.exe. But, we must use suited store file to build a provisioning package. As a default, store file is "Microsoft-Common-Provisioning.dat," you found. But, we must pass correct store file path to icd.exe.
When we want to provision desktop device, we select "desktop device provisioning," or select "advanced provisioning" at first screen. And if we select "advanced provisioning," we decide provisioning type after naming a provisioning project and filename. Then we can set "ComputerName" in "Accounts/ComputerAccount."
And, when building provisioning package with icd.exe CLI, we must put the path of "Microsoft-Desktop-Provisioning.dat" as /StoreFile option, instead of the default option, "Microsoft-Common-Provisioning.dat" in the icd.exe installed path.
I've verified desktop configuration only, but we must pass a path of store file when we select provisioning type.
Could you verify this procedure? I thinks it's needed to modiry icd.exe cli reference document. It is enough to add these store files path to StoreFile option.
Friday, October 20, 2017 6:30 AM
Hi Nayuta,
If you want to use Windows Configuration Designer command-line interface (CLI) to build provisioning packages, 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, read this article:
Windows Configuration Designer command-line interface (reference)
/en-us/windows/configuration/provisioning-packages/provisioning-command-line
Here I suggest you Windows Configuration Designer to build provision package directly to avoid to use command line to do:
Create a provisioning package for Windows 10
/en-us/windows/configuration/provisioning-packages/provisioning-create-package
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Friday, October 20, 2017 9:04 AM
Hi Karen,
I'm sorry for confusing tools name in my post. In my environment, "icd.exe" is named "Windows Imaging and Configuration Designer" at the start menu. But, window title of GUI is "Windows Configuration Designer."
My purpose is generating customizations.xml and building it. For example, I want to change computer name on each machine.
I'd thought we could build customizations.xml that only saved icd.exe GUI, and not added multivariant configurations. But, is it not correct understand about using icd.exe CLI?
Very thanks,
Nayuta
Wednesday, October 25, 2017 10:13 AM
Hi Nayuta,
You can change computer name as the following WCD GUI tool:
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Wednesday, October 25, 2017 10:31 AM
Hi Karen,
ComputerName is just example. It's not my point.
I want to build provisioning profile with CLI.
And, with procedure wrote in below URL, I could not build it.
How can I build provisioning profile with GUI?
Is it impossible?
Thursday, October 26, 2017 10:22 AM
What's provisioning profile? What purpose did you want to achieve?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Thursday, October 26, 2017 11:28 AM
Hi Karen,
I want to generate customizations.xml and build ppkg file from with icd.exe cli.
Currently, we configuration pre-installed windows full manualy. But, it needs more and more time with the increasing number of machine setup. And, I want to construct the system with people include engineer. Then, I want to automate OOBE process of Windows pre-installed PC.
It is so useful to me that written in below URLs procedure. But, I'd failed following it in my environment.
Can I build provisioning package with icd cli using below URL or not? If I cannot, I'll work for gui automation with your answer above. But if I can, It is wonderful to other companies users and me.
Friday, October 27, 2017 6:39 AM
Hi Nayuta,
First of all, we could confirm that the command line could build a ppkg successfully.
Then according to your error message, it seems that there is something wrong with the customizations.xml template(computer accounts configuration). The correct template example:
Generally, we use the UI to create the template(create and save then check the customizations.xml in the project folder ). Here is a link for reference(check the create a provisioning package with multivariant settings part):
/en-us/windows/configuration/provisioning-packages/provisioning-multivariant
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Wednesday, November 1, 2017 9:59 AM
Hi,
Was your issue resolved?
If yes, please mark the helpful reply as answer in order that other community members could find the helpful reply quickly.
If no, please reply and tell us the current situation in order to provide further help.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Thursday, November 2, 2017 9:21 PM
Hi Karen,
I'm in trouble about it since now...
I'd create customizations.xml by icd.exe and build it with icd.exe cli. But, it was failed.
Could you write your customizations.xml by character, not image, here? I want to check different from your one and mine.
<?xml version="1.0" encoding="utf-8"?>
<WindowsCustomizations>
<PackageConfig xmlns="urn:schemas-Microsoft-com:Windows-ICD-Package-Config.v1.0">
<ID>{9f5029ea-c639-4c5c-98c4-6a651dd762b5}</ID>
<Name>Project_18</Name>
<Version>1.0</Version>
<OwnerType>OEM</OwnerType>
<Rank>0</Rank>
<Notes />
</PackageConfig>
<Settings xmlns="urn:schemas-microsoft-com:windows-provisioning">
<Customizations>
<Common>
<Accounts>
<ComputerAccount>
<Account>admin</Account>
</ComputerAccount>
</Accounts>
</Common>
</Customizations>
</Settings>
</WindowsCustomizations>
Friday, November 3, 2017 9:28 AM
Hi Nayuta,
After a deep test, I found that the “Computer Account” parameter is not supported with the ICD command line.
I checked the icd.log and found that those parameters should be based on the “C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Imaging and Configuration Designer\x86\Microsoft-Common-Provisioning.dat”. I tested the “Computer Account” parameter on Windows 10.1607, Windows 10.1703, Windows 10 1709. Both of them won’t support this parameter.
For the latest windows 10.1709 ADK, those parameters are removed from the WICD UI, too. Only the “Azure” account parameter was supported for the “Accounts” parameter.
So we’d better to use the latest ADK to build the provisioning package in case some parameters are no longer supported.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Wednesday, November 8, 2017 9:11 AM
Hi Nayuta,
First of all, I would make an apology that I have missed the point to change the store file and thanks for updating.
I have tested with the desktop store file and it worked. I am glad we have figured out the issue finally. I have been very impressed with your high level of technical proficiency. It is my pleasure to work with you.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Thursday, November 9, 2017 6:18 PM
Hi Karen, I'm relieved to see it worked in your environment. Resolving this problem without your works are impossible. It is glad for me to work with you on this problem. Very thanks for your cooperation!