Installation guide

ManualsBrandsVMware ManualsOtherVCM 5.3 - CONFIGURATION MANAGER SECURITY ENVIRONMENT REQUIREMENTS

151

152

153

154

155

156

157

158

159

160

Linux, UNIX, and Mac OS Agent Files

VCM Linux, UNIX, and Mac OS Agent files are architecture specific. When you install the Agent using

VCM, the target operating systems are evaluated and the corresponding Agent is installed. If you are

manually installing the Agent on the target machine, you must ensure that you use to correct Agent

binary packages.

The Agent packages are located on the Collector in \Program Files (x86)

\VMware\VCM\Installer\Packages by default.

Operating SystemVersion Agent Binary

Red Hat Enterprise Linux 5.0–5.10, 6.0–6.4

SUSE Linux Enterprise Server 10.0–10.4, 11.0–11.2

Oracle Enterprise Linux (OEL) 5.0–5.10, and 6.0

CentOS 5.0–5.10, and 6.0

CMAgent.5.7.1.Linux

Solaris 10 and 11 for SPARC

CMAgent.5.7.0.SunOS

Solaris 10 and 11 for x86

CMAgent.5.7.0.SunOS.x86.5.10

HP-UX 11i 1.0 and 2.0 (11.11 and 11.23 for PA-RISC)

CMAgent.5.4.0.HP-UX.11.pa

HP-UX 11i 3.0 (11.31 for PA-RISC)

CMAgent.5.7.0.HP-UX.11.pa

HP-UX 11i 2.0 (11.23 for Itanium)

CMAgent.5.4.0.HPUX.11.ia64

HP-UX 11i 3.0 (11.31 for Itanium)

CMAgent.5.7.0.HPUX.11.ia64

AIX 6L, 6.1, 7.1

CMAgent.5.7.0.AIX.5

Mac OS X 10.6

CMAgent.5.5.0.Darwin

Mac OS X 10.7, 10.8

CMAgent.5.7.0.Darwin

Table 15–2. VCM Linux, UNIX, and Mac OS Agent Files

Windows Custom Information Supports PowerShell 2.0

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, although this usage is not supported or tested. If the collection scripts do not use PowerShell

2.0 commands, any of your WCI filters that use the in-line method to pass a WCI script to PowerShell

will operate correctly.

With PowerShell 2.0, you can set the script signing policies at the machine, user, and process levels. The

process level runs a single execution of powershell.exe.

In VCM, Windows Custom Information (WCI) uses script type information in the collection filter to

determine how to execute PowerShell and how to pass the script to it.

For more information, see the VCM Administration Guide.

vCenter Configuration Manager Advanced Installation Guide

160

VMware, Inc.