Ayuda de vídeo de Screencast
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Capture and Deploy images with Altiris 7.1

Created: 17 Enero 2013 | 4 comments

I am having to convert from GSS 2.5.1 to altiris and am having some logic correltion issues. I using a sysprep to automate all of our imaging process except the naming of the PC. I have relied upon configuration files in GSS to do that in the past. 

I used the same procedures that I have in the past created a clone PC in audit mode and set it up and used Altiris to reboot to automation then capture image task all in a job. When I deployed it using the same Sysprep file from GSS that works it fails to copy the profile and image correctly. I am not sure where the Configuration task is supposed to fall in place. 

Comentarios ComentariosIr al último comentario

el cuadro de los Pankaj Lokhande

Hello,

To capture Sysprep image you will first need to execute "Prepare for Image Capture" task. This task executes Sysprep. After this task you can proceed with "Create Image" task. Please do let us know your result.

Regards,

Pankaj

el cuadro de los mclemson

I provided an overview on this which may be helpful:
https://www-secure.symantec.com/connect/forums/exa...

Two KBs may also be useful for you.  One is a list of commonly used DS 7.1 KBs (http://www.symantec.com/docs/HOWTO55859) and the other is a quick start overview of imaging in DS 7.1 (http://www.symantec.com/docs/HOWTO30267).

Your sysprep answer file shouldn't be GSS-specific but should simply be one that validates in WAIK.  Does this help?

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner
intuitivetech.com

el cuadro de los Gh0stRyd3r

OK thanks for the advice I will look over it when I get back.

As for the sysprep I made it with the WAIK image tool. I just meant the sysprep didn't act like it was even called in the deploy stage.

el cuadro de los Gh0stRyd3r

Ok still stuck on the apply system configuration, I am depending on it to name the PC in the oobe Welocme stage. Also not sure why the script to run netdom.exe to join the domain fails along with after finished the administrator password has to blanked out to login.