Deployment Solution

 View Only
  • 1.  Altiris DAgent not reporting status

    Posted Aug 08, 2011 05:01 AM

    Hi all,

    I have an Altiris problem, we are currently using Altiris 6.9 with SP5. When booting into the WinPE environment the client no longer reports back it's computer name or MAC address. It has been working fine and I'm not sure what I've changed to stop this from working. Does anyone have any ideas? Because it no longer reports it's computer name and MAC address it won't appear in the Altiris console so I'm unable to drop a job on that machine



  • 2.  RE: Altiris DAgent not reporting status

    Posted Aug 08, 2011 05:09 AM
      |   view attached

    This is where it gets to and stops.



  • 3.  RE: Altiris DAgent not reporting status

    Posted Aug 08, 2011 06:21 AM

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


    Could this be the case? If this does not solve the issue, then turn on dagent loging from automation and show us the log. You need to edit your WinPE and enable log from there, also rebuild the image to apply the changes.



  • 4.  RE: Altiris DAgent not reporting status

    Posted Aug 08, 2011 06:40 AM

    I've just created a new WinPE boot and it has solved the issue. The problem I have now is that the client after it reports its computer name and MAC address it doesn't wait for me to drop a job on to it. It just says connection terminated.



  • 5.  RE: Altiris DAgent not reporting status
    Best Answer

    Posted Aug 08, 2011 06:58 AM

    If the computer is already known to DS then basicly what happens is that client boots to automation, checks if there's a job or not and terminates if no job assigned. 

    If you now would assign a job to that client and reboot it, it should pick up the job and run it. 



  • 6.  RE: Altiris DAgent not reporting status

    Posted Aug 08, 2011 07:11 AM

    I could see the client within the console, so tried removing all jobs associated with that client, yet still it would close the session. So removed the client completely from the deployment console and it resolved the issue.

     

    Many Thanks R.V.