User`s guide

Procedure
1. On your VCM Collector, click Administration.
2. Select Job Manager > History > InstantCollections > Past 24 Hours.
3. In the Instant Collections pane, select a collection job that includes WCI data.
4. In the Job History Machine Detail pane, select View Details.
A single row appears for each WCI filter that ran in the collection job. Information about the WCI
script and the script results parsing appears in the row.
5. In the View Details by Machine window, select the managed machines to view and click OK.
Detailed job history results appear for the WCI filters and managed machines.
n
If a WCI collection job encounters errors on a VCM managed machine, VCM reports detailed
information about the failure. Failures can occur when PowerShell starts, during script execution, or
when interpreting the script results.
n
If PowerShell is not installed on the managed machine, an error can occur in the PowerShell startup
process. Because PowerShell is an optional component, a status of Not Executed can appear in the
job details to indicate the skipped steps. The Not Executedstatus does not appear as an error in
the VCM job.
n
If a PowerShell script generates errors due to defects in the script, such as syntactical or
typographical errors, VCM reports the status as finished with errors in the collection job.
What to do next
n
Review the WCI collection results. See "Windows Custom Information Collection Results" on page 109.
n
Generate your own reports. See "Run Windows Custom Information Reports" on page 110.
Windows Custom Information Collection Results
Examine the results of your Windows Custom Information (WCI) collected data in the VCM tree views
and list view.
Prerequisites
Collect WCI data and confirm that the WCI collection job finished. Click Administration and select Job
Manager > History > Other Jobs > Past 24 Hours. See "Collect Windows Custom Information Data" on
page 106.
Getting Started with VCM
VMware, Inc. 109