Video Screencast Help
Symantec Secure Login will be live on Connect starting February 25. Get the details here.

Asset Management Suite in Hierarchy

Created: 12 Sep 2012 • Updated: 11 Oct 2012 | 4 comments
Language Translations
odami's picture
+6 8 Votes
Login to vote

Understand Your Environment

This article is not intended to replace any professional consulting and these steps should NOT be taken without first testing them in a development environment. Always backup your database FIRST. The following are general steps and guidelines that you can use in order to understand special changes that need to be made when considering the use of Asset Management Suite in a large environment with hierarchy.

Now it is important to understand what your current environment looks like. Use the following scenarios to understand the steps you should take in order to configure AMS for a large environment with hierarchy. Again, these are general guidelines, and these suggestions may not fit every environment. However, in any case the following are always true.



"I haven't installed any Symantec Products yet, and I'm still in design"

Install AMS on the server that will be the "Parent" server in your environment ONLY. Configure the servers a hierarchy, using the configuration in section "C"

"I currently have servers in a hierarchy with CMS on each server"

Install AMS on the server that will be the "Parent" server in your environment ONLY. Configure the servers a hierarchy, using the configuration in section "C"

"I have 2+ servers in my environment in hierarchy and they all have AMS installed"

1. Ensure that Replication Activity is stopped section B

2. Break Hierarchy

3. Remove AMS from the Child Servers OR rebuild boxes with AMS section A

4. Bring the servers back into Hierarchy and configure the rules listed here, as well as your additional rules section C

A) Remove Asset Management Suite if Installed on Child NS

If AMS has already been installed on a server that will function as a "Child Node", best practice would be to rebuild the box in order to ensure no AMS SQL tables are still in the CMDB. However, if AMS has already been installed, the product can be uninstalled and the tables in the database ignored. Follow the steps here to be sure that the product is removed.

1. Open the Symantec Installation Manager by using the Right Click – Run as Admin

2. Find the ‘Asset Management Suite’ in the list of Installed Products

3. Click ‘Uninstall’

4. Confirm that only the following Products are listed:

a. Barcode Solution

b. Asset Management Solution

c. Asset Management Suite

5. Complete the prompts to finish the uninstall

B) Manually Ensure that Replication has Stopped when Breaking Hierarchy

Only break hierarchy if you need to remove AMS from a child server, otherwise skip this step.

Run the following SQL query from SQL Management Studio to make sure that all possible replication jobs have been stopped before breaking hierarchy.

select * from replicaitonjob where state = 3

C) Replication Configuration for Asset Management Suite

·       Software Resource Summary Relocation

·       Computer Replication

·       Software Component Resources for installed software component

·       Metering Summary Data Classes

·       Metered Files Properties Data Class data

·       Inventory Data Classes data – Software Data Classes

·       Inventory Data Classes data – Hardware Data Classes

·       Inventory Data Classes data – User Data Classes

·       Inventory Data Classes data – OS Data Classes

Comments 4 CommentsJump to latest comment

Vaibhav Sharma's picture

Good article.

Login to vote
vikas1101's picture

Hi Odami

One of our customer having environment like this, CMS and AMS both are on different box.

We connected CMS and AMS server through replication, where AMS as parent and CMS as child.

We need to configure Inventory forwarding from CMS to AMS 

So suggest us what best practice we follow?

When we done replication, on CMS server enhanced console view got change ( Normall if u go to manage -- Computer, you will see all computer information also If u go to manage -- software on right hand side top corner you will see software over deploy and under deploy infomation, usage details etc. this information we not able to see now on both the server CMS and AMS)

Login to vote
odami's picture

Unless there has been a change since this article was written: Replication and Inventory Forwarding alone will not work. If you do not use full hierarichy you will have issues in your implementation and your Enhanced Console view will not function properly when trying to manage Software Products (Duplicates of Software Products will appear and installation information will dissapear from some of the Products).

Login to vote
SK's picture

It is possible to use standalone replication instead of hierarchy replication in this scenario, as I have provided support to a customer that does it.

Their implementation is not perfect, as they replicate software from the Slave's to the Master instead of the other way round; however, it has not caused them too many headaches.

Connect Etiquette: "Mark as Solution" those posts which resolve your problem, and give a thumbs up to useful comments, articles and downloads.

Login to vote