Re: [MDT-OSD] NIC not loading in WinPE 5.1
which version number of the driver are you injecting? To be sure, you are loading the windows 8.1 driver into the boot image, that is what pe 5.1 requires. - Original Message - On a Dell Optiplex 980, when booting from a USB stick with a WinPE 5.1 image created by SCCM 2012/MDT 2013 I am not getting an IP address. I am pretty sure I have the correct driver loaded in the WIM, but for some reason it is not loading correctly and then I do not get an IP address. I am able to find the correct driver in the X:\Windows\INF folder in the Boot Wim when booted from the stick as “OEM28.inf” – so the driver is injected properly as far as I can tell. I am able to load the driver using “drvload oem28.inf” from a command prompt. When I load the driver in this way and do “wpeutil initializeNetwork” then I get an IP address. So I think I have the right driver in there, but it is just not being detected correctly. Does anyone have any tips? I am pretty sure the ven/dev code for the Ethernet device in the Optiplex 980 is 8086/10EF- and that code is listed as supported in the driver that gets loaded by adding the drivers to the WIM (as evidenced by OEM28.inf Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.
[MDT-OSD] NIC not loading in WinPE 5.1
On a Dell Optiplex 980, when booting from a USB stick with a WinPE 5.1 image created by SCCM 2012/MDT 2013 I am not getting an IP address. I am pretty sure I have the correct driver loaded in the WIM, but for some reason it is not loading correctly and then I do not get an IP address. I am able to find the correct driver in the X:\Windows\INF folder in the Boot Wim when booted from the stick as OEM28.inf - so the driver is injected properly as far as I can tell. I am able to load the driver using drvload oem28.inf from a command prompt. When I load the driver in this way and do wpeutil initializeNetwork then I get an IP address. So I think I have the right driver in there, but it is just not being detected correctly. Does anyone have any tips? I am pretty sure the ven/dev code for the Ethernet device in the Optiplex 980 is 8086/10EF- and that code is listed as supported in the driver that gets loaded by adding the drivers to the WIM (as evidenced by OEM28.inf Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you.
Re: [MDT-OSD] WDS getting corrupt
if someone was booting to that wim during the replace, it could do bad things. - Original Message - Hi Everyone, I am new to administrating to MDT and have encountered a problem 3 times. I am curious if I am doing something wrong. The problem is, is when I add drivers to the Out-of-Box Drivers folder, WinPE, I update the deployment share to generate new boot WIMS. I then import then into WDS ServerBoot folder by choosing the replace option for each x86 and x64 wim. I am not shutting the WDS service down … or anything else. I am supporting servers worldwide and on 3 occasions we could no longer boot into MDT even though 5 mins earlier we could. I then get an error saying Windows Deployment Service is corrupt and I am not able to recover from it even after running the commands to uninitialized and initialize the server. Is this just bad luck or am I not doing something correctly and breaking WDS? I am left having to remove WDS from the server, reboot and reinstall WDS to get it to work. Regards, Dave Landry
[MDT-OSD] WDS getting corrupt
Hi Everyone, I am new to administrating to MDT and have encountered a problem 3 times. I am curious if I am doing something wrong. The problem is, is when I add drivers to the Out-of-Box Drivers folder, WinPE, I update the deployment share to generate new boot WIMS. I then import then into WDS ServerBoot folder by choosing the replace option for each x86 and x64 wim. I am not shutting the WDS service down ... or anything else. I am supporting servers worldwide and on 3 occasions we could no longer boot into MDT even though 5 mins earlier we could. I then get an error saying Windows Deployment Service is corrupt and I am not able to recover from it even after running the commands to uninitialized and initialize the server. Is this just bad luck or am I not doing something correctly and breaking WDS? I am left having to remove WDS from the server, reboot and reinstall WDS to get it to work. Regards, Dave Landry
