Altiris CMDB Solution 7.1 SP2 from Symantec User Guideorigin-symwisedownload.symantec.com/resources/sites/SYMWISE/... · IntroducingCMDBSolution This chapter includes the following

Altiris™ CMDB Solution 7.1SP2 from Symantec™ UserGuide

Altiris™ CMDB Solution 7.1 SP2 from Symantec™ UserGuide

The software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Legal NoticeCopyright © 2011 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo Altiris, and any Altiris or Symantec trademarks used inthe product are trademarks or registered trademarks of Symantec Corporation or its affiliatesin the U.S. and other countries. Other names may be trademarks of their respective owners.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software and Documentation by the U.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and/or Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers software upgrades

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our Web siteat the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level



■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf your Symantec product requires registration or a license key, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Support agreement resourcesIf you want to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

mailto:[email protected]



Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Introducing CMDB Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About CMDB Solution .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9What's new in CMDB Solution 7.1 SP2 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9What you can do with CMDB Solution .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Where to get more information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Chapter 2 Configuring CMDB Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

About configuring CMDB Solution settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Creating custom status values ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Configuring default values for configuration item type

fields ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Checking license usage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Configuring organizational hierarchy update settings ... . . . . . . . . . . . . . . . . 17

About CMDB configuration tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18About CMDB rules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Configuring ownership settings ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 3 Managing your organizational structure . . . . . . . . . . . . . . . . . . . . . . . . 23

About organizational configuration item types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23About the Company configuration item type .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25About the User configuration item type .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Setting up your organizational structure ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Creating a location .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Creating a cost center ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Creating a department ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Updating your organizational hierarchy manually ... . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Chapter 4 Managing security in Asset Management Suite . . . . . . . . . . . 33

About managing security in Asset Management Suite ... . . . . . . . . . . . . . . . . . . . . . . 33Predefined asset management security roles ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Managing security on an organizational group .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Assigning an organizational group to a security role ... . . . . . . . . . . . . . . . . . . . . . . . . 35

Contents

Configuring security permissions for an organizational group .... . . . . . . . . . . 36

Chapter 5 Managing configuration items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

About configuration item types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38About base configuration item types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38About CMDB data classes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39About predefined configuration item types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40About datacenter configuration item types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41About configuration items .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42About configuration item associations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43About configuration item association types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Tracking the associations of a configuration item .... . . . . . . . . . . . . . . . . . . . . . . . . . . 45Automatically creating configuration items for network devices ... . . . . . . . . 46About importing configuration item data from other systems .... . . . . . . . . . . 46About merging duplicate configuration items .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Merging two configuration items .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Creating and editing a configuration item .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Managing edit views .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Specifying ownership percentage of a configuration item .... . . . . . . . . . . . . . . . . 50About asset life cycle ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51About tracking the total cost of an asset ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Chapter 6 Managing custom configuration item types . . . . . . . . . . . . . . . . . . 55

About custom configuration item types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Creating a custom data class ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Creating a custom configuration item type .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Creating a custom configuration item association type .... . . . . . . . . . . . . . . . . . . . . 58About data input masks .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Contents8

Introducing CMDB Solution

This chapter includes the following topics:

■ About CMDB Solution

■ What's new in CMDB Solution 7.1 SP2

■ What you can do with CMDB Solution

■ Where to get more information

About CMDB SolutionCMDB (Configuration Management Database) Solution is a component of AssetManagement Suite. This solution lets you model configuration items for anycomponent in your environment and the relationships between them in acentralized database.

CMDB Solution lets you identify all components and relationships and to instigateany required changes. The solution actively manages configuration items accordingto user-specified instructions in jobs, tasks, configuration policies, and customCMDB rules.

See “What you can do with CMDB Solution” on page 10.

What's new in CMDB Solution 7.1 SP2The 7.1 SP2 release of CMDB Solution includes enhancements to refine productquality.

See “About CMDB Solution” on page 9.

1Chapter

What you can do with CMDB SolutionSee “About CMDB Solution” on page 9.

CMDB Solution has many features and uses, including the following:

Organizational configuration items such as departments andcost centers mirror the structure and hierarchy of yourorganization. CMDB Solution hierarchy features and child toparent relationships specify standard settings throughout anorganizational hierarchy. For example, a task that is applied toa parent department can be automatically pushed down to childdepartments. Setting up organizational configuration itemsshould be the first thing you do with CMDB Solution.

When you set up associations between configuration items duringthe CMDB Solution installation, organizational views areautomatically created with the same hierarchy and membership.

See “Setting up your organizational structure” on page 26.

For more information, see the topics on organizational views andgroups in the Symantec Management Platform User Guide.

Define organizationalgroups and hierarchy.

Configuration items such as assets and contracts are enteredinto the database using predefined templates called configurationitem types. The base configuration item types should be usedwhen possible. The base configuration item types leverage otherconfiguration item types. They provide summary data on thecreated configuration items and include associated reports andfunctionality that is not available in custom configuration itemtypes. If none of the base configuration item types meet yourneeds, you can create a new configuration item type.

You can specify default configuration item type values so thatall configuration items based on a configuration item type arecreated with predefined values. When you enter data for assets,certain fields have the same value for many assets of a particularasset type. You can populate these fields with a default value.For example, users in a particular location have the same phonenumber prefix. You can save time by having the prefix alreadyentered into the appropriate field.

See “Creating and editing a configuration item” on page 49.

Define configurationitems.

Introducing CMDB SolutionWhat you can do with CMDB Solution

10

Importing is the easiest and the most efficient method of enteringdata into the system. You can also enter data manually. As youset up a configuration item management system, there is certaindata that makes sense to enter before other data. For example,most configuration items rely on the availability of organizationaldata.

See “Automatically creating configuration items for networkdevices” on page 46.

See “About importing configuration item data from othersystems” on page 46.


Add data to the CMDB.

You can track where an asset is located, who owns an asset, andwhich assets are associated with each owner. The ResourceAssociation Diagram feature lets you view the relationships ofconfiguration items in a graphical format.

You can specify the format, the filter, and the number of levelsand nodes to display. To customize and easily recreate the displayfor your environment, you can save the display options andfilters.

See “Tracking the associations of a configuration item”on page 45.

Track the associationsand relationships ofconfiguration items.

See “About CMDB configuration tasks” on page 18.Clean up and configuredata management withready-madeconfiguration items.

CMDB rules target a group of assets based on their type andproperties, and then make changes to these assets. Out of thebox configuration items address the most commonly requiredconfiguration item management policies. CMDB rules providethe flexibility to create custom policies for individualconfiguration item management needs.

See “About CMDB rules” on page 19.

For more information, see the topics about CMDB rules in theSymantec Management Platform User Guide.

Create customized itemactions and CMDB rulesto manage data.

11Introducing CMDB SolutionWhat you can do with CMDB Solution

If multiple users work with configuration items, for exampleentering and editing data, then you should configure security.CMDB Solution includes predefined security roles. You can modifypredefined security roles or you can create your own roles. Youcan also restrict or allow access to configuration item types anddata classes. Hierarchy features are used to set and enforcesecurity settings throughout a hierarchy.

With the role-specific views, you can choose to show or hidemenu items depending on a user's security role. For example,you can give a user access to the Reports menu but not to theManage menu. You can also add menus and customizesub-menus.

See “Managing security on an organizational group” on page 34.

For more information, see the topics about organizational viewsand groups in the Symantec Management Platform User Guide.

Configure security.

Where to get more informationUse the following documentation resources to learn about and use this product.

Table 1-1 Documentation resources

LocationDescriptionDocument

The SupportedProductsA-Z page, which is available at the followingURL:

http://www.symantec.com/business/support/index?page=products

Open your product's support page, and then under Common Topics,click Release Notes.

Information about newfeatures and importantissues.

Release Notes

■ The Documentation Library, which is available in the SymantecManagement Console on the Help menu.

■ The Supported Products A-Z page, which is available at thefollowing URL:


Open your product's support page, and then under CommonTopics,click Documentation.

Information about howto use this product,including detailedtechnical informationand instructions forperforming commontasks.

