Users Guide
Compliance and Change Reporting | Change Management and Compliance
524 OMNM 6.5.3 User Guide
Compliance and Change Reporting
The Compliance Policy Violation report is seeded when you have ProScan/Change Management in
OpenManage Network Manager. Inventory Compliance Attributes for reporting can also appear in
report templates when you install ProScan. These report in-compliance or out-of-compliance, the
last compliance date (when last compliant or not compliant), last config date (when configuration
last changed), last checked date (when change was last determined).
You can also run the Change Determination Report that displays changes made to configurations.
See Generating a Report
on page 274
for more about reporting capabilities.
The Change Determination Report report displays detected changes based on a configuration
change flag set when OpenManage Network Manager detects a change made to the device. To
successfully execute this report, you must enable a scheduled
Change Determination Process
. The
process must run before the reports has any contents. To run the process, go to the Schedules
portlet, and schedule that change determination process.
Reporting Limitations
The Configuration Change Report only reports on incremental configuration changes discovered
in the CD process. Simply making changes to configurations and backing them up in OpenManage
Network Manager does
not
ensure these appear in
Configuration Change Reports
. They appear in
reports only after running the CD process.
The
Configuration Change Report
includes a Filter that you can alter at runtime. By default, the
report filters on
Ty p e
only. If you want more filter criteria—like device IP, and/or date ranges—you
must edit the Report filter. To edit the filter, in the Reports manager, right-click the
Configuration
Change Report,
and select
Open,
then edit the filter in the
Filter
screen by selecting that node on
the left.
NOTE:
A recommended best practice is to execute the CD process as an operation run against multiple
resources following a scheduled group backup of these resources. If you run backups every day, the
Configuration Change Report then shows the daily changes, until they are purged from the database.
The application stores the specifics of what changed for future reporting.