Deployment Solution

 View Only

  • 1.  Boot loader issues when deploying XP WIM file

    Posted Mar 18, 2009 06:14 PM
    Morning
    I have an issue I would like some help with
     
    I have an Installed a clean Altiris Client Deploy 6.9 SP1
    I installed the Altiris Win PE 2.1 files.
    I have a captured XP WIM image.
    2003 ad DHCP/DNS/etc
    I create a job that deploys the image to the PC
    That deploys the image correctly but
    During the process is creates the partition
    Sets the type to ntfs52 with bootsect
    Formats the partition
    Sets to active etcBUT then it sets the boot sector to ntfs60 (i.e. vista)Images the PC
    Reboots and fails on the vista boot loaderI can rerun bootsec /ntfs52 reboot and the syspreped XP runs fine
     
    How do I stop the script from changing the boot loader to the vista one?
    I don’t seem to have the ability to change the partitions sizes (the advanced button is greyed out) when using WIM can that only be done with an IMG?
     
     
    Cheers


  • 2.  RE: Boot loader issues when deploying XP WIM file

    Posted Mar 18, 2009 07:34 PM

    There are two sample jobs that could help you create your own.

    DS COnsole | Sample Jobs |  ImageX jobs 

    There are two jobs one is to create and the other to restore.

     

    Nelson



  • 3.  RE: Boot loader issues when deploying XP WIM file

    Posted Mar 18, 2009 08:47 PM

    Yes that is correct I did try that, but unfortunatly if i use the sample job imagex, it drops the image down fine, but i lose the sysprep features (well have to do it manually) and driver injection/hardware indepentant restore

    I just want to rem out that one line in the orgional script, does anyone know where it is?



  • 4.  RE: Boot loader issues when deploying XP WIM file

    Posted Mar 19, 2009 12:03 PM

    The engine creates the file on demand. what you could do :)  Is capture the the  file created in the temp folder and see what commands the engine is passing.  Then create your job.  For this I believe you need to set the logging to level 5 or more.  Let me know if u need help enabling DS logging.

     

    nelo