As an update to this, mounting the x86 WIM and adding those registry keys seems to have done the trick for me. Imaging seems to be running smoothly once again without having to fish around inside systems to pull memory. Thanks for that info!
-Richard Poole From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Friday, September 18, 2015 9:57 AM To: [email protected] Subject: RE: [MDT-OSD] Driver injection on Lenovo M79 w/ > 4GB of RAM We saw similar issues after our R2 upgrade with WinPE 5.0 x86, it was only on machines with > 4GB of RAM. Our solution was to switch from an x86 boot image to x64. We had a case open with Microsoft as well and they filed it as a bug. See attached for a little detail. Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Richard Poole Sent: Friday, September 18, 2015 11:44 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] Driver injection on Lenovo M79 w/ > 4GB of RAM Hey everyone, Wanted to see if anyone else was having imaging issues with some of the Lenovo M-series models (M78, M79, & M83) with Win8.1 x64. Right after the image install and driver injection (even if the driver package is completely blank), if the system has more than 4GB of RAM it will reboot and start up like it’s going to configure devices and then the screen goes black and hangs. Same process with 4GB or less of RAM and task sequence completes without problem. Disable the driver package injection step and it also completes with the greater amount of RAM. I’ve recreated the driver packages and updated BIOS to latest, no change. Hopefully someone else has seen this and it’s a stupidly simple fix that I’m missing. Thanks, Richard Poole The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
