/build/static/layout/Breadcrumb_cap_w.png

Image creationg from a Co-Op machine.

When you follow the procedures to capture an image from a Machine thats in Coop mode(With the default agent), the machine logs off, runs the scripts. It then reboots never triggers off the Ghost process to create the image. Then it runs the postimage capture process of Sysprep. So the image never gets created, even though the process says it was successful, has anyone found a method that works for them capturing image with this method?


I have a pending case with Symantec right now involving this issue.

0 Comments   [ + ] Show comments

Answers (1)

Posted by: Timanator 17 years ago
Third Degree Blue Belt
0
Ok, the issue is solved. Kind of a mix up with the instructions between me and their support. Maybe this will help others with image capture issues from a Co-op mode machine.

Steps to make this work:

1. Use a batch file or Command Center to deploy an Agent to the machine you want the image to be captured from.

2. After making sure agent is installed correctly, put the machines Bios to Boot from Network first in the boot order. Without this, the Pre-os jobs will never execute.

3. Assign a partition job to the Computer in the Command Center in Coop mode, which will delete all jobs for the machine. So if you click on the machine in the left pane, the right pane of the Command center, there will not be any jobs at all after the partition job is assigned.

4. Create a Computer profile(I named it Co-op Image Capture Prepare). Assign the following jobs to it, all in coop mode.
The OS package(I used MS WIndows XP Professional, and added the settings for our environment)
Symantec LiveState Agent for Windows V7.1.4(You have to ask Support for this new Agent, but 7.1.3 works also)
Symantec Livestate TCP pre-OS Agent V6.0


5. Copy and Paste the Computer Profile to the target PC in the Command Center. And assign one more package to the PC.

Symantec Image Delivery Prepare Image.(Populate the new image name you like to create)




The Target PC should reboot, run the Livestate Image prepare scripts, and reboot one more time and start the Ghost session. When this is done, that machine will need to be rebuilt, or you can re image it with teh new image you have just captured.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