User Guide

Introducing CMDB SolutionWhere to get more information

12



Table 1-1 Documentation resources (continued)

LocationDescriptionDocument

The Documentation Library, which is available in the SymantecManagement Console on the Help menu.

Context-sensitive help is available for most screens in the SymantecManagement Console.

You can open context-sensitive help in the following ways:

■ The F1 key when the page is active.

■ The Context command, which is available in the SymantecManagement Console on the Help menu.

Information about howto use this product,including detailedtechnical informationand instructions forperforming commontasks.

Help is available at thesolution level and at thesuite level.

This information isavailable in HTML helpformat.

Help

In addition to the product documentation, you can use the following resources tolearn about Symantec products.

Table 1-2 Symantec product information resources

LocationDescriptionResource

http://www.symantec.com/business/theme.jsp?themeid=support-knowledgebaseArticles, incidents, andissues about Symantecproducts.

SymWISESupportKnowledgebase

http://www.symantec.com/connect/endpoint-managementAn online resource thatcontains forums, articles,blogs, downloads, events,videos, groups, and ideasfor users of Symantecproducts.

SymantecConnect

13Introducing CMDB SolutionWhere to get more information

http://www.symantec.com/business/theme.jsp?themeid=support-knowledgebase

http://www.symantec.com/connect/endpoint-management

Introducing CMDB SolutionWhere to get more information

14

Configuring CMDB Solution


■ About configuring CMDB Solution settings

■ About CMDB configuration tasks

■ About CMDB rules

■ Configuring ownership settings

About configuring CMDB Solution settingsThe CMDB Solution settings let you set up an environment for managingconfiguration items in your system. For example, you can specify default valuesfor configuration item type fields, configure organizational hierarchy updatesettings, and configure ownership settings. You can also specify custom statusvalues for configuration items.

See “Creating custom status values” on page 15.

See “Configuring default values for configuration item type fields” on page 16.

See “Checking license usage” on page 16.

See “Configuring organizational hierarchy update settings” on page 17.

See “Configuring ownership settings” on page 20.

Creating custom status valuesFor some resources, your company might need to use a status that is not one ofthe predefined values. In this situation, you can create a custom status value.

2Chapter

Warning: If you assign a custom status to an asset, it becomes inactive and doesnot appear in the reports. Instead of using custom statuses, Symantec recommendsthat you create a custom status as a Location and assign the asset to this location.

See “About configuring CMDB Solution settings” on page 15.

To create custom status values

1 In the Symantec Management Console, on the Settings menu, click AllSettings.

2 In the left pane, expand Service and Asset Management > CMDB Solution,and then click CMDB Global Settings.

3 In the right pane, in the Custom Status box, type the name of the customstatus value, and then click Add.

Configuring default values for configuration item type fieldsThe default values automatically populate the fields on the configuration itemcreation page and let you save data entry time. For example, if most of the contractsin your company are assigned to the same user, you can set that user as the default.Then you only need to change the default value when the contract is assigned toa different user.

Note: When you import data, the default values are not applicable.


To configure default values for configuration item type fields


2 In the left pane, expand Service and Asset Management > CMDB Solution,and then click Default Values.

3 In the right pane, click the item for which you want to set the default values.

4 In the Data Entry default values dialog box, specify the default values, andthen click OK.

Checking license usageThe License Usage page lets you monitor the number of CMDB Solution licensesthat you own and that are in use.

Configuring CMDB SolutionAbout configuring CMDB Solution settings

16

A license is consumed each time you log in to the Symantec Management Consoleand use Asset Management Solution functions or CMDB Solution functions. AssetManagement Solution functions include software licensing, viewing or editing acontract, and viewing or editing a purchase order. CMDB Solution functions includeviewing and editing a configuration item.

A single console instance only consumes one Asset Management Solution or oneCMDB Solution license. When you work with a software licensing feature, or youedit a configuration item that has cost items attached to it, you only consume anAsset Management Solution license. When you edit a configuration item that doesnot have any cost items attached to it, you only consume a CMDB Solution license.Reporting does not use either type of license.

Asset Management Solution and CMDB Solution are licensed per concurrentconnection. For example, if you simultaneously log in to the Symantec ManagementConsole on two different computers and use Asset Management Solution functionsor CMDB Solution functions on both computers, two licenses are consumed.

Note: If you have only one CMDB license and you access the Edit ConfigurationItem page, then any subsequent users get the ThelicensecountforCMDBSolutionhas been exceeded message. After you access the Edit Configuration Item page,the license is held for 5 minutes, and then is released.



To check license usage


2 In the left pane, expand Service and Asset Management > CMDB Solution,and then click License Usage.

Configuring organizational hierarchy update settingsWhen you add new locations, cost centers, or departments into your database,the items do not appear in the Organizational Views and Groups list until theorganizational hierarchy gets updated. The Organizational Hierarchy Settingspage lets you define how often you want to update the organizational hierarchy.The default update interval is 30 seconds.

In large environments, Symantec recommends that you disable the automaticupdate task to improve the performance. If you disable the automatic update, you

17Configuring CMDB SolutionAbout configuring CMDB Solution settings

can manually run the Update Organizational Hierarchy task to update theorganizational hierarchy.


See “Updating your organizational hierarchy manually” on page 30.

To configure organizational hierarchy update settings


2 In the left pane, expand Service and Asset Management > CMDB Solution,and then click Organizational Hierarchy Settings.

3 In the right pane, configure the update interval.

4 Click Save changes.

About CMDB configuration tasksCMDB Solution lets you model configuration items for any component in yourenvironment and the relationships between them in a centralized database. It letsyou identify all components and relationships and to instigate any requiredchanges. The solution actively manages configuration items according touser-specified instructions in jobs, tasks, configuration policies, and custom CMDBrules.

When you as administrator initially set up your configuration item managementsystem, you perform several configuration tasks.

You can access CMDB configuration tasks from the Manage menu, at Jobs andTasks > System Jobs and Tasks > Service and Asset Management > CMDB.

Table 2-1 Common CMDB configuration tasks

DescriptionTask

The settings to assign Computer'sOwnership to be the PrimaryUser.Recommended schedule is daily during off peak hours.

AssignComputer'sOwnership to bethePrimaryUser

A task to clean the data for ownership relationships. Recommendedschedule is every 12 hours.

CleanOwnership

Configuring CMDB SolutionAbout CMDB configuration tasks

18

Table 2-1 Common CMDB configuration tasks (continued)

DescriptionTask

The settings for the automatic merging of Asset Computer andInventory Computer configuration items that is based on a duplicatekey. Recommended schedule is daily during off peak hours.

See “About merging duplicate configuration items” on page 47.

See “Merging two configuration items” on page 48.

DuplicateComputerMerge

The settings for the automatic merging of duplicate users that is basedon a key. Recommended schedule is daily during off peak hours.



Duplicate UserMerge

The settings to clean up inventory data for computers with the selectedasset status. Recommended schedule is daily during off peak hours.

Inventory CleanUp

The settings to control the synchronization of inventory and assetinformation. Recommended schedule is daily during off peak hours.

Inventory ToAssetSynchronization

Automatic merging of duplicate configuration items that is based ona key. Recommended schedule is daily during off peak hours.



Resource MergeRule

The settings to control the automatic update of the location of networkresources. Recommended schedule is daily during off peak hours.

Update NetworkResourceLocation

A task to update the Organizational Hierarchy groups to match theassociations in the database.

UpdateOrganizationalHierarchy

About CMDB rulesCMDB rules are the custom rules that users create for managing data and tasks.CMDB rules let you manipulate the data that is already in the CMDB. These ruleslet you normalize data or fix other consistency problems with your CMDB data.

You can create your own CMDB rules. You can target a group of assets based ontheir type and properties and then make changes to them. To create a rule, youmust define the criteria for the targeted assets, the changes that occur, and the

19Configuring CMDB SolutionAbout CMDB rules

type of action to be taken. You can test custom CMDB rules before you run them,create schedules, and notify relevant personnel.

