To retrieve this information, see the instructions in Compliance and Change Reporting on page
329.
How To:
Run Change Determination
Follow these steps to run the Default Change Determination:
In the Schedules portlet, locate the Default Change Determination operation.
1
Right-click and select Open.
2
Configure the schedule
3
This runs Change Determination with the target group of All Devices (all discovered devices).
Change Determination Defaults
By default, Change Determination can run against all devices without requiring the config change
update flag be set or updated based on events tied to the Conifg Update Flag event processing rule/
action.
To disable the manual run-ability of the Change Determination process, uncomment the property
in \owareapps\changemgmt\lib\cm.properties (or add it to
\owareapps\installprops\lib\installed.properties).
#############################################
# Change Determination Flag
# Allows system to be flagged to only run
# change determination against devices we
# have received Config Change Event for.
# Default Behavior is to run change determination
# for All targets (the same as setting the below property = false)
#com.dorado.changemgmt.change.determination.require.config.events=true
Compliance and Change Reporting
The Compliance Policy Violation report is seeded when you have ProScan / Change Management
in Dell 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).
Compliance and Change Reporting | Change Management – ProScan
329
Need help?
Do you have a question about the OpenManage Network Manager and is the answer not in the manual?
Questions and answers