/build/static/layout/Breadcrumb_cap_w.png

Deploying sysprepped image fails

I used the Sysprep Wizard from ITNinja. I can deploy the image fine but when it restarts it gets stuck at apply system settings. One error was 'windows setup could not configure windows to run on this computer's hardware'.  We are a non-dell organization, but have the drivers for the different models in the drivers_postinstall folder. Should i check the 'use driver feed' or not? It looks like I have not enabled driver feed since I thought that was for Dell drivers only.

OS is Windows 7

Thanks
Asked 9 years ago 1667 views
3 Comments   [ + ] Show comments
  • Are you deploying to one model of hardware or different models? It is always a good idea to include as much detail as possible including hardware types.
    Please bear in mind that the operating system you are installing is not made by Dell so driver settings are not just for Dell machines. If you also think back to the manual install process for Windows, the one thing that you are always asked for during the early stages of install is to provide block drivers (if required) to allow the operating system to access the hard disk subsystem. Therefore, errors reporting that windows could not be installed or configured on that hardware are generally due to a lack of the correct block drivers. Pretty much everything else can be handled with Windows native drivers or without loading drivers if they are not available - leading to the yellow exclamation marks in device manager. - EdT 9 years ago
  • I guess I am still confused. Should I be checking the 'use driver feed'? What do you mean by Block drivers? I have never seen requirement in a Windows installation to provide block drivers. - jfrasier 9 years ago
  • By all means try checking "use driver feed". Block drivers are drivers for any device that moves data in blocks, such as a hard disk. Microsoft refer to them as Mass Storage Drivers. Installation of Windows 7 and later tend to provide a more graphical interface, but if you think back to XP (for example) there is an initial boot to a DOS-like environment where you get a chance to choose drive partitions for installation, and are also asked if you want to install a driver at that point. This is a request for what I refer to as a block driver. In the old days, all PCs came with IDE drives which were natively supported by Windows and no additional drivers were required unless you had a high end server and were using SCSI hard disks. These days, machine come with SATA hard disks pretty much as standard, and these have been manufactured in SATA-l SATA-ll and SATA-lll interface speeds. At the same time, there have been many different SATA chipsets manufactured to handle these drives. Consequently, you need to provide these drivers during the initial installation of the operating system as otherwise, the installation programs will not be able to access the hard disk and installation will fail. These drivers are handled separately in sysprep.ini as they are loaded way before windows starts and the plug and play subsystem starts loading device drivers for peripheral equipment.
    So if all your machines are the same model, or use the same SATA chipset then your operating system should at least boot. but if you have different hardware, your image needs to take account of these differences and provide the correct drivers. - EdT 9 years ago

Answers (1)

Posted by: khanthecomputerguy 9 years ago
Senior White Belt
0
Did you get anywhere with this? Let me know if you still haven't found the fix and I will be able to help.
Comments:
  • I haven't gotten it yet, but I have an idea. I will get back to you if needed. I really appreciate your help - jfrasier 9 years ago
  • Stuck. I used the driverfeedbuilder.exe to create the folders and files for all of the drivers in the drivers_postinstallation folder. I did put the msd driver in the drivers folder, recached the drivers and created a new KBE.

    I enabled driverfeed and checked the Use Driver Feed. We do not buy Dell computers so am wondering if there is something I am missing with regard to drivers. Since the folder is called drivers_postinstall am I supposed to create a post install task to load those drivers at the end?

    Anyway the result of deploying this sysprepped imaged is that Windows can't run (install?) on this hardware.

    Thanks. - jfrasier 9 years ago
    • The driverfeedbuilder.exe puts the drivers in the post_install folder. Do I need to copy those drivers to the drivers folder and recache to have those drivers available to apply to a sysprepped image when it is deployed? - jfrasier 9 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