Warning: CMDB rules are powerful and can alter vast amounts of data. Before youuse a custom CMDB rule in a production environment, Symantec highlyrecommends that you test the rule by clicking the Test rule option on the CMDBRule page.

You can also run CMDB rules using tasks and jobs.

For more information, see the topics about editing CMDB data and about runninga CMDB rule as a task in the Symantec Management Platform User Guide.


Configuring ownership settingsMultiple users, departments, and cost centers can partly own the sameconfiguration item. CMDB Solution lets you assign ownership percentage to aconfiguration item so that you can define the percentage that each of the multipleusers, departments, or cost centers owns. To allow a configuration item to havemultiple owners you must configure ownership settings.

See “Specifying ownership percentage of a configuration item” on page 50.


To configure ownership settings


2 In the left pane, expand Service and Asset Management > CMDB Solution,and then click Ownership Settings.

3 In the right pane, under Ownership Style, in the drop-down list, click one ofthe following options to allow a configuration item to have multiple owners:

■ Multiple

Warning: Once you set multiple ownership, you can no longer go back tosingle association.

■ Multiple With WarningOnce you set multiple with warning ownership, you receive a notificationwhen you assign ownership to a currently owned asset.

Configuring CMDB SolutionConfiguring ownership settings

20

4 To specify what type of owners to keep in the event of a conflict of ownership,in the right pane, under Ownership Rule, in the drop-down list, click one ofthe following options:

■ User Precedence

■ Department Precedence


21Configuring CMDB SolutionConfiguring ownership settings

Configuring CMDB SolutionConfiguring ownership settings

22

Managing yourorganizational structure


■ About organizational configuration item types

■ About the Company configuration item type

■ About the User configuration item type

■ Setting up your organizational structure

■ Creating a location

■ Creating a cost center

■ Creating a department

■ Updating your organizational hierarchy manually

About organizational configuration item typesOne of the main purposes of Asset Management Suite is to enable you to createand maintain associations among organizations, assets, and resources. Forexample, you can associate a computer with a user, a department, and a location.You can also associate a department with a specific cost center. After you specifythese logical groups and associations, you can keep track of an asset. You cantrack where an asset is located, who has it, and which department or cost centerhas responsibility for it.

Before you can make the associations, you must add organizational configurationitems into the Configuration Management Database (CMDB). The organizationalconfiguration item types let you enter organizational data and define the structure

3Chapter

of your organization. Organizational configuration item types are the essentialbuilding blocks upon which all of your other asset and contract data is based.


Organizational configuration item types are unique because they support ahierarchy for organizing resources. Organizing information in a hierarchysimplifies management and access to the data. You can view information atdifferent levels of detail. For example, you can look at the reports for all computersat a building, site, geographical region, or company level.

You must define these groups to meet the needs of your company. For eachorganizational configuration item type, decide what groups you want to use andenter the corresponding data into the CMDB. You can use the groups that yourcompany already has for departments and cost centers, unless these groupingsare too broad or too granular.

Before you enter any data, consider your organizational needs and the relationshipsthat the resources have with each other. Symantec recommends that you planand set up organizational configuration items correctly at the beginning. However,you can update and edit the organizational configuration items later.

You can use the following predefined organizational configuration item types toenter your organizational data:

■ Company

■ Cost Center

■ Department

■ Location

■ User

After you enter your organizational data and associate it with assets, contracts,and users, the system automatically creates organizational groups under theorganizational views. Organizational groups offer a great benefit when you wantto manage your assets by location or department. For example, you can applypolicies and tasks separately to the different resource targets that you create fromthe organizational groups. You can also create and configure site-specific securityroles to restrict each asset management team, so that they can only view andmanage assets of their own site.


For more information, see the topics about organizational views and groups, andconfiguring resource security in the SymantecManagement PlatformUserGuide.

Managing your organizational structureAbout organizational configuration item types

24

About the Company configuration item typeThe Company configuration item type lets you specify data for the internal or theexternal companies in the Configuration Management Database (CMDB).

See “About organizational configuration item types” on page 23.

For internal companies, the Company configuration item lets you create the toplevel of your company's organizational hierarchy, if you have subsidiaries. Insome situations, a single company consists of multiple smaller companies. TheCompany configuration item type lets you record data about these companies. Ifyou have structured your configuration item management system as a singlecompany, this configuration item type might not be needed for internal companydata.

For external companies, you can use the Company configuration item type toinsert data of the companies from whom you purchase assets. In the procurementfeature of Asset Management Suite, these companies are called suppliers.

Additionally, the Company configuration item type gets populated by the SoftwareManagement Framework. The Software Discovery scan collects data about theinstalled software and creates the software resources with the minimum metadata:the company (vendor) name, software name, and version.

For more information, see the topics about discovering software on managedcomputers in the Symantec Management Platform User Guide.

Note that the Company configuration item type does not let you create ahierarchical structure of companies.

About the User configuration item typeThe User configuration item type lets you enter data about people of your companyinto the Configuration Management Database (CMDB). The User configurationitem type is associated with the Company and the Department configuration itemtypes. You can also specify a manager for a user.

When you use Asset Management Suite for the first time, you do not have to insertuser data manually. Symantec recommends that you use Microsoft Active DirectoryImport to enter all your company's existing users into the CMDB. If the user datathat you import also contains department data, you can use it to automaticallyassign users to the departments. To accomplish this task, you must enter thedepartment data before you import the user data.

See “About importing configuration item data from other systems” on page 46.

25Managing your organizational structureAbout the Company configuration item type

You can add users manually in the Symantec Management Console when you needto add a few users at a time. For example, when you add information about newhires.


Setting up your organizational structureOrganizational configuration item types help you organize assets and configurationitems into logical groups, associations, and relationships. You use theorganizational configuration item types to create the structure of yourorganization.


Symantec recommends that you add organizational configuration items firstbecause many other configuration items are associated to them. When you createentries for assets and other configuration items, you can then associate theseitems with the organizational information that already exists.

Note that ideally you would enter all data for a configuration item at once andthen move on to the next configuration item. However, when you create anorganizational configuration item, it is often not possible. Organizationalconfiguration items have associations with each other. When you create anorganizational configuration item, you can specify all data, except the associationdata. You must create the associated configuration item, and then you can go backto the original configuration item and specify the association data. For example,if you have not created a cost center, you cannot specify a cost center for adepartment.

Table 3-1 Process for setting up your organizational structure

DescriptionActionStep

When you set up your organizational structure in the Asset ManagementSuite, the first step is to create locations. The location organizational typelets you add geographical or physical locations into the ConfigurationManagement Database (CMDB).

See “Creating a location” on page 27.

Create locationsStep 1

The cost center organizational type lets you add your company's costcenters into the CMDB.

Note that if you enter cost center data, and have not created a location, youcannot specify a location for a cost center.

See “Creating a cost center” on page 28.

Create cost centersStep 2

Managing your organizational structureSetting up your organizational structure

26

Table 3-1 Process for setting up your organizational structure (continued)


The department organizational type lets you add your company'sdepartments into the CMDB.

If you enter department data, and have not created a location and a costcenter, you cannot create according associations for a department.

See “Creating a department” on page 29.

Create departmentsStep 3

When you set up your organizational structure in the SymantecManagement Console, the organizational items do not appear in theOrganizational Views and Groups list until the organizational hierarchygets updated. By default, the automatic update runs every 30 seconds andupdates the organizational hierarchy.

If you have disabled the automatic updating of organizational hierarchy,you must use the Update Organizational Hierarchy task to manuallyrefresh the hierarchy.

See “Updating your organizational hierarchy manually” on page 30.

(Optional) Update theorganizationalhierarchy manually

Step 4

Creating a locationThe Location organizational type lets you add geographical or physical locationsinto the Configuration Management Database (CMDB). If your company hasmultiple sites around the world, you can use the geographical locations, such ascountry, state, and city, to create a location for each site. You can then associatethe assets of each site with the locations that you define. Physical locations, suchas building, floor, and cubicle, let you create separate locations at a single site.You can then associate assets of each building, floor, or cubicle to its correspondinglocation.

