We have a base task sequence which we deploy out to machine and then layer apps over the top which is working fine no probs at all. Anyway we have ended up with a batch of Lenovo X100e laptops which are nice looking but a pain in the *** On initial testing of the issue deploying our TS down to the machine it would apply the OS and do steps you had up until there was a reboot in the TS. At that point the machine would go through the BIOS and then either Blue Screen of death or come up with a hardware issue. So initially I played around with AHCI settings injecting the driver pre-boot, however I still have not managed to solve the issue. From looking around on a few forums I think the issue seems to be that our Vanilla image was built from a machine that was Intel based and hence trying to deploy the image out to an AMD machine is where it fails. ( i know its the TS as a XP disc all is fine) As we only use 1 .wim and layer the apps on top i dont want to be having a seperate .wim for the AMD nor do I think its feasabily possible with the stage were at, so im after some ideas on how to get out of this little mess. has anyone run into this before? there are a few hints on the net which i am looking at to to determine if they are worth trying but any assistance would be appreciated. ThanksLee Martin

Hi Lee Martin, Have you replaced HAL in your Windows XP image?Kind regards Tim Nilimaa IT Consultant at Mindgrape (Sweden) Please remember to mark this answer as helpful if it helped you.

As of yet I have not cracked open the original image yet to make any alterations. I was kinda trying to see if there is anything that can be done as it is, by adding a driver or a setting or a KB something like that before i deploy it down and have to change things before capturing it again. What are your suggestions??? ThanksLee Martin

Hi Martin, It's a problem with an Intel driver, I've had it on our single WIM image and some Dell's that were AMD where we normally use Intel. Check out my blog post to fix it: http://systemscentre.blogspot.com/2010/07/bsod-during-osd-amd-cpus.html Cheers, SBMy System Center Blog

Hi This post from Johan Arwidmark may also be useful: http://www.deployvista.com/Default.aspx?tabid=78&EntryID=145

Excellent worked a treat!!! Im assuming it does not matter that that file is sitting around on an AMD machine,. think going to work on getting the core image built on virtual to get away from this issue in the future. Thank-you so much for your help!Lee Martin

No probs Lee, however.... building it on a virtual might not get you around the problem. Our single WIM is built on a virtual platform and we still ran into this problem. Cheers, SBMy System Center Blog

yes i did wonder that as even on Virtual it must have some kind of architecture. So after testing this it does appear to do what it says on the can. My only question would be: does it cause any un-toward issues by them files being on the machine? there must be some kind of driver in the image and could it potentially cause issues in the future as if not then i guess building virtual or non virtual doesnt make a huge difference from that perspective. Thanks for your help LeeLee Martin