Deployment Solution

 View Only
  • 1.  HII Configuration

    Posted Nov 14, 2008 07:34 AM
    Maybe this is a dumb question, but I'm pretty new to Hardware Independent Images...

    What I want to happen:
    I want to reimage a computer already in my computer list in the Deployment console and after it images, it reconfigures the computer to that computername and re-joins to the domain... Basically so I dont' have to mess with another step...

    Right now when i do this task, it reimages, gives the computer another name and that's it.. it just sits there.. i then have to manually go select configure and put in the info all over again to get the correct computer name and join it to our domain...

    Is there a way to make this happen with Hardware Independent Images?

    Thanks
    Jeff


  • 2.  RE: HII Configuration

    Posted Nov 14, 2008 08:51 AM
    I believe you can accomplish this by using tokens. I don't use this a lot though, so I can't offer too much insight into how to use the tokens.


  • 3.  RE: HII Configuration

    Posted Nov 14, 2008 09:54 AM
    It sounds like you need to be using Sysprep (Microsoft's System Preparation Tool).

    Sysprep will enable you to re-generate Windows' SIDs and re-run the mini-setup wizard to provide new information/configuration (computer name, domain, etc.) on the next reboot. You can provide an answer file to automatically fill in specific information.

    See: http://technet.microsoft.com/e.../library/bb457073.aspx


  • 4.  RE: HII Configuration

    Posted Nov 14, 2008 10:21 AM
    I am using sysprep...

    I set it to join the domain, but i can't test the darn thing yet because altiris won't deploy my flippin image... see my other post here.

    Anyway.. i understand how to make it join the domain through sysprep, but how do you give it it's name???

    Thanks


  • 5.  RE: HII Configuration

    Posted Nov 17, 2008 06:28 AM
    I use the %COMPNAME% token. Just before I copy the sysprep file to the computer, I run a ReplaceTokens command. The beauty of it is that is keeps the old name if it is a computer known to the deployment console. Otherwise, it follows the naming convention I set up with my Initial Deployment job.

    My job looks like this (my PXE environment is Linux):

    Distribute the image
    Run script to inject a customized sysprep file and drivers

    Here is the script:
    # Hardware Independent Imaging

    export PATH=$PATH:/mnt/ds/RDeploy/Linux

    # Token Replacement Task for Sysprep.inf file
    # Replacetokens ./temp/SYSPREP.TXT ./temp/%COMPNAME%.INF
    FIRM Copy /mnt/ds/temp/%COMPNAME%.INF PROD:/sysprep/sysprep.inf

    # suppress aclient post configuration
    Firm delete prod:/aclient.cfg


    # Set MODEL variable to product name
    MODEL="%#!computer@model_num%"

    echo "$MODEL" - Copying Drivers > /dev/tty1

    case "$MODEL" in
    '0944')
    Firm -recurse Copy "/mnt/ds/Drivers/NC6230" "prod:/drv"
    ;;
    '097Ch')
    Firm -recurse Copy "/mnt/ds/Drivers/DC7100" "prod:/drv"
    ;;
    '09F0h')
    Firm -recurse Copy "/mnt/ds/Drivers/DC7600" "prod:/drv"
    ;;
    '09F8h')
    Firm -recurse Copy "/mnt/ds/Drivers/DC7600" "prod:/drv"
    ;;
    '0A54h')
    Firm -recurse Copy "/mnt/ds/Drivers/DC7700" "prod:/drv"
    ;;
    '0AA8h')
    Firm -recurse Copy "/mnt/ds/Drivers/DC7800" "prod:/drv"
    ;;
    '308A')
    Firm -recurse Copy "/mnt/ds/Drivers/NC6230" "prod:/drv"
    ;;
    '30AA')
    Firm -recurse Copy "/mnt/ds/Drivers/NC6320" "prod:/drv"
    ;;
    '30AC')
    Firm -recurse Copy "/mnt/ds/Drivers/NC6400" "prod:/drv"
    ;;
    '30C0')
    Firm -recurse Copy "/mnt/ds/Drivers/NC6710" "prod:/drv"
    ;;
    *)
    echo Unsupported Model - "$MODEL" > /dev/tty1
    sleep 3
    ;;
    esac