You can associate each location with its manager and with a cost center. Whenyou enter data for a location, you can also specify the hierarchy for it. For example,you can create a location for the United States, and then create sub-locations forthe states, such as California, Utah, and Texas.

Note that on the Location page, all location items are displayed in the flat list.You can see the hierarchy of the locations on the Organizational Views andGroups page.

For more information, see the topics about organizational views and groups inthe Symantec Management Platform User Guide.

This task is a step in the process for setting up your organizational structure.

27Managing your organizational structureCreating a location


To create a location

1 In the Symantec Management Console, on the Home menu, click ServiceandAsset Management > Manage Configuration Items.

2 In the left pane, expand Organizational Types.

3 Right-click Location and click Create Location.

4 In the Create configuration item dialog box, give the location a name.

5 (Optional) To create a hierarchy, under Location Hierarchy, specify theparent location for the item that you currently edit.

You can also first insert all locations and then use the bulk edit function toadd a parent location to a group of locations at once. To add a parent locationto a group of locations, do the following:

■ Select the locations to which you want to add the parent location.

■ Right-click one of the locations, and then click CMDB Functions >Assignment Functions > Assign Parent Location.

■ In the Select a Resource dialog box, select the parent location, and thenclick OK.

6 (Optional) If you enter the Location To Subnet parameter and then enablethe UpdateNetworkResourceLocation task, the task automatically assignsthis location to the network devices that belong to the entered subnet.

7 Click OK.

Creating a cost centerThe Cost Center organizational type lets you add your company's cost centersinto the Configuration Management Database (CMDB). Cost centers are associatedwith the departments or other sections of the company that create costs. Forexample, an engineering department, IT department, or services department caneach include one or more cost centers. The managers of these cost centers areresponsible for approving all asset purchases and ensuring that the expendituresare kept within budgets.

With each cost center, you can associate a location and a manager of a cost center.However, if your organization has a single cost center that spans multiple locations,you do not use this field. You can then only specify a cost center for each location.

See “Creating a location” on page 27.

Managing your organizational structureCreating a cost center

28

The Cost Center configuration item type lets you create a hierarchical structureof the cost centers in your company. Note that on the Cost Center page, all costcenter items are displayed in the flat list. You can see the hierarchy of the costcenters on the Organizational Views and Groups page.




To create a cost center



3 Right-click Cost Center and click Create Cost Center.

4 In the Create configuration item dialog box, give the cost center a name andspecify the Cost Center Code.

You use Cost Center Code value for accounting related data.

5 To create a child cost center, under Cost Center Hierarchy, select a parentcost center.

6 Click OK.

Creating a departmentThe Department organizational type lets you add your company's departmentsinto the Configuration Management Database (CMDB). You associate eachdepartment with a location, cost center, and a barcode that is used for physicalaudits. The Department configuration item type also lets you specify a managerfor the department.

When you enter data for a department, you can specify its hierarchical positionwithin the company. Note that on the Department page, all departments aredisplayed in the flat list. You can see the hierarchy of the departments on theOrganizational Views and Groups page.




29Managing your organizational structureCreating a department

To create a department



3 Right-click Department and click Create Department.

4 In the Create configuration item dialog box, give the department a name.

5 To create a child department, under Department Hierarchy, select a parentdepartment.

6 Click OK.

Updating your organizational hierarchy manuallyWhen you add new locations, cost centers, or departments in the SymantecManagement Console, the items do not appear in the Organizational Views andGroups list until the organizational hierarchy gets updated. By default, theautomatic update runs every 30 seconds and updates the organizational hierarchy.

In large environments, Symantec recommends that you disable the automaticupdate task to improve the performance. You can disable it on the OrganizationalHierarchySettings page that you access from the Settings menu, at AllSettings> Service and Asset Management > CMDB Solution.

If you have disabled the automatic updating of the organizational hierarchy, youcan use the Update Organizational Hierarchy task to manually refresh thehierarchy on demand. You can run this task immediately or on a specified schedule.For example, you need to run the task after every import of your organizationaldata.

This task is an optional step in the process for setting up your organizationalstructure.


To update organizational hierarchy manually

1 In the Symantec Management Console, on the Manage menu, click Jobs andTasks.

2 In the left pane, expand System Jobs and Tasks > Service and AssetManagement > CMDB, and then click Update Organizational Hierarchy.

3 On the Update Organizational Hierarchy page, add the organizationalhierarchies that you want to update.

Managing your organizational structureUpdating your organizational hierarchy manually

30

4 (Optional) Under Task Status, schedule the task.

For more information, see the topics about running a task in the SymantecManagement Platform User Guide.


31Managing your organizational structureUpdating your organizational hierarchy manually

Managing your organizational structureUpdating your organizational hierarchy manually

32

Managing security in AssetManagement Suite


■ About managing security in Asset Management Suite

■ Predefined asset management security roles

■ Managing security on an organizational group

■ Assigning an organizational group to a security role

■ Configuring security permissions for an organizational group

Aboutmanaging security in AssetManagement SuiteManaging security is an important part of asset management. Setting up thesecurity properly ensures that your data is secure while permitting users to havethe access they need.

In most environments, you have different users who need various degrees ofaccess to the Asset Management Suite features. These users might be data inputworkers, managers, or administrators. Each type of user has different accessneeds. For example, a supervisor user needs the rights to verify and updateresource entries. A manager user needs to access the reports. An administratoruser needs the rights to do everything. To set up security roles for all types ofusers, you can modify the predefined asset management security roles, or youcan create new security roles.

In a large and a complex organization that has offices in several countries,additional security management might be necessary. For example, you mightwant to restrict each asset management team, so that they can only view and

4Chapter

manage the assets for their own site. To accomplish this task, you need to createand configure site-specific security roles.


For more information, see the topics about creating and configuring a securityrole in the Symantec Management Platform Guide.

Predefined asset management security rolesWhen you install Asset Management Suite, the system automatically adds thepredefined asset management security roles to the Symantec Management Console.The predefined security roles get automatically assigned the privileges and thepermissions that their respective jobs and tasks require.

See “About managing security in Asset Management Suite” on page 33.

Table 4-1 Predefined asset management security roles

DescriptionSecurity role

This security role has privileges for managing the basicconfiguration item types. The security role also has privilegesfor the managing functions that are related to special contracttypes, software licensing, and procurement.

Asset Managers

This security role is a restricted data entry user role.Barcode User

This security role has privileges for managing basic configurationitem types, such as hardware and the base contract configurationitem type.

CMDB Managers

Managing security on an organizational groupManaging security is an important part of asset management. You can grantdifferent levels of access according to the responsibilities and location of theusers. These settings ensure that only authorized users can access and modifythe data.

See “About managing security in Asset Management Suite” on page 33.

Managing security on an organizational group involves two main steps. You assignan organizational group to a security role, and then you set the securitypermissions for the organizational group.

Managing security in Asset Management SuitePredefined asset management security roles

34

Table 4-2 Process for managing security on an organizational group


When you want to manage security on an organizational group, the firststep is to create the custom security roles. Custom security roles can helpyou better manage the assets that are dispersed over multiple sites ororganizational units.

For more information, see the topics about creating and configuring asecurity role in the Symantec Management Platform User Guide.

(Optional) Create acustom security role

Step 1

After you create a security role, you can assign an organizational group toit. Only users who are assigned to this security role can view and managethe assets of this organizational group.

See “Assigning an organizational group to a security role” on page 35.

Assign anorganizational group toa security role

Step 2

To control what a security role can do with asset records of anorganizational group, you must configure its security settings.

See “Configuring security permissions for an organizational group”on page 36.

Configure securitypermissions for anorganizational group

Step 3

Assigning an organizational group to a security roleAssigning an organizational group to a security role lets you specify the userswho can view and manage the assets in this organizational group. You can assignan organizational group to a predefined or to a custom security role. If you wantto assign the organizational group to a custom security role, you must create thecustom security role first.

For more information, see the topics about creating and configuring a securityrole in the Symantec Management Platform User Guide.

This task is a step in the process for managing security on an organizational group.


To assign an organizational group to a security role

