Windows Thread, XP SP3 Sysprep Domain Join 'weirdness' in Technical; Hi folks
I have a flat XP SP3 image with some network drivers added into the flat image, which sits ...
20th July 2010, 01:07 PM #1
- Rep Power
XP SP3 Sysprep Domain Join 'weirdness'
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?
IDG Tech News
20th July 2010, 01:15 PM #2
Are the network drivers signed?
20th July 2010, 02:02 PM #3
- Rep Power
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.
By JonR in forum O/S Deployment
Last Post: 3rd June 2009, 06:15 PM
By machin05 in forum Windows
Last Post: 30th September 2008, 11:07 PM
By link470 in forum Windows
Last Post: 8th September 2008, 01:55 AM
By saundersmatt in forum Windows
Last Post: 22nd May 2008, 10:38 PM
By MGSTech in forum Windows
Last Post: 7th May 2008, 12:42 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)