intel I219-LM - Optiplex 7060 - installation problem network drivers during Sysprep
-
Hi,
We encounter a problem with network chipset intel I219-LM during Sysprep step.
We have this problem only with Dell Optiplex 7060 and 7460 AIO.
Problem is that computer not add to Active Directory because have not network at this step (Sysprep).
We have test Dell drivers, Intel Drivers, WinPE drivers but not work.
What is strange is after Sysprep steps, when logon on Windows 10 network drivers are installed and network works.
We use UEFI.
We have also test to “legacy option ROMs” and “enable attempt legacy boot”.
Have you solution for this problem or ideas ?
See logs for this problem :
-setupapi.setup.log (log install drivers during sysprep):
PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028&REV_10\3&11583659&0&FE -> Configured [null] and unstarted (ProblemCode = 28, ProblemStatus = 0xC0000490, ConfigFlags = 0x00000040). Code 28 (CM_PROB_FAILED_INSTALL) Indicates that the installation failed and there is no driver selected for this device, although the kernel did not report a problem (and there is no DNF_XXX match for this the problem). This problem can be the result of an on-board system device (ISA timer, ISA RTC, RAM Memory, and so forth) that does not yet have an INF file-setupapi.dev.log (log install drivers windows, who works but after windows start normally):
{Install Device - PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028&REV_10\3&11583659&0&FE} 11:38:41.294 dvi: Device Status: 0x01802400, Problem: 0x1c (0xc0000490) dvi: Parent device: ACPI\PNP0A08\0 dvi: {Configure Device - PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028&REV_10\3&11583659&0&FE} 11:38:41.309 dvi: Device Status: 0x01802400, Problem: 0x1c (0xc0000490) dvi: Parent device: ACPI\PNP0A08\0 sto: {Configure Driver Package: C:\WINDOWS\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_6828698491cd7eda\e1d65x64.inf} sto: Source Filter = pci\ven_8086&dev_15bb&subsys_085a1028 inf: Class GUID = {4d36e972-e325-11ce-bfc1-08002be10318} inf: Class Options = Configurable inf: {Configure Driver: Intel(R) Ethernet Connection (7) I219-LM} inf: Section Name = E15BB.10.0.1 inf: {Add Service: e1dexpress} inf: Start Type = 3 inf: Service Type = 1 inf: Error Control = 1 inf: Image Path = \SystemRoot\System32\drivers\e1d65x64.sys inf: Display Name = Intel(R) PRO/1000 PCI Express Network Connection Driver D inf: Group = NDIS inf: Created new service 'e1dexpress'. inf: {Add Service: exit(0x00000000)} inf: Hardware Id = PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028 inf: {Configure Driver Configuration: E15BB.10.0.1} inf: Service Name = e1dexpress inf: Included INFs = pci.inf inf: Config Flags = 0x00000000 inf: {Configure Driver Configuration: exit(0x00000000)} inf: {Configure Driver: exit(0x00000000)} flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_6828698491cd7eda\e1d65x64.sys' to 'C:\WINDOWS\System32\drivers\e1d65x64.sys'. flq: Copying 'C:\WINDOWS\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_6828698491cd7eda\e1d65x64.din' to 'C:\WINDOWS\System32\e1d65x64.din'. dvi: Existing files modified, may need to restart related services. sto: {Configure Driver Package: exit(0x00000bc3)} dvi: Restart required for any devices using this driver. dvi: Install Device: Configuring device (oem4.inf:pci\ven_8086&dev_15bb&subsys_085a1028,E15BB.10.0.1). 11:38:41.356 dvi: Install Device: Configuring device completed. 11:38:41.356 dvi: Device Status: 0x01802000, Problem: 0x0 (0x00000000) dvi: {Restarting Devices} 11:38:41.356 dvi: Start: PCI\VEN_8086&DEV_15BB&SUBSYS_085A1028&REV_10\3&11583659&0&FE ! dvi: Device pending start: Device has problem: 0x38 (CM_PROB_NEED_CLASS_CONFIG), problem status: 0x00000000. dvi: {Restarting Devices exit} 11:38:41.403 dvi: {Configure Device - exit(0x00000000)} 11:38:41.403 dvi: Device Status: 0x01802400, Problem: 0x38 dvi: {Install Device - exit(0x00000000)} 11:38:41.403 dvi: {Core Device Install - exit(0x00000000)} 11:38:41.403 dvi: Waiting for device post-install to complete. 11:38:41.403 dvi: Device post-install completed. 11:38:41.700 ump: {Plug and Play Service: Device Install exit(00000000)}-setupact.log:
Info [DJOIN.EXE] Unattended Join: JoinDomain = [mydomain.local] Info [DJOIN.EXE] Unattended Join: JoinWorkgroup = [NULL] Info [DJOIN.EXE] Unattended Join: Domain = [mydomain.local] Info [DJOIN.EXE] Unattended Join: Username = [toto] Info [DJOIN.EXE] Unattended Join: Password = [secret not logged] Info [DJOIN.EXE] Unattended Join: MachineObjectOU = [OU=xx,OU=xx,OU=xx,OU=xx,OU=xx,DC=mydomain,DC=local] Info [DJOIN.EXE] Unattended Join: DebugJoin = [true] Info [DJOIN.EXE] Unattended Join: DebugJoinOnlyOnThisError = [NULL] Info [DJOIN.EXE] Unattended Join: TimeoutPeriodInMinutes = [NULL] Info [DJOIN.EXE] Unattended Join: Enabled DC Locator ETW tracing. Log file: C:\WINDOWS\Panther\UnattendGC\UnattendedJoinDCLocator.etl Info [DJOIN.EXE] Unattended Join: Checking that auto start services have started. Info [DJOIN.EXE] Unattended Join: Calling DsGetDcName for mydomain.local... Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 10 seconds... ...same error during 15 minutes Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 10 seconds... -
I have resolve this with add this in my xml unattend file :
Pass Specialize : Microsoft-Windows-Deployment
<RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Description>Injection Pilotes</Description> <Path>pnputil /add-driver C:\drivers\*.inf /subdirs /install</Path> </RunSynchronousCommand> </RunSynchronous> -
This is a great example of why I force install all drivers when I want, not when Windows wants to.
I do this in setupcomplete.cmd
REM "Driver Installation Pass 1 of 3" "C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se REM "Driver Installation Pass 2 of 3" "C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se REM "Driver Installation Pass 3 of 3" "C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se REM "Cleanup" del /Q /F c:\windows\system32\sysprep\*.xml del /Q /F c:\windows\panther\unattend.xml rd /s /q C:\temp REM "Shutdown when complete" shutdown -s -t 5 -
Thanks for your response.
SetupComplete is launch at the end of Sysprep steps.
Install drivers here not resolve problem where my computers not add to active directory like is set in sysprep.I go to try same in sysprep :
<Order>1</Order> <Description>Injection Pilotes</Description> <Path>C:\temp\drivers\dpinst.exe" /path "C:\temp\drivers" /q /se</Path> </RunSynchronousCommand> </RunSynchronous> -
I have resolve this with add this in my xml unattend file :
Pass Specialize : Microsoft-Windows-Deployment
<RunSynchronousCommand wcm:action="add"> <Order>1</Order> <Description>Injection Pilotes</Description> <Path>pnputil /add-driver C:\drivers\*.inf /subdirs /install</Path> </RunSynchronousCommand> </RunSynchronous> -
I’m glad that method works for you. It’s not ideal for me as I must account for 30+ different makes/models of systems with wildly different driver requirements and some systems with tiny storage. Adding all of my drivers whether they get installed or not bloats up the driver repository unnecessarily by several GiB.
-
@sudburr
In my case in my postinstall script (fog) i copy only driver for concerned model, not all drivers of all model.
After this command in sysprep add driver who are copied in c:\drivers in the driver store.
For not doing this for all model i go to add “if” in my postinstall script to add this in my xml only for model 7060 and 7460