1 In the Symantec Management Console, on the Manage menu, click AllResources.

2 In the left pane, expand any organizational view, right-click an organizationalgroup that you want to assign to a security role, and then click ManageSecurity > Assign Management Rights.

3 In the Assign Management Rights dialog box, select the security role.

4 Click OK.

35Managing security in Asset Management SuiteAssigning an organizational group to a security role

Configuring securitypermissions for anorganizationalgroup

Security permissions let you control the actions that the users of a security rolecan perform with asset records in an organizational group.

This task is a step in the process for managing security on an organizational group.


To configure security permissions for an organizational group

1 In the Symantec Management Console, on the Manage menu, click AllResources.

2 In the left pane, expand any organizational view, right-click an organizationalgroup for which you want to configure the security permissions, and thenclick Security.

3 In the Security Role Manager dialog box, in the Role list, click the securityrole that you want to configure.

4 Configure the security permissions.


Managing security in Asset Management SuiteConfiguring security permissions for an organizational group

36

Managing configurationitems


■ About configuration item types

■ About base configuration item types

■ About CMDB data classes

■ About predefined configuration item types

■ About datacenter configuration item types

■ About configuration items

■ About configuration item associations

■ About configuration item association types

■ Tracking the associations of a configuration item

■ Automatically creating configuration items for network devices

■ About importing configuration item data from other systems

■ About merging duplicate configuration items

■ Merging two configuration items

■ Creating and editing a configuration item

■ Managing edit views

■ Specifying ownership percentage of a configuration item

5Chapter

■ About asset life cycle

■ About tracking the total cost of an asset

About configuration item typesA configuration item (also known as a resource) is an individual entry in theConfiguration Management Database (CMDB) that represents any resource inyour environment. A configuration item stores the data of a resource, and enablesNotification Server to manage this resource. For example, the Computerconfiguration item lets you manage computers.

Configuration item types are the templates for creating configuration items inthe CMDB. A configuration item type is the base for all items that AssetManagement Suite monitors or manages.

A configuration item type consists of the following components:

Base configuration item type is the foundation on which aconfiguration item type is built. A configuration item typeinherits the data classes of the base configuration item type.Besides Asset and Contract, all configuration item types are basedon another configuration item type.

See “About base configuration item types” on page 38.

Base configuration itemtypes

Data classes are the building blocks of a configuration item type.Each data class defines the attributes that you can record abouta configuration item.

See “About CMDB data classes” on page 39.

Data classes

Configuration item association types create associations betweenconfiguration items and allow related data to be linked together.

See “About configuration item association types” on page 44.

Configuration itemassociation types

About base configuration item typesA base configuration item type (also known as a base resource type) is theconfiguration item type on which you base custom configuration item types asyou create them. For example, to create a custom configuration item type namedMac, you might use the Computer base configuration item type.

See “About configuration item types” on page 38.

Base configuration item types let you effectively manage configuration item types.A custom configuration item type inherits all data classes of its base configuration

Managing configuration itemsAbout configuration item types

38

item type. If the base configuration item type changes, any configuration itemtypes that are based on it also change. For example, you can create the GenericInvoice base configuration item type that includes the attributes for all invoices.You can then use the base configuration item type to create any specific invoicesthat require unique attributes. You only need to add the additional data classesfor the unique attributes.

Base configuration item types let you take advantage of built-in features such asasset aggregation, reporting, and accounting data. Any configuration item typecan serve as a base configuration item type. No special configuration is requiredto allow a configuration item type to be a base configuration item type. You performthis action when you specify a base configuration item type for a new configurationitem type. For example, most predefined asset types and contract types are basedon the Asset and Contract configuration item types correspondingly.

About CMDB data classesData classes are the building blocks of a configuration item type. They representthe categories of data that you want to record about a configuration item. Forexample, the Computer configuration item type contains the Manufacturer dataclass.

See “About configuration item types” on page 38.

CMDB Solution includes the predefined data classes that you can use. You canalso create custom data classes.

The predefined data classes let you easily create configuration item types.Predefined data classes provide many elements that configuration item typesneed. You cannot modify or delete predefined data classes. You can modify anddelete the custom data classes that you define.

Data classes specify the type of data you want to record about resources. Imported,manually entered, or predefined data populates data classes.

A data class has the following components:

Data class attributes define the data that data classes store. Dataclass attributes appear as fields when you enter data. After youadd a data class attribute to a data class, you can edit certainaspects of the attribute. You can edit the description and controlif it is hidden, but you cannot delete the description from thedata class. You cannot add data class attributes to a predefineddata class. For example, the Manufacturer data class containsthe Manufacturer Name and Model data class attributes.

Data class attribute

39Managing configuration itemsAbout CMDB data classes

Data class attribute parameters specify the characteristics of adata class attribute such as name, description, and maximumlength of the attribute. For each data class attribute, you mustspecify values for each of the parameters. You can specify thetype, number, and order of characters in a field. For example, thename to be entered into the Manufacturer Name data classattribute might have a parameter of less than 256 characters.

Data class attributeparameter

You can access CMDB data classes from the Settings menu, at All Settings >Notification Server > Resource and Data Class Settings > Data Classes > CMDBData Classes.

CMDB data classes represent the categories of data that CMDB configuration itemtypes contain.

CMDB data classes can be of the following types:

The event data classes such as Asset Merge Event andConcurrent Licensing are the predefined data classes that youcannot modify.

Predefined data classes

CMDB data classes of different types such as DatacenterClasses,Contract Details, or Identity. You can define these data classesaccording to your needs and modify the data class attributes.

Editable data classes

About predefined configuration item typesPredefined configuration item types (also known as predefined resource types)are the templates that define what data is created and stored about a specificconfiguration item.

See “About configuration items” on page 42.


Asset Management Suite provides predefined configuration item types for manytypes of assets. You can add custom fields to the predefined configuration itemtypes. You can also create new configuration item types, if required. However,Symantec recommends that you use predefined configuration item types, becausedifferent features and reports are available for the predefined configuration itemtypes.

Table 5-1 Predefined configuration item types of CMDB Solution

Predefined configuration item typesCategory

Contract, Service Level Agreement.Contract Management

Managing configuration itemsAbout predefined configuration item types

40

Table 5-1 Predefined configuration item types of CMDB Solution (continued)

Predefined configuration item typesCategory

Cell Phone, Desk Phone.Communication Equipment

Computer, Monitor, Network Printer, Peripheral, Scanner, VirtualMachine.

Computers and Peripherals

Computer Type, Power, Rack, Services, Systems, UPS.

See “About datacenter configuration item types” on page 41.

Datacenter Types

Asset, Network Resource.Generic Asset Types

Furniture and Fixtures, Office Equipment, Site, Subnet.Other Assets

Company, Cost Center, Department, Location, User.


Organizational Types

About datacenter configuration item typesDatacenter configuration item types let you track different IT managementcomponents and services. Datacenter configuration item types are the predefinedconfiguration item types of CMDB Solution.

See “About predefined configuration item types” on page 40.

Table 5-2 Datacenter configuration item types

DescriptionConfiguration itemtype

Includes the predefined Server, Test, and Workstation types tolet you specify what type of function or role a computer has. Youdetermine the computer type when you edit or create a newcomputer configuration item.

Computer Type

The power sources that the network uses and that are intendedto be associated with UPS configuration items.

Power

Network resource racks. You can specify which network resourcesare included in each rack.

Rack

41Managing configuration itemsAbout datacenter configuration item types

Table 5-2 Datacenter configuration item types (continued)

DescriptionConfiguration itemtype

The functions that support one or more business areas.

For example, the Service configuration item type lets you managethe information about your email service. Email service consistsof several components such as Active Directory, Exchange Server,and Web Mail. Each of these components might be located on aseparate server. When you set up the email service in theSymantec Management Console, you first create the systems thatsupport this service. After you create the systems, you create theService and in the Create configuration item window, underSupportingSystems, you add all related systems. When you thenreceive an incident that is related to the email service, you canuse the Resource Association Diagram to track down the problem.The Resource Association Diagram lets you quickly view all thecomponents that are connected to this particular service.

