sking Posted February 13, 2014 Report Share Posted February 13, 2014 So, after getting Lenovo's new 4th generation based Intel machines, I'm having some issues getting the keyboard and mouse to work upon starting up SmartDeploy. I've created a new BOOT.WIM with a platform pack from the M73 as well as a custom pack built with the M73's USB 3.0 drivers in the WinPE section. The second pack, and BOOT.WIM work sporadically - an issue I cannot figure out. The first BOOT.WIM, built from the unaltered M73 platform pack for Windows Deployment Services, does not ever work. It boots properly, and the SmartDeploy screen comes up, but the keyboard and mouse are no longer detected and no longer work. I'm not able to get any kind of log file or see where the issue is. Is there a driver for the M73 that controls the USB hub that is missing or is there a reason why a basic HID device would fail in the WinPE environment? Link to comment Share on other sites More sharing options...
Allen Marsh Posted February 13, 2014 Report Share Posted February 13, 2014 We've seen issues with these new ThinkCentre's if the USB drivers are in PE. So, can you build boot media from just the single M73 pack from our website? Can't be combined with any other pack. This pack does not have USB drivers in the Windows PE node, and that has fixed the same issue on the M93. Thanks, SmartDeploy Support Link to comment Share on other sites More sharing options...
sking Posted February 13, 2014 Author Report Share Posted February 13, 2014 Well I'll be. Under preliminary testing, that seems to have fixed the issue. What I have to figure out now, is how it to make it work with the rest of the models that we work with. In your testing with the M93, were you able to add other network drivers to the platform pack to work with other machines or was its success limited to being isolated to the single set of ethernet drivers? Link to comment Share on other sites More sharing options...
SmartDeploySupport Posted February 14, 2014 Report Share Posted February 14, 2014 We had found success in isolating the drivers, although it really depends which models are imported into the combined pack. We would advise importing one pack at a time to isolate which pack is causing the issue. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now