Asset Management Suite

Connecting Systems, Services and Users.

Requesting suggestions for connecting users to Systems and Services automatically:

The Problem:  Users are placed in Ad Groups.  These groups are automatically imported into an organizational view based on the service catalog. 

Current Situation;  I have services such as “clients processing” or “Project Office”  These Services are entries in in the Symantec Management Platform in “services”  Each “service” has several systems associated to them, such as “project office/Dev”, “project office/Production”  and “project office/testing”  Each of these systems  has several servers associated to them

Hierarchy example:

• Service
  • System1
    • Server A
    • Server B
    • Server C
  • System2
    • Server A
    • Sever F
    • Server G
  • System3

Need:

                Now I need to associate Users from the Organizational View(ad import) to these Systems and have it reportable in a very non complicated way. 

I’ve been searching thought connect and not found a built in solution, which is surprising.  Symantec is trying to sell themselves as a fairly complete CMDB but even if you have Service Desk connecting an incident/problem or change control with the CMDB is not very good at all. 

Any suggestions are appreciated. 

Probably you can try to use a "Data Connector" to perform import of required data from Active Directory and then map it with appropriate DataClasses on NS server via Resource Import rule of Data Connector.

1. Create "LDAP Data Source"

// Set there required LDAP path and filter

2. Create Resource Import Rule and set appropriate OU/CN to be mapped with required Data Classes during import to NS server (Symantec_CMDB)

• How to use Data Connector to import data into the Symantec Management Platform database

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

The import wasnt the problem.  The problem was associating a mass list of uses who were imported from AD,

The solution I found was was to create a new multi line data class that is an associate item, not a resource.  that way I can choose the filter created by the import and I have the ability to lookup on the dataclass entry menu to instantly show me users. 

The plus side is reporting is much easier because you are using the resoruceguid of the system, and the resource guid of the collection to get the list so it can be exported.