See “Tracking the associations of a configuration item”on page 45.

Services

The components that support services. For example, an ExchangeServer.

Systems

Uninterrupted power supply resources. Includes the details onvoltage, input and output frequencies, currents, and so on.

UPS

About configuration itemsAsset Management Suite stores all the asset-related information in theConfiguration Management Database (CMDB). To track an asset, you must enterits data into the database.

You enter information into the database as a configuration item (also known asa resource) entry. A configuration item represents an object or any detail that youwant your system to track. These items can be assets, locations, invoices, schedules,users, contracts, and so on.

The following items are examples of configuration items:

■ A user named Jon

■ A location named California

■ A computer named GX260

■ A depreciation schedule named Straight Line

Managing configuration itemsAbout configuration items

42

■ An invoice named Invoice0002

You can associate a configuration item with other configuration items. Forexample, you can associate a user named Jon with a location named Californiaand with a computer named GX260. After you create these associations betweenconfiguration items, you can track items and manage information in your assetmanagement environment.

Although you can enter any type of information about any configuration itemtype, Asset Management Suite provides predefined configuration item types.Configuration item types are the templates that define the data that you can storeabout a specific configuration item.



About configuration item associationsUnderstanding the relationships between various configuration item types,especially the crucial organizational configuration item types, helps you to identifythe dependencies within the Configuration Management Database (CMDB). Youcan view relationships between configuration items in the Resource AssociationDiagram that you access in the Resource Manager, in the left pane.

See “Tracking the associations of a configuration item” on page 45.

Not all configuration item types can have direct associations with each other butmost of them have indirect associations with each other. Associations are usefulfor reporting purposes. For example, a computer asset is associated with a userand the user is associated with a department. Although the asset may not bedirectly associated with the department, the asset is reported as one of thedepartment’s assets.

The following table shows direct configuration item type associations. Theconfiguration item type column presents the child (from) configuration item type,and the direct association column presents the parent (to) configuration itemtypes.


Table 5-3 Direct associations of configuration item types

Direct associationConfiguration itemtype

Cost Center, Location, User, Department, and Asset.Asset

43Managing configuration itemsAbout configuration item associations

Table 5-3 Direct associations of configuration item types (continued)

Direct associationConfiguration itemtype

Creates no direct associations.Company

Location and Manager (User).Cost Center

Cost Center, Location, and Manager (User).Department

Cost Center and Manager (User).Location

Company, Department, Location, and Manager (User).User

The following table shows indirect configuration item type associations, includingthe path for creating the association. The configuration item type column presentsthe child (from) configuration item type, and the indirect association columnpresents the parent (to) configuration item types.

Table 5-4 Indirect associations of configuration item types

Indirect associationConfiguration itemtype

User > Company

User > Department

User > User

Asset

Creates no indirect associations.Company

Creates no indirect associations.Cost Center

Cost Center > UserDepartment

Cost Center > UserLocation

Existing Users can be specified as Managers.Manager

Department > Cost Center

Department > Location

User

About configuration item association typesA configuration item association type (also known as a resource association type)lets you link resources for more convenient access to associated data. You canthen easily track the data about related configuration items. A configuration item

Managing configuration itemsAbout configuration item association types

44

association type is a template for creating a child to parent relationship betweenconfiguration items. This association links child configuration items to a parentconfiguration item. You can associate a computer monitor with a computer, a cellphone with a user, and several pieces of equipment with a lease. For example, thePower to Network Resource association type represents a group of networkresources that are directly connected to the power rather than covered by a backuppower system (UPS).

When you create a configuration item association type, a new field appears in thechild configuration item type. The field contains the list of configuration itemsthat the parent configuration item type defines. You can associate any of themwith the child configuration item type. For example, you can create a configurationitem association type that links the Monitor configuration item type to theComputer configuration item type. The Monitor configuration item type includesthe field with the list of computers that you can associate with the monitor.

CMDB Solution includes numerous predefined configuration item associationtypes. You can also create custom configuration item association types.

You can access the CMDB configuration item association types from the Settingsmenu, at Notification Server > Resource and Data Class Settings > ResourceAssociations > CMDB Association Types.

See “About configuration item associations” on page 43.

See “Tracking the associations of a configuration item” on page 45.

For more information, see the topics about viewing resource association typeinformation in the Symantec Management Platform User Guide.

Tracking the associations of a configuration itemThe Resource Association Diagram displays a graphic that shows a configurationitem and all its associated configuration items. The Resource Association Diagramlets you view relationships between assets, users, locations, departments, andcost centers. In a large environment, this graphic makes it easier to track downan asset and its dependencies.


To track associations of configuration items

1 In the Symantec Management Console, on the Manage menu, click Assets.

2 In the left pane, click the desired configuration item type.

45Managing configuration itemsTracking the associations of a configuration item

3 In the configuration items list, right-click the configuration item that youwant to track, and then click CMDB Functions > Resource AssociationDiagram.

4 (Optional) Adjust the ResourceAssociationDiagram view according to yourrequirements.

Automatically creating configuration items fornetwork devices

Gathering and entering asset information is one of the first steps in assetmanagement. You must create a configuration item for each asset that you wantto track.


You can manually create configuration items or they can be automatically created.You must manually create configuration items for non-networked assets likeoffice equipment, racks, and monitors. For networked devices, you can useinventory management tools to automate the task of creating a configurationitem. For example, you can gather inventory data about computers on yournetwork, and then have each computer automatically created as a configurationitem.

To automatically create configuration items for network devices

1 In the Symantec Management Console, on the Actions menu, click Discover> Import Microsoft Active Directory.

2 Specify the import settings and click Apply.

Each identified device is set up as a configuration item in the system.

3 (Optional) To view the configuration items, in the Symantec ManagementConsole, on the Home menu, click ServiceandAssetManagement>ManageConfigurationItems, and then click the correct folder and configuration itemtype.

About importing configuration item data from othersystems

If you have configuration item data available in a file or in another application,you can import it into the Configuration Management Database (CMDB). Importingconfiguration item data lets you save time and reduce data entry errors.

Managing configuration itemsAutomatically creating configuration items for network devices

46

You can also take advantage of the import feature when you manage part of yourdata outside of the CMDB. To make sure that the data in CMDB remains currentand accurate, Symantec recommends that you work out a process for gettingregular updates. When the data is continuously maintained outside of the assetmanagement system, you can schedule a regular import from the external datasource into the CMDB.

When you import data, ensure that the key that you use to identify a configurationitem is unique. Do not change this key when you import the same data. If the keyis not unique or is changed, duplicate entries of configuration items and otherdata import problems may appear.

You can use the following tools to import data into the CMDB:

This solution lets you transfer data from various commonmechanisms, such as OLE, ODBC, CSV files, XML files, and LDAP.

For more information, see the topics about managing CMDB datawith Data Connector in the SymantecManagementPlatformUserGuide.

Data Connector

This tool works with Data Connector Solution to import datafrom enterprise management applications, such as HP OpenViewand Remedy Action Request System.

Connector Packs

These components of Notification Server let you import datafrom sources such as Microsoft Active Directory.

For more information, see the topics about importing resourcedata in the Symantec Management Platform User Guide.

Data importcomponents


About merging duplicate configuration itemsThe feature of merging configuration items lets you merge duplicate configurationitems.

You can merge the configuration items only of the same configuration item type.For example, you can merge the two assets: a printer and a network printer. Youcan merge two contracts. But you cannot merge an asset and a contract.

When you merge two configuration items, you select the configuration item thatyou want to keep. For the data classes that both configuration items have, youselect the data class that you want to keep. If a data class exists only for theconfiguration item that you decide to delete, the data for this data class is alsodeleted.

47Managing configuration itemsAbout merging duplicate configuration items

Associations of the configuration item that you decide to delete are transferredto the configuration item that you keep. If there is more than one association ofthe same type, only the newest association remains.

You can use tasks and rules to automate recurring configuration item merges.

