Asset Management Suite

 View Only
  • 1.  How to replicate asset status from child NS to parent NS? (ITMS7.5 SP1)

    Posted May 16, 2016 09:44 AM

    I try to create a replicate rules from "Settings" -> "NS" -> "Hierarchy"->"Replication"->"Resources".

    Which particular data classes or other method available to replicate computer status from Child NS to Parent NS with ITMS7.5 sp1?

     

     

    rep arc.JPG

     

     

    Data classes.JPG

     

     



  • 2.  RE: How to replicate asset status from child NS to parent NS? (ITMS7.5 SP1)

    Posted Jun 10, 2016 07:40 AM

    Here is an article how Asset Management should be installed in hierarchy:

    https://www.symantec.com/connect/articles/asset-management-suite-hierarchy

    And here are some articles how child / parent manage the status of computers:

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

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

     

    How do you set the status on the child NS? Do you use purging maintenance to automatically set to retire? You should in that case set the same setting both on parent and child.

     

    purging_maintenance.PNG



  • 3.  RE: How to replicate asset status from child NS to parent NS? (ITMS7.5 SP1)

    Posted Jul 08, 2016 06:42 AM

    Data class where the status information is being kept is ResourceAssociation

     

    Here is a simple query to get the status:
    select * from inv_aex_ac_identification as ac

    JOIN ResourceAssociation AS ra5 ON ra5.[ParentResourceGuid] = ac.[_resourceGuid] AND ra5.[ResourceAssociationTypeGuid] =  '3028166F-C0D6-41d8-9CB7-F64852E0FD01' -- Asset Status                      

    JOIN vItem AS ser ON ser.[Guid] = ra5. [ChildResourceGuid]

     

    Anyway I do not think you can set the custom replication rule to replicate that.

    What exactly are you trying to achieve? You want to speed up the process or the status is not replicated even during the regular replication?

    You might consider to use Symantec Workflow and custom right click action to change status directly on the parent form the child server. It would also give you possibility to use more statuses than Active and Retired but it would be time consuming to set it up.