Windows 10: Windows 10 Image - Customize in Audit Mode with Sysprep
I have a problem. I made an image, exatly so like this guide said. But after the installation is the windows actived with a blocked key. I dont know this key. The Windows Image is from MedienCreationTool. The apps and the options work.
I read the entire thread but there is no mention on how to inject drivers and allow to be installed on windows 10 during sysprep phase. I have a bout 28 model that I need to install the drivers at build time. I have one universal image and inject the drivers of the specific model to c:\windows\inf and it detect the drives during sysprep which works without issues in windows 7.
I am totally lost on how this process is done exactly in windows 10. Copy(injecting) the drives from winpe boot disk to c:\windows\inf will not allow the drivers to be installed during sysprep phased in windows 10. Does anyone know how exactly to do this or point me in the right direction? I googled for weeks without any solid answer.
From how i understand syspreps works you should be able to do specify driver installation within your unattend.xml. I'm not sure you can do it for multiple different models unless you are using MDT or SCCM. You can specify it your windpe pass of the unattend if you have boot, and non-boot critical drivers using the component Microsoft-Windows-PnpCustomizationsWinPE, and setting a driver path. If you only have non-boot critical drivers specify it in auditSystem pass in your unattend file using the component Microsoft-Windows-PnpCustomizationsNonWinPE . I have only started messing with unattend files since Windows 8. Links to where if found the information.
Microsoft-Windows-PnpCustomizationsNonWinPE - Microsoft-Windows-PnpCustomizationsNonWinPE
Microsoft-Windows-PnpCustomizationsWinPE - Microsoft-Windows-PnpCustomizationsWinPE
Thanks joelh. I will look into it. I will test the Microsoft-Windows-PnpCustomizationsNonWinPE and see if that works. I have it setup to login as local admin as was done in XP, 7. I don't want to login to audit mode but just login to local admin after detecting and installing the drivers by using sysprep.exe /generalize /oobe /shutdown /unattend:c:\windows\system32\sysprep\sysprep.xml. The documentation seem to be saying that it HAS to login to audit mode to install the drivers.
Confirmed: you cannot update to Build 10586 (or any other build) while in Audit Mode. You will receive the following message upon attempting this:
"You can't install Windows while running in Audit Mode."
I cannot believe how many "gotchas" Windows 10 has. Every time you think you have it figured out, they put another obstacle in the way. It's really getting frustrating.
What this means is that you'll need to recreate your image every 3 to 4 months. In enterprise (and especially education), that's unacceptable. Provisioned packages only go so far and can't be used in many environments.
Came across this this morning. Seriously, this is just nuts. If we have to redownload WADK to create a new answer file and redownload the iso image of the latest build to do it ALL over again, again, this just crazy. I mean come on right.
And the kicker is that this is apparently intentional!
Coke Robot said:
Does Microsoft really not care about enterprise/education at all? It's beginning to seem like a joke, with all the obstacles they're throwing up. There is no way they are this short-sighted...right?
In fact, if we have to recreate the image this often, why even have Audit Mode, anymore? What's the point?
I think they're trying encourage not using Audit mode and doing the wipe and reload method of deployment but running build upgrades every so often that may or may not botch an entire system....
Thing is, not every enterprise/educational/IT setup functions in such a way where that's feasible to do. There are still MANY setups where there is typical either a single or multiple customized images used for deployment to target certain machines and their usages. It's such a hindrance when things like this occur. It's like, really?
This along with not being able to easily setup a custom Start experience is killing me.
Has anyone tried sysprepping with build 1511? It was just released 4 days ago on the 12th of November.
Finnish but not finished
It's the same. CopyProfile works but it leaves built-in admins desktop to end user's Quick Access, as well as built-in admin's recent documents, for instance the answer file used.
How to Customize Default User Profile for New Accounts in Windows 10
Default User Profile is stored in a hidden folder in main profile folder Users. When a new user is created, either when installing Windows or any time later, Windows uses this...
how Customize the Windows 10 Log-On and Log-Off Screen in Build 10240? i like a black color! :confused:
I'm trying to sysprep a Windows 10 Enterprise build 10162 so that i can capture, but i'm getting some errors and hope you guys have some sort of solution.
I've tried removing The upgrade key in HKLM system, but that didn't help.
I've tried to go into AUDIT mode to change the User profiles over to a different HDD on 10122. I get a fatal sysprep error. All i've used is an answer file with User profiles set to I:\Users
Program Data is not moved, copyprofile not set. Only...
Read more: NCC Group to audit OpenSSL for security holes | ZDNet