Solved. Created a driver pack just for that model in MDT, specified it by model in the Rules tab. It worked. Now looking to implement total control for all models ;)
Sent from a dog and bone. On 27 Aug 2013, at 21:14, "Stuart Watret" <[email protected]> wrote: The machine builds normally with our standard thin image process, with the same driver database. It loops at Starting Windows, just before the four colours appear, safe mode falls over just after an and specific chipset driver, sort not in the office, anyway I've whipped that out it was in the vm, trying again overnight. Sent from a dog and bone. On 27 Aug 2013, at 18:19, "[email protected]" <[email protected]> wrote: Are you injecting the drivers for the amd machine? And where does it boot loop, do you see the “customizing settings” boot screen, then boot loop after that? Christopher Catlett Consultant | Detroit <image001.jpg> Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 <http://www.us.sogeti.com/> www.us.sogeti.com From: [email protected] [mailto:[email protected]] On Behalf Of Stuart Watret Sent: Tuesday, August 27, 2013 10:57 AM To: [email protected] Subject: [mssms] win7 image not booting on amd I thought this was an XP issue only ! Build a new Win7 image in hyperv, captured with MDT. Deployed back to new VM = ok, deployed to two physical machines one intel one amd. Intel one = ok, AMD = boot loop. Is the intelppm thing still relevant or could this be something else? Regards Stuart Watret Offshore - IT Ltd
