Earlier I was asking you guys many times about mass storage device issues, and now it's all solved. Today I have an image, which covers all business laptops with Intel based chipset. Now I'm wondering, wherever I can spread it to ATI and Nvidia based computers. I tried this image on Nvidia (nForce 570 ultra chipset), and it goes to BSOD while first boot / minisetup with code 0x0000007E which appers to be common drivers incompatibility issue, am I right? So perhaps I should remove something related to Intel, but how and what? I know how to map image contant with DISM and modify files. The image was build on VMware machine which had some Intel system driver and it coudn't be removed before capturing.

the two most common issues are HAL related and Storage, have you checked for both eventualities in your task sequence ? My step by step SCCM Guides I'm on Twitter > ncbrady

Agree with Niall, but 0x0000007E is never storage, is either HAL or IntelPPM.sys driver (which needs to de disabled when deploying to AMD machines) / JohanRegards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

the two most common issues are HAL related and Storage, have you checked for both eventualities in your task sequence ? My step by step SCCM Guides I'm on Twitter > ncbrady There is a HAL swap task in my task sequence, which does work between different intel architecture. Image is build on Advanced Configuration and Power Interface (ACPI) PC and it really swaps it to multiprocessor, if I install 2-core machine with this image. I've done the HAL swap with unofficial best practises, so there is c:\drivers\unihal directory inside the image, which contains different kernel files. Now, only Intel based hardware can be installed using this TS.

IntelPPM.sys driver (which needs to de disabled when deploying to AMD machines) How it can be disabled? Should I mount the wim with dism and erase or modify some .inf lines, or do I need to re-capture the .wim? Do you have a detailed infomation on that? Thank you :)

No need to recapture, just add a script to your task sequence... you can use the following as a sample (you may have to update it slightly for MDT 2010, it's been a while since I wrote the script) TechEd 2007 - Over and Out (TechEd 2007 Sample Files) / JohanRegards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

No need to recapture, just add a script to your task sequence... you can use the following as a sample (you may have to update it slightly for MDT 2010, it's been a while since I wrote the script) TechEd 2007 - Over and Out (TechEd 2007 Sample Files) / Johan Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch Hello again. Please could you describe at what stage of default task sequence to put this script running? Any thoughts, what should be modified to make it compatible with MDT2010 U1?

The code-snippet needs to run in the post-install phase (after the image has been applied, but before rebooting into mini-setup) As for the script itself, as long as you declare the variables, and update the path to the offline registry, it should work fine in any of the MDT 2008/2010 script templates. A single command-line that simple deletes the intelppm.sys file should also do the trick (with a condition to only run on AMD cpu's). / JohanRegards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

I just wanted to confirm, that running DisableIntelPPM.vbs as command line during TS really gives an opportunaty to install Windows XP image (which was captured on Intel), on AMD based machine. For the first time I could install my AMD based desktop computer with OSD :) I didn´t have to do any changes in script.

Great, and thanks for posting back... / JohanRegards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

I also tried first an easier approach, I created Run Command Line task starting from c:\windows\system32\drivers and command was del intelppm.sys but here I got an error, that file cannot be found or something like that. I mapped .wim with dism, and it was there. Here I gave up and entered the vbs script :)

One another issue - it seems that WMI is corrupted after deploying XP image from .wim file during task sequence. For example, I cannot run gpresult command, it gives me an error which refairs to wmi. I captured the image with SCCM capture media, not imagex. Should I just capture it again, and before it to check WMI functionality? Or may I do something wrong here?