The base for merge tasks and rules are the merge keys. Predefined configurationitem type data classes define the merge keys. For example, to create a merge rulefor desk phones, you select the DeskPhone configuration item type. You can thenselect one of the available merge keys. The list of the merge keys is based on thedefault data classes for Desk Phone configuration item type, such as a phonenumber.

You can use Connector Solution to define the additional resource lookup keys thatappear in the Merge Key drop-down list.

A custom data class that you add to a predefined configuration item type cannotbe used as a merge key.


See “About CMDB configuration tasks” on page 18.

See “About CMDB rules” on page 19.

Merging two configuration itemsYou can merge two configuration items into a single configuration item. Forexample, if network discovery creates a new item for a computer that you alreadyset up manually, you can combine the two items. You can merge only configurationitems of the same type.



To merge two configuration items

1 Ctrl-click two configuration items of the same type.

2 Right-click one of the selected items, and then click Merge Resources.

3 In the Merge Resources dialog box, do the following:

■ For Primary Resource, check the check box next to the name that youwant to use as the item name.

■ In the Keep columns, check the check box next to the data classinformation that you want to keep.

Managing configuration itemsMerging two configuration items

48

An asterisk (*) indicates the most recently updated data.


Creating and editing a configuration itemConfiguration items represent the resources and information that you want totrack in your environment. To create a configuration item, you can use thepredefined configuration item types that Asset Management Suite provides. Youcan also create and use custom configuration item types.



See “About custom configuration item types” on page 55.

To create and edit a configuration item

1 In the Symantec Management Console, on the Manage menu, click Assets.

2 In the left pane, expand the desired folder.

3 To create a configuration item, right-click a configuration item type, and thenclick the context menu option that lets you create a new configuration item.

4 (Optional) To edit a configuration item, do one of the following:

■ In the configuration items list, double-click a configuration item.

■ In the configuration items list, right-click a configuration item, and thenclick the context menu option that lets you edit the configuration item,add associations, or change the status.

5 In the Createconfigurationitem or Editconfigurationitem window, specifythe details of the configuration item.

To make creating and editing configuration items more convenient, you canadjust the default edit view according to your needs.

See “Managing edit views” on page 50.

To speed up data entry, you can set the default data entry values forconfiguration item types.

See “Configuring default values for configuration item type fields” on page 16.

6 Do one of the following:

■ Click Save and create new, to save the data and create the next item.

■ Click Apply, to save the data and continue editing the same item.

■ Click OK, to save the data and close the window.

49Managing configuration itemsCreating and editing a configuration item

Note that in the configuration items list, you must click Refresh to displaythe changes.

Managing edit viewsAsset Management Suite offers the default edit views that let you insert dataabout your assets, purchase orders, software licenses, and other configurationitems.


When you open the dialog box to create or edit a configuration item, the defaultedit view opens. On the default edit view, you can specify information for all thedata class attributes that apply to this configuration item type. On the defaultedit view, you can also create all associations that are possible for thisconfiguration item type. When you do not need to insert some data or you preferto insert the data in a different order, you can edit the default views. You can alsocreate new views.

To manage edit views

1 Open the dialog box to create or edit a configuration item.


2 In the dialog box, in the View drop-down list, click Manage Views....

3 In the Change Edit Views dialog box, do one of the following:

■ To create a new edit view, click New, insert the name of the view, and thenclick OK.

■ To modify a default edit view, select the view that you want to edit.

4 Select the Data classes and Associations that are displayed on the Editconfiguration item page when you select the view.

Symantec suggests that you select the Data classes and Associations basedon your data entry roles.


Specifying ownership percentage of a configurationitem

Multiple users and cost centers can partly own the same configuration item. Toassign ownership percentages, first, you must allow configuration items to havemultiple users.

Managing configuration itemsManaging edit views

50

See “Configuring ownership settings” on page 20.

Then, you specify ownership by user, department, and cost center, and setownership percentages.

Ownership percentages are calculated in the following way:

■ Configuration item ownership must total 100%. If there is one owner assigned,ownership is calculated at 100%, if there are two owners assigned, theircombined values must total 100%.

■ If the ownership totals less or more than 100%, you can click the AutoCalculate option in the Ownership Details section. You can access theOwnership Details section on the Edit configuration item page. In this casethe ownership is calculated by multiplying both percentages with what isrequired to make 100%, while the ratio is maintained. For example, if oneowner owns 85% and another owns 10%, the ownership is increased to total100%. The 85:10 ratio is maintained.

■ If the ownership percentage totals more than 100%, the ratio is maintainedand the percentages are decreased to total 100%.

To specify ownership percentage of a configuration item


2 On the CI Management page, in the Asset Common Tasks Web part, clickFind and edit a CI.

3 In the Find a CI and edit it wizard, click the configuration item type of theconfiguration item to which you want to assign ownership percentage, andthen click Next.

4 Click the configuration item to which you want to assign ownership percentageand then click Finish.

5 On the Edit configuration item page, under Ownership Details, click AutoCalculate.

6 Click OK.

About asset life cycleYou can track an asset through all stages of its life cycle, from procurement toretirement. After you purchase an asset and enter its data into the ConfigurationManagement Database (CMDB), the asset starts its regular life cycle. You canmodify the Asset Status according to the changes in the life cycle.


51Managing configuration itemsAbout asset life cycle

You can also create custom statuses and set them to your assets. However, anasset with a custom status becomes inactive and does not appear in the reports.Instead of using custom statuses, Symantec recommends that you create thecustom status as a Location and assign the asset to this location.

The following example presents the life cycle of a laptop computer:

■ You request a laptop. Purchase Order lets you enter purchase data into theCMDB. The asset status is On Order.

■ You acquire the laptop. You specify the laptop data in the CMDB. The assetstatus is In Stock.

■ You deploy and inventory the laptop. You get the laptop and connect it to thenetwork. You run inventory on the laptop. As a result of inventory scan, thelaptop appears as an active asset. The asset status is Active.

■ The laptop breaks. You send the laptop to the supplier to have it fixed orreplaced under warranty. The asset status is RMA.

■ The laptop is lost or stolen. The asset status is Missing.

■ The laptop reaches its end of life. You retire the laptop. The asset status isRetired.

■ You dispose of the laptop. The asset status is Disposed.

After you set the status to Retired or Disposed, the asset becomes inactive anddoes not appear in the reports.

About tracking the total cost of an assetAsset Management Suite lets you track all the costs that occur during the lifecycleof an asset.

On average, 25% of an asset costs come from the initial purchase and 75% of thecosts are the services and the indirect costs that arise later. Tracking the totalcost lets you keep track of all the costs that incur against an asset, a user, or anorganization.

To track the costs that are associated with an asset, you use the cost items. Youcan apply the cost items to an asset manually on the Edit configuration itempage, or automatically using the receiving process.

Tracking the total cost may involve any or all of the following costs:

■ Initial purchase cost

■ Contract costsAny contractual costs that are related to an asset are included in the total costof an asset. For example, the software licenses that a computer uses.

Managing configuration itemsAbout tracking the total cost of an asset

52

■ Costs of the additional fixed assets or consumable itemsFor example, you buy a mouse for a computer or replace the toner for a printer.The receiving feature in procurement process lets you automatically apply afixed asset or a consumable item as a cost item to an existing resource.

■ Maintenance, servicing, and technical support costsYou can extend cost items by customizing a workflow to apply cost items toan asset if a certain event occurs. For example, you can apply a cost item whenan incident ticket is resolved with a particular closure code.

53Managing configuration itemsAbout tracking the total cost of an asset

Managing configuration itemsAbout tracking the total cost of an asset

54

Managing customconfiguration item types


■ About custom configuration item types

■ Creating a custom data class

■ Creating a custom configuration item type

■ Creating a custom configuration item association type

■ About data input masks

About custom configuration item typesAsset Management Suite provides predefined configuration item types (also knownas resource types) for many types of assets.


If the predefined configuration item types do not meet all your requirements, youcan customize them in your environment. For example, for some configurationitems you might have the information that cannot be stored in the existing dataclasses of the predefined configuration item types. In this situation you can defineand add custom data classes and custom configuration item association types tothe predefined configuration item types.

