tmsmith2

Ever since upgrading from DS 6.9 177 to DS 6.9 SP1 our system account can not run configuration tasks after imaging.

As you can see I have checked
AUTOMATICALLY PERFROM CONFIGURATION TASK AFTER COMPLETETING IMAGE TASK.

AND
BOOT TO PRODUCTION TO COMPLETE IMAGING TASK.

Here is the strange thing. After it fails it gives a 122 error code.
If I run a manual configuration to join to the domain (same credentials) then it works without issue. Any ideas. This is happening on all 16 Deployment Servers.

Attached Thumbnails

 

Soupy

No idea why it's happening, but it would appear to be a 6.9 SP1 issue and it's causing us no end of sh*t as well.

It started going wrong for us with the SP1 update, for the time being i'm going to write a netdom script that joins the PC to the domain as a work around. Then i'm going to log a call with Altiris to get it fixed.

Rezin8

We have the same problem here. Our solution was replacing the Aclient in our image with the latest and greatest. Seems to fix the problem-must be a compatibility problem with the Aclient versions.

Soupy

hmm...

My understanding of SP1 is that DAgent is now the agent of choice for XP and Vista rather than having AClient for XP and DAgent for vista.

We don't put a copy of Aclient (DAgent) into our image, it gets installed after the image is pushed down. (Installation files firmed down to the image and a runonce key executing a .bat file to install the agent, for those who were wondering) We updated our agent to the version of DAgent shipped with SP1 and that's when the problem started for us.

Brandon

I am having this issue as well but I am still at 6.9. I am not sure it has ever worked. I did find this: https://kb.altiris.com/article.asp?article=33222&p=1

Have you tried using the FQDN for the domain? Neither is working for me but it may for you.

__________________
Brandon

tmsmith2

The Aclient was out of date. Once the new update was applied no issues.