Client Management Suite

 View Only

  • 1.  NS server name incorrect

    Posted Apr 15, 2009 07:19 AM
    When I push the NS agent to clients it goes through successfully. However the client is unable to send an inventory or receive updated configurations from the server. As a result I can't see/administer the clients. I also can't retire old PC's.
    What I noticed is that there are very old clients on the server in my collections. They all point to a servername that hasn't been in existence for a long time. I'm assuming there is a setting in NS that is holding this old information? I've checked under the DB settings in the configuration and the correct server name is displayed. Has anyone seen this before?



  • 2.  RE: NS server name incorrect

    Broadcom Employee
    Posted Apr 16, 2009 12:25 PM
    Do the client machines you are mention simply list an old Notification Server when you look at your collections or are they listing the old server when you open the Altiris Agent details on the machine itself.

    Were these machines originally managed by the old server? Was Inventory Forwarding setup at one time to push the information from the old server to this new server? If this is the case part of the Inventory Forwarding process is to include the information for the Notification Server that managed those clients and that is what is being displayed in the collection information.

    As far as why the agents aren't communicating have you examined the agent logs on the client machines? Also you can examine the IIS logs for your Notification Server to see if any errors are occuring while the agent attempts to communicate.

    HTH


  • 3.  RE: NS server name incorrect

    Posted Apr 17, 2009 06:38 AM
    There  is a problem in your servername
    rename it & try to push ns agent


  • 4.  RE: NS server name incorrect

    Posted Apr 18, 2009 05:48 PM
    If you have a DS, you can leverage that to resolve the issue.  I have seen this before and I set up a job in DS to first remove the NS Agent, then wait 15-30 seconds, then install the NS agent again.  There are several ways to accomplish each step.  What I used for the sake of simplicity was AEXNSC.EXE for both the uninstall and install and sleep.exe from the NT Resource kit for the wait.  This resolved my issues.