User`s guide

11. Click Next and then Finish.
12. Run a collection using your new collection filter.
13. Ensure the job completes.
14. View data in the Custom Information nodes ( Console > Windows > Operating System > Custom
Information).
When the Windows Custom Information data is available in the VCM database, you can generate reports
and enforce compliance.
Change Detection in Windows Custom Information Data
Deltas in WCI are maintained on a per-filter basis at the client side, which means that if multiple filters
return data under the same top-level element name (such as NetStat), each filter will have its own change
detection.
In the following example, using multiple filters that collect the same open ports data and return it under
the NetStat top-level element name, if a client machine has just started listening on port 80, each filter will
report this new data as a newly created value the first time the filter “sees” this data. The best practice is to
avoid this type of overlap of filters.
For example, two copies of the File Permission With Audit filter could be created in order to collect file
permissions data from different parts of the file system, but they should not overlap. Having one filter get
data from C:\ and another filter get data from C:\Windows would be a good practice. However, having
one filter get data from C:\Windows with audit information and another filter get data from C:\Windows
without audit information would not be a good practice because both filters would generate "new file" and
"deleted file" events each time a new file was added or removed.
n
For an element such as NetStat, only one filter should be used.
n
For an element such as NTFS file system (NTFSDirectory), multiple filters would likely be used. For
example, one filter would be used to obtain the details under C:\, and another filter would be used for
C:\Windows\System. Both would merge under the NTFSDirectory top-level element, but there
should be no overlap; instead they would each collect separate parts of the file structure to avoid
“extra” change reporting.
Purge for Windows Custom Information
As with other data types, purge for WCI will purge all data for a machine. This means that if a single WCI
filter is collected with the “Do not limit to delta” option selected, all WCI data for that machine will be
purged from the client’s master file and from the VCM database, and it will be replaced with the resulting
data from the single filter.
Job Status Reporting for WCI
Job status reporting for WCI is provided on a per script/filter level, and includes detailed reporting about
exit codes and process standard error output. As each script/filter is executed, VCM captures detailed
results information during the execution of the WCI collection filter scripts.
You can view the detailed information in the VCM user interface in the Administration > Job Manager >
History node by selecting the executed job and then selecting View Details in the Job History Machine
Detail pane of a collection job that includes WCI data.
vCenter Configuration Manager Installation and Getting Started Guide
90 VMware, Inc.