Client Management Suite

When trying to set up hierarchy with SEPIC NS servers, I receive the following error:

"Hierarchy Node Process failed. Please review the log for details"

I have it installed on the D drive but when looking for the log directory (D:\Program Files\Altiris\Notification Server\) the log directory does not exist.

Where can I find these log files to determine the issue I'm having?

Hi Brewabel,

Ensure the credentials are valid and entered correctly:
http://www.symantec.com/docs/TECH41411

There's also a known issue where you cannot create a new hierarchy relationship when Altiris was configured to use a non-default port.  This was fixed in 7.0 SP5, so if you are running an earlier release, be sure to upgrade.  It sounds like you're on 7.1 since the logs couldn't be located, but you didn't specify.

As mentioned, the logs are in different locations in 7.1 vs. 7.0 due to the different Microsoft OS.

So I found the logs and am looking through them.  The line I'm seeing now is:

<event date="Oct 11 15:12:08 +00:00" severity="1" hostName="SEPIC-WC-P01" source="Altiris.NS.Replication.Hierarchy.AsynchronousHierarchyOperations.AddNode_Synchronous" module="AeXSVC.exe" process="AeXSvc" pid="1844" thread="99" tickCount="-582877751"><![CDATA[Failed to retrieve remote server guid

The account credentials are correct and in the correct format.  I've tried using both short name & FQDN for the server I'm trying to make the child as well.

Using 7.1 also.

That's definitely the same error as the KB above (http://www.symantec.com/docs/TECH41411).  Are you working from the Child NS's console session to make it the child, or the Parent NS's console session to make the other a child?

I'm working from the Parent NS's console session to make the other server a child.  Think I've found the issue though.  It appears the child NS does not have a site server and therefore won't let me set up the hierarchy.

Yes, that will do it.  The Child NS requires a package server.  You can confirm the other requirements are met by reviewing this KB: http://www.symantec.com/docs/HOWTO44284.

mclemson, is there any way to make a NS a site server as well?  Or is this a bad thing to try and do?

I have limited experience with this and mostly use it with the SEPIC component to distribute SEP, so my apologies if these sound like crazy questions.

You can install package services or task services on the NS, but it's really not recommended. An NS already has the task service and package service functions, but for hierarchy, you must have a site server running package services deployed in the same site as the Parent NS and the Child NS('s).  If you put package services on an NS, you could continue with the hierarchy setup, but it's not at all recommended.  That's because it puts a pretty heavy load on the NS when packages and other items need to be replicated in the hierarchy.