This is the RealTek PCI GBE Controller, version 7.71.327.2013.
I’ve noticed the domain join step doesn’t appear to be working, even when it
has an IP (ours is set to run the domain join before we apply drivers). I see
this in the SMSTS.LOG:
==============================[ OSDNetSettings.exe ]===========================
OSDNetSettings 7/7/2015 4:21:47 PM 464
(0x01D0)
Command line: "osdnetsettings.exe" configure OSDNetSettings
7/7/2015 4:21:47 PM 464 (0x01D0)
Setting %SystemRoot% to "C:\WINDOWS" OSDNetSettings
7/7/2015 4:21:47 PM 464 (0x01D0)
Loading existing answer file "C:\WINDOWS\panther\unattend\unattend.xml"
OSDNetSettings 7/7/2015 4:21:48 PM 464 (0x01D0)
Configuring global network settings OSDNetSettings
7/7/2015 4:21:48 PM 464 (0x01D0)
Join type: 0 OSDNetSettings 7/7/2015 4:21:48 PM 464
(0x01D0)
Joining domain: csuchico.edu OSDNetSettings 7/7/2015 4:21:48
PM 464 (0x01D0)
Join OU:
LDAP://OU=CMGT,OU=ECC-Labs,OU=ECC,OU=LABS,OU=Departments,DC=csuchico,DC=edu
OSDNetSettings 7/7/2015 4:21:48 PM 464 (0x01D0)
Getting namespace "Microsoft-Windows-UnattendedJoin" for architecture "amd64"
OSDNetSettings 7/7/2015 4:21:48 PM 464 (0x01D0)
DNS domain: OSDNetSettings 7/7/2015 4:21:48 PM 464
(0x01D0)
DNS domain search order: OSDNetSettings 7/7/2015
4:21:48 PM 464 (0x01D0)
IP filter sec enabled: false OSDNetSettings 7/7/2015
4:21:48 PM 464 (0x01D0)
No adapters found in environment. Performing global configuration only.
OSDNetSettings 7/7/2015 4:21:48 PM 464 (0x01D0)
Writing configuration information to C:\WINDOWS\panther\unattend\unattend.xml
OSDNetSettings 7/7/2015 4:21:48 PM 464 (0x01D0)
Successfully saved configuration information to
C:\WINDOWS\panther\unattend\unattend.xml OSDNetSettings
7/7/2015 4:21:48 PM 464 (0x01D0)
Configuring "OSDNetSettings.exe finalize" to run on first boot OSDNetSettings
7/7/2015 4:21:48 PM 464 (0x01D0)
OSDNetSettings finished: 0x00000000 OSDNetSettings 7/7/2015
4:21:48 PM 464 (0x01D0)
Process completed with exit code 0 TSManager 7/7/2015 4:21:48 PM
864 (0x0360)
From: [email protected] [mailto:[email protected]] On
Behalf Of Chris Carbone
Sent: Tuesday, July 7, 2015 5:50 PM
To: [email protected]
Subject: RE: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
It took me a good week in a half and 20+ driver attempts for one of the new
Intel NUC’s. It was the Intel l218-V(3) NIC driver. Turns out I FINALLY found
the correct driver, and it was from 2013. The previous gen of NUC’s I had 0
issues with so go figure that one out. Anyway, the issue I had was when WinPE
booted and got to the “Preparing Network Connections” step, it would sit there
for a bit and then abort itself out and reboot the computer, instead of
prompting for password.
So it’s not the same issue but similar.
And just curious, after you run the TS and it fails if you look in device
manager does the NIC show installed? And I think the driver log is bdd.log? Can
look in there see if anything sticks out.
Good luck, I know how aggervating this can be.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Murray, Mike
Sent: Tuesday, July 7, 2015 6:40 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
OK, I’ve tried many methods, including what you suggested. My latest attempt
was only installing the NIC driver and nothing else. As soon as the computer
reboots and goes through setting up windows, devices, etc, then goes back into
the TS, the network connection is lost. I loaded this computer with a Windows 7
disk and used the same driver after installation, and it was the correct driver.
I’m at my wits end. Any other suggestions?
Thanks!
Mike
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Kent, Mark
Sent: Monday, July 6, 2015 9:55 AM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
Perhaps add the new NIC driver by itself, make its own category. Then add a
step to your task sequence. Do Apply Driver Package, choose that package, and
create a WMI query to filter out the 3020 only so that it doesn’t run on any
other models. Place this step AFTER your Auto Apply Drivers step. If it still
doesn’t work, perhaps flip around the driver steps and try once more.
Mark Kent (MCP)
Sr. Desktop Systems Engineer
Computing & Technology Services - SUNY Buffalo State
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Murray, Mike
Sent: Monday, July 6, 2015 12:49 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
The old ones are categorized differently. In the apply drivers step, I’ve only
selected the new driver category. I’ve also tried switching from “install only
the best matched compatible drivers” to “install all compatible drivers”.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Kent, Mark
Sent: Tuesday, June 30, 2015 4:04 PM
To: [email protected]<mailto:[email protected]>
Subject: RE: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
Do you categorize your drivers and if so, dud you pull the older ones out first
for that model?
Sent from my Windows Phone
________________________________
From: Murray, Mike<mailto:[email protected]>
Sent: 6/30/2015 6:13 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
I downloaded the latest driver pack and tried with it, same issue. :(
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Kent, Mark
Sent: Tuesday, June 30, 2015 10:41 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
Funny you should mention this because recently we had problems with the NIC on
the 9020’s, Win7 x64. And we have been imaging/deploying them for 2 years. I
uploaded the latest drive CAB’s for the 9020’s which fixed it. Still
perplexing.
Mark Kent (MCP)
Sr. Desktop Systems Engineer
Computing & Technology Services - SUNY Buffalo State
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Murray, Mike
Sent: Tuesday, June 30, 2015 1:31 PM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
We auto-apply based on the model. The drivers do apply, there just seems to be
an issue with the NIC driver either not existing or perhaps it’s the incorrect
driver.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Michael Timm
Sent: Tuesday, June 30, 2015 10:14 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
Are you auto applying drivers? Or is this a model specific task sequence?
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Aday, Karalene B (RCIS)
Sent: Tuesday, June 30, 2015 11:08 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] RE: Issues imaging OptiPlex 3020 - Win7 x64
We are having the same issue with the 9020’s.
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Murray, Mike
Sent: Tuesday, June 30, 2015 11:56 AM
To: [email protected]<mailto:[email protected]>
Subject: [mssms] Issues imaging OptiPlex 3020 - Win7 x64
3020’s are failing repeatedly when imaging via ConfigMgr 2012 OSD. After the
apply drivers step in the TS, it loses network connectivity. No IP address
whatsoever. I’m using a recent Windows 7 driver cab from Dell. Anyone else?
Best Regards,
Mike Murray
Desktop Management Coordinator - IT Support Services
California State University, Chico
530.898.4357
[email protected]<mailto:[email protected]>
________________________________
CONFIDENTIALITY NOTICE: This message is intended only for the use and review of
the individual or entity to which it is addressed and may contain information
that is privileged and confidential. If the reader of this message is not the
intended recipient, or the employee or agent responsible for delivering the
message solely to the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please notify
sender immediately by telephone or return email. Thank you.
This electronic mail transmission may contain confidential information intended
only for the use of the individual(s) identified as addressee(s). If you are
not the intended recipient, you are hereby notified that any disclosure,
copying, distribution or the taking of any action in reliance on the contents
of this electronic mail transmission is strictly prohibited. If you have
received this transmission in error, please notify me by telephone immediately.
