i tried deploying an image captured from one make to another hardware... everything works till & the machine restarts as if everything is done...then it doesnt come up - i believe drivers prob... well... i think i can only import drivers in inf & oem format... n/w drivers which i have are inf but all others are exe, which i cant even extract... how do i import them... any clue?? now see the belwo strange.... when i deploy the image on same hardware, the image gets deployed, still i get the following via fsp: ************** rsalSerialBus(USB)Controller'. Failedtofindasuitabledevicedriverfordevice'MultimediaAudioController'. Failedtofindasuitabledevicedriverfordevice'UniversalSerialBus(USB)Controller'. Failedtofindasuitabledevicedriverfordevice'IDEController'. Failedtofindasuitabledevicedriverfordevice'UniversalSerialBus(USB)Controller'. Failedtofindasuitabledevicedriverfordevice'PCIHOSTBridge'. Failedtofindasuitabledevicedriverfordevice'VideoController(VGACompatible)'. Failedtofindasuitabledevicedriverfordevice'ATAChannel0'. Failedtofindasuitabledevicedriverfordevice'ATAChannel1'. Failedtofindasuitabledevicedriverfordevice'ATAChannel0'. Failedtofindasuitabledevicedriverfordevice'ATAChannel1'. Failedtofindasuitabledevicedriverfordevice'RamDisk'. Failedtofindasuitabledevicedriverfordevice'ROOT\ACPI_HAL\0000'. Failedtofindasuitabledevicedriverfordevice'ROOT\VOLMGR\0000'. ************** when i deploy the image on different hardware, image doesnt start up, ofcourse no drivers, i get the following via fsp: ******************* asuitabledevicedriverfordevice'PCISimpleCommunicationsController'. Failedtofindasuitabledevicedriverfordevice'ATAChannel0'. Failedtofindasuitabledevicedriverfordevice'ATAChannel1'. Failedtofindasuitabledevicedriverfordevice'RamDisk'. Failedtofindasuitabledevicedriverfordevice'ROOT\ACPI_HAL\0000'. Failedtofindasuitabledevicedriverfordevice'ROOT\VOLMGR\0000'. Failedtofindasuitabledevicedriverfordevice'Genericvolume'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB\4&18DAC57C&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB\4&1F90C461&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB\4&25E3E0CB&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB\4&2A7B014A&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB20\4&2EA026E2&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB20\4&C2A72D7&0'. Exitingwithreturncode0x00000000 ******************* i cant understand whats going on.... Is the product team listening please?

I had this problem too - look further up in your logs. Is your NIC failing to load? You need to sort that out first before it will copy drivers across from the server. Check permissions on the drivers folder for your SMS Advanced network account.

everything is fine dude... same machine capturecan be deployed to same machine without any issue, but still i get the errors as pasted above... different hardware is also posting errors... tell me if you could get a solution... we better resolve ourselves without product team involvement...

Harry, Are you deploying to the same HAL type? Simon

Simon, I have mentioned in my post above the errors which i get via FSP, w.r.t. to deploying the OS on same or different HAL. For same HAL, OS gets deployed, but still i get errors in reporting in drivers details (see above) when i deploy the image on same hardware, the image gets deployed, still i get the following via fsp: ************** rsalSerialBus(USB)Controller'. Failedtofindasuitabledevicedriverfordevice'MultimediaAudioController'. Failedtofindasuitabledevicedriverfordevice'UniversalSerialBus(USB)Controller'. Failedtofindasuitabledevicedriverfordevice'IDEController'. Failedtofindasuitabledevicedriverfordevice'UniversalSerialBus(USB)Controller'. Failedtofindasuitabledevicedriverfordevice'PCIHOSTBridge'. Failedtofindasuitabledevicedriverfordevice'VideoController(VGACompatible)'. Failedtofindasuitabledevicedriverfordevice'ATAChannel0'. Failedtofindasuitabledevicedriverfordevice'ATAChannel1'. Failedtofindasuitabledevicedriverfordevice'ATAChannel0'. Failedtofindasuitabledevicedriverfordevice'ATAChannel1'. Failedtofindasuitabledevicedriverfordevice'RamDisk'. Failedtofindasuitabledevicedriverfordevice'ROOT\ACPI_HAL\0000'. Failedtofindasuitabledevicedriverfordevice'ROOT\VOLMGR\0000'. ************** For different, the OS gets or seems to be applied, but when it restarts, it couldnt come up & i get errors logged. when i deploy the image on different hardware, image doesnt start up, ofcourse no drivers, i get the following via fsp: ******************* asuitabledevicedriverfordevice'PCISimpleCommunicationsController'. Failedtofindasuitabledevicedriverfordevice'ATAChannel0'. Failedtofindasuitabledevicedriverfordevice'ATAChannel1'. Failedtofindasuitabledevicedriverfordevice'RamDisk'. Failedtofindasuitabledevicedriverfordevice'ROOT\ACPI_HAL\0000'. Failedtofindasuitabledevicedriverfordevice'ROOT\VOLMGR\0000'. Failedtofindasuitabledevicedriverfordevice'Genericvolume'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB\4&18DAC57C&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB\4&1F90C461&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB\4&25E3E0CB&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB\4&2A7B014A&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB20\4&2EA026E2&0'. Failedtofindasuitabledevicedriverfordevice'USB\ROOT_HUB20\4&C2A72D7&0'. Exitingwithreturncode0x00000000 ******************* Secondly, well... i think i can only import drivers in inf & oem format... n/w drivers which i have are inf but all others are exe, which i cant even extract... how do i import them... any clues??

