Hardware agnostic image?
I know this is offtopic but I just want try if someone here have a solution, otherwise I will probably have to jump to MDT. I want to make a hardware agnostic W10 image as we have 3 different models of computers. When we were with W7, there was no problem as I can inject drivers after the image deployment process and before the computer first start and Windows can find those drivers (I even had a post in old CrucibleWDS forums with the process). But it seems that in Windows 10 I can no longer get Windows to install drivers on time. At least not the network drivers that computer needs to join the domain.
I have tried to add drivers to C:\Windows\System32\DriverStorage\FileRepository and C:\Windows\INF but without luck. I have also added a custom folder C:\Drivers to registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\DevicePath and I get the network driver installed but after the reboot it does after it has failed to join to the domain.
So does someone knows a proper way to inject drivers to the computer before the first start so the setup process can find them?
Thanks a lot! Any help is welcome.
I believe this process did change for Windows 10 and you now need to specify the drivers in the sysprep answer file. The registry method no longer works.
Something like this.
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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">
<PathAndCredentials wcm:action="add" wcm:keyValue="1">
Thanks for the answer. I had already done that but didn't work. If I understand it correctly, using CD we bypass the WinPE and OfflineServicing passes altogether, so it is not going to work. I have to find something that works on the Specialize pass or that can be done from Linux (at deployment phase).
Windows installation stages: https://technet.microsoft.com/fi-fi/library/cc749307(v=ws.10).aspx
I see now. I don't really understand the workflow for Sysprep as I don't use it, but makes sense now. It seems there may not be a solution to this one, and like you said it may be time to move on. Lately I have been thinking about stopping development of CloneDeploy, and the more I think about it the more I think I'm done.
Hei man, I can understand you. Anyway whatever you decide I just want to thank you for your effort and your time. I wish I can help more but I just don't have the time (and probably I'm not as talented as you).
Thanks, I'm not that talented, I have just put the time in. I'm at least going to release 1.3.0 since it's already about 80% done and we'll see where it goes from there. If you ever figure out this driver issue let me know. Why does Windows always need to change things and I thought Windows 10 was supposed to have many generic drivers built in to at least get you through sysprep.