IT Analytics Solution for
Symantec User Guide
Version 7.0 SP2
IT Analytics Solution for Symantec User Guide
The softwaredescribed inthis bookis furnishedunder alicense agreementand maybe used
only in accordance with the terms of the agreement.
Documentation version 7.0 SP2
Legal Notice
Copyright © 2009-2010 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, Altiris, and any Altiris or Symantec trademarks used in the
product are trademarks or registered trademarks of Symantec Corporation or its affiliates
in 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 document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATIONISPROVIDED "ASIS" AND ALLEXPRESS OR IMPLIEDCONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLYINVALID.SYMANTEC CORPORATIONSHALLNOT BELIABLEFOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,
PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED
IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The LicensedSoftware andDocumentation aredeemed to be commercial computer software
as definedin FAR 12.212 and subject to restricted rights as defined in FAR Section52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations. Any use, modification, reproduction release,
performance, displayor disclosure of the Licensed Software and Documentation by the U.S.
Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s primary role is to respond to specific queries about product features
and functionality.The Technical Support group also creates content forour online
Knowledge Base. The Technical Support group works collaboratively with the
other functional areas within Symantec to answer your questions in a timely
fashion. Forexample, theTechnical Supportgroup works with Product Engineering
and SymantecSecurity Response to provide alerting services andvirus definition
updates.
Symantec’s maintenance offerings include the following:
■ A range of support options that give you the flexibility to select the right
amount of service for any size organization
■ Telephone and Web-based support that provides rapid response and
up-to-the-minute information
■ Upgrade assurance that delivers automatic software upgrade protection
■ Global support that is available 24 hours a day, 7 days a week
■ Advanced features, including Account Management Services
For information about Symantec’s Maintenance Programs, you can visit our Web
site at the following URL:
www.symantec.com/techsupp/
Technical Support .......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 4
Chapter 1 Introducing IT Analytics Solution ... ..... ..... ..... ..... ......... .... 15
IT Analytics Solution ... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ....... 15
How IT Analytics works .... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ... 15
Chapter 2 Installing and configuring IT Analytics Solution .... ..... .. 17
Installing and configuring IT Analytics Solution . ..... ..... .... ..... ..... ..... .. 18
Hardware prerequisites ... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... 20
Software prerequisites ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ... 20
Installing IT Analytics Solution . ..... ..... ..... .... ..... ..... ..... ..... ......... ..... 21
Licensing IT Analytics Solution ... ..... ..... ..... .... ..... ..... ..... ..... ......... ... 21
Configuring IT Analytics Solution ........ ..... ..... ..... ..... .... ..... ..... ..... .... 22
Configuring Symantec Endpoint Protection connections ..... ..... ......... .. 23
Symantec Endpoint Protection connection fields ... ..... ..... ..... ..... ........ 24
Adding Symantec Endpoint Protection connections ..... ..... ..... ..... ........ 25
Editing Symantec Endpoint Protection connections ..... ......... ..... ..... .... 25
Deleting Symantec Endpoint Protection connections . ..... ..... ..... .... ..... . 26
Configuring the ServiceDesk connection ... ..... ..... ......... ..... ..... ..... ..... 26
ServiceDesk connection fields . .... ..... ..... ..... ..... ......... ..... ..... ..... ..... .. 27
Editing the ServiceDesk connection ... ..... ..... ..... ......... ..... ..... ..... ..... .. 28
Deleting the ServiceDesk connection .... ..... ..... ..... ......... ..... ..... ..... .... 28
Adding cubes .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... .. 29
Adding reports ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .... 29
Configuring the cube processing tasks ... ..... ......... ..... ..... ..... ..... ........ 30
Verifying your installation ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ... 30
Uninstalling IT Analytics .... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... . 31
Removing the IT Analytics Packs . ..... ..... .... ..... ..... ..... ..... ......... ..... ... 31
Uninstalling IT Analytics Solution ... ..... ..... ..... ......... ..... ..... ..... ..... ... 32
Hosting Symantec Management Platform and SQL 2005 Reporting
Services on the same server . ..... .... ..... ..... ..... ..... ......... ..... ..... .... 32
Contents
Chapter 3 Implementing IT Analytics Solution ..... ..... ......... ..... ..... ... 37
Accessing IT Analytics Solution ..... .... ..... ..... ..... ..... ......... ..... ..... ..... . 38
Viewing a dashboard report . ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... 40
Viewing a detailed report . .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... 40
Creating a new report ... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... . 40
About Pivot tables . ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .... 42
Pivot table prerequisites . ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... 42
Pivot table fields ... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ... 43
Top pivot toolbar functions . ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 43
Pivot toolbar functions ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ........ 44
Pivot charts toolbar functions ... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... 45
Saving a pivot table view . ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... .... 45
Loading a pivot table view .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... 46
Modifying a pivot table view .... ......... ..... ..... ..... ..... ......... ..... ..... ..... .. 46
Deleting a pivot table view . ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... .. 47
About displaying pivot data results ......... ..... ..... ..... ..... ......... ..... ..... . 48
Displaying results in a pivot chart . ..... ......... ..... ..... ..... ..... .... ..... ..... .. 48
Displaying results in a pivot table ..... ..... ..... ......... ..... ..... ..... ..... ....... 49
Exporting pivot table results .... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... . 49
Removing warning messages .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ..... 50
Creating a pivot table using the Computer cube example . ..... ..... ..... ..... 51
About Key Performance Indicators (KPIs) ..... ......... ..... ..... ..... ..... .... ... 52
Creating Key Performance Indicators (KPIs) ... ..... ..... ......... ..... ..... ..... . 53
Setting the status of a KPI (advanced) . ..... ..... ..... ..... .... ..... ..... ..... ..... . 54
Chapter 4 Granting access to IT Analytics Solution . ..... ..... ..... ........ 57
About security ........ ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 58
SQL Server Database Engine ........ ..... ..... ..... ..... ......... ..... ..... ..... ..... . 58
SQL Server Analysis Services . ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ... 59
Granting access to cubes using the Symantec Management
Console ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ... 60
Adding a user to a default role ........ ..... ..... ..... ..... ......... ..... ..... ..... .... 61
Modifying role privileges ... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... .. 61
Creating a role .... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... . 61
Deleting a role . ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .... 62
Granting access to cubes using SQL Server Management Studio . ..... .... . 62
SQL Server Reporting Services ... ..... ......... ..... ..... ..... ..... .... ..... ..... .... 63
Granting access to reports for authorized users using the Symantec
Management Console ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .... 64
Granting access to reports for authorized users using the Report
Manager Web site ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... 65
Granting access to the dashboards, pivot tables, and reports ... ..... .... .... 66
Contents6
Symantec Management Platform role-based privileges .... ......... ..... ..... 67
Granting access to save and load views and create new reports .... ..... .... 67
Filtering role-based cubes (advanced) ..... ......... ..... ..... ..... ..... ......... ... 68
Distributed architecture considerations (advanced) ..... ..... ..... ......... .... 69
Chapter 5 IT Analytics Solution packs .... ..... ..... ..... ..... ......... ..... ..... .... 71
About IT Analytics Solution packs ... ......... ..... ..... ..... ..... ......... ..... ..... 71
IT Analytics Asset Management Pack .... ..... ..... .... ..... ..... ..... ..... ......... 71
IT Analytics Client and Server Management Pack .... ......... ..... ..... ..... ... 72
IT Analytics Symantec Endpoint Protection Pack ..... ..... ..... ..... ..... ...... 73
IT Analytics ServiceDesk Pack .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ... 74
Appendix A Cube reference . ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... 75
Application Metering Cube .... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ... 77
Assets Cube .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... 78
Computers Cube .... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... .... 79
ESX Servers Cube ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... . 81
Event Console Alerts Cube ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ... 82
IIS Servers Cube .... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ........ 83
Installed Files Cube ... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... 84
Installed Software Cube .... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ... 85
Monitor Metrics Cube . ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ... 86
Monitor NT Events Cube .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .. 90
Monitored Processes Cube ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ... 91
Package Distribution Events Cube .... ..... .... ..... ..... ..... ..... ......... ..... .... 93
Package Server Configuration Events Cube .... ..... ..... ..... ......... ..... ..... . 94
Package Server Status Cube ... ..... ......... ..... ..... ..... ..... ......... ..... ..... ... 95
Patch Management Cube .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... . 96
ServiceDesk Changes Cube ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ... 97
ServiceDesk Incidents Cube ... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... .. 100
ServiceDesk Problems Cube . ..... ..... .... ..... ..... ..... ..... ......... ..... ..... .... 104
ServiceDesk Releases Cube ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ....... 107
Software Delivery Execution Events Cube . ..... ..... ..... ......... ..... ..... .... 110
Software Delivery Package Events Cube ... ......... ..... ..... ..... ..... .... ..... . 111
Software Delivery Status Events Cube ..... ......... ..... ..... ..... ..... .... ..... . 113
Software License Compliance Cube ... ..... ..... ..... ..... .... ..... ..... ..... ..... . 114
Software Purchases Cube . ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... .. 115
SQL Servers ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... .. 116
Symantec Endpoint Protection Access Rights Cube .... ..... ..... ..... .... .... 117
Symantec Endpoint Protection Alerts ..... ..... ......... ..... ..... ..... ..... ...... 118
Symantec Endpoint Protection Clients .... ..... ..... ..... ..... ......... ..... ..... 120
Symantec Endpoint Protection Policies ..... ..... ......... ..... ..... ..... ..... ... 121
7Contents
Symantec Endpoint Protection Scans ....... ..... ..... ..... ..... ......... ..... .... 122
Tasks . ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... .... 124
Appendix B Dashboard reference .... ..... ......... ..... ..... ..... ..... .... ..... ..... .... 125
Altiris Agent Dashboard ..... ..... ..... ..... ..... ......... ..... ..... ..... ..... ........ 126
Asset Control Dashboard ... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... 126
Computer Inventory Dashboard ... ..... ..... ..... ..... ......... ..... ..... ..... ..... 126
Event Console Alerts Dashboard .... ..... ..... ..... ..... ......... ..... ..... ..... .... 126
IT Analytics Usage Dashboard . ......... ..... ..... ..... ..... .... ..... ..... ..... ..... 126
Monitor Alerts Dashboard . ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 126
Patch Management Dashboard .... ..... ..... ..... ..... .... ..... ..... ..... ..... ...... 126
ServiceDesk Change Trend Dashboard .... ..... ..... ..... ......... ..... ..... ..... 127
ServiceDesk Incident Trend Dashboard ..... ..... ..... ..... ......... ..... ..... ... 127
ServiceDesk Problem Trend Dashboard .... ..... ..... ..... ..... ......... ..... .... 127
ServiceDesk Release Trend Dashboard . ..... ..... ......... ..... ..... ..... ..... ... 127
Software Compliance Dashboard . .... ..... ..... ..... ..... ......... ..... ..... ..... .. 128
Software Delivery Dashboard ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ... 128
Software Installs Dashboard ... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... . 128
Symantec Endpoint Protection Client Dashboard ..... ..... ..... ......... ..... 128
Symantec Endpoint Protection Risk Dashboard ..... ..... ..... ..... ......... ... 128
Vista Readiness Dashboard ... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... .. 128
Windows 7 Readiness Dashboard .... ..... ..... ..... ..... ......... ..... ..... ..... .. 129
Appendix C Report reference . ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ..... 131
Add Remove Programs by Name . ..... ..... .... ..... ..... ..... ..... ......... ..... ... 134
Add Remove Programs Search ..... ..... ......... ..... ..... ..... ..... ......... ..... . 134
Advertisement Execution Event Summary . ..... ..... ..... ......... ..... ..... ... 134
Alert and Task Details ... ..... ......... ..... ..... ..... ......... ..... ..... ..... ..... .... 135
Application Metering by File Name . ..... ..... ......... ..... ..... ..... ..... ........ 135
Application Metering Search .... ..... ..... ..... ......... ..... ..... ..... ..... ........ 135
Asset Search ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... 135
Assets by Asset Type ... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... . 135
Assets by Cost Center . ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ....... 135
Assets by Department ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... .. 136
Assets by Location ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ... 136
Assets by Model ..... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... 136
Client Version Details .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .... 136
Computer Search ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... 136
Computers by CPU . ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... . 136
Computers by Domain ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... .. 136
Computers by Manufacturer ... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... . 137
Computers by Memory . ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... . 137
Contents8
Computers by Operating System ... ......... ..... ..... ..... ..... .... ..... ..... ..... 137
Computers by System Type ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... 137
Event Console Alert Details .... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 137
Event Console Alerts Trend . ..... ..... ..... ......... ..... ..... ..... ..... ......... .... 137
Installed Files by File Name ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... 137
Installed Files Search ... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... 137
Intrusion Prevention Signature Details .... ..... ......... ..... ..... ..... ..... ..... 138
IT Analytics Configuration Events ... ......... ..... ..... ..... ..... .... ..... ..... ... 138
IT Analytics Usage Events . ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... . 138
Microsoft Server Applications ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ... 138
Microsoft Software Installs . ......... ..... ..... ..... ..... .... ..... ..... ..... ..... .... 138
Monitor Alert Details ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ... 138
Monitor Metrics CPU Utilization Trend ..... ..... ..... ......... ..... ..... ..... ... 139
Monitor Metrics Disk Utilization Trend ... ..... ..... ..... .... ..... ..... ..... ..... 139
Monitor Metrics Network Utilization Trend ..... ..... ..... .... ..... ..... ..... .. 139
Monitor Metrics Trend .... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ....... 139
Monitored Processes CPU Utilization Trend .... ..... .... ..... ..... ..... ..... ... 139
Package Download Event Summary . ..... ..... ..... ......... ..... ..... ..... ..... .. 139
Package Server Availability - Monthly . .... ..... ..... ..... ..... ......... ..... ..... 140
Package Server Availability - Daily .... ..... ..... ......... ..... ..... ..... ..... ..... 140
Patch Management Bulletin Summary .... ..... ..... ..... ..... ......... ..... ..... . 140
Patch Management Details ... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ... 140
Patch Vulnerability ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 141
Patch Vulnerability Search . .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ..... 141
Scan Trend ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 141
Servers by Type and Version .... ..... ......... ..... ..... ..... ..... ......... ..... .... 141
ServiceDesk Change Search . ..... ..... ..... ..... ......... ..... ..... ..... ..... .... .... 141
ServiceDesk Changes by Assigned to User .... ..... ..... ..... .... ..... ..... ..... . 141
ServiceDesk Changes by Impact ..... ......... ..... ..... ..... ..... ......... ..... .... 142
ServiceDesk Changes by Priority .... ..... ..... ......... ..... ..... ..... ..... ........ 142
ServiceDesk Changes by Status ... ..... ..... ..... ......... ..... ..... ..... ..... ...... 142
ServiceDesk Changes by Type . .... ..... ..... ..... ..... ......... ..... ..... ..... ..... . 142
ServiceDesk Changes by Urgency ..... ......... ..... ..... ..... ..... ......... ..... .. 142
ServiceDesk Incident Search .... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... 142
ServiceDesk Incidents by Assigned to User ..... ..... ..... ......... ..... ..... .... 143
ServiceDesk Incidents by Category ... ..... ..... ..... .... ..... ..... ..... ..... ...... 143
ServiceDesk Incidents by Impact . ..... ..... .... ..... ..... ..... ..... ......... ..... .. 143
ServiceDesk Incidents by Priority ..... ..... ..... ..... .... ..... ..... ..... ..... ...... 143
ServiceDesk Incidents by Status .... ..... ..... ..... ..... .... ..... ..... ..... ..... .... 143
ServiceDesk Incidents by Type ... ......... ..... ..... ..... ..... ......... ..... ..... ... 144
ServiceDesk Incidents by Urgency . ..... ......... ..... ..... ..... ..... ......... ..... 144
ServiceDesk Problem Search ........ ..... ..... ..... ..... ......... ..... ..... ..... .... 144
ServiceDesk Problems by Assigned to User .... ..... ..... ......... ..... ..... ..... 144
9Contents
ServiceDesk Problems by Category . ..... ..... ..... ......... ..... ..... ..... ..... ... 144
ServiceDesk Problems by Impact ..... ..... ..... .... ..... ..... ..... ..... ......... ... 144
ServiceDesk Problems by Priority .... ..... ..... ..... ..... .... ..... ..... ..... ..... .. 145
ServiceDesk Problems by Status ........ ..... ..... ..... ..... .... ..... ..... ..... ..... 145
ServiceDesk Problems by Urgency ..... ..... ......... ..... ..... ..... ..... ......... . 145
ServiceDesk Release Search .... ..... ..... ..... ......... ..... ..... ..... ..... ......... . 145
ServiceDesk Releases by Assigned to User . ..... ......... ..... ..... ..... ..... .... 145
ServiceDesk Releases by Status ..... ..... ......... ..... ..... ..... ..... ......... ..... 146
Software Delivery Search ... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... 146
Software License Compliance by Cost Center ......... ..... ..... ..... ..... ...... 146
Software License Compliance by Department ..... .... ..... ..... ..... ..... ..... 146
Software License Compliance by Location ........ ..... ..... ..... ..... .... ..... .. 146
Software License Trend .... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ...... 147
Top 10 Applications Consuming CPU ... .... ..... ..... ..... ..... ......... ..... .... 147
Top 10 Applications Consuming Memory ......... ..... ..... ..... ..... ......... .. 147
Top 10 Users Consuming CPU . ..... ..... .... ..... ..... ..... ..... ......... ..... ..... . 147
Virus Alert Details ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ... 147
Virus Alert Trend .... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... 147
Virus Definition Distribution Details ... ......... ..... ..... ..... ..... ......... ..... 148
Vista Readiness Details .... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... .. 148
Windows 7 Readiness Details ..... ..... ..... ..... ......... ..... ..... ..... ..... ....... 148
Appendix D Dimension Attribute reference ..... ..... ..... ..... ..... .... ..... ..... 149
Add Remove Programs .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .. 155
Asset ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... . 155
Asset Status ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... . 155
Asset Type ........ ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... .... 156
Computer ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... 156
Cost Center . ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... . 156
Created Date ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... . 157
Date . ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... . 157
Department ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ...... 157
EP Access Right .... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ...... 157
EP Administrator ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ... 158
EP Alert .... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ... 158
EP Alert Date .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... 158
EP AntiVirus Policy .... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... . 159
EP Application and Device Control Policy ..... .... ..... ..... ..... ..... ......... .. 160
EP Client . ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... 161
EP Computer ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... 161
EP Creation Date .... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ..... 162
EP Domain ... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... 162
Contents10
EP Firewall Policy ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... 163
EP Group .... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ..... 163
EP IDS Policy ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... 163
EP Intrusion Prevention Signature .... ..... ......... ..... ..... ..... ..... .... ..... . 164
EP Last Checkin Date .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .... 164
EP Last Scan Date .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... .... 164
EP Last Virus Date . ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... . 164
EP Live Update Policy ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ........ 165
EP Scan .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ....... 165
EP Scan Client User ........ ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... .. 165
EP Scan Start Date ... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ......... 166
EP Scan Status ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ....... 166
EP Server .... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... . 166
EP Site .... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... 166
EP Virus . ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... 166
EP Virus Definition .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... .. 167
ESX Storage Volume . ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ... 167
ESX Virtual Machine ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... .... 167
Event Console Alert . .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... 168
Event Console Alert Action Audit Type ..... ......... ..... ..... ..... ..... ......... 168
Event Console Alert Category .... ..... ..... ..... ..... .... ..... ..... ..... ..... ....... 168
Event Console Alert Severity ... ..... ......... ..... ..... ..... ..... ......... ..... ..... 168
Event Console Monitor Rule ... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... . 168
File .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ........ 169
Filter ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... . 169
IIS FTP Site .... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 169
IIS Server ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... 169
IIS Virtual Directory . ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ........ 170
IIS Web Site .... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ... 171
Last Basic Inventory Date .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 172
Location .. ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .... 172
Logical Disk ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .. 172
Monitor Metric . ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ..... 173
Monitor Metric Detail Level ... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... .. 173
Monitor Metric Instance ... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 173
Monitor Metric Source ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 173
Monitor NT Event Category .... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... . 173
Monitor NT Event Description ......... ..... ..... ..... ..... ......... ..... ..... ..... . 173
Monitor NT Event ID ... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 173
Monitor NT Event Log File ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ....... 174
Monitor NT Event Message DLL . ..... ..... ......... ..... ..... ..... ..... ......... ... 174
Monitor NT Event Rule Triggered ........ ..... ..... ..... ..... ......... ..... ..... ... 174
Monitor NT Event Source . ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... .. 174
11Contents
Monitor NT Event Type ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... 174
Monitor NT Event User .... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... .. 174
Monitor Process Name ... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ... 174
Monitor Process Owner . ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... .... 175
Monitor Task ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... . 175
Organizational Group .... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... .... 175
Package .... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ... 175
Package Distribution Event Status .... ..... ..... ..... ..... ......... ..... ..... ..... . 175
Package Download Method ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... . 175
Package Download Source ....... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... 175
Package Download URL ... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... .. 176
Package Server . ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... . 176
Package Status ..... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... .. 176
Parent Task ... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... .... 176
Processor . ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... .... 176
ServiceDesk Affected User .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ...... 176
ServiceDesk Assigned to User . ......... ..... ..... ..... ..... ......... ..... ..... ..... . 177
ServiceDesk Change . ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... .... 178
ServiceDesk Change Impact ........ ..... ..... ..... ..... ......... ..... ..... ..... ..... . 178
ServiceDesk Change Location ..... ..... ..... ..... ..... .... ..... ..... ..... ..... ...... 178
ServiceDesk Change Priority .... ......... ..... ..... ..... ..... .... ..... ..... ..... .... 178
ServiceDesk Change Source . ..... ..... ..... ..... ......... ..... ..... ..... ..... ........ 178
ServiceDesk Change Status ... ..... ......... ..... ..... ..... ..... ......... ..... ..... .. 179
ServiceDesk Change Type ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... .. 179
ServiceDesk Change Urgency ........ ..... ..... ..... ..... ......... ..... ..... ..... .... 179
ServiceDesk Contact Type .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 179
ServiceDesk Created by User . ..... ..... ..... ..... ......... ..... ..... ..... ..... ...... 179
ServiceDesk Date Closed ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... .... 180
ServiceDesk Date Due .... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ... 180
ServiceDesk Date Ended ... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... . 180
ServiceDesk Date Implemented ... ..... ..... ..... ..... .... ..... ..... ..... ..... ...... 181
ServiceDesk Date Modified ... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ... 181
ServiceDesk Date Needed .... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... 181
ServiceDesk Date Opened .... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... .... 181
ServiceDesk Date Resolved . ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... 182
ServiceDesk Date Reviewed ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... 182
ServiceDesk Date Scheduled .... ..... ..... ..... ......... ..... ..... ..... ..... ......... 182
ServiceDesk Date Started .... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... .... 182
ServiceDesk Incident .... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... . 183
ServiceDesk Incident Category . ......... ..... ..... ..... ..... ......... ..... ..... ..... 183
ServiceDesk Incident Close Code . ..... ..... ..... ......... ..... ..... ..... ..... .... .. 183
ServiceDesk Incident Impact . ......... ..... ..... ..... ..... .... ..... ..... ..... ..... .. 184
ServiceDesk Incident Location ... ..... .... ..... ..... ..... ..... ......... ..... ..... ... 184
Contents12
ServiceDesk Incident Priority ..... ..... ......... ..... ..... ..... ..... ......... ..... .. 184
ServiceDesk Incident Source .... ......... ..... ..... ..... ..... ......... ..... ..... ..... 184
ServiceDesk Incident Status .... ..... ..... ......... ..... ..... ..... ..... ......... ..... 184
ServiceDesk Incident Type ... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ... 184
ServiceDesk Incident Urgency . .... ..... ..... ..... ..... ......... ..... ..... ..... ..... 184
ServiceDesk Last Modified by User ... ......... ..... ..... ..... ..... .... ..... ..... .. 185
ServiceDesk Problem . ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... .. 185
ServiceDesk Problem Category ..... ......... ..... ..... ..... ..... ......... ..... ..... . 185
ServiceDesk Problem Impact ..... ......... ..... ..... ..... ..... ......... ..... ..... ... 186
ServiceDesk Problem Location . ..... ......... ..... ..... ..... ..... ......... ..... ..... 186
ServiceDesk Problem Priority .... ..... ..... ......... ..... ..... ..... ..... ......... ... 186
ServiceDesk Problem Source .... .... ..... ..... ..... ..... ......... ..... ..... ..... .... 186
ServiceDesk Problem Status ... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... . 186
ServiceDesk Problem Urgency ..... ......... ..... ..... ..... ..... .... ..... ..... ..... . 186
ServiceDesk Reference .... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... .. 186
ServiceDesk Release .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... . 187
ServiceDesk Release Location ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ... 187
ServiceDesk Release Status ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... 187
ServiceDesk Resolved by User ..... ..... ......... ..... ..... ..... ..... ......... ..... .. 187
ServiceDesk Time Closed ..... ..... ..... ..... ..... ......... ..... ..... ..... ..... ....... 188
ServiceDesk Time Due ........ ..... ..... ..... ..... ......... ..... ..... ..... ..... ........ 188
ServiceDesk Time Ended . ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ... 188
ServiceDesk Time Implemented ........ ..... ..... ..... ..... ......... ..... ..... ..... 189
ServiceDesk Time Modified ... ..... ..... ..... ..... ......... ..... ..... ..... ..... ...... 189
ServiceDesk Time Needed .... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ... 189
ServiceDesk Time Opened .... ..... ..... ......... ..... ..... ..... ..... ......... ..... ... 189
ServiceDesk Time Resolved . ..... ..... ..... .... ..... ..... ..... ..... ......... ..... .... 190
ServiceDesk Time Reviewed ..... ..... ..... ..... ..... ......... ..... ..... ..... ..... ... 190
ServiceDesk Time Scheduled ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ... 190
ServiceDesk Time Started .... ..... ..... ......... ..... ..... ..... ..... ......... ..... ... 190
ServiceDesk User . ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .. 191
Software Component .... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... 191
Software Delivery Advertisement ..... ..... ..... ..... ..... .... ..... ..... ..... ..... . 191
Software Delivery Execution Event Command Line . ..... ..... .... ..... ..... .. 192
Software Delivery Execution Event Status . ..... ..... .... ..... ..... ..... ..... .... 192
Software Delivery Package Event Status .... ..... ..... ..... ..... ......... ..... ... 192
Software Delivery Status Event Status .... ..... ..... ..... ..... ......... ..... ..... . 192
Software Delivery Status Event Type ..... ..... ......... ..... ..... ..... ..... .... .. 192
Software License . ..... ..... ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ........ 192
Software Product .... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... . 192
Software Purchase . ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... . 193
Software Update . ......... ..... ..... ..... ..... .... ..... ..... ..... ..... ......... ..... .... 193
SQL Cluster . ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... . 193
13Contents
SQL Cluster Resource . .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 193
SQL Database . ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... .. 194
SQL Database Creation Date .... ..... ..... ......... ..... ..... ..... ..... ......... ..... 194
SQL Database System ........ ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... 194
SQL Storage Area . ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ... 195
SQL User . ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... .... 195
Task .... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ... 195
Task Server ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... .. 195
Time ..... ..... .... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... . 196
User ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... .. 196
Index .. ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... ......... ..... ..... ..... ..... .... ..... ..... .. 197
Contents14
Introducing IT Analytics
Solution
This chapter includes the following topics:
■ IT Analytics Solution
■ How IT Analytics works
IT Analytics Solution
IT Analytics Solution software complements and expands upon the traditional
reporting that is offered in most Symantec solutions. It brings multi-dimensional
analysis and robust graphical reporting features to Symantec Management
Platform. This functionality allows users to explore data on their own, without
advanced knowledge of databases or third-party reporting tools. It empowers
users to ask and answer their own questions quickly, easily, and effectively.
IT Analytics Solution represents the information and relationships that are at
the coreof the IT decision making process. The result isa robust multi-dimensional
model that provides an entirely new way to explore and view IT data. It enables
users to answer dynamic sequences of questions as fast as they are asked. The
focus shifts to thought leadership and positive change within the organization.
Now users don’t need to toil over complex reports and base decisions upon
assumptions or incomplete data.
How IT Analytics works
Data is extracted from the CMDB as well as from external databases, transformed
through a multidimensional model, and stored in cubes within the Microsoft
Analysis Servicesdatabase. These cubes act as the datasource for the presentation
1
Chapter
layer. They consist of pivot tables as well as reports and dashboards that are
hosted in Microsoft SQL Reporting Services.
IT Analytics Solution uses the following software components:
■ Symantec Management Platform 7.0–The primary component that interacts
and accesses the functionality that IT Analytics Solution provides.
■ Microsoft SQL Server Analysis Services–Used as the primary data layer for
the dashboards, pivot tables, and reports.
■ Microsoft SQL Server Reporting Services–Used as the presentation layer for
the reports and dashboards.
■ Microsoft Office Web Components 11 (2003)–Used as one of the presentation
layers to provide raw access to browse the cubes through pivot tables.
IT Analytics Solution isthe foundationsolution thatprovides allof thefunctional
components. The solution is a prerequisite solution for IT Analytics Packs that
does not require a license (similar to Symantec Management Platform). However,
on its own, IT Analytics Solution does not contain any cubes or reports.
The actualdefinitions for the cubes, reports, and dashboardsare contained within
the IT Analytics Packs that align with the existing Symantec suites. These
definitions provide the business value for IT Analytics Solution.
The following IT Analytics Packs are available for IT Analytics Solution 7.0:
■ IT Analytics Asset Management Pack
■ IT Analytics Client and Server Management Pack
■ IT Analytics Symantec Endpoint Protection Pack
■ IT Analytics ServiceDesk Pack
Introducing IT Analytics Solution
How IT Analytics works
16
Installing and configuring
IT Analytics Solution
This chapter includes the following topics:
■ Installing and configuring IT Analytics Solution
■ Hardware prerequisites
■ Software prerequisites
■ Installing IT Analytics Solution
■ Licensing IT Analytics Solution
■ Configuring IT Analytics Solution
■ Configuring Symantec Endpoint Protection connections
■ Symantec Endpoint Protection connection fields
■ Adding Symantec Endpoint Protection connections
■ Editing Symantec Endpoint Protection connections
■ Deleting Symantec Endpoint Protection connections
■ Configuring the ServiceDesk connection
■ ServiceDesk connection fields
■ Editing the ServiceDesk connection
■ Deleting the ServiceDesk connection
■ Adding cubes
2
Chapter
■ Adding reports
■ Configuring the cube processing tasks
■ Verifying your installation
■ Uninstalling IT Analytics
■ Removing the IT Analytics Packs
■ Uninstalling IT Analytics Solution
■ Hosting Symantec Management Platform and SQL 2005 Reporting Services
on the same server
Installing and configuring IT Analytics Solution
From the Symantec Management Console, you can install, configure, and setup
your version of IT Analytics Solution.
Table 2-1
Process for installing and configuring IT Analytics Solution
DescriptionActionStep
You must ensure that your computer
meets the hardware prerequisites and
install specificsoftware before you install
IT Analytics Solution.
See “Hardwareprerequisites” on page 20.
See “Software prerequisites” on page 20.
Verify that your computer meets
the hardware prerequisites and
that theproper softwareis installed
and configured.
Step 1
You caninstall ITAnalytics Solutionfrom
within the Symantec Installation
Manager.
See “Installing IT Analytics Solution”
on page 21.
Install IT Analytics Solution.Step 2
You can install a seven-day trial version,
extend your trial, or purchase an IT
Analytics Solution license.
See “Licensing IT Analytics Solution”
on page 21.
License IT Analytics Solution.Step 3
Installing and configuring IT Analytics Solution
Installing and configuring IT Analytics Solution
18
Table 2-1
Process for installing and configuring IT Analytics Solution
(continued)
DescriptionActionStep
You can specify the name of your
Analysis Services server, database,
Reporting Servicesvirtual directory, and
report folder.
See “Configuring IT Analytics Solution”
on page 22.
Configure IT Analytics Solution.Step 4
You canconfigure the Symantec Endpoint
Protection connections that the IT
Analytics SymantecEndpoint Protection
Pack uses.
See “Configuring Symantec Endpoint
Protection connections” on page 23.
(Optional) Configure the Symantec
Endpoint Protection connections.
Step 5
You can configure the ServiceDesk
connections that IT Analytics
ServiceDesk Pack uses.
See “Configuring the ServiceDesk
connection” on page 26.
(Optional) Configure the
ServiceDesk connections.
Step 6
You can choose the cubes that you want
to include in your environment.
See “Adding cubes” on page 29.
Add the cubes.Step 7
You can choose the reportsthat you want
to include in your environment.
See “Adding reports” on page 29.
Add the reports.Step 8
You can choose how often each installed
cube is processed. Usually, each cube is
processed daily.
See “Configuring the cube processing
tasks” on page 30.
Schedule thecube processingtasks.Step 9
You can check to see that your
installation was successful and that your
version of IT Analytics Solution contains
all the necessary parts.
See “Verifying your installation”
on page 30.
Verify your installation.Step 10
19Installing and configuring IT Analytics Solution
Installing and configuring IT Analytics Solution
Hardware prerequisites
The computerthat you want to install IT Analytics Solution onshould meetspecific
hardware requirements.
See “Installing and configuring IT Analytics Solution” on page 18.
In addition to the hardware required for the Symantec Management Platform,
the following hardware is recommended:
■ Pentium 4 1.8 GHz CPU
■ 1 GB RAM
■ 5 GB of free disk space
Software prerequisites
IT Analytics Solution requires that specific software be installed.
See “Installing and configuring IT Analytics Solution” on page 18.
Before you install IT Analytics Solution, the following software must be installed
and configured:
■ Symantec Management Platform 7.x
■ Microsoft SQL Server Analysis Services (for IT Analytics Cube database)
Supported versions: 2005 SP2 and 2008 SP1.
For more information about proper configuration, see the Microsoft MSDN
Web site at http://msdn2.microsoft.com/en-us/library/ms143764.aspx.
■ Microsoft SQL Server Reporting Services (for IT Analytics Reports)
Supported versions: 2005 SP2 and 2008 SP1.
For more information about proper configuration, see the Microsoft MSDN
Web site at http://go.microsoft.com/fwlink/?LinkID=91847.
We recommend that you disable Internet Explorer Enhanced Security on the
computer that hosts Microsoft SQL Server 2005 Reporting Services.
■ ADOMD.NET 9.0
Installed on Notification Server.
Install the ADOMD.NET.msi file with the default configuration.
For the downloadable file, see
http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60a13c-4479-9b91-9e8b9d835cdc&displaylang=en.
■ Microsoft Office Web Components 11 (2003)
Installed on all computers that access the console.
Installing and configuring IT Analytics Solution
Hardware prerequisites
20
The owc11.exe file is installed with the default configuration.
For the downloadable file, see
http://www.microsoft.com/downloads/details.aspx?familyId=7287252C402E-4F72-97A5-E0FD290D4B76&displaylang=en.
Installing IT Analytics Solution
You can install IT Analytics Solution from the Symantec Management Console.
See “Installing and configuring IT Analytics Solution” on page 18.
To install IT Analytics Solution
1
Launch the Symantec Installation Manager.
2
Click Install New Products.
3
Change the filter from Suites to Solutions.
4
Scroll down the list, and check IT Analytics Solution, IT Analytics Client
andServerManagement Pack, ITAnalyticsSymantecEndpointProtection
Pack, IT Analytics Asset Management Pack, and IT Analytics ServiceDesk
Pack.
5
Click Review Selected Products.
6
Click Next.
7
Follow the rest of the installation instructions.
Licensing IT Analytics Solution
IT Analytics Solution is installed with a seven-day trial license. For an extended
trial or to purchase IT Analytics Solution, contact Altiris Sales. For more
information on registering your solution, see the Altiris Getting Started Guide.
See “About IT Analytics Solution packs” on page 71.
See “Installing and configuring IT Analytics Solution” on page 18.
To install IT Analytics Solution licenses
1
Launch the Symantec Installation Manager.
2
Click Add/Install Updates.
3
Click the Apply licenses symbol.
4
Browse to and select the appropriate license.
5
Click Open.
21Installing and configuring IT Analytics Solution
Installing IT Analytics Solution
Configuring IT Analytics Solution
You can configure IT Analytics Solution to meet the needs of your environment.
See “Installing and configuring IT Analytics Solution” on page 18.
To configure IT Analytics Solution
1
From the Symantec Management Console, on the Home menu, click IT
Analytics.
2
In the left pane, expand the Settings folder.
3
Click Configuration.
4
In the right pane, click the General tab.
5
Under Analysis Server, enter the hostname of the Analysis Services server.
If you did not install SQL Server as the default instance, specify the following
format: servername\instancename.
We recommendusing theserver name where Analysis Services resides. Using
localhost restricts access from the Symantec Management Console to the
computer where Analysis Services resides.
6
Click VerifyConnection, and confirm that the Analysis Server namehas been
verified and saved.
7
Under Analysis Server Database, select an Analysis Server Database.
For a new standard configuration, in the Create New Database box, accept
the default to create a new Analysis Server Database with the IT Analytics
name. If you select an existing database, note that the existing data sources
are overwritten with the current Symantec Management Platform database
settings.
8
Click SaveDatabaseSettings and confirm that Analysis Server Database has
been verified and saved.
9
Under Reporting Server, in the Reporting Server Virtual Directory URL
box, enter the full URL of the Reporting Services ReportServer virtual
directory.
If you did not install SQL Server as the default instance, specify the virtual
directory in the following format:
http://servername/ReportServer$InstanceName/.
We recommend using the server name where Reporting Services resides.
Using localhost restricts access from the Symantec Management Console to
the computer where Reporting Services resides.
Installing and configuring IT Analytics Solution
Configuring IT Analytics Solution
22
10
Click Verify Connection and confirm that the Reporting Server name has
been verified and saved.
11
In the Create New Report Folder box, accept the default to create a new IT
Analytics Report Folder.
If you select an existing folder, existing data sources are overwritten with
the current Analysis Server Database settings.
12
Under AuthenticationType, click one of the following options for accessing
Reporting Services:
■ Windows Integration Authentication lets the user's Windows credentials
pass through to the Reporting Server. This method is recommended for
restricting access to Reporting Services on a per user basis. This method
is best suited for environments where all users are on the same domain.
■ Stored Credentials explicitly defines the user credentials. Access to
Reporting Services is always authenticated with the same rights for all
users. This method is recommendedwhen theusers that access Reporting
Services are not in Active Directory or are not in the same domain.
13
Click SaveFolderSettings and confirm thatthe Report Folder name is verified
and saved.
14
(Optional) Click the Optional Settings tab and verify that the Report
Integration URLscontain thecorrect Symantec Management Platform name.
If necessary, you can click Edit URLs to make changes.
Configuring Symantec Endpoint Protection
connections
You need to complete these steps only if the IT Analytics Symantec Endpoint
Protection Pack is installed.
Configure theseconnections beforeyou install the IT Analytics Symantec Endpoint
Protection cubes.
See “Installing and configuring IT Analytics Solution” on page 18.
To configure Symantec Endpoint Protection connections
1
From the Symantec Management Console, on the Home menu, click IT
Analytics.
2
In the left pane, expand the Settings > Connections folders.
3
Click Symantec Endpoint Protection.
23Installing and configuring IT Analytics Solution
Configuring Symantec Endpoint Protection connections
4
In the right pane, enter the information for each of the connection fields.
See “Symantec Endpoint Protection connection fields” on page 24.
5
Click Apply.
6
(Optional) Add, edit, and delete Symantec Endpoint Protection connections.
See “Adding Symantec Endpoint Protection connections” on page 25.
See “Editing Symantec Endpoint Protection connections” on page 25.
See “Deleting Symantec Endpoint Protection connections” on page 26.
Symantec Endpoint Protection connection fields
You can add, edit, and modify Symantec Endpoint Protection connections by
entering information for the corresponding fields.
See “Adding Symantec Endpoint Protection connections” on page 25.
See “Editing Symantec Endpoint Protection connections” on page 25.
See “Deleting Symantec Endpoint Protection connections” on page 26.
See “Configuring Symantec Endpoint Protection connections” on page 23.
Table 2-2
Fields for Symantec Endpoint Protection connections
DescriptionField
The name of the server that hosts the Symantec
Endpoint Protection Manager database.
SEP Database Server Name
The name of the Symantec Endpoint Protection
Manager database.
The defaultdatabase name and schema name is SEM5.
If you use several Symantec Endpoint Protection
Managers in your environment, you might want to
change this name.
SEP Database Name
The user name for the Symantec Endpoint Protection
Manager database.
SEP Database Username
The password for the Symantec Endpoint Protection
Manager database.
SEP Database Password
The confirming password for the Symantec Endpoint
Protection Manager database.
SEP Database Password
Confirmation
Installing and configuring IT Analytics Solution
Symantec Endpoint Protection connection fields
24
Adding Symantec Endpoint Protection connections
IT Analytics Solution lets you add Symantec Endpoint Protection connections so
their relevant data can be leveraged for reporting purposes.
See “Editing Symantec Endpoint Protection connections” on page 25.
See “Deleting Symantec Endpoint Protection connections” on page 26.
See “Configuring Symantec Endpoint Protection connections” on page 23.
See “Installing and configuring IT Analytics Solution” on page 18.
To add Symantec Endpoint Protection connections
1
From the Symantec Management Console, on the Home menu, click IT
Analytics.
2
In the left pane, expand the Settings > Connections folders.
3
Click Symantec Endpoint Protection.
4
In the right pane, click New, and enter the information for each of the
connection fields.
See “Symantec Endpoint Protection connection fields” on page 24.
5
Click Apply.
Editing Symantec Endpoint Protection connections
IT Analytics Solution lets you edit Symantec Endpoint Protection connections so
that data can be leveraged for reporting purposes.
See “Adding Symantec Endpoint Protection connections” on page 25.
See “Deleting Symantec Endpoint Protection connections” on page 26.
See “Configuring Symantec Endpoint Protection connections” on page 23.
See “Installing and configuring IT Analytics Solution” on page 18.
To edit Symantec Endpoint Protection connections
1
From the Symantec Management Console, on the Home menu, click IT
Analytics.
2
In the left pane, expand the Settings > Connections folders.
3
Click Symantec Endpoint Protection.
4
In the right pane, select the server that you want to add from the drop-down
list.
The information appears for the server that you selected.
25Installing and configuring IT Analytics Solution
Adding Symantec Endpoint Protection connections
5
Change the information for any of the following fields:
■ SEP Database Username
■ SEP Database Password
■ SEP Database Password Confirmation
See “Symantec Endpoint Protection connection fields” on page 24.
6
Click Apply.
Deleting Symantec Endpoint Protection connections
IT Analytics Solution lets you delete Symantec Endpoint Protection connections
to remove data from reports.
You might have only oneSymantec EndpointProtection connection left and there
are IT Analytics Symantec Endpoint Protection cubes installed on your system.
In that case, you cannot delete the server until you uninstall the cubes.
See “Adding Symantec Endpoint Protection connections” on page 25.
See “Editing Symantec Endpoint Protection connections” on page 25.
See “Configuring Symantec Endpoint Protection connections” on page 23.
See “Installing and configuring IT Analytics Solution” on page 18.
To delete Symantec Endpoint Protection connections
1
From the Symantec Management Console, on the Home menu, click IT
Analytics.
2
In the left pane, expand the Settings > Connections folders.
3
Click Symantec Endpoint Protection.
4
In theright pane, select the server that youwant to delete from the drop-down
list.
5
Click Delete.
Configuring the ServiceDesk connection
You need to complete these steps only if the IT Analytics ServiceDesk Pack is
installed.
Configure a connection before you install the IT Analytics ServiceDesk cubes.
See “Installing and configuring IT Analytics Solution” on page 18.
Installing and configuring IT Analytics Solution
Deleting Symantec Endpoint Protection connections
26
To configure the ServiceDesk connection
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings > Connections folders.
3
Click Symantec ServiceDesk.
4
In the right pane, enter the information for each of the connection fields.
See “ServiceDesk connection fields” on page 27.
5
Click Apply.
6
(Optional) Edit and delete the ServiceDesk connection.
See “Editing the ServiceDesk connection” on page 28.
See “Deleting the ServiceDesk connection” on page 28.
ServiceDesk connection fields
You can edit and modify the ServiceDesk connection by entering information for
the corresponding fields:
See “Editing the ServiceDesk connection” on page 28.
See “Deleting the ServiceDesk connection” on page 28.
See “Configuring the ServiceDesk connection” on page 26.
See “Installing and configuring IT Analytics Solution” on page 18.
Table 2-3
Fields for ServiceDesk connections
DescriptionField
The nameof theserver thathosts theServiceDesk
database.
ServiceDesk Database Server Name
The name of the ServiceDesk database.ServiceDesk Database Name
The user name for the ServiceDesk database.ServiceDesk Database Username
The password for the ServiceDesk database.ServiceDesk Database Password
The confirming password for the ServiceDesk
database.
ServiceDesk Password Confirmation
The base URL to theProcess Manager that is used
to open the incident from the Incident Search
report.
Process Manager Base URL
27Installing and configuring IT Analytics Solution
ServiceDesk connection fields
Editing the ServiceDesk connection
IT Analytics Solution lets you edit the ServiceDesk connection so that the data
can be leveraged for reporting purposes.
See “Deleting the ServiceDesk connection” on page 28.
See “Configuring the ServiceDesk connection” on page 26.
See “Installing and configuring IT Analytics Solution” on page 18.
To edit the ServiceDesk connection
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings > Connections folders.
3
Click Symantec ServiceDesk.
4
Change the information for any of the following fields:
■ ServiceDesk Database Username
■ ServiceDesk Database Password
■ ServiceDesk Password Confirmation
See “ServiceDesk connection fields” on page 27.
■ Report Integration URL, which lets you specify an alternate base URL to
access the Process Viewer page for this ServiceDesk instance. The IT
Analytics reports uses this URL to launch a specific incident to display
further details.
5
Click Apply.
Deleting the ServiceDesk connection
IT Analytics Solution lets you delete the ServiceDesk connection to remove its
data from the reports.
See “Editing the ServiceDesk connection” on page 28.
See “Configuring the ServiceDesk connection” on page 26.
See “Installing and configuring IT Analytics Solution” on page 18.
To delete the ServiceDesk connection
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings > Connections folders.
3
Click Symantec ServiceDesk.
Installing and configuring IT Analytics Solution
Editing the ServiceDesk connection
28
4
In the right pane, from the drop-down list, click the server that you want to
delete.
5
Click Delete.
Adding cubes
You can add cubes to your environment that match your needs.
See “Installing and configuring IT Analytics Solution” on page 18.
To add cubes
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings > Cubes folders.
3
In the Cube Setup window, click the Available tab.
4
Select each cube to install.
5
Click Save Changes.
6
At the prompt, click OK to proceed with the installation.
7
Verify that the cubes were successfully created by clicking the Installed tab,
and then review the list of cubes.
Adding reports
You can add reports to your environment that match your needs.
See “Installing and configuring IT Analytics Solution” on page 18.
To add reports
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings > Reports folders.
3
In the Report Setup window, click the Available tab.
4
Select each report to install.
5
Click Save Changes.
6
At the prompt, click OK to proceed with the installation.
7
Verify that the reports were successfully installed by clicking the Installed
tab, and then review the list of reports.
29Installing and configuring IT Analytics Solution
Adding cubes
Configuring the cube processing tasks
You can create and assign processing schedules for all installed cubes. Your
business needs dictate how often the cubes should be processed. For a typical
configuration, all cubes should be processed daily.
Multiple processingtasks can be used for more granular control ofcube processing.
More than one cube can share a dimension. However, the last processed date of
all cubes that use that dimension updates to the last processed date of the shared
dimensions inthis case. However, the actual fact data in the cubes is not processed
until a processing task is run that is configured to process that specific cube.
See “Installing and configuring IT Analytics Solution” on page 18.
To configure the cube processing tasks
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings > Processing folders.
3
Select the schedule that you want for the default processing tasks, and then
click Enable Schedule.
4
Check the box for each available cube that you want to be processed on the
current schedule.
For a typical configuration, select all cubes.
5
Click Save Changes and confirm that the Default Processing Task is saved.
6
Click Run Now.
The selected Processing Tasks starts asynchronously, which means that the
task won’tfinish by the time that the pagerefreshes. This task can take several
minutes to execute. The execution time depends on the number of the cubes
that are selected and the size of data within the CMDB. You can view the
events inthe EventViewer window while the manual processing task executes
to monitor its progress.
This task is essential for the solution to function properly because the cubes
won’t have any data until the process completes.
Verifying your installation
You can verify your installation and ensure that all of your configuration steps
complete successfully.
See “Installing and configuring IT Analytics Solution” on page 18.
Installing and configuring IT Analytics Solution
Configuring the cube processing tasks
30
To verify your installation
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
Verify that the correct items appear in your installation.
The left pane should include the following items:
■ Dashboards
■ Pivot Tables
If you experience pop-up dialogs while your pivot tables load, you need
to remove the warning messages.
See “Removing warning messages” on page 50.
■ Reports
■ Settings
Uninstalling IT Analytics
You can uninstall IT Analytics Solution by removing the IT Analytics Packs from
Symantec Management Platform and then uninstalling IT Analytics Solution
itself.
Table 2-4
Process for uninstalling IT Analytics
DescriptionActionStep
You can use Symantec Installation
Manager to remove your IT Analytics
Packs.
See “Removing the IT Analytics Packs”
on page 31.
Remove the IT Analytics Packs
from Symantec Management
Platform.
Step 1
You can use Symantec Installation
Manager to safely remove IT Analytics
Solution.
See “Uninstalling IT Analytics Solution”
on page 32.
Uninstall IT Analytics Solution.Step 2
Removing the IT Analytics Packs
Before you uninstall IT Analytics Solution, you need to remove all of your IT
Analytics Packs.
See “Uninstalling IT Analytics” on page 31.
31Installing and configuring IT Analytics Solution
Uninstalling IT Analytics
To remove the IT Analytics Packs
1
Launch Symantec Installation Manager.
2
In the InstalledProducts window, scroll down and click IT Analytics Client
andServerManagement Pack, ITAnalyticsSymantecEndpointProtection
Pack, IT Analytics Asset Management Pack, and IT Analytics ServiceDesk
Pack.
3
Click Uninstall.
4
To confirm the uninstall process, click Yes.
5
On the Uninstallation Complete page, click Finish.
Uninstalling IT Analytics Solution
You can use Symantec Installation Manager to uninstall IT Analytics Solution.
See “Uninstalling IT Analytics” on page 31.
To uninstall IT Analytics Solution
1
Launch Symantec Installation Manager.
2
In theInstalled Products window, scroll down and click ITAnalytics Solution.
3
Click Uninstall
4
To confirm the uninstall process, click Yes.
5
On the Uninstallation Complete page, click Finish.
Hosting Symantec Management Platform and SQL
2005 Reporting Services on the same server
You need to perform some additional configuration to host the instance of SQL
Server 2005Reporting Services that IT Analytics Solution uses. Theconfiguration
changes letReporting Serviceswork on the same server as Symantec Management
Platform. The IIS script that runs as part of the Symantec Management Platform
installation causes the default Reporting Services virtual directories to stop
functioning.
To fix this issue, create a separate IIS Web site and application pool for Reporting
Services.
We do not recommend that you use the default Web site and default application
pool for Symantec Management Platform. Also, avoid creating a new Web site
Installing and configuring IT Analytics Solution
Uninstalling IT Analytics Solution
32
and application pool to use with the two virtual directories that SQL Server 2005
Reporting Services requires.
To host Symantec Management Platform and Reporting Services on the same server
1
In the c:\inetpub directory, create a new folder to use as the base folder for
the new Web site.
2
Assign adescriptive name to the new folder (forexample, ReportingServices).
3
On the server that hosts Symantec ManagementPlatform andSQL Reporting
Services, launch IIS.
4
In IIS, expand the servername node.
5
Right-click the Web Sites node, and then click New > Web site.
6
On the Web Site Creation Wizard page, click Next.
7
In the Description box, type a descriptive name for the new Web site (for
example, ReportingServices).
8
Click Next.
9
Set the appropriate IP address and port settings.
■ In the IPAddresses drop-down list,the default is usually AllUnassigned.
However, you can specify that this Web site is configured to a specific IP
address. Change this box only if you know the appropriate setting.
■ For the TCP port, use a port that is not currently in use by another Web
site under IIS. You can check the ports that other Web sites useby clicking
Properties under the Web site folder. Usually, the default Web site is
configured to use port 80. You can also use port 8080, which is a common
practice.
■ Leave the Host Header box blank.
10
Click Next.
11
In the path box, browse to the new folder that you created.
Leave Allow anonymous access to this Web site checked.
12
Click Next.
13
Check the following options:
■ Read
■ Run scripts
■ Execute
14
Click Finish.
33Installing and configuring IT Analytics Solution
Hosting Symantec Management Platform and SQL 2005 Reporting Services on the same server
15
In Windows, click Start > All Programs > Microsoft SQL Server 2005 >
Configuration Tools > Reporting Services Configuration to launch SQL
Reporting Services.
16
Connect to the local instance.
17
In the left pane, click Report Server Virtual Directory.
18
Click New.
19
Select the new Web site that you created.
Leave Virtual Directory as the default.
20
Click OK.
21
In the left pane, select Report Manager Virtual Directory.
22
Click New.
23
Select the new Web site that you created.
Leave Virtual Directory as the default.
24
Click OK.
25
In the left frame, click Web Service Identity.
26
Ensure that the Report Server and Report Manager drop-down lists specify
an applicationpool that is different than the one thatSymantec Management
Platform uses.
If you can’t tell if the application pool is different, you can create a new
application pool in this window. You can then use that application pool for
both drop-down lists.
27
Click Apply.
28
Launch the Symantec Management Console.
29
On the Home menu, click IT Analytics > Settings > Connections.
30
Under Reporting Server, next to the Report Server Virtual Directory URL
setting, click the edit symbol.
31
Type in the name of the server and the port number in the following format:
http://servername:port/ReportServer
Servername is the name of the server thatis running Reporting Services. Port
is the port number that you assigned to the new Web site that you created.
32
Next to the Report Folder Name setting, click the edit symbol.
Leave IT Analytics as the default.
33
Click Save Folder Settings.
Installing and configuring IT Analytics Solution
Hosting Symantec Management Platform and SQL 2005 Reporting Services on the same server
34
34
In theleft pane of the Symantec Management Console, clickthe ReportSetup
task.
35
Click the Available Reports tab.
36
Check all of the reports that you want to install.
To install all of the available reports, in the header row of the table, click
Install.
37
Click Apply.
A progress window launches.
38
Once the Close symbol is enabled, click it.
39
Ensure that you can access the dashboards and reports.
35Installing and configuring IT Analytics Solution
Hosting Symantec Management Platform and SQL 2005 Reporting Services on the same server
Installing and configuring IT Analytics Solution
Hosting Symantec Management Platform and SQL 2005 Reporting Services on the same server
36
Implementing IT Analytics
Solution
This chapter includes the following topics:
■ Accessing IT Analytics Solution
■ Viewing a dashboard report
■ Viewing a detailed report
■ Creating a new report
■ About Pivot tables
■ Pivot table prerequisites
■ Pivot table fields
■ Top pivot toolbar functions
■ Pivot toolbar functions
■ Pivot charts toolbar functions
■ Saving a pivot table view
■ Loading a pivot table view
■ Modifying a pivot table view
■ Deleting a pivot table view
■ About displaying pivot data results
■ Displaying results in a pivot chart
3
Chapter
■ Displaying results in a pivot table
■ Exporting pivot table results
■ Removing warning messages
■ Creating a pivot table using the Computer cube example
■ About Key Performance Indicators (KPIs)
■ Creating Key Performance Indicators (KPIs)
■ Setting the status of a KPI (advanced)
Accessing IT Analytics Solution
You can access IT Analytics Solution in many ways.
Implementing IT Analytics Solution
Accessing IT Analytics Solution
38
To access IT Analytics Solution
◆
Access IT Analytics Solution in one of the following ways:
DescriptionMethod
In the Symantec Management Console, on
the Home menu, click IT Analytics > Pivot
Tables.
Using pivot tables, you can construct and
save the report views that are based on
predefined measures and dimensions. The
pivot tables are configured for each cube to
allow exportable, dynamic, and customized
reports. You can also load previously saved
views for quick access to data that you
frequently need.
Symantec Management Console- Pivot
Tables
In the Symantec Management Console, on
the Home menu, click IT Analytics
>Dashboards or Reports.
These reports were developed to give you a
representative view of your IT assets. You
can export the reports to many different
formats, including HTML, Excel, and PDF.
You can also create additional reports by
using the SQL Reporting Services Report
Builder and then easily import your reports
in IT Analytics.
Symantec Management Console Dashboards/Reports
With thebuilt-in CubeBrowser, youcan view
cube data natively through the SQL Server
Management Studio. This option allows an
administrator to have raw access to cube
data and to have direct access to Analysis
Services.
Microsoft SQL Server Management
Studio
You canuse third-partyreporting tools,such
as ProClarity or Excel 2007, to report on the
data that is contained in each cube. These
tools provide rich cube browsing or cube
reporting capabilities.
Third-party Reporting Products
39Implementing IT Analytics Solution
Accessing IT Analytics Solution
Viewing a dashboard report
Dashboards display a top-level management view of precompiled data in a
graphical and color-rich format. Dashboards also provide click-through features
so that you can drill down and view the underlying IT Analytics reports in detail.
To view dashboard reports
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Content folder.
3
Click Dashboards.
4
Select a dashboard to view.
Viewing a detailed report
Reports provide you with access to various IT Analytics data views. They also
provide youwith click-through capabilities to the Symantec Management Console
pages.
To view IT Analytics reports
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Content folder.
3
Click Reports.
4
Select a report to view.
Creating a new report
You cancreate new SQL Server Reporting Services reports by using theSQL Server
Reporting Services Report Builder. The SSRS Report Builder provides you with
access to the IT Analytics Cubes that let you create the customized reports that
you can distribute.
Report Builder is a client-side application that you can use to create and design
reports. Using Report Builder, you can design the reports that are based on your
data. You can use Report Builder without having to understand the underlying
schema or complex programming languages. For more information on using this
tool, see http://msdn2.mcirosoft.com/en-us/library/ms159267.aspx.
To create a report
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings folder.
Implementing IT Analytics Solution
Viewing a dashboard report
40
3
Click Reports.
4
In the right pane, click the Report Builder tab.
5
Click Launch Report Builder.
6
In the right pane of theReport Builder, fromthe configuration options, select
a Reporting Services Site.
The default is http://servername/ReportServer.
7
Select a data source for your report.
Choose from any of the installed cubes. For example, Computer Cube.
8
Select a report layout.
For example, Chart.
9
Click OK.
The Object Explorer appears on the left side, and a Report Model appears in
the center of your screen.
10
In the top left pane, select from the available entities.
The available fields for each entity appear in the lower left pane.
11
In the lower left pane, drag and drop fields to one of the categories in the
report model.
Keep dragging and dropping until the report displays the way that you want
it to. For example, you can drag and drop data value fields, series fields, or
category fields.
12
Name your report.
13
Click Run Report on the toolbar to ensure the report renders properly.
If the report does not run correctly, click Design Report on the toolbar and
make the necessary changes.
14
Click Save on the toolbar to save your report.
Save your report with a name that represents how the report displays in the
Symantec Management Console. The file name is used to name the report in
the Symantec Management Console.
15
In the Symantec Management Console, click the IT Analytics tab.
16
In the left pane, select the folder where you want the new report to appear.
17
Right-click the folder, and then click New > New Report (or click New
Dashboard if you designed a dashboard report).
18
Select the new report from the Report Name drop-down list.
41Implementing IT Analytics Solution
Creating a new report
19
Select the initial functionality for the parameter area: visible or collapsed.
20
Click Apply to import the report.
21
In the left pane, select your report and verify that it renders properly.
About Pivot tables
A pivot table is an interactive view of an IT Analytics Cube. You can use it to
dynamically analyzedata from within the Symantec Management Console. It uses
Microsoft Office Web Components that are embedded within Microsoft Office
products or that are freely available to download.
Pivot tables were developed for each cube in the IT Analytics Solution packs to
let youview, organize, and summarize data into on-demand, personalized reports.
See “Pivot table prerequisites” on page 42.
See “Pivot table fields” on page 43.
See “Top pivot toolbar functions” on page 43.
See “Pivot toolbar functions” on page 44.
See “Pivot charts toolbar functions” on page 45.
Pivot table prerequisites
You mustinstall the Microsoft Office Web Components to work with aninteractive
pivot table in your browser. If the freely available components are installed and
you don’t have Microsoft Office already installed, you can view the components
with reduced functionalities.
For instructions on how to download and install the Office Web Components, see
http://www.microsoft.com/downloads/details.aspx?FamilyId=7287252C
-402E-4F72-97A5-E0FD290D4B76&displaylang-en.
You must also install Microsoft SQL Server 2005 Analysis Services 9.0 OLE DB
Provider forthe OfficeWeb Components.The DB Provider is a standard component
that is bundled with Microsoft products such as Office 2007 and SQL Server 2005
Management Studio. It is also available from the Microsoft Web site.
For instructions on how to download and install the OLE DB Provider, see
http://www.microsoft.com/downloads/details.aspx?familyid=df0ba5aa
-b4bd-4705-aa0a-b477ba72a9cb&displaylang=en.
See “About Pivot tables” on page 42.
Implementing IT Analytics Solution
About Pivot tables
42
Pivot table fields
The following pivot table fields are available.
See “About Pivot tables” on page 42.
Table 3-1
Pivot table fields
DescriptionField
The value on which to filter the given results.Drop Filter Fields Here
The columnsof the pivot table. As fields are added, the
field name appears and displays (+)(-) next to the field
name. These symbols let youdrill down into the values
of eachfield. Youcan placeadded fields before or after
the existing fields to modify the structure.
Drop Column Fields Here
The rows of the pivot table. As fields are added, the
field name appears and displays (+)(-) next to the field
name. These symbols let youdrill down into the values
of eachfield. Youcan placeadded fields before or after
the existing fields to modify the structure.
Drop Row Fields Here
The aggregate count or summary results of the fields
that are defined in the filter, row, and column fields.
Drop Totals or Details Fields Here
Top pivot toolbar functions
The following toolbar functions are available in the top toolbar.
See “About Pivot tables” on page 42.
Table 3-2
Top pivot toolbar functions
DescriptionFunction
Loads the previously configured and saved pivot table or
pivot chart views. You must select the appropriate view
from the list of available views.
Open
Saves the configuration of a pivot table or pivot chart to
allow for quick and easy access to the same information
format in the future.
Save
Displays the additional options for defining a new Key
Performance Indicator.
New KPI
43Implementing IT Analytics Solution
Pivot table fields
Table 3-2
Top pivot toolbar functions (continued)
DescriptionFunction
Deletes the currently loaded pivot table or pivot chart view.Delete
Displays the data and results as a pivot table.Display as Pivot Table
Displays the data and results as a pivot chart.Display as Pivot Chart
Pivot toolbar functions
The following toolbar functions are available in the pivot toolbar
See “About Pivot tables” on page 42.
Table 3-3
Pivot toolbar functions
DescriptionFunction
Copies the selected results. You must highlight the results
that you want to copy.
Copy
Sorts the selected column in ascending order. Click it to
clear the current sort order and to select a new sort order.
Sort Ascending
Sorts the selected column in descending order. Click it to
clear the current sort order and to select a new sort order.
Sort Descending
Enables or disables the auto filter function. IT Analytics
Solution retainsyour filtersettings asyou toggleon andoff
the Auto Filter. Fields that have anapplied filter have a blue
arrow at the selected field.
Auto Filter
Changes the format with which the data results are
represented. Options include the actual value or a percent
of values.
Show As
Refreshes the results of the pivot table.Refresh
Launches Microsoft Excel and exports the results into an
Excel pivot table.
Export to Excel
Configures theadvanced options for the pivot table orpivot
chart, suchas font type, font size, sorting, column headings,
legends, and colors.
Commands & Options
Implementing IT Analytics Solution
Pivot toolbar functions
44
Table 3-3
Pivot toolbar functions (continued)
DescriptionFunction
Displays the available attributes within the cube. Each
attribute can be added to the pivot table to shape your
results.
Field List
Pivot charts toolbar functions
The following toolbar functions are available only for pivot charts.
See “About Pivot tables” on page 42.
Table 3-4
Pivot charts toolbar functions
DescriptionFunction
Displays theavailable chart types that can be displayed. For
example, bar, area, line, and pie.
Chart Type
Toggles on and off the chart legend display.Show/Hide Legend
Switches the x axis of the chart to either row headings or
column headings and allows the displayed data to be
represented correctly.
By Row/Column
Saving a pivot table view
You can save pivot configurations, or views, in both chart formats and table
formats. Using this functionality, you don’t have to reconfigure the pivot views
that youmost commonly access. In addition, these saved viewscan be private and
available only to the user that created it. You can also choose to make a view
publicly available to all console users.
See “About Pivot tables” on page 42.
To save a pivot view
1
Configure a pivot table or chart.
2
From the toolbar at the top of the pivot page, click Save.
45Implementing IT Analytics Solution
Pivot charts toolbar functions
3
In the Save Pivot View dialog box, choose from the following options:
Saves the current configuration asa new viewwith the
name that you specify.
Save as New View
Overwrites a previously saved view with the current
configuration.
Save as Existing View
4
Check Available to All Users if this view should be publicly available.
Otherwise, leave the box unchecked (default).
5
Click Save.
Loading a pivot table view
You can load a pivot table view that you previously created.
See “About Pivot tables” on page 42.
To load a pivot table view
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Pivot Tables folder.
3
Click the cube that contains your saved view.
For example, the Computer cube.
4
From the toolbar at the top of the pivot page, click Open.
5
From the drop-down list, select the saved view to load.
6
Click Open.
The page refreshes and displays the name of the view under the name of the
cube.
Modifying a pivot table view
You can modify a pivot table view that you previously created.
See “About Pivot tables” on page 42.
To modify a pivot table view
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Pivot Tables folder.
Implementing IT Analytics Solution
Loading a pivot table view
46
3
Click the cube that contains your saved view.
For example, the Computer cube.
4
From the toolbar at the top of the pivot page, click Open.
5
From the drop-down list, select the saved view that you want to modify.
6
Click Open.
The page refreshes and displays the name of the view under the name of the
cube.
7
Modify the pivot configuration as necessary.
8
From the toolbar at the top of the pivot page, click Save.
9
In the Save Pivot View dialog box, choose from the following options:
Saves the current configuration asa new viewwith the
name that you specify.
Save as New View
Overwrites a previously saved view with the current
configuration.
Save as Existing View
10
Check Available to All Users if this view should be publicly available.
Otherwise, leave the box unchecked (default).
11
Click Save.
The page refreshes and displays the name of the view under the name of the
cube.
Deleting a pivot table view
You can delete a pivot table view that you previously created.
See “About Pivot tables” on page 42.
To delete a pivot table view
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Pivot Tables folder.
3
Click the cube that contains your saved view.
For example, the Computer cube.
4
From the toolbar at the top of the pivot page, click Open.
5
From the drop-down list, select the saved view that you want to delete.
47Implementing IT Analytics Solution
Deleting a pivot table view
6
Click Open.
The page refreshes and displays the name of the view under the name of the
cube.
7
From the toolbar at the top of the pivot page, click Delete.
8
Click OK to confirm the deletion.
9
Click OK to confirm that the view has been deleted.
The page refreshes without a named view under the name of the cube.
About displaying pivot data results
You can display pivot data as either a table or chart. Both tables and charts let
you interact with and drag and drop the available fields. The default presentation
is a pivot table.
Usually, it is easier to configure a pivot table with the required fields and
configuration. Then, you can switch to a pivot chart, instead of building a pivot
chart from the beginning.
You canposition the available fields on the chartor table by dragging and dropping
fields from the Field List box. You can also use filters to define the data for each
field that you want displayed in the chart. For example, you can check Altiris
Managed only.
See “About Pivot tables” on page 42.
Table 3-5
Pivot data results display options
DescriptionDisplay option
Lets you see a summary of the information in graphical format
for easier comparison.
See “Displaying results in a pivot chart” on page 48.
Pivot chart
Lets you expand and collapse rows and columns to identify
specific values. This option is the default view.
See “Displaying results in a pivot table” on page 49.
Pivot table
Displaying results in a pivot chart
Pivot charts make it easier to compare pivot data because you can see a summary
of the information in graphical format.
See “About Pivot tables” on page 42.
Implementing IT Analytics Solution
About displaying pivot data results
48
See “About displaying pivot data results” on page 48.
To display results in a pivot chart
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Pivot Tables folder.
3
Click the cube that you want to configure a pivot chart for.
For example, the Computer cube.
4
From the toolbar at the top of the pivot page, click Display as Pivot Chart.
Displaying results in a pivot table
Pivot tables make it easier to identify specify values because you can expand and
collapse various rows and columns. A pivot table is the default view for pivot
information.
See “About Pivot tables” on page 42.
See “About displaying pivot data results” on page 48.
To display results in a pivot table
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Pivot Tables folder.
3
Click the cube that you want to create a pivot table for.
For example, the Computer cube.
4
From the toolbar at the top of the pivot page, click Display as Pivot Table.
Exporting pivot table results
You can export data from a pivot table list to other programs, such as Microsoft
Excel.
If you want to further analyze the data, you can export the list to a Microsoft Excel
pivot table. You can also print a customized version of the data from a Microsoft
Excel pivot table. This feature requires that you install Microsoft Excel on each
computer that connects to the Symantec Management Console.
See “About Pivot tables” on page 42.
To export pivot table results
1
In the Symantec Management Console, click the IT Analytics tab.
2
In the left pane, expand the IT Analytics > Pivot Tables folders.
49Implementing IT Analytics Solution
Displaying results in a pivot table
3
Open an existing pivot table.
4
On the toolbar, click Export to Excel.
5
Follow the on-screen instructions.
Removing warning messages
While trying to access pivot tables within IT Analytics Solution, you might
encounter the following warning messages:
Click OK in both of these instances.
These warnings can be attributes to Internet Explorer security settings and might
display when the following conditions occur:
■ A pivot table list attempts to access the data that is on another domain. For
example, if the hostname of the SQL Server Analysis Server is different than
the hostname of Symantec Management Platform.
■ The site that the control accesses is not included in the list of trusted sites.
You need to change your Internet Explorer security settings so these warning
messages do not appear.
To remove warning messages
1
In Internet Explorer, on the Tools menu, click Internet Options.
2
On theSecurity tab, select the appropriate Web content zones(Local Intranet
and Trusted Sites).
3
For theLocalIntranet zone, add the URL string for the Symantec Management
Console.
For example, http://localhost/.
Implementing IT Analytics Solution
Removing warning messages
50
4
For theTrusted Sites zone, add the URL string for theSymantec Management
Console.
For example, http://servername/.
5
Click Local Intranet Zone.
6
Click Custom Level.
7
Under Miscellaneous, set Access data sources across domains to Enable.
8
Under User Authentication, set the Logon box to Automatic logon with
current user name and password.
9
Repeat for the Trusted Sites zone.
This page no longer prompts the user for credentials or trusts the Web site
and data provider.
Creating a pivot table using the Computer cube
example
You can create a Computer cube pivot table that displays computers by system
type, OS name, and system manufacturer in this example.
See “About Pivot tables” on page 42.
To create a Computer cube pivot table
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
Click Pivot Tables.
A list of available cubes displays.
3
Choose the Computer cube.
4
Click Field List.
The Pivot Table Field List displays the fields that are available within the
cube. You can add each of these fields to the pivot table to shape your results.
5
In the Computer cube, expand Totals.
6
Click Computer Count to select the measure value that you want to use.
Measures, or totals, are the aggregate summary counts for each cube. Your
data is totaled in the metric.
7
From the field list, click Computer - OS Name, and then drag it to the Row
area.
This field displays the operating system by name.
51Implementing IT Analytics Solution
Creating a pivot table using the Computer cube example
8
From the field list, click Computer - System Manufacturer, and then drag it
to the Row area.
9
Because you already have an existing field (Computer - OS Name), you have
the option of place the new field before or after the existing field. A blue bar
highlights the existing field. You can place the field in different places to
dynamically change how your data is presented.
10
From the field list, click Computer - System Type, and then drag it to the
Row area.
This field displays each system type and the total results for the name and
the system manufacturer. You can select the drop-down arrow next to each
System Type to further define your results.
11
Expand the OS Name to view the results by each system manufacturer.
In thetotals area, you can view the number ofeach System by Type, OS Name,
and System Manufacturer. Grand total values are also included at the end of
each category.
About Key Performance Indicators (KPIs)
One of the advantages of using OLAP is the ability to use an intuitive reporting
framework. This framework lets you quickly translate large data volumes with
the goal of making informed business decisions. Analysis Services leverages this
capability through Key Performance Indicators (KPIs). KPIs are defined as
quantifiable measures that represent a critical success factor in an organization.
The emphasis is on the action of quantifying something in the environment. For
example, theKPIs must be measurable to successfully be monitored and compared
against a given objective.
In IT Analytics Solution, KPIs are created from existing measures. However, not
all measuresare good candidates for KPI utilization. Ameasure should be leverage
in aKPI only if it represents a critical success factor to gauge performance. Besides
being measurableand performance-oriented,KPIs should be used to track progress
against strategic,typically the long-term goals that remain fairlystatic in nature.
KPIs consistof four critical elements, and IT AnalyticsSolution offers the flexibility
to define each of the following expressions:
■ A Value Expression is an MDX expression that represents the primary
measurement for this KPI. For example, Computer Count.
■ A Goal Expression is an MDX expression that represents the desired target for
the measure that is used for the Value Expression.
Implementing IT Analytics Solution
About Key Performance Indicators (KPIs)
52
■ A Status Expression is typically used to compare the Value Expression with
the GoalExpression. However, it can be any MDX expression that is meaningful
for this KPI. This expression is typically a number between 1 (goal has been
met) and -1 (value is below the goal).
■ A Trend Expression is typically used to represent the current trending over
time of the Value Expression compared with the Goal Expression. However, it
can be any MDX expression that is meaningful for this KPI. This expression
is typicallya number between 1 (increasing or gettingbetter) and -1 (decreasing
or getting worse).
For more information on KPIs in SQL Server Analysis Services, see
http://technet.microsoft.com/en-us/library/ms166869(SQL.90).aspx.
Creating Key Performance Indicators (KPIs)
IT AnalyticsSolution lets you create KPIs by manually defining themin the console
navigation under the Settings folder. You can also directly create KPIs through
the pivot tables.
This procedure is an example of creating KPIs for computers with critical patch
vulnerability definedthrough thecube. The example highlights how this procedure
automatically populates some of the MDX code that is needed to define the KPI.
To create KPIs
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Pivot Tables folder.
3
Click Patch Management Cube.
4
Click anywhere inside the cube to display the Pivot Table Field List.
5
Click anddrag the Software Update - Severity field intothe DropRowFields
Here section.
6
Click and drag Vulnerable Computer Count into the Drop Totals or Detail
Fields Here section.
7
Click and drag Applicable Computer Count into the Drop Totals or Detail
Fields Here section.
8
Right-click the cell in the cube that represents Vulnerable Computer Count
with Critical Severity and click Use as KPI Value.
9
Right-click the cell in the cube that represents Applicable Computer Count
with Critical Severity and click Use as KPI Goal.
10
In the New Key Performance Indicator section, verify that KPI Value and
KPI Goal are defined.
53Implementing IT Analytics Solution
Creating Key Performance Indicators (KPIs)
11
Click Create KPI.
12
In the resulting pop-up window, in the KPI Name box, enter Computers with
Critical Vulnerability.
13
Verify that the following boxes are correctly filled out:
■ Database Name. This box should be the name of the Analysis Services
database that IT Analytics Solution is configured to use.
■ Cube Name. This box should already be set to the Patch Management
Cube.
■ Associated Measure Group. This box should already be set to Applicable
Patches.
■ Value Expression. This box should already be populated with the MDX
code that represents the measure that was selected for the KPI Value.
■ Goal Expression. This box should already be populated with the MDX
code that represents the measure that was selected for the KPI Goal. You
might want to compare the number of vulnerable computers to a
percentage of all applicable computers. By adding “0.1*” directly before
the MDX string, you define your goal as 10% of all applicable computers.
With this measure in place, any KPI value that is below our goal is
acceptable. Any value above our goal is an undesirable state where there
are too many computers in the environment with critical patch
vulnerabilities.
14
Click Save Changes.
15
Click OK to allow the window to refresh.
16
In the left pane, open the Settings folder.
17
Click Key Performance Indicators.
The new KPI should now display in the list with the current value and goal
already defined.
Setting the status of a KPI (advanced)
IT Analytics Solution can leverage some of the graphical capabilities of Analysis
Services and Reporting Services. It looks for visual status indicators, such as a
stoplight or other images. This functionality gives a quick, high-level view of the
current state of defined KPI.
The Status Expression of the KPI is defined as a number between 1 and -1. The
most flexible way of defining how these values are populated is through an MDX
string.
Implementing IT Analytics Solution
Setting the status of a KPI (advanced)
54
This procedure is an example of enhancing the KPI that was previously created.
To set the status of a KPI
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings folder.
3
Click Key Performance Indicators to edit the KPI that was already created.
4
In the Status Expression box, click MDX Expression.
5
In the text area box that pops up, enter the following MDX code:
CASE
WHEN
aggregate({[Software Update].[Software Update - Severity].&[Critical]},
[Measures].[Vulnerable Computer Count])
< 0.1 * aggregate({[Software Update].[Software Update - Severity].&[Critical]},
[Measures].[Applicable Computer Count])
THEN 1
WHEN
aggregate({[Software Update].[Software Update - Severity].&[Critical]},
[Measures].[Vulnerable Computer Count])
> 0.25 * aggregate({[Software Update].[Software Update - Severity].&[Critical]},
[Measures].[Applicable Computer Count])
THEN -1
ELSE 0
END
6
For Status Graphic, click Traffic Light.
7
Click Save Changes.
8
Refresh the list of KPIs.
A stoplight should display under the Status column. It indicates the current
status for this KPI.
55Implementing IT Analytics Solution
Setting the status of a KPI (advanced)
Implementing IT Analytics Solution
Setting the status of a KPI (advanced)
56
Granting access to IT
Analytics Solution
This chapter includes the following topics:
■ About security
■ SQL Server Database Engine
■ SQL Server Analysis Services
■ Granting access to cubes using the Symantec Management Console
■ Adding a user to a default role
■ Modifying role privileges
■ Creating a role
■ Deleting a role
■ Granting access to cubes using SQL Server Management Studio
■ SQL Server Reporting Services
■ Granting access to reports for authorized users using the Symantec
Management Console
■ Granting accessto reports for authorized users using the ReportManager Web
site
■ Granting access to the dashboards, pivot tables, and reports
■ Symantec Management Platform role-based privileges
■ Granting access to save and load views and create new reports
4
Chapter
■ Filtering role-based cubes (advanced)
■ Distributed architecture considerations (advanced)
About security
This section provides an overview of the security concepts. These concepts help
you to understand the interactions between the application components of IT
Analytics Solution and users. In addition, we included instructions to help you
configure user security for a standard configuration. We also included other
information that is relevant to the advanced security options.
In some instances, you might want to manage a standard security configuration.
In this configuration, all users of IT Analytics are granted the same rights to view
cubes and report information. In this instance, a recommended best practice is
to create a Domain Security Group. Your group can contain all of the users and
groups of users that require access to IT Analytics. For the purpose of this
configuration example, this group is called IT Analytics Users.
Users typically use the Symantec Management Console to access IT Analytics
Solution. Users must have access through a Symantec Management Platform
security role and have at least Symantec Guests role privileges. They must also
have access to the data within the Analysis Services cubes and reporting services
reports to have full functionality.
For the standard security configuration, users in the IT Analytics Users group
already have access to the Altiris Guests Security role in Symantec Management
Platform.
SQL Server Database Engine
IT Analytics Solution provides configuration and the user functionality that is
hosted inside Symantec Management Platform. It supports all database versions
that Symantec Management Platform 7.0 supports.
You can access the solution-specific configuration information and the user
functionality through the Symantec Management Console. The relational data
that the CMDB hosts acts as the source for the cubes that are installed in SQL
Server Analysis Services.
During the configuration of the Analysis Server section of the Connection page
in the IT Analytics Solution Settings folder, the data source gets created.The data
source is created in the specified SQL Server Analysis Services Database that
inherits the configured settings for the host Symantec Management Platform
database. The data source also connects from Analysis Services to the database
Granting access to IT Analytics Solution
About security
58
engine at the time of cube processing. The SQL Server Database Engine that IT
Analytics Solution uses stores the IT Analytics Solution configuration settings,
events, and cube processing settings. IT Analytics Solution has no other
interactions with the SQL Server Database Engine.
Specific configurations within Symantec Management Platform might cause the
data sources in Analysis Services to fail to connect to the relational Database
Engine. In case this situation happens, it is important that you understand how
and whenthe data sources in Analysis Servicesare created. You should also know
how to reconfigure the data sources if a connection fails.
When you click Save Database Setting for the Analysis Server database box, the
current connection settings for CMDB are used. This situation happens while you
configure the Analysis Server section of the Connection Settings. The connection
settings areused to either create new data sources in the Analysis Server database
(if they do not already exist). They can also overwrite the existing settings. To
repair the data sources that fail to connect, click the edit symbol for the Analysis
Server database box. Then, click Save Database Settings without altering the
configuration. This action sets the data sources to the current values. This step
is necessarywhenever the database settings for Symantec Management Platform
are altered.
If you need to make advanced configuration changes to the data sources, you can
directly manipulate the data sources by using SQL Server Management Studio.
For example, you might want to change the host name or its credentials. The
configuration changes persist as long as the Analysis Server database is not
reconfigured usingthe instructions in this section. This actionmight be necessary
when Notification Server is configured to connect to the CMDB using localhost.
It also might be necessary when the Analysis Server database is not on the same
host as Notification Server and the database engine.
SQL Server Analysis Services
SQL ServerAnalysis Services is accessed during the configuration ofthe Analysis
Services database and its contents. The users that access the cubes as a source of
information forpivot tables, dashboards, and reports also access Analysis Services.
In addition, the currently configured application identity of Notification Server
is used to access Analysis Services during the setup process.
For theapplication identity to configure objects in the designated Analysis Server,
one of the following conditions must be true:
■ The application identity is a local administrator on the Analysis Services host
computer. It also has administrator rights to the local Analysis Services
instance.
59Granting access to IT Analytics Solution
SQL Server Analysis Services
■ The application identity is a member of the designated Analysis Services
instance server role. This membership lets the users that are not local
administrators haveadministrative privilegeson the Analysis Services instance.
You can add a user to the Analysis Services server role from the SQL Server
Management Studio by accessing the properties dialog box for the Analysis
Services instance. Then, navigate to the Security page. On this page, you can
add the application identity user or a group to which the user belongs.
■ The target Analysis Services database for IT Analytics Solution is already
created on the designated Analysis Services instance before the configuration
of IT Analytics Solution. The application identity is in a role in that database
that has administrative privileges.
The most common access to Analysis Services is for users to connect to cubes to
perform analysis and run reports. These connections commonly use the pivot
tables and the data source to an SQL Server Reporting Services report that is
accessed through the Symantec Management Platform. You can also use a
third-party application that is designed for cube browsing, including Microsoft
SQL Server Management Studio, Microsoft Excel, ProClarity, and others.
You can manage the user rights in Analysis Services through the user of roles. To
view a cube, a user must be in a role that has read access to a cube. Roles also let
you control the fine-grain details of what cubes, what dimensions of cubes, and
the actual dimension members and data within cubes. You can grant read access
to cubes by using the Security tab on the Cube Setup page in the Symantec
Management Console.
Granting access to cubes using the Symantec
Management Console
You can grant cube access to users that do not already have administrative
privileges on the Analysis Server instance that hosts the IT Analytics cubes.
To grant access to cubes
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings folder.
3
Click Cubes.
4
In the right pane, click the Security tab.
5
(Optional) Add members to the default IT Analytics users role or create and
manage new roles.
Granting access to IT Analytics Solution
Granting access to cubes using the Symantec Management Console
60
Adding a user to a default role
You can add members to the default IT Analytics users role.
To add a user to the default role
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings folder.
3
Click Cubes.
4
In the right pane, click the Security tab.
5
In the Role Members section, click Add.
6
Select users or groups of users from the local computer or domain.
7
Click OK.
After the screen refreshes, the selected users or groups display in the Role
Members section.
Modifying role privileges
You can modify the privileges for each defined role.
To modify privileges for a role
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings folder.
3
Click Cubes.
4
In the right pane, click the Security tab.
5
Under Cube Read Access, click to select or clear the check boxes you want.
Selecting the check box next to a cube grants members or the selected role
access to thatspecific cube.An emptybox indicatesthat members of this role
do not have access to that cube. An empty box also indicates that any pivot
tables, dashboard, or the reports that include this cube have reduced data
sets or return no results.
6
Click Apply.
Creating a role
You cancreate a new role that is separate from the default IT Analyticsusers role.
61Granting access to IT Analytics Solution
Adding a user to a default role
To create a role
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings folder.
3
Click Cubes.
4
In the right pane, click the Security tab.
5
Under Roles, click New.
6
Enter a name for the role.
7
Add members to the role.
8
Grant read access to the required cubes.
9
Click Apply.
Deleting a role
You can delete any roles that you created.
To delete a role
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings folder.
3
Click Cubes.
4
In the right pane, click the Security tab.
5
Under Roles, select the role that you want to delete from the drop-down list.
6
Wait for the screen to refresh, and then click Delete.
The screen refreshes again, and a message displays at the top of the page,
which states that the role was successfully deleted.
7
Click Apply.
Granting access to cubes using SQL Server
Management Studio
You can also use SQL Server Management Studio to grant access to cubes.
To grant access to a cube using SQL Server Management Studio
1
Open SQL Management Studio.
2
Connect toAnalysis Services using an account that hasadministrative rights.
Granting access to IT Analytics Solution
Deleting a role
62
3
Within the IT Analytics database, right-click the Roles folder.
4
Click New Role.
5
On the Create Role dialog box, enter IT Analytics Users as the role name.
6
Select the Read Definition database permission for the role.
7
On the Cubes page, set the Access drop-down list to Read for each cube that
you want this role to have access to.
If you install additional cubes in the future, you need to explicitly grant the
read privilege for each cube after you install it.
8
On the Membership page, click Add to specify users and groups for this role.
9
Click Object Types, and then select Groups to allow the security group to be
added to the role.
10
Click OK.
11
Click Location and change the location to the domain for which you created
the IT Analytics Users security group.
12
Click OK.
13
In the box for objects to select, add the IT Analytics Users group.
14
Click OK.
Members of this role now have the appropriate rights to view the cubes that
this role permits. You might need to configure Notification Server security
to see the IT Analytics tab and installed cubes or reports.
SQL Server Reporting Services
SQL ServerReporting Servicesis accessed during the configuration of the reporting
services folder andits content. The contents includes the data source reports that
are used to access cubes as well as the installation of dashboards and reports.
Reporting Services is also accessed each time that a user runs an IT Analytics
Solution report in the Symantec Management Platform. They can also access
reports directly through the Reporting Services Report Manager Web site.
During configuration of the reporting services folder, the currently configured
application identity of Notification Server is used to access Reporting Services.
The IT Analytics Solution configuration pages help with this configuration. The
application identitymust be granted the content manager privilegeto a Reporting
Server. The application identity needs this privilege to configure objects in the
designated Reporting Server.
63Granting access to IT Analytics Solution
SQL Server Reporting Services
By default, the local administrators group on the Reporting Server has content
manager privileges. However, if the application identity is not part of this group,
it can be granted the system administrator privilege. You can start this process
by navigating to the permissions page of the properties dialog box within SQL
Server Management Studio for that Reporting Server.
By default, only the users in the local administrators group have access to the
reports on the SQL Reporting Service. The browser role must be granted in SQL
Server Reporting Server. This role is used to access the reports through either IT
Analytics Solution or the SQL Reporting Server Web console.
The browser role can be applied at the top-level folder, where all child reports
inherit the role. Alternatively, security can be applied to individual reports if you
want more granular control. You can apply security within the Security tab of the
Report Setuppage. This functionality is similar to how Readaccess is administered
for individual cubes. Alternatively, the Report Manager Web site within SQL
Reporting Services can be used to manage user Read access to specific reports.
For reportsto return data, the account thatyou use must have at least Read access
to the Analysis Server cubes that the report accesses.
Granting access to reports for authorized users using
the Symantec Management Console
You can grant access to the users that do not already have browser privileges
using the Symantec Management Console.
To grant access to a report using the Symantec Management Console
1
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
2
In the left pane, expand the Settings folder.
3
Click Reports.
4
In the right pane, click the Security tab.
5
(Optional) Add members to the default IT Analytics Users role.
You can also create and manage new roles.
6
Select the specific reports that you want to grant Read access to for the given
role.
Granting access to IT Analytics Solution
Granting access to reports for authorized users using the Symantec Management Console
64
Granting access to reports for authorized users using
the Report Manager Web site
You can grant reports access to the users that do not already have browser
privileges on the report server instance that hosts the IT Analytics reports.
To grant access to a report using the Report Manager Web site
1
As a user with system administrator privileges for the reporting services
instance, access the Report Manager Web site.
The URL for the report manager is similar to http://servername/Reports/. If
you did not install SQL Server Reporting Services as the default instance, the
URL might be http://servername/Reports$InstanceName/.
2
Navigate to the folder that is configured to host the IT Analytics reports.
By default, it is the IT Analytics folder.
3
Navigate to the Properties tab for the current folder.
4
In the left pane, navigate to the Security page.
5
Click New Role Assignment.
6
In the Group or user name box, enter IT Analytics Users.
7
Select the browser role.
8
Click OK.
Members of this rolenow havethe appropriaterights toview thereports that
this role permits. You might need to configure Notification Server security
to see the IT Analytics tab and any installed cubes or reports.
9
(Optional) If the IT Analytics Users role or any individual users need access
to create reports using Report Builder, you must grant the System User
privilege using the following steps.
■ Click Site Settings in the top right-hand corner.
■ Under the Security header, click Configure site-wide security.
■ Click New Role Assignment.
■ In the Group or user name box, enter IT Analytics Users.
■ Select the System User role.
■ Click OK.
Members ofthis rolenow have the appropriate rights to create reports through
Report Builder.
65Granting access to IT Analytics Solution
Granting access to reports for authorized users using the Report Manager Web site
Granting access to the dashboards, pivot tables, and
reports
You cangrant access through a Notification Server security roleto the dashboards,
the pivot tables, and the reports that are available on the IT Analytics tab.
To grant access to the IT Analytics features
1
In the Symantec Management Console, on the Settings menu, click Security
> Roles.
2
In the left pane, select the IT Analytics Users security role.
3
Navigate to the Privileges tab for the IT Analytics Users role.
4
Under Privileges, click View IT Analytics Tab.
5
On the Membership tab, click Add new member(s).
6
In the Name Query box, select Starts With.
7
Enter IT Analytics Users.
8
Click Find to locate the group.
9
Select the result that was returned for the IT Analytics Users group.
10
Click OK.
11
Click Apply to save the settings.
12
In theSymantec ManagementConsole, onthe Home menu, click IT Analytics.
13
In the left pane, right-click the IT Analytics folder.
14
Select Properties.
15
On the Properties window, click the Security tab.
16
Under Permissions, click Add.
17
Click the IT Analytics Users role, and then click Select.
18
On the Permissions Selection dialog box, in the Altiris System Permissions
section, click the read permission.
19
Click Select.
Granting access to IT Analytics Solution
Granting access to the dashboards, pivot tables, and reports
66
20
Click the Replace permissions on all child objects option.
21
Click Apply.
All users in the IT Analytics Users security group now have access to the IT
Analytics features in the Symantec Management Console. They also have full
access to the installed IT Analytics cubes and reports.
We addedseveral Notification Server role-based privileges to helpyou secure
the data that is available within IT Analytics. These added privileges let
administrators specify which Notification Server roles can save (author) and
read (load) pivot views.
Symantec Management Platform role-based privileges
The following Symantec Management Platform role-based privileges exist.
Table 4-1
Symantec Management Platform role-based privileges
DescriptionPrivilege
Lets the users save the configured pivot table or
the pivot chart views as private views.
Author Private Pivot Views
Lets the users save the configured pivot table or
the pivot chart views as public views.
Author Public Pivot Views
Lets the users open or load the previously saved
pivot table or the pivot chart views that are
marked as private.
Read Private Saved Pivot Views
Lets the users open or load the previously saved
pivot table or the pivot chart views that are
marked as public.
Read Public Saved Pivot Views
Lets the user create or edit a Key Performance
Indicator from a configured pivot table view.
Author Key Performance Indicators
Granting access to save and load views and create
new reports
You can grant the privileges that allow other users to author and save pivot table
or pivotchart views. You can let others load and read those same views and create
new reports.
67Granting access to IT Analytics Solution
Symantec Management Platform role-based privileges
To grant access to save and load views and create new reports
1
In the Symantec Management Console, on the Settings menu, click Security
> Roles.
2
In the left pane, select the role that you want to grant access to.
3
In the right pane, click the Privileges tab.
4
Scroll down to the IT Analytics privileges section, and expand it if necessary.
5
Select the privileges that you want to grant the role.
6
Click Apply.
You can configure additional, scope-based security for each individual
dashboard, report, or pivot table.
Filtering role-based cubes (advanced)
SQL ServerAnalysis Services has a wide range of advancedsecurity opportunities.
You can explore these opportunities through theSQL ServerManagement Studio.
One such feature is the ability to filter the data that a role has access to by
restricting access to specific members of a dimension.
You can restrictaccess for the IT Analytics Users role to return thecube dataonly
for computerswith a Win32 system type. For this example, you must grantaccess
to the Computer cube for the IT Analytics Users role.
To filter a role-based cube
1
In SQL Server Management Studio, in the IT Analytics analysis services
database, navigate to the properties for the IT Analytics Users role.
2
In the Edit Role dialog box, navigate to the Dimension Data page.
3
In the Dimension drop-down list, click the Computer dimension.
4
Select the Deselect all members radio symbol.
5
In the Attribute Hierarchy drop-down list, click Computer - System Type.
6
Select the dimension members that you want the role to have access to.
In our example, there is an Win32 member. Actual names are specific to each
instance of Notification Server.
7
Navigate to the Advanced tab of the Dimension Data page.
Granting access to IT Analytics Solution
Filtering role-based cubes (advanced)
68
8
Click Enable Visual Totals.
This step prevents the role from seeing the aggregate totals that are
independent of the configured filtering and restricts aggregations.
9
Click OK to save the role configuration.
Users in the configured role now see the results only for the computers that
have a Win32 system type across all cubes. This filtering is enforced across
all means of accessing the cubes, including dashboards, pivot tables, report,
and third-party applications.
Distributed architecture considerations (advanced)
We recommend that the SQL Server Analysis Services and SQL Server Reporting
Services instances that IT Analytics uses reside on the same host computer. You
can hostthese services on different computers in a highly distributed environment.
However, additional configuration might be necessary to ensure that
authentication is managed appropriately across all application tiers.
The SQL Server Reporting Services data sources that are configured on the
Connection Settingspage use Windows integrated security by default. This feature
allows for granular control of the reports that a user has access to, and it also
enables filtering of the available cube data.
The delegation features and impersonation features that are available with
Windows integrated security can exist across multiple servers. In order for this
feature to work, the network environment in which IT Analytics Solution is
installed must be configured to use the Kerberos protocol. Without the Kerberos
protocol, Windows credentials are passed across only one computer connection
before they expire.
When the SQL Server Analysis Services and SQL Server Reporting Services are
hosted on the same computer, the credentials of the user that wants to access a
report through the Symantec Management Console are passed across only one
computer connection. The credentials are passed from the user’s computer to the
computer that hosts both Analysis Services and Reporting Services. Delegating
credentials succeeds without enabling the Kerberos protocol.
Where SQLServer AnalysisServices and SQL Server Reporting Services are hosted
on different computers, one additional connection is required to pass the
credentials of the user from the Reporting Server to the Analysis Server. Without
enabling Kerberos, the second connection is attempted as an anonymous user,
which fails authentication in a typical configuration.
69Granting access to IT Analytics Solution
Distributed architecture considerations (advanced)
To complete the two-step delegation process from the user’s computer to the
Reporting Server and back to Analysis Services, you can use one of the following
two options:
■ Enable the Kerberos protocol to allow credential delegation over multiple
connections. For more information, see the Microsoft knowledge base article
entitled, "How to configureSQL Server2004 AnalysisServices touse Kerberos
authentication" at http://support.microsoft.com/kb/917409.
■ Configure the reporting services data sources to use stored credentials or
prompted credentials to access the analysis services cubes. If you use stored
credentials, all connections from reporting services to analysis services occur
in a predefined user context. Also, role-based filtering does not function as
documented.
Granting access to IT Analytics Solution
Distributed architecture considerations (advanced)
70
IT Analytics Solution packs
This chapter includes the following topics:
■ About IT Analytics Solution packs
■ IT Analytics Asset Management Pack
■ IT Analytics Client and Server Management Pack
■ IT Analytics Symantec Endpoint Protection Pack
■ IT Analytics ServiceDesk Pack
About IT Analytics Solution packs
The following packs correspond to common Symantec licensing scenarios and
functionality:
■ IT Analytics Asset Management Pack
See “IT Analytics Asset Management Pack” on page 71.
■ IT Analytics Client and Server Management Pack
See “IT Analytics Client and Server Management Pack” on page 72.
■ IT Analytics Symantec Endpoint Protection Pack
See “IT Analytics Symantec Endpoint Protection Pack” on page 73.
■ IT Analytics ServiceDesk Pack
See “IT Analytics ServiceDesk Pack” on page 74.
IT Analytics Asset Management Pack
Licensed 1:1 with the licensed amount of Altiris Asset Management Solution
software. Equivalent to a 1:1 ratio with ownership of Altiris Asset Management
Suite.
5
Chapter
This pack contains all of the core functionality of IT Analytics Solution for the
configuration of cubes and reports.
See “About IT Analytics Solution packs” on page 71.
It also contains the pivot tables and the reports that are associated with the
following licensed cubes:
■ Assets
■ Software License Compliance
■ Software Purchases
IT Analytics Client and Server Management Pack
Licensed 1:1 with the licensed amount of Altiris Inventory Solution software.
Equivalent to a 1:1 ratio with ownership of Altiris Client Management Suite and
Server Management Suite.
This pack contains all of the core functionality of IT Analytics Solution for the
configuration of cubes and reports.
See “About IT Analytics Solution packs” on page 71.
It also contains the pivot tables and the reports that are associated with the
following licensed cubes:
■ Add Remove Programs
■ Application Metering
■ Computers
■ ESX Servers
■ Event Console Alerts
■ IIS Servers
■ Installed Files
■ Installed Software
■ Monitor Metrics
■ Monitor NT Events
■ Monitor Processes
■ Package Distribution Events
■ Package Server Configuration Events
■ Package Server Status
IT Analytics Solution packs
IT Analytics Client and Server Management Pack
72
■ Patch Management
■ Software Delivery Execution Events
■ Software Delivery Package Events
■ Software Delivery Status Events
■ SQL Servers
■ Tasks
IT Analytics Symantec Endpoint Protection Pack
Licensed 1:1 with the number of computers that have the Symantec Endpoint
Protection client installed.
The cubes and reports in this pack use the configuration information of the
Symantec Endpoint Protection Manager servers. The configuration information
is captured when the SEP cubes are installed from the cube setup page. The
information is used as the foundation of the data source views that are used to
process thecubes. This functionality lets the Symantec Endpoint Protectioncubes
read data from the Configuration Management Database, as well as from each
configured Symantec Endpoint Protection database. It also allows the data to
come together into a single, unified view of all Symantec Endpoint Protection
clients, alerts, and scan activity.
Before installingany cubes, ensure that the Symantec Endpoint Protection Server
is fullyconfigured for each Symantec Endpoint Protection Manager that youwant
represented in the IT Analytics Symantec Endpoint Protection cubes.
This pack contains all of the core functionality of IT Analytics Solution for the
configuration of cubes and reports.
See “About IT Analytics Solution packs” on page 71.
It also contains the pivot tables and reports that are associated with the following
licensed cubes:
■ Symantec Endpoint Protection Client
■ Symantec Endpoint Protection Alert
■ Symantec Endpoint Protection Scan
■ Symantec Endpoint Protection Access Rights
■ Symantec Endpoint Protection Policies
73IT Analytics Solution packs
IT Analytics Symantec Endpoint Protection Pack
IT Analytics ServiceDesk Pack
Licensed 1:1 with the ServiceDesk Solution licenses.
The cubes and reports in this pack use the configuration information of the
ServiceDesk servers. The configuration information is captured when the
ServiceDesk cubesare installed from the cube setup page.The information is used
as thefoundation of the data source views that are used to process the cubes. This
functionality letsthe ServiceDesk cubes read data from the ServiceDesk databases.
Before installingany cubes, ensure that the ServiceDesk server is fully configured
for the ServiceDesk instance that you want represented in the IT Analytics
ServiceDesk cubes.
This pack contains all of the core functionality of IT Analytics Solution for
configuration of cubes and reports. The pack also contains all of the pivot tables
and reports that are associated with the following licensed cubes:
■ ServiceDesk Incidents
■ ServiceDesk Problems
■ ServiceDesk Changes
■ ServiceDesk Releases
See “About IT Analytics Solution packs” on page 71.
IT Analytics Solution packs
IT Analytics ServiceDesk Pack
74
Cube reference
This appendix includes the following topics:
■ Application Metering Cube
■ Assets Cube
■ Computers Cube
■ ESX Servers Cube
■ Event Console Alerts Cube
■ IIS Servers Cube
■ Installed Files Cube
■ Installed Software Cube
■ Monitor Metrics Cube
■ Monitor NT Events Cube
■ Monitored Processes Cube
■ Package Distribution Events Cube
■ Package Server Configuration Events Cube
■ Package Server Status Cube
■ Patch Management Cube
■ ServiceDesk Changes Cube
■ ServiceDesk Incidents Cube
■ ServiceDesk Problems Cube
A
Appendix
■ ServiceDesk Releases Cube
■ Software Delivery Execution Events Cube
■ Software Delivery Package Events Cube
■ Software Delivery Status Events Cube
■ Software License Compliance Cube
■ Software Purchases Cube
■ SQL Servers Cube
■ Symantec Endpoint Protection Access Rights
■ Symantec Endpoint Protection Alerts
■ Symantec Endpoint Protection Clients
■ Symantec Endpoint Protection Policies
■ Symantec Endpoint Protection Scans
■ Tasks
Cube reference76
Application Metering Cube
Application Metering Cube – Contains data that is primarily associated with
Altiris Inventory Solution. It represents a historical view of application execution.
Dimensions
■ Computer
■ Date
■ File
■ Filter
■ Software Component
■ Organizational Group
■ Software Product
■ User
Measures
Computer Count
The distinct number of computers.
Denial Count
The number of times that an application was denied execution.
File Count
The total number of files that matched the given criteria. If an application is
in multiple locations on the same computer, this number can be larger than
the Computer Count.
Run Count
The number of times that the application was executed.
Total Run Time
The amount of time that the application was running.
77Cube reference
Application Metering Cube
Assets Cube
Assets Cube – Contains the information that is primarily associated with Asset
Management Solution. It provides details about the ownership, status, location,
and the type of asset that is intended to be used within the organization.
Dimensions
■ Asset
■ Asset Status
■ Asset Type
■ Cost Center
■ Department
■ Location
■ User
Measures
Asset Count
The number of distinct assets of all types that are in the CMDB.
Cube reference
Assets Cube
78
Computers Cube
Computers Cube – Contains data that is primarily associated with Altiris Inventory
Solution. It represents a current view of the information that the hardware and
operating systemscans that are stored in Symantec Management Platform collect.
Dimensions
■ Computer
■ Created Date
■ Filter
■ Last Basic Inventory Date
■ Logical Disk
■ Organizational Group
■ Processor
Measures
Computer Count
The distinct count of computers.
Logical Disk Free Space GB
The sum of the available space on logical disks. The results are in Gigabytes.
Logical Disk Count
The countof logical disks. This number might be more than oneper computer.
Logical Disk Size GB
The sum of the size of logical disks. The results are in Gigabytes.
Physical Memory Capacity GB
The sum of the physical memory capacity of the installed memory devices.
The results are in Gigabytes.
Physical Memory Device Count
The count of physical memory devices that are installed. This number might
be more than one per computer.
Physical Memory Array Max Capacity GB
The maximum capacity of memory that the physical memory arrays for a
device support. This number is equal to or greater than the actual installed
79Cube reference
Computers Cube
memory capacity that is represented in the Physical Memory Capacity
measure. The results are in Gigabytes.
Physical Memory Array Max Device Count
The maximumnumber ofdevices that the physical memory arrays for a device
support. This number is equal to or greater than the actual installed memory
device count that is represented in the Physical Memory Device Count
measure.
Processor Speed GHz
The maximum speed of a processor for a device or set of devices. The results
are in gigahertz.
Processor Count
The count of processors for a device or set of devices.
Cube reference
Computers Cube
80
ESX Servers Cube
ESX Servers Cube – Contains the data about the virtual machines that are hosted
on ESX Servers.
Dimensions
■ Computer
■ Storage Volume
■ Virtual Machine
Measures
Host Count
The number of machines that host one or more virtual machines.
Storage Volume Count
The number of storage volumes.
Virtual Machine Count
The number of virtual machines by the selected criteria.
81Cube reference
ESX Servers Cube
Event Console Alerts Cube
Event Console Alerts Cube – Contains the information about the alerts that
are available within the Event Console. It represents a historical view of alerts
and provides the ability to search for recurring issues or clients with problems.
Dimensions
■ Computer
■ Date
■ Event Console Alert
■ Event Console Alert Action Audit Type
■ Event Console Alert Category
■ Event Console Alert Severity
■ Filter
■ Organizational Group
■ Time
Measures
Action Count
The number of actions that were launched.
Alert Count
The number of alerts that were triggered.
Computer Count
The distinct number of computers.
Cube reference
Event Console Alerts Cube
82
IIS Servers Cube
IIS Servers Cube – Contains the informationabout theconfiguration andsettings
of servers that host IIS.
Dimensions
■ Computer
■ FTP Site
■ Server
■ Virtual Directory
■ Web Site
Measures
FTP Site Count
The distinct number of FTP sites.
Server Count
The number of identified servers.
Virtual Directory Count
The number of virtual directories.
Web Site Count
The number of individual Web sites that were found.
83Cube reference
IIS Servers Cube
Installed Files Cube
Installed Files Cube – Contains data that is primarily associated with Altiris
Inventory Solution. It represents a current view of the information that the
Software Inventory that is stored in Symantec Management Platform collects.
Dimensions
■ Computer
■ File
■ Filter
■ Organizational Group
■ Software Component
■ Software Product
Measures
Computer Count
The distinct number of computers.
File Count
The total number of files that matched the given criteria. If a software
component is in multiple locations on the same computer, this number can
be larger than the Computer Count.
Cube reference
Installed Files Cube
84
Installed Software Cube
Installed Software Cube – Contains data that is primarily associated with the
Altiris Software Management Framework. It represents a current view of the
information thatis collectedfrom the managed computers and stored in Symantec
Management Platform.
Dimensions
■ Add Remove Programs
■ Computer
■ Filter
■ Organizational Group
■ Software Component
■ Software Product
Measures
Computer Count
The distinct number of computers.
Instance Count
The total number of times that a software component matched the given
criteria. If a software component is in multiple locations on the same
computer, this number can be larger than the Computer Count.
85Cube reference
Installed Software Cube
Monitor Metrics Cube
Monitor Metrics Cube – Contains the historical information regarding alerts,
metrics, rules, and the tasks that Monitor Solution captures. Monitor Solution
sets up the rules that can trigger alerts and the tasks that are based on a collected
set of metrics. This cube provides insight into how these items work together to
resolve issues on monitored clients.
Dimensions
■ Computer
■ Date
■ Event Console Alert
■ Event Console Alert Action Audit Type
■ Event Console Alert Category
■ Event Console Alert Severity
■ Event Console Monitor Rule
■ Filter
■ Monitor Metric
■ Monitor Metric Detail Level
■ Monitor Metric Instance
■ Monitor Metric Source
■ Monitor Task
■ Organizational Group
■ Task Server
■ Time
Measures
Action Count
The number of actions that were launched.
This measure group is not valid with the following dimensions:
■ Event Console Monitor Rule
■ Monitor Metric
Cube reference
Monitor Metrics Cube
86
■ Monitor Metric Detail Level
■ Monitor Metric Instance
■ Monitor Metric Source
■ Monitor Task
■ Task Server
Alert Count
The number of alerts that were triggered.
This measure group is not valid with the following dimensions:
■ Event Console Alert Action Audit Type
■ Monitor Metric
■ Monitor Metric Detail Level
■ Monitor Metric Instance
■ Monitor Metric Source
■ Monitor Task
■ Task Server
Computer Count
The distinct number of computers.
This measure group is not valid with the following dimensions:
■ Event Console Alert
■ Event Console Alert Action Audit Type
■ Event Console Alert Category
■ Event Console Alert Severity
■ Event Console Monitor Rule
■ Monitor Task
■ Task Server
Duration
The amount of time (in seconds) that the given value was in effect for.
This measure group is not valid with the following dimensions:
■ Event Console Alert
■ Event Console Alert Action Audit Type
■ Event Console Alert Category
87Cube reference
Monitor Metrics Cube
■ Event Console Alert Severity
■ Event Console Monitor Rule
■ Monitor Task
■ Task Server
Max
The maximum value that was recorded for the given metric.
This measure group is not valid with the following dimensions:
■ Event Console Alert
■ Event Console Alert Action Audit Type
■ Event Console Alert Category
■ Event Console Alert Severity
■ Event Console Monitor Rule
■ Monitor Task
■ Task Server
Metric Count
The number of metrics that were recorded.
This measure group is not valid with the following dimensions:
■ Event Console Alert
■ Event Console Alert Action Audit Type
■ Event Console Alert Category
■ Event Console Alert Severity
■ Event Console Monitor Rule
■ Monitor Task
■ Task Server
Min
The minimum value that was recorded for the given metric.
This measure group is not valid with the following dimensions:
■ Event Console Alert
■ Event Console Alert Action Audit Type
■ Event Console Alert Category
■ Event Console Alert Severity
Cube reference
Monitor Metrics Cube
88
■ Event Console Monitor Rule
■ Monitor Task
■ Task Server
Task Count
The number of tasks that were launched.
This measure group is not valid with the following dimensions:
■ Event Console Alert
■ Event Console Alert Action Audit Type
■ Event Console Alert Category
■ Event Console Alert Severity
■ Monitor Metric
■ Monitor Metric Detail Level
■ Monitor Metric Instance
■ Monitor Metric Source
Avg
The average value that was recorded for the given metric.
This measure group is not valid with the following dimensions:
■ Event Console Alert
■ Event Console Alert Action Audit Type
■ Event Console Alert Category
■ Event Console Alert Severity
■ Event Console Monitor Rule
■ Monitor Task
■ Task Server
89Cube reference
Monitor Metrics Cube
Monitor NT Events Cube
Monitor NT Events Cube – Contains theWindows NT event log data that Monitor
Solution captures. It represents a historical view of the Windows NT event log of
all monitored client computers.
Dimensions
■ Category
■ Computer
■ Date
■ Description
■ Event ID
■ Filter
■ Log File
■ Message DLL
■ Organizational Group
■ Rule Triggered
■ Source
■ Time
■ Type
■ User
Measures
Computer Count
The distinct number of computers.
Event Count
The number of events.
Cube reference
Monitor NT Events Cube
90
Monitored Processes Cube
Monitored Processes Cube – Contains the Windows process data that Monitor
Solution captures. It represents a historical view of the process data from all
monitored client computers, including processor and virtual memory utilization.
Dimensions
■ Computer
■ Date
■ Filter
■ Monitor Process Name
■ Monitor Process Owner
■ Organizational Group
■ Time
Measures
Max Process CPU Percent Usage
The maximum recorded percent of CPU utilization.
Max Process CPU Time
The maximum CPU time that was used for the given dimension.
Max Process Handle Count
The maximum handle count for the given dimension.
Max Process Thread Count
The maximum number of process threads.
Max Process Virtual Memory Size
The maximum virtual memory size that was consumed (in KB) for the given
dimension.
Max Process Working Set Size
The maximum working set size (in KB) for the given dimension.
Min Process CPU Percent Usage
The minimum recorded percent of CPU utilization.
Min Process CPU Time
The minimum CPU time that was used for the given dimension.
91Cube reference
Monitored Processes Cube
Min Process Handle Count
The minimum handle count for the given dimension.
Min Process Thread Count
The minimum number of process threads.
Min Process Virtual Memory Size
The minimum virtual memory size for the given dimension.
Min Process Working Set Size
The minimum working set size for the given dimension.
Process Count
The count of processes.
Process CPU Percent Usage
The percent usage of a CPU for a given process.
Avg Process CPU Percent Usage
The average CPU percent utilization for the given dimension.
Avg Process CPU Time
The average process CPU time for the given dimension.
Avg Process Handle Count
The average process handle count for the given dimension.
Avg Process Thread Count
The average process thread count for the given dimension.
Avg Process Virtual Memory Size
The average process virtual memory size for the given dimension.
Avg Process Working Set Size
The average process working set size for the given dimension.
Cube reference
Monitored Processes Cube
92
Package Distribution Events Cube
Package Distribution Events Cube – Contains the information regarding the
actual distribution of packages to package servers. This information is valuable
to verifythat packages are properly transferred to theappropriate package server
in a timely basis. It also provides details on the status of each transfer and the
ability to view distribution events over time.
Dimensions
■ Package
■ Package Distribution Event Date (alias for Date Dimension)
■ Package Distribution Event Status
■ Package Distribution Event Time (alias for Time Dimension)
■ Package Server
Measures
Package Servers
The number of package servers that host a package.
Package Distribution Events
The number of distribution events that were sent from the package server to
Symantec Management Platform during package replication.
93Cube reference
Package Distribution Events Cube
Package Server Configuration Events Cube
Package Server Configuration Events Cube – Contains the information
regarding the configuration requests that the package servers generate. Package
servers receive instructions from Symantec Management Platform using these
configuration requests,and the requests are scheduled to occur at regularintervals.
The information in this cube is valuable to verify the availability of each package
server and to identify periods of time during which a package server did not
communicate with Symantec Management Platform.
Dimensions
■ Package Server
■ Configuration Request Date (alias for Date Dimension)
■ Configuration Request Time (alias for Time Dimension)
Measures
Configuration Requests
The number of configuration requests that were sent between the package
servers and Symantec Management Platform. This measure can be used to
determine package server availability.
Package Servers
The number of package servers on which matching events occurred.
Cube reference
Package Server Configuration Events Cube
94
Package Server Status Cube
Package Server Status Cube – Represents the current state of the package
server infrastructure. This information includes the measures and dimensions
that provide clarity into the associations between package servers and packages.
It also includes the status of each package on each package server.
Dimensions
■ Package Server
■ Package
■ Package Status
Measures
Disk Space Used Bytes GB
The amount of disk space that is used to host the package.
Package Servers
The number of package servers.
95Cube reference
Package Server Status Cube
Patch Management Cube
Patch Management Cube – Contains data that is primarily associated with Patch
Management Solution. It represents the current state of the Patch Management
Inventory scan information for Symantec Management Platform.
Dimensions
■ Computer
■ Filter
■ Organizational Group
■ Software Update
Measures
Applicable Computer Count
The numberof computers that meet the requirements for a patch bythe given
criteria.
Applicable Patch Count
The number of patches that match the given criteria.
Installed Computer Count
The number of computers that have patches installed that match the given
criteria.
Installed Patch Count
The number of patches that are installed that match the given criteria.
Vulnerability Count
The number of patches that are required for the given criteria.
Vulnerable Computer Count
The number of computers that require a patch to match the given criteria.
Cube reference
Patch Management Cube
96
ServiceDesk Changes Cube
ServiceDesk Changes Cube – Contains data that is associated with ServiceDesk
Change Managementand represents a current status. It also represents a historical
view of Change Requests in ServiceDesk.
Dimensions
■ Assigned to User
■ Change
■ Contact Type
■ Date Closed
■ Date Ended
■ Date Implemented
■ Date Opened
■ Date Scheduled
■ Date Started
■ Impact
■ Location
■ Priority
■ Reference
■ Source
■ Status
■ Time Closed
■ Time Ended
■ Time Implemented
■ Time Needed
■ Time Opened
■ Time Scheduled
■ Time Started
■ Type
■ Urgency
97Cube reference
ServiceDesk Changes Cube
■ User
Measures
Change Count
The number of changes.
Failed Changes
The number of changes that failed.
Rejected Changes
The number of changes that were rejected.
Unplanned Changes
The number of changes that were unplanned.
Change Assignment Count
The number of assigned users.
Closed Change Count
The number of closed changes.
Completed On Time
The number of changes that were completed within the allotted time period.
Contact Count
The number of users that are associated with the change.
Open Change Count
The number of changes where the status is not a closed state.
Reference Count
The number of references. References are items in your environment, such
as locations, departments, and assets.
Avg Age (Days)
The number of days that the change has been opened. This number is useful
for understanding the age of the change. The measure is valid for all changes
that do not have a Resolved or Closed state.
Avg Age (Hours)
The numberof hours that the change has been opened.This number is useful
for understanding the age of the change. This measure is valid for all changes
that do not have a Resolved or Closed state.
Cube reference
ServiceDesk Changes Cube
98
Avg Age (Minutes)
The number of minutes that the change has been opened. This number is
useful for understanding the age of the change. This measure is valid for all
changes that do not have a Resolved or Closed state.
Avg Cost To Implement
The cost to implement the change. This number is averaged across all of the
changes using the selected criteria.
Avg Cost To Not Implement
The cost to not implement the change. This number is averaged across all of
the changes using the selected criteria.
Avg Days to Resolve
The number of days it takes to resolve the change.
Avg Hours to Resolve
The number of hours it takes to resolve the change.
Avg Minutes to Resolve
The number of minutes it takes to resolve the change.
Avg Percent Complete
The average percent complete for the changes using the selected criteria.
99Cube reference
ServiceDesk Changes Cube
ServiceDesk Incidents Cube
ServiceDesk Incidents Cube – Contains datathat isassociated with ServiceDesk
Incident Management and represents a current and a historical view of Incidents
in ServiceDesk.
Dimensions
■ Affected User
■ Assigned to User
■ Category
■ Close Code
■ Contact Type
■ Created by User
■ Date Closed
■ Date Modified
■ Date Opened
■ Impact
■ Incident
■ Last Modified by User
■ Location
■ Priority
■ Reference
■ Resolved by User
■ Source
■ Status
■ Time Closed
■ Time Modified
■ Time Opened
■ Type
■ Urgency
■ User
Cube reference
ServiceDesk Incidents Cube
100
Loading...