Hi, The Failed to find a suitable device driver messages are warnings not errors. They just mean that the Auto Apply Driver action did not find a driver in the driver catalog for the given device (but there may still be a suitable driver in the image that you are deploying). If your machines are booting successfully and have the correct drivers you can safely ignore these warnings (however you may want to look at them once and a while to see if there are other drivers you might want to import into your driver catalog). Getting the INF files for a driver can be a bit tricky. Many hardware manufacturers re-package drivers in an executable. In most cases, when you run these executables they will extract the driver files to a temporary directory and then install the driver. So, I usually run these executables on a test system and then copy the extracted files to a UNC share and import them into the driver catalog. -- Brett

Thanks Brett, i think i can only import drivers in inf & oem format... n/w drivers which i have are inf but all others are exe, which i cant even extract... i have executables for all other drivers like storage, vga etc... i think storage is a must for a machine to boot up, else everything is a waste... which temp folders would exe dump the files, when you try to install in a test system... after getting the dump, shall i get the entire folder & then import it to the drivers & make a driver package? which drivers ideally should be included into a boot image & which ones in the OS image? how do you do driver categorization, is it automatically done, i mean do i need to associate the drivers with boot/os images?

Harry, EXE drivers will extract to a number of places, for example Dell drivers are all WinZip combatible and can simply be extracted with WinZip, or when you run the EXE, they extract by default to C:\Dell\ and then execute the installation from there. Intel drivers typically extract to C:\Program Files\Intel ATI drivers typically extract to your Local Settings\Temp directory (%temp%) Some driver installation package support command line options to 'extract' only, check readme files or try /? when executing the install. If you want any assistance with a particular driver point me to where I can download it and I'll do some investigation for you. As for importing into SCCM, it's easier if you have all your drivers in one place to point SCCM to that folder and let it find all the .inf's for you, otherwise just import the drivers one by one. Catergorisation is a manual process, for example I'm adding all my network drivers and Mass Storage drivers to their own categories, I've also categorised each driver set per hardware model. I'm also creating a driver package for each hardwaremodel to add more granularity to the driver revisions for each hardware model. Finally, you only need to associate drivers to the boot images if you find the boot image can't connect to the network or can't see the mass storage device for example. Hope that's of some use to you. Simon

Hi Simon, lets talk about the drivers of HP computers. Except for n/w, rest of the drivers are executables which i cant extract. Well, do you want me to put all the drivers in one folder for all the makes & then import it to drivers option in the console, then make a package of it all & then include it into both the boot & OS images?

Hi Harry, For testing purposes I find it easier to concentrate on one model of hardware at a time, so pick one and get all the drivers for that, I don't care if you put them all in one place or in seperate places, whatever you find easier. But yes, import them all using the console and make a package for them, make sure you then distribute that package. You do not need to include them into the boot/os images at this stage. regards, Simon

reread the SYSPREP documentation more carefully. did you run the image against the original equipment in the AUDIT MODE FIRST TO CHECK YOUR HARDWARE SETUP? YOU ALSO DON'T SPECIFY IF YOU USED THE FACTORY COMMAND, OR THE -RESEAL COMMANDS BEFORE YOU TRIED TO TRANSFER THE IMAGE. I WOULD SUGGEST YOU RE-READ THE DOCUMENTATION, APPLY THE SWITCHES WHILE RUNNING THE COMMANDS, AND CHECK OUT THE INSTALLATION ON YOUR MASTER COMPUTER BEFORE TRYING TO TRANSFER THE IMAGE OVER A NETWORK. "While there is NO SUCH THING as a WRONG QUESTION, the EASIEST THING TO GET in the world is a WRONG ANSWER!" 15 years of hands-on-how-to; I "DO" WINDOWS !!!