User`s guide
Table Of Contents
- VCM Installation and Getting Started Guide
- Updated Information
- About This Book
- Preparing for Installation
- Installing VCM
- Using Installation Manager
- Installing and Configuring the OS Provisioning Server and Components
- Installing the Operating System Provisioning Server
- Preparing Boot Images for Windows Provisioning
- Copy the VCM Certificate to the OS Provisioning Server for Linux Provisioning
- Importing Distributions into the OS Provisioning Server Repository
- Configuring the OS Provisioning Server Integration with the VCM Collector
- Maintaining Operating System Provisioning Servers
- Upgrading or Migrating vCenter Configuration Manager
- Upgrade and Migration Scenarios
- Prerequisites
- Back up Your Databases
- Back up Your Files
- Back up Your Certificates
- Software Supported by the VCM Collector
- Migration Process
- Prerequisites
- Foundation Checker Must Run Successfully
- Use the SQL Migration Helper Tool
- Migrate Only Your Database
- Replace your existing 32-Bit Environment with the Supported 64-bit Environment
- How to Recover Your Machine if the Migration is not Successful
- Migrate a 32-bit environment running VCM 5.3 or earlier to VCM 5.4
- Migrate a 64-bit environment running VCM 5.3 or earlier to VCM 5.4
- Migrate a split installation of VCM 5.3 or earlier to a single-server install...
- After You Migrate VCM
- Upgrade Process
- Upgrading Existing Windows Agents
- Upgrading Existing Remote Clients
- Upgrading Existing UNIX Agents
- Upgrading VCM for Virtualization
- Getting Started with VCM Components and Tools
- Getting Started with VCM
- Discover, License, and Install Windows Machines
- Verifying Available Domains
- Checking the Network Authority
- Assigning Network Authority Accounts
- Discovering Windows Machines
- Licensing Windows Machines
- Installing the VCM Windows Agent on your Windows Machines
- Performing an Initial Collection
- Exploring Windows Collection Results
- Getting Started Collecting Windows Custom Information
- Discover, License, and Install UNIX/Linux Machines
- Discover, License, and Install Mac OS X Machines
- Discover, License, and Collect Oracle Data from UNIX Machines
- Customize VCM for your Environment
- How to Set Up and Use VCM Auditing
- Discover, License, and Install Windows Machines
- Getting Started with VCM for Virtualization
- Getting Started with VCM Remote
- Getting Started with VCM Patching
- Getting Started with Operating System Provisioning
- Getting Started with Software Provisioning
- Getting Started with VCM Management Extensions for Assets
- Getting Started with VCM Service Desk Integration
- Getting Started with VCM for Active Directory
- Accessing Additional Compliance Content
- Installing and Getting Started with VCM Tools
- Maintaining VCM After Installation
- Troubleshooting Problems with VCM
- Index
Prerequisites
VCM 5.4 now supports 64-bit environments only, which include 64-bit hardware, a 64-bit operating
system, and SQL Server 2008 R2. If you migrate from a 32-bit environment to a 64-bit environment, you
must prepare your 64-bit environment for a VCM installation. For details about configuring a 64-bit
machine as a Collector, see the VCM Hardware and Software Requirements Guide.
Before you migrate to VCM 5.4:
n
Your version of VCM must be VMwareVCM 5.3, EMC Ionix SCM 5.0 or later, or Configuresoft ECM
4.11.1 or later.
n
The current VCM installation must be functional.
n
Back up your content, including databases, the CMFILES$ share, any files used to customize the
Collector, any reports that are exported to a non-default location, and certificates.
n
All running jobs must be complete and jobs must not be scheduled to begin during the migration
process. The migration process stops the SQLAgent service, which prevents any new jobs from
starting.
n
All users must be logged off, and users must not attempt to access VCM for the duration of the
migration process.
n
To simplify the steps to reconfigure scheduled jobs and product logins, download the VCM SQL
Migration Helper Tool from the VMware download site.
n
If you upgrade VCM Remote, and want older agents to function properly, you must use the same
name for the new Remote virtual directory that was used in your previous installation. If you change
the Remote virtual directory name, all corresponding agents must be updated to reflect the new virtual
directory.
n
Your existing environment must include Microsoft .NET Framework required versions.
n
Existing 32-bit environments must include SQL Server 2005 and SP3.
n
Existing 64-bit environments must include 64-bit SQL Server 2005 and SP2 and 32-bit SQL Server
Reporting Services and SSRS SP3. Prior to VCM 5.4, only the 32-bit of SSRS was supported in 64-bit
VCM environments.
CAUTION Before you begin the migration, to avoid any potential loss of data you must back up your
content, including databases, the CMFILES$ share, any files used to customize the Collector, any reports
that are exported to a non-default location, and certificates.
vCenter Configuration Manager Installation and Getting Started Guide
46 VMware, Inc.