Windows 7 and New Laptops

[Ahmed.IT]

Dear All,

 

I am facing small problem in deploying windows 7 to New HP laptops for example 8440p laptops.

 

First my problem was, the boot image was unable to detect the network driver for 8440p. And I fixed it by injecting the driver into the image and the problem solved.

 

Now my problem is after the task sequence install windows 7 OS and it reach to install the software, it get the error of unable to detect network driver and it fail to install or continuing the TS because it can't install or detect the network driver.

 

I added network driver package to the TS but with no use.

Anyone solved this problem before? or any solutions?

 

Regards,

Ahmed

[Eswar Koneti]

Post smsts.log ?

 

 

[Lucid]

First off, when you say your boot image didn't have the driver and you injected it, do you mean you added it in the ConfigMgr console and generated a new boot image, and then created a new CD? You need to make sure the correct driver is added to the SCCM environment, and made available to both your boot image and the deployment Task Sequence (depending on how you set up your TS you may need to add a WMI query to make sure it uses that model's driver package).

 

So are you sure you...

Added the right driver?

Created a new boot image?

Have your task sequence using the added driver?

[Ahmed.IT]

what I did was injecting the driver in to SCCM default boot image and it worked perfectly .Then in the OSD TS I created a task to install same driver from drivers package (I created Drivers Package for the laptop to install only Network driver)

 

I tested the driver on same laptop and it worked before I add it in to TS.

[Lucid]

Well, as long as you added the driver to the boot image, and didn't crack open the boot.wim file itself and inject it, you should (theoretically) be getting the right driver during the boot process. And as long as you don't have a bad WMI query or something on the driver in your task sequence it should pick it up.

 

I think you may need to paw through your log files and/or post some of the errors listed in them.

 

If you've added Command Line Support to the boot image, after the imaging process errors out, you can boot from your CD again, and once you're into Windows PE, press F8. You can then browse through the old install on the machine and snag the log files off of it (copy them to a USB key or a network share or something).

[Ahmed.IT]

which log file i should look into ??

[Eswar Koneti]

which log file i should look into ??

 

 

smsts.log ?