Symantec Management Platform (SMP) Community

 View Only
  • 1.  Clients detect TaskServer by part of name, not FQDN

    Posted Apr 01, 2010 01:03 PM
    On a new SMP 7.0u3 client systems are pushed the Altiris agent.  (Client systems are linux based).  When "/usr/bin/aex-cta ts" is run, the TaskServer returned is just the host name, not the full name.  Example:  host.fqdn.com would be "host", this is causing an issue as some clients are in different domain zones and a box with the same name might exist in the zone they are in.  (So they try to connect to the incorrect system).

    Example:
    TaskServer:  tserver.company.com  *this is the taskserver they are suppose to be using, as this is setup to SMP.
    ClientName: client100.subzone1.company.com
    AnotherServer for something else:   tserver.subzone1.company.com

    When the client goes to find it's task server it is told it is "tserver", and then a lookup will return the incorrect system because FQDN was not given.

    Looking in SMP under the "Jobs and Tasks Portal" for each of the clients in question it has the task server listed as "tserver", without the FQDN.
    Also to note (and why I assume it is doing it) - Listing all managed computers we see "tserver" listed NOT "tserver.company.com".  It is like the install places the TaskServer with just the host name into the system, not the FQDN.  (TaskServer and NotificationServer are the same system for this example).

    Ideas?

    Thanks



  • 2.  RE: Clients detect TaskServer by part of name, not FQDN

    Posted Apr 13, 2010 05:08 AM

    This is also still an issue with the Windows Client. There was a hotfix for the SP3 but with the release of the SP4 they reintroduced the problem again.
    See the following KB article for the information about the hotfix: Link