See “Creating a custom data class” on page 56.

See “Creating a custom configuration item association type” on page 58.

In the environment where the predefined configuration item types are notsufficient, you can create custom configuration item types. Symantec recommends

6Chapter

that when you create a custom configuration item type, you specify a baseconfiguration item type for it. The custom configuration item type inherits thedata classes, associations, and functionality from the base configuration itemtype. To extend the definition of the base configuration item type, you add customdata classes and custom resource association types.

See “Creating a custom configuration item type” on page 57.

Creating a custom data classA data class can be visualized as a table in the Configuration Management Database(CMDB). Each data class has a set of attributes that define its properties. Whenyou create a data class, you can customize it by adding, editing, and deleting itsattributes.

After you create a custom data class, you can add it to a predefined configurationitem type or to a custom configuration item type that you create.

See “Creating a custom configuration item type” on page 57.

To create a custom data class


2 In the left pane, expand Notification Server > Resource and Data ClassSettings > Data Classes > CMDB Data Classes, right-click the folder whereyou want to create a custom data class, and then click New > Editable DataClass.

3 On the NewEditableDataClass page, give the data class a name and add theattributes.

The name of the database table that is linked to the data class is created fromthe name of this data class. It begins with the prefix Inv_ followed by the dataclass name. The spaces in the data class name are replaced with the underscorecharacter. Note that the table name persists even if you later change the nameof the data class.

Symantec recommends that you do not use special characters in the customdata class names because they may cause errors.

See “About data input masks” on page 59.


Managing custom configuration item typesCreating a custom data class

56

Creating a custom configuration item typeAsset Management Suite provides predefined configuration item types for manytypes of assets. However, sometimes the predefined configuration item types arenot sufficient and you might need to create custom configuration item types.


The first step in defining a custom configuration item type is to determine whatinformation you want to track for it. You also need to decide which data types youwant to exist in only this configuration item type and which data types you wantto be linked to other configuration item types. For the data types that you wantto exist in only this configuration item type, you create the corresponding dataclasses. For the data types that you want to link to other configuration item types,you create custom association types.


See “Creating a custom configuration item association type” on page 58.

To create a custom configuration item type


2 In the left pane, expand Notification Server > Resource and Data ClassSettings > Resource Types, right-click the folder where you want to createa custom configuration item type, and then click New > Resource Type.

3 On the New Resource Type page, give the configuration item a name andspecify its settings.

If you specify the Base Resource Type, the custom configuration item typeinherits all data classes, associations, and functionality of the selected baseconfiguration item type.

To add custom data classes to the configuration item type, click Add dataclasses.


5 (Optional) To make it easier to access the custom configuration item type,create a link to this configuration item type in the CI Management portal.

To create the link, do the following:

■ In the Symantec Management Console, on the CI Management page, inthe left pane, right-click the folder where you want to place the link, andthen click New > Resource Type Link.

■ In the Select a Resource Type dialog box, click the custom configurationitem type, and then click OK.

57Managing custom configuration item typesCreating a custom configuration item type

Creating a custom configuration item associationtype

A configuration item association type defines a child (to) to parent (from)relationship between one configuration item type to one or more configurationitem types.



If the predefined associations of a configuration item type do not meet all yourrequirements, you can create custom configuration item associations. For example,you might want to associate a contract to each of your vendors as part of thecontract management. In Asset Management Suite, the default associations of aContract configuration item type do not let you create such an association. In thiscase you can create a custom configuration item association type.

To create a custom configuration item association type


2 In the left pane, expand Notification Server > Resource and Data ClassSettings > Resource Associations > CMDB Association Types, right-clickthe folder where you want to create a custom association type, and then clickNew > Editable Association Type.

3 On the NewEditableAssociationType page, give the association a name andspecify its details.

To create an association between a contract and a vendor, configure thedetails as follows:

■ Type Contract'sVendor, as the name of the new editable association type.

■ In the Reverse Display name box, type Vendor's Contracts.

■ For the From Type configuration item type, select Contract.

■ For the To Type configuration item type, select Company.

■ In the Minimum Cardinality box, type 0.

■ In the Maximum Cardinality box, type 1.Note that when you create a new association, you can only specify theminimum cardinality and maximum cardinality from parent to child. Thecardinality from child to parent is always from 0 to many, and you cannotchange it.

Managing custom configuration item typesCreating a custom configuration item association type

58

■ Under Enable Editing From, check Contract, and in the drop-down list,click Resource Association Picker for Asset.


About data input masksData input masks are the filters that selectively include or exclude certain values.When you define a data class, you can assign the masks that indicate what sortof value the data class attributes should hold. Values that do not conform to themask cannot be entered.

See “About CMDB data classes” on page 39.


Table 6-1 Data input mask characters

MeaningCharacter

Any letter. Entry required.A

Any letter. Entry optional.a

Any digit or space. Entry optional; “+” and “-” not allowed.9

Any digit (0 to 9). Entry required; “+” and “-” not allowed.0

Any letter, digit, space, “+”, or “-”. Entry optional; spaces areremoved when data is saved.

*

Any letter, digit, “+”, or “-”. Entry required.#

Treat the masking character following the “\” as a regularcharacter with no special masking properties.

\

59Managing custom configuration item typesAbout data input masks

Managing custom configuration item typesAbout data input masks

60

Aasset

life cycle 51total cost 52

asset life cycleabout 51

associationstracking 45

associations of configuration itemstracking 45

Bbase configuration item types

about 38base resource type. Seebase configuration item type

CCMDB configuration

CMDB rules 19ownership percentage of configuration items 50tasks 18

CMDB data classesabout 39

CMDB rulesabout 19

CMDB Solutionabout 9features 10new features 9settings 15

CMDB Solution settingsconfiguring 15license usage 16ownership 20

companies 23about 25

company configuration itemsabout 25

configuration item association typesabout 44

configuration item type associationsabout 43direct 43indirect 43

configuration item typesabout 38, 40association type 44base 38components 38default values 16predefined 40

configuration item types default valuesdefault values 16

configuration itemsabout 38, 42creating 46, 49editing 49–50importing 46merging 48ownership percentage 50

configuration tasksabout 18

context-sensitive help 12contracts

associating to a vendor 58cost center configuration items

creating 28cost centers 23

creating 26, 28custom configuration item association types

adding 57creating 58

custom configuration item typesabout 55creating 56–58

custom data classadding 57creating 56

custom resource typesabout 55

custom status valuesconfiguring 15

Index

Ddata class attribute 39data class attribute parameter 39data classes

components 39data input masks

about 59datacenter configuration item type 41default edit views

editing 50department configuration items

creating 29departments 23

creating 26, 29direct associations 43documentation 12duplicate configuration items

merging 47–48

Eedit views

creating 50editable data classes 39

Hhelp

context-sensitive 12

Iindirect associations 43

Llicense usage

checking 16License Usage page

about 16location configuration items

creating 27locations 23

creating 26–27

Mmanaging security

about 33merging configuration items

about 47

Nnetwork devices

creating automatically 46

Oorganizational configuration items

about 23creating structure 26organizing 26

organizational groupsconfiguring security permissions 36managing security 34permissions 34privileges 34security 34security permissions 34, 36security role 35

organizational hierarchyupdating 30

organizational hierarchy settingsconfiguring 17

organizational hierarchy updateconfiguring 17

organizational structurecreating 26setting up 26

ownership details 50ownership percentage

specifying 50ownership percentage of configuration items

about 50ownership settings

configuring 20

Ppredefined asset management security roles 34predefined configuration item types 40

RRelease Notes 12resource. See configuration itemsResource Association Diagram 45resource association type. See configuration item

association typeresource type. See configuration item types

Index62

Ssecurity

managing 33security permissions

configuring 36security roles

assigning 35predefined 34

Ttotal cost of an asset

tracking 52

Uuser configuration items

about 25users 23

about 25

63Index

Documents

Altiris CMDB Solution 7.1 SP2 from Symantec User Guideorigin-symwisedownload.symantec.com/resources/sites/SYMWISE/... · IntroducingCMDBSolution This chapter includes the following