Search the Community
Showing results for tags 'nic'.
Found 4 results
Hello all, I just received a batch of Dell Precision Tower 7810 workstations and I need to get them imaged and deployed. The issue I am having is with the NIC and some odd behavior during OSD and afterward. I have the driver from Dell that came from their system driver pack (http://en.community.dell.com/techcenter/enterprise-client/w/wiki/7556.precision-t7810-windows-7-driver-pack) and it seems to install okay. However, I can't get any of my applications to install during the TS with this driver. I can hit F8 and ping my DP and everything, but nothing will download and install. Once the TS finishes, and the machine boots into Windows, the taskbar shows the NIC as disconnected, but I have a network connection. The machine is added to the domain during the TS without issue. The SCCM client is installed during the TS, but it won't communicate with my management server once booted into Windows. I'm able to ping internally and externally without issue. I saw the comment on the Dell CAB webpage where the user used a newer driver, and I tried that as well with no success. So far, I have tried: the driver that comes in the Dell driver pack the driver download individual from Dell for this model the driver off Intels website the driver I pulled off a computer that came from Dell before I attempted to image with my organizations image All of these drivers exhibit the same behavior. The computer right out of the box using Dells image works fine. Anything done with OSD, and there are problems. I have no issues imaging any other machine whether it be made from Dell or HP For giggles, I installed Windows manually off a USB thumb drive and used the same drivers as above, and everything worked fine. I'm really scratching my head here on this one. I would say there is a problem with my image, but I don't have any issue with any other model across several vendors using the same image, so now I'm really at a loss. None of it really makes any sense at this point. The Dell T7810 uses the Intel I217-LM NIC, which I have other models that use as well, but the T7810 is the only one giving me issues. Any help/advice is greatly appreciated
Hallo everyone, After MDT have been running the first Windows Update of eighth it returns in Windows to continue the TS it fails because the NIC gets an IP to slow. After 2. sec the LAN icon change and we're able to press retry and it will continue. <![LOG[Error searching for updates: ERROR_INTERNET_TIMEOUT: Retry! (-2147012894)]LOG]!><time="16:06:12.000+000" date="01-29-2016" component="ZTIWindowsUpdate" context="" type="1" thread="" file="ZTIWindowsUpdate"> This is the same for all our computermodels. Anyone have an idea what it can be or how to fix it? Server Setup: Windows 2012 R2 MDT 6.3.8298.1000 ADK 10.0.26624 Default Windows Update Script: NIC Status from Windows (2-4 sec.): MDT Error message: (If I click "forsøg igen/Try again" it continues.)
Hi, I have a really odd problem that I’ve never seen before when deploying an OSD TS to an HP ProBook 6560b. I’m deploying Windows 7 Enterprise 64bit using Confg Manager 2012 SP1. I have the latest driver pack for this model from HP (sp61783.exe), and the correct driver pack is selected in the TS using a WMI query. The driver package is installed OK, however the wrong NIC driver is installed. The NIC is an Intel 82579V (PCI\VEN_8086&DEV_1503), however the driver for the 82579LM (PCI\VEN_8086&DEV_1502) gets installed. Checking the setupapi.dev.log I can see that in the first boot session (i.e. after SCCM has copied the drivers to the driverstore and the laptop reboots to install the drivers) the hardware is detected as DEV_1502. The 82579LM driver is selected and installed, however the device fails to start. After the next reboot in the TS the setupapi.dev.log shows that it has detected DEV_1503 and the 82579V driver is installed and the device starts. Things I’ve tested so far: A driver package with only the NIC driver in case another driver was causing the issue. Installing no drivers at all – the device is still detected as the 82579LM. Creating a new driver package. Several different versions of the driver including the latest from Intel rather than HP. A different install.wim (the original just has IE9 slipstreamed, but I get the same result from the install.wim from the Win7 ISO). Running the TS using standalone media. A couple of interesting things: It’s not a hardware problem as it build correctly in our SCCM 2007 environment – using the same drivers. The same TS works correctly on a ProBook 6570b and this has the same 82579V NIC. If I install manually using the Windows 7 DVD the device is detected correctly as the 82579V. Any help VERY much appreciated! first_boot_dev_1502.txt second_boot_dev_1503.txt
Hi Currently using SCCM2007 and have been building many machines without issue. We have recently purchased a large amount of new HP 4535 laptps and are having particulat issues getting them to build on SCCM. Have created the task sequence, collection added the laptop to SCCM ect but when booting to image the laptop it fails. The laptop PXE boots and loads WinPE but then on prepares itself and just reboots. I have got into the command prompt in PE and can see that it is not connecting to the network so tried to inject the Realtek GBE family drivers into the boot image both within SCCM and using the ImageX command and no matter which drivers i pick it seem to fail to add them into the image. Any suggestions? Thanks