5.6
Table Of Contents
- VMware vCenter Configuration Manager Installation Guide
- Contents
- About This Book
- Achieving a Successful VCM Installation
- Hardware Requirements for Collector Machines
- Software and Operating System Requirements for Collector Machines
- Preparing for Installation
- System Prerequisites to Install VCM
- Configure Resources to Install VCM on a Virtual Machine
- Secure Communications Certificates
- Single-Tier Server Installation
- Two-Tier Split Installation
- Three-Tier Split Installation
- Configuring a Three-Tier Split Installation Environment
- Installation Prerequisites for All Servers
- Configuring the VCM Database Server
- Configuring the Web Server
- Verify the Server Role Services on the Web Server
- Verify the IIS Server-Side Includes Role Service
- Verify the ISAPI Extensions
- Install the .NET Framework
- Verify the Authentication Settings
- Install SQL Server on the Web Server
- Install SQL Server 2008 Utilities
- Place the Web Server in the Internet Explorer Trusted Zone
- Configuring SSRS on the Web Server
- Configuring the VCM Collector
- Configuring Additional Components for a Three-Tier Environment
- Installing VCM
- Configuring SQL Server for VCM
- Upgrading or Migrating VCM
- Upgrading VCM and Components
- Upgrading Virtual Environments Collections
- Migrating VCM
- Prerequisites to Migrate VCM
- Migrate Only Your Database
- Replace Your Existing 32-Bit Environment with a Supported 64-bit Environment
- Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Tier, Two-Tier...
- How to Recover Your Collector Machine if the Migration is not Successful
- Maintaining VCM After Installation
- Hardware and Operating System Requirements for VCM Managed Machines
- VCM Agent Support on Non-English Windows Platforms
- VCM Managed Machine Requirements
- Windows Custom Information Supports PowerShell 2.0
- Supported OS Provisioning Target Systems
- Software Provisioning Requirements
- UNIX and Linux Patch Assessment and Deployment Requirements
- Support for VMware Cloud Infrastructure
- vCenter Operations Manager Integration Features
- FIPS Requirements
- Agent Sizing Information
- Hardware and Software Requirements for the Operating System Provisioning Server
- Installing, Configuring, and Upgrading the OS Provisioning Server and Components
- Index
Agent Supported Operating System Supported
Hardware
Platform
Platforms
To Be
Upgraded
SUSE Linux Enterprise Server (SLES) 10.3–10.4, 11.0–11.2
SUSE Linux Enterprise Server (SLES) 10.0–10.2 (up to 5.5.0
Agent only)
x86 and x64
Mac OS X
(Servers and
Workstations)
Mac OS X 10.6 (up to 5.5.0 Agent only) Intel-based
Apple
platforms
only
Mac OS X 10.7 Intel-based
Apple
platforms
only
Oracle 9i
Solaris 10 Sparc and
Sparc-V9
Oracle 10g
Solaris 10 Sparc-V9,
x86, and x64
Active
Directory
Microsoft Windows 2000 x86
Microsoft Windows 2003 x86 and x64
Microsoft Windows 2003 R2 x86 and x64
Microsoft Windows 2008 x86 and x64
VCM Remote Supports the same platforms as the VCM Windows Agent.
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.
Hardware and Operating System Requirements for VCM Managed Machines
VMware, Inc.
123