New
#170
Are you connected it to a domain when you deploy? This may not be the same, but in Windows 8.1, CopyProfile would keep the Start layout under two conditions : (a) if you were deploying Pro if connected to a domain and (b) Enterprise whether connected to a domain or not.
Of course, I believe now you can save the layout into an XML file and then script an export after deployment, so that may be the official way now...not sure.
So I've got my image working pretty good so far with the unattend.xml file which copies the default profiles, sets taskbar items, runs first logon commands, etc.
Now that step has been completed I then decided to jump on the autounattend.xml file to allow the installation to proceed with no interaction from the user short of booting off the media. This is where things get strange. It works fine, we boot off the USB stick and Windows 10 begins to install with 0 prompts for configuration. However, once it boots to the installed image I find that the unattend.xml file is no longer being applied to the image. Default profile did not copy, taskbar items did not map, first logon commands did not run, etc. Why would this be? I've tested the same image with and without the autounattend file and only have issues when the file is used. Below is my autounattend.xml file.
Code:<?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <SetupUILanguage> <UILanguage>en-US</UILanguage> </SetupUILanguage> <InputLocale>en-US</InputLocale> <SystemLocale>en-US</SystemLocale> <UILanguage>en-US</UILanguage> <UserLocale>en-US</UserLocale> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DiskConfiguration> <WillShowUI>OnError</WillShowUI> <Disk wcm:action="add"> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> <!--System partition--> <CreatePartitions> <CreatePartition wcm:action="add"> <Order>1</Order> <Type>Primary</Type> <Size>500</Size> </CreatePartition> <CreatePartition wcm:action="add"> <Order>2</Order> <Type>Primary</Type> <Extend>true</Extend> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Format>NTFS</Format> <Label>System Reserved</Label> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> <!--Windows partition--> <ModifyPartition wcm:action="add"> <Format>NTFS</Format> <Label>Win7Ent</Label> <Letter>C</Letter> <Order>2</Order> <PartitionID>2</PartitionID> </ModifyPartition> </ModifyPartitions> </Disk> </DiskConfiguration> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>2</PartitionID> </InstallTo> <WillShowUI>OnError</WillShowUI> <InstallToAvailablePartition>false</InstallToAvailablePartition> </OSImage> </ImageInstall> <UserData> <AcceptEula>true</AcceptEula> </UserData> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/win10/sources/install.wim#Windows 10 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
I'm using Windows 10 Enterprise and Education, both showing the same symptoms whether joined to a domain or not. The same process which I mentioned earlier was also used on Windows 8.1 Enterprise, but the joining to a domain never made any difference because it always worked to copy my start menu layout.
Have you tried the XML export and import? You export the one you want, and then import that same one after generalization.
Using Import-StartLayout to a local system
This is basically how you have to set file associations and default programs, too: export to file before generalization, run generalization, and export the file after generalization. That's how it was in Windows 8.1, too. CopyProfile no longer copies default programs and file associations.
It's best to script all this so you don't have to think about it.
Yes, I have tried the export/import method to copy the start menu however my start menu worked fine when I deployed the WIM file using DISM. Otherwise, with an unattend file in SCCM task sequence, the tiles were not deployed in the order I set them.
The weird thing is that my unattend file used to work just fine in Windows 8.1 deployment to copy my default profile, default associations etc... I guess that I need to test this out further to see what I can get out of it.
Hello, I'm trying to use the ADK to build my answer file but am getting this error when trying to Select Windows Image in the Windows System Image Manager. (Part 5 in this guide).
The ADK is version however 10.0.10240.16384 downloaded today. The install.wim is copied out from a Windows 10 Pro 10240 ISO downloaded today using the media creation tool. The D: drive is a partition on my SSD so it is writable.Code:16:23 : This application requires version 10.0.10240.16384 of the Windows ADK. Install this version to correct the problem 16:23 : 16:23 : Error opening Windows image at D:\install.wim. 16:23 : 16:23 : System.ComponentModel.Win32Exception (0x80004005): An attempt was made to load a program with an incorrect format at Microsoft.ComponentStudio.ComponentPlatformInterface.WimFileHandle..ctor(String wimPath) at Microsoft.ComponentStudio.ComponentPlatformInterface.WimInfo..ctor(String wimPath) at Microsoft.ComponentStudio.ComponentPlatformInterface.Cpi.OpenWim(String wimPath) at Microsoft.ComponentStudio.ImagePicker.GetImageInfoFromPath(String path) at Microsoft.ComponentStudio.ImagePicker.ValidateImageFileOrFolder(String fileOrFolder)
I've seen some posts on other sites saying that Windows 10 Pro (build 10240) doesn't work and you must use Enterprise. Is that the case or am I making a mistake?
I am having the issue with start menu do not work when updated windows before sysprep......I wonder if I do it rightly or problem in Windows?? If I do not apply the patches updates before sysprep the problem stops.are we not allowed to do updates before sysprep??
Kari I read conversations I see 2 people have different opines but he stopped to argue so you continue and junking up thread now so if you do not stop I will ignore you to!!
He stopped by telling I am constantly attacking him, only because he could not admit being wrong and not knowing what he does. The last drop for him was me providing evidence (video) showing how it is done correctly, he could not accept that. I stopped after explaining this, now you brought it up again. I had never again mentioned this conversation without your post.
Please ignore me, put me on your ignore list; I prefer to continue this conversation about Sysprep and its possibilities and issues with people who have at least some idea about what we are talking about and are not afraid to admit being wrong when that's the case.
Have a nice day!
Kari