Video Screencast Help

Altiris 7 keeps failing on configuration tasks

Created: 20 Nov 2013 • Updated: 24 Nov 2013 | 4 comments
This issue has been solved. See solution.

We have Symantec Management Console 7.1 aka altiris installed on Windows Server 2008 R2 Datacenter.

I'm currently trying to reimage 30 lab computers with Windows 7 Professional 32bit in my school. The capture and deploy tasks are running well with no problem at all, the configuration task is the problem I'm facing.

Everytime I tried to run the task on the computers, I got an error message saying failure with return code -1 from the agent. The agent can actually receive and run the task, but resulted in a failure.

I'm using very simple names for those lab computers, for example, 'gl01'. I don't think the name format should cause any problem to the task.

Anyone got any idea why this is happening? I would appreciate it if any one can give me any clue on it. Thanks.

Operating Systems:

Comments 4 CommentsJump to latest comment

md investigate's picture

Hi,

what is the purpose of the configuration task? Rename the client or join to domain or...? Is the deployment plugin installed on client? (I guess it's included in image?)

Did you had a look for the agent.log?

Regards

kzhang's picture

Hi md,

Thanks for your reply. I'm using the configuration task to rename and join those lab computers to the domain. I've already included the agent and deployment plugin in the image. As a new user of Altiris 7, I have no idea how I can find the log file of the agent. I had a look at the altiris agent folder, but I didn't find any clue where it is hiding. I would appreciate it if you can tell me the location of the agent log file. Thanks.

Regards,

kzhang

md investigate's picture

Hi,

just try to divide the two purposes in different tasks for testing. So, just try a rename and fire to the client and try a domain join for itself. I can remember that it could be a problem to fullfill this purposes with one task.

You can find the logs in "%programdata%\symantec\Symantec Agent\Logs".

Regards

SOLUTION
kzhang's picture

Hi md,

Thanks for your help. It is working now. Appreciate it.

Regards,

kzhang