Video Screencast Help

Deploy Image Task Fails using Ghost

Created: 01 Oct 2013 | 9 comments

I am trying to use the task 'Deploy Image' within a client job so I can deploy an image I created with the task 'Create Image'. Creating the image, with ghost went well. Now I am trying to deploy that image and the outcome of the task fails. Ghost deploys the image, then when it is done I am left with a blank Automation wallpaper that does nothing. I see in the console that the task failed. My only option is hard reset or type exit at the X:\> prompt to move on. I read on some other forums about this subject to try not to use DeployAnywhere. Using DA and not using DA still makes the task fail. The Drivers Manifest.txt file was at 0 KB. I removed the file, then it regenerated at 527 KB. I uploaded many drivers for most of my Dell Optiplexs and Latitudes.

Last year I tried this imaging approach with DA enabled and I was successful. Last month our NS Server had to be re-built, so I am trying to see if I can finally use this imaging approach, but I am having this problem. Can anyone help? Thanks

Operating Systems:

Comments 9 CommentsJump to latest comment

md investigate's picture

Hi,
Have a look for the log in preboot. There is a log for the Image deploy in x:\program files\altiris\altiris agent\logs.

Can you Access the hard drive in preboot? Maybe here is a driver issue.

Regards

MJammer's picture

Here are three log files, not sure which one in particular you need.

AttachmentSize
logs.zip 12 KB
md investigate's picture

Hi,

which version do you use? Maybe this here affects you: http://www.symantec.com/docs/TECH198111 ?

Regards

MJammer's picture

It is now working. I never would have thought that firm.exe needed to be copied to Deployment\Task Handler.

I also had to re-generate the Divers.Manifest.txt file. It went blank on me for the second day in a row. It should be at 527KB, it was at 0KB when I took care of firm.exe. Re-generated the manifest text file, tried again and now DP is working as it should. Thank you for the help with firm.exe.

Side note, why does Drivers.Manifest.txt blank out so often? It does it many times for myself to the point where imaging with Jobs/Tasks become VERY UNRELIABLE!!!! I do not do this approach to imaging in a Production Environment.

Right now for production I use a boot cd with a customized startup.bat.

Gavin Sanish's picture

By seeing the log files a lot of critical drivers are missing.
You should add all new drivers in the deployanywhere and try to do this.

--

 

...

G. Gavin Sanish

T : +91 9884877206
&a
MJammer's picture

Critiacal dirvers are the sata drivers and nic drivers? If so, what if I have them uploaded already? When you look at those error logs they are prior to my reply above.

md investigate's picture

Hi,

yes, crititcal drivers are storage and network drivers. For deployanywhere even wireless nic drivers are critical (can be a problem with notebook installations).

In a new installation it can be the best to start with a new driversdb, i.e. remove all drivers and only fill up with drivers needed in your environment.

Regarding the 0kb drivers.manifest.txt have a look here: http://www.symantec.com/docs/TECH186025

Did you installed the package server role on the ns?

Regards

MJammer's picture

I did upload wireless network drivers for our Dell Latitudes. I have not tried jobs/tasks imaging with laptops yet. Focusing on desktops right now that are in a 3 room training lab.

Is it good practice to remove pre-existing Drivers DB drivers taht out of the box with Altiris?

Yes, package and task services are installed and running on our NS. I think they are also installed and running on our site servers. My altiris server admin could verify that for sure.

md investigate's picture

Hi,

it's a question of what you want. The pre-existing drivers db is good for most drivers and you can add special ones needed. But you really don't know what is exactly in there. For best driver handling it is sometimes very important to know which exact driver version you use and sometimes different version are interfering.

I often start with a clean drivers db and add only drivers I really need for the clients.

Package server is not recommended to be on NS. Please have a look for the article: http://www.symantec.com/docs/TECH186025 . There you can see the relation regarding the 0kb drivers.manifest.txt.

Regards