Jump to content

Recommended Posts

Posted (edited)

Hello All,

 

I am attempting to deploy Windows 7 to HP AIO machines. I have been sucessful in creating the .wim files. However, once the client machine PXE boots, I have no keyboard or mouse. I have captured drivers from a functional HP AIO (a machine identical to what will be used in the deplotment) and imported them into the boot.wim. I am assuming this is a USB 3.0 issue as I am aware usb 3.0 isn't native to Win 7. This is why I captures all drivers from an exact system to use for the deployment.

 

Can anyone hepl me out here? Thanks in advance!

Edited by greenkeyTN
Posted
Instead of capturing the drivers I would download them from HPs website and then add the USB 3 drivers to the image via SCCM.
Posted
If there's not a specific USB driver on their site you might have to do a bit of research to find which driver package contains them as I've seen it where they are part of the Chipset in the past.
Posted

Fazza,

 

I believe you are correct. The drivers are part of the chipset on this machine. I have tired inserting many different ubs 3.0 drivers into the boot.wim using WDS and MDT. No luck. This is why I extracted the drivers from a machine that was functioning. My thoughts were, hey if this machine's keyboard and mouse are working, then it's drivers should be good to insert into the boot.wim. Still no lucj with that either. The PEX boot works as it should, however, I can't proceed due to no keyboard or mouse.

Posted

Snoochie,

 

I don't think my BOIS will allow me to diable them. I have looked and found nothing. I have tried unplugging the keyboard, relocating ports, no luck. I have tried different keyboards as well.

 

I will try your link for this next go around.

Posted

Ok, I found the chipset drivers, tried inserting them using DISM GUI. No change. I still get to the "User Credential" screen with no keyboard or mouse. Does anyone have any other suggestion? I am running out of ideas..

 

Thanks in advance!

 

More Details:

Machine: HP 24-B016 AIO

OS: Windows 7 PRO

Posted
Ok, I found the chipset drivers, tried inserting them using DISM GUI. No change. I still get to the "User Credential" screen with no keyboard or mouse. Does anyone have any other suggestion? I am running out of ideas..

 

Thanks in advance!

 

More Details:

Machine: HP 24-B016 AIO

OS: Windows 7 PRO

 

I haven't done it for a while, but two things that you want to check is that the driver has actually been applied in DISM Gui. I think there was something you have to do to before saving it.

 

Also, you might need a different driver because you're booting into Win PE rather than Win 7.

 

Sorry that i'm not much more help, it was a while ago when i did this.

  • Thanks 1
Posted

Authur,

 

Thank you for your reply! Could you explain your question? :) I have used both DISM GUI and WDS/MDT to insert many driver/driverpackages during this process. Regarding the install.wim, I haven't attempted adding drivers to it, unless MDT does that when creating the image. Also, I haven't been able to locate "PE" drivers. I have been using drivers found related to windows 7 and my hardware. Maybe I am looking at this incorrectly. Being that I am faily new to WDS & MDT, I am all for being educated on the matter. :)

 

Thanks

Posted
OK, I now see that there could be several indexes in the boot.wim. It could be possible that I've been adding drivers to only one of those. Assuming that the indexes are x64 and x86. How do I know which index MDS is writing to?
Posted

Arthur,

 

You nailed it man! I ran back through the DISM GUI and there it was "index" drop down. I mounted both indexes with the drivers I had orginally captured from my client PC. Copied the boot.wim to my images folder, added it to WDS boot images, booted my test pc via PXE network, PC booted as it should to the setup and with keyboard and mouse functioning!!!

 

Thanks for pointing me in the right direction!!

Posted
OK, I now see that there could be several indexes in the boot.wim. It could be possible that I've been adding drivers to only one of those.

Yeah. That's an easy thing to do. I'm glad to hear you have sorted it now. :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...