Sysprep +disabling the NIC

[Dos_Box]

Is there anyway I can stop sysprep disabling the NIC (drivers) so I can RIS the sysprepped image? I'm still faffing around with XP SP3 and have never needed to sysprep an image before when using RIS.

[Michael]

I would still recommend you run sysprep anyway, but chances are you're not using signed drivers for your network card. If you find signed drivers, that should solve the problem (theoretically).

[Dos_Box]

I think you have completely misunderstood the problem (the drivers are WHQL from M$ update anyway). I want to sysprep the image then be able to RIS it. I can't RIS the image if I can't access the network.

[Michael]

Apologies for mis-understanding. You'd be much better off using RIprep. Hope this helps.

[ricki]

Hi

I dont know the answer and am talking a bit off the top of my head, but does sysprep normally disable the nic card or is it just on this machine.

If it normally works could you not install another nic card to take the image.

Just an idea.

Richard

[Dos_Box]

I usually use Riprep, but due to the SP3 blue screen and reboot issues I am trying out everything I can. SP3 will deploy from a CD based image, but anything Riprepped goes into the reboot cycle once deployed. The errors point to a driver issue, so I'm trying a variety of things to get SP3 deployed with my images.
Oh, and these are SFF Dell PCs with zero room for expansion.

[Michael]

I dont know the answer and am talking a bit off the top of my head, but does sysprep normally disable the nic card or is it just on this machine.

No sysprep doesn't, which is why I suggested it may be to do with unsigned drivers. Using Riprep is definitely the recommended method.

I did a bit of googling and I think I may of found the answer. When you first configure RIS it asks for the OS media to install on the server. Chances are you used an XP SP2 disc. You should be able to successfully upload the SP3 image, however when applying the image it will mix files from the SP3 image and the XP SP2 disc you installed on the server, which is creating the BSOD.