Video Screencast Help

DS 7.1 Image capturing using sysprep failed

Created: 24 Jan 2012 • Updated: 24 Jan 2012 | 4 comments
vikasj's picture


I am not able to capture image using sysprep the task got suddenly failed

it gives no any error messege only shoing failure return code 1

Comments 4 CommentsJump to latest comment

mclemson's picture

Check the basics:

  • Is the username/password valid and not expired or disabled for the Application Identity?
  • Have you recreated the Preboot configuration?
  • Is your licensing valid and not expired?
  • Is the client system able to reach the NS on the specified ports?
  • Is the client system able to resolve the FQDN or the NS and any site servers running task/package/deployment handlers?

Smells like a DNS issue to me.

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

vikasj's picture

1) Username/password is not expired or disabled it perfect

2) Preboot configuration we already created and we used for other location also they not giving problem for other location

3) No any licensing issue or expired

4) Yes client system able to reach NS on specified ports

5) Clien resolve FQDN

Best Regards

Vikas Jagtap

Vaibhav Sharma's picture

Correct my understanding that you are getting failure return code 1 while running Prepare for Image Capture task (which is mentioned as capture image using sysprep).

This issue could be because of missing DS Automation Plug-in at client computer. Where after successful sysprep process client is not able to find autoutils to boot the client into Automation (this is just a wild guess though)

I would suggest you to enable *client side* DS debug logs for the task execution status details as follows:

Regedit> HKLM> Software> Altiris> Deployment> New String> (NAME)Debuglogs – (Value/Data) c:\Logs

Create c:\logs and run the task again. Check the created log for failure reasons (share with us also).  

vsharma's picture

in my case.. components were installed but needed a reboot to reset everything and the reboot got it working. Also check your Prduct serial number