Deployment and Imaging Group

When I deploy an image, all of the tasks work up until the "apply system configuration."  It will say it failed on "reboot to production," but that is because there is no communication with the agent to know that it actually worked.  This is because the agent never registers (it says this in the agent logs as well).  My configuration task adds the computer to the domain.  If I add the computer to the domain manually, the agent registers (a lot of good that does me).  This happens with new images using 7.5 agents and imported images with 7.1 agents.

There is a difference with the registry settings on these two agents however.  They both have the server information in HKLM\software\altiris\altiris agent\server\<servername> in a string called “web” that has a value of http://<servername>/altiris .  With two machines added to the domain, lf I delete this entry on the one with the 7.1 agent and reset the agent, it registers again.  If I do the same thing on the one with the 7.5 agent, it will not register again.

If I modify the “Web” value to http://<servername>.<domainname>/altiris , the 7.5 agent will register and finish the rest of the tasks in the deployment job.

I know I can probably get away with modifying my images to include this in the registry but don’t feel I should have to.  Does the 7.5 agent only use the web setting?  Is there something I missed in the DS settings that caused this?  Setting an alternate URL in the advanced tab of the targeted agent settings didn’t help either, and oddly enough, one of the default URLs is preset to have the settings that will actually work.

We had the same issue eric, I went ahead and created a new image to reflect the new client versions. The temporary work around that we did was to repush the Altris installaton to those machines until the new image was created. Sure it was not the answer you were looking for.  I did not want any upgrade issues with any new version releases and patches that I am sure will be released down the road. Good LUCK!

I ended up using my answer file to add it to the domain.  However, after showing the problem to one of my colleagues in our networking group, he found an entry in the DNS suffix settings of the NIC card that wasn't there on the image.  That setting was put in there by the default answer file (I combined my settings with the default to use some of the tokens).  I deleted the "<component name="Microsoft-Windows-DNS-Client.." section from the answer file to fix this, and that took care of the agent initializing part of the problem.  The boot to production fails once it registers, saying, "ErrorMessage: Automation Environment (autoutil) not found value=0, error=0," but only seems to fail on images with the old agent.

I was having the same issue in my demo lab, Ive applied the 7.5 HF2 and the jobs now pass through fine and dont fail on the reboot task

The hotfix is available now and the release notes are here.

http://www.symantec.com/docs/DOC7076