Installation guide

1. "Collecting Windows Custom Information" on page 98
To collect Windows Custom Information (WCI) using script-based filters, you create and verify your
custom PowerShell scripts, install PowerShell on the VCM managed machines, and use VCM to collect
the WCI data.
Prerequisites to Collect Windows Custom Information
To collect Windows Custom Information from VCM managed machines, you must configure the
prerequisites.
Prerequisites
n
Write your own PowerShell script to return data in a VCM compatible, element-normal XML format,
or obtain PowerShell scripts from VMware Professional Services or another source. See "Using
PowerShell Scripts for WCI Collections" on page 87.
n
Understand the script signing policies if you use PowerShell 2.0. See "PowerShell Script Signing Policies"
on page 91.
n
Set the PowerShell execution policy on the VCM managed machine. See "Built-In PowerShell Policy
Settings" on page 92.
n
Understand how to write and run PowerShell scripts. See "References on PowerShell and Script Signing"
on page 92.
n
Verify that your PowerShell script is accessible when you paste the script content into the Script area of
the collection filter on the VCM Collector.
n
Confirm that the VCM Collector includes PowerShell 2.0 if the Collector is a client for WCI collections.
n
Understand how VCM manages Windows Custom Information data changes. See "Windows Custom
Information Change Management" on page 97.
n
Confirm that PowerShell 2.0 is installed on each VCM managed machine that will be used for WCI
collections. See "Install PowerShell" on page 100.
n
Upgrade older VCMAgents on the VCM managed machines from which you collect Windows Custom
Information, and then install the VCM 5.3 Agent or later on these machines.
n
Confirm or update the Agent Thread Administration settings on the VCM Collector. The default value
is set to below normal thread priority, and the Agent Data Retention default is set to a 15-day change
log.
Using PowerShell Scripts for WCI Collections
Windows Custom Information (WCI) uses PowerShell as the scripting engine and the element-normal
XML format as the output that is inserted into the VCM database.
WCI supports PowerShell 2.0 and works with later versions of PowerShell.
n
PowerShell 2.0 is the base requirement for WCI in VCM because of its ability to set the execution policy
at the process level.
n
You can run WCI PowerShell collection scripts against Windows machines that have PowerShell 1.0
installed if needed, although this usage is not supported or tested. If the collection scripts do not use
PowerShell 2.0 commands, your WCI filters that use the in-line method to pass a WCI script to
PowerShell will operate correctly.
Configuring Windows Machines
VMware, Inc.
87