Driver Pack No Longer Being Applied During Task Sequence

Question

Hi all,
So... this week a really strange issue manifested itself. I've been trawling through logs for the last day and I don't seem to be getting anywhere.
A task sequence, which has been working for months and hasn't been changed, all of a sudden decided to start throwing error code 0x87D00269 yesterday. It was at the stage where applications that are installed during the task sequence started to
install.
So after a looking into the error, it seems the machines are unable to download the packages, possibly through not being joined to the domain. At this stage in the task sequence, the machine should definitely be joined to the domain. We have
the command support console enabled, so I hit F8 and tried to ping the MP and the DP. Nothing. Ran ipconfig, nothing listed under the adapter. Very odd. So I checked the NIC on the back of the machine and it was up, so I booted from the task sequence
media USB stick again and hit f8. Ran ipconfig and the machine had picked up an address from DHCP no problem and shortly after, the task sequences available to the machine loaded. So I started the task sequence again and it started fine, formatted
the disk, downloaded the W7 pro x86 image, applied it, downloaded the driver pack and seemingly applied the drivers (according to the task sequence), then the machine rebooted. It started to go through the installing drivers phase (the black screen
with the sunrise), which seemed to take a longer than normal. The machine rebooted and sat at the applying settings stage for a long while, which also seemed odd and I remarked the graphics drivers didn't seem to be installed because the screen resolution
was set really low. Of course at this stage, F8 doesn't work so I waited until just before the applications started to install again. Pressed F8, ran ipconfig and no IP address. So rather than wait for the task sequence to fail again, I manually powered off
the machine and powered it back on.
So the machine boots, still with the low resolution, comes to the login screen and at this point, it's clear the machine hasn't joined the domain. I logged in with local admin account and it became clear none of the drivers had installed from the driver
pack. This is a driver pack that has run absolutely fine for months and as far as I'm aware, nothing has changed so I'm a little bit confused as to why it would just stop working.
I can't see anything in the smsts log that would explain what's happening and I've looked through the dism log but I can't find anything relevant in there.
Any ideas on where to go? This is happening on multiple machines of the same type.

Answer 1

Hi,
0x87D00269  CCM_E_REQ_MP_NOTFOUND
Ran ipconfig, nothing listed under the adapter.
These evidence indicate that no network driver in boot image. Is this a customized boot image? Is the machine a new model?
Press F8, run wpeinit to initialize network. If this is not working, re-add driver to boot image and try again.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]
Hi Daniel,
The boot image hasn't been modified and this machine is the exact same model as one built just a few weeks ago, with the exact same hardware. I know this because I've compared the hardware IDs of the devices side by side and they're identical.
I'm sorry but I don't follow. This issue only occurs after the driver pack downloads and (allegedly) applies. Up to that point, the machine has connectivity to the DP/MP and downloads and runs the first sections of the task sequence without issue. If I hit
F8 prior to the drivers being applied, I have my adapter listed and, of course, an IP address. That to me suggests the generic drivers already in the boot image work fine and don't need to be altered.