XP SP3 Sysprep Domain Join 'weirdness'

[_techie_]

Hi folks

I have a flat XP SP3 image with some network drivers added into the flat image, which sits on a WDS mixed mode 2003 box.
I have a HP 530 laptop. This images fine with the intel network driver (PRO 100/VE) as it goes. No other drivers end up in the image.

I then capture the fully setup, completed machine. I have sysprepped the machine, all goes successfully (reseal, mini-setup, shutdown).
As part of sysprep, I make it an unattended install, with license key etc etc. This works okay. I can then capture the image as a wim back up to a new x64 2008 r2 WDS server, using WinPE.

I have done the same thing with other machines, and no problems!

My problem occurs with this laptop, when it tries to do a domain join, it fails, saying it cannot join the domain. I presume that this is because it is missing some network drivers, or something similiar. And yes, I have checked the network connection, thrice!

Is there anyway to spoon feed sysprep the network drivers for the laptop, during the sysprep process? Is there anything else worth trying?

Cheers
_techie_

[Michael]

Are the network drivers signed?

[_techie_]

No idea...i guess I would have to do a basic build from a CD to find out...
I did add driversigningpolicy=ignore to the inf file, but no use.