Deployment Solution

 View Only
  • 1.  Altiris Hardware-Independent Image BSOD on New SATA Laptops

    Posted Mar 10, 2010 03:54 PM
    Hello

    Our hardware-independent image is constantly rebooting when starting up (0x07B BSOD).  It is an HP ProBook 6545b AMD laptop.  We use model-specific sysprep files that copy SATA drivers in the SysprepMassStorage section.  The files are correctly defined, and the image works if the BIOS is changed from AHCI to IDE, however this as a proposed fix is NOT an option.  We have another similar model laptop (HP 6735b) that works with the hardware-independent image and uses simliar AHCI drivers.  However, copying these drivers and settings to the new laptop after pushing the image does not work.  The image is both Intel and AMD platform compatible.

    Any ideas?

    Thanks


  • 2.  RE: Altiris Hardware-Independent Image BSOD on New SATA Laptops

    Posted May 20, 2010 12:23 PM
    We have struggled with the same things.   Could you possibly share what you did to make the 6735 work with the SATA drivers.   WE have never been able to get the 6545 to work either.

    Thanks

    Brian Grinstead


  • 3.  RE: Altiris Hardware-Independent Image BSOD on New SATA Laptops

    Posted May 23, 2010 04:22 AM

    I presume you're refering to a Windows XP HII ?

    You also reference model specific sysprep files -  Are you including the mass storage drivers for the 6545b when you run sysprep on your HII image or using a clever mass storage injection tool when you drop the image on that specific model?  Why are you sure the files are correctly defined?

    Something I reccommend is to run your HII OS build sequence directly on that model type.  If you can sysprep, capture and redeploy on the same model with the ACHI mode turned on then I suggest that you have some mis-configuration in your HII process.



  • 4.  RE: Altiris Hardware-Independent Image BSOD on New SATA Laptops

    Trusted Advisor
    Posted May 24, 2010 05:25 AM
    Hi,

    Alarm bells are ringing for me when you say "We use model-specific sysprep files that copy SATA drivers in the SysprepMassStorage section". Are you ammending the SysprepMassStorage section at image deployment time and injecting files into the image? If you are, this does not work unless you are using technology in addition to sysprep (like DeployAnywhere) which makes deployment time file and registry injections. 

    If you don't use the really clever stuff  you need to sysprep your images with all the mass-storage drivers you are likely to see in the next few months as well as those we already have in you environment. This will allow all your models to see the harddisk when they boot.

    There are lots of articles and discussions on Connect on Sysprep and HII. He's a couple it would be worth a look over (if you haven't already),
    Kind Regards,
    Ian./