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
Procedure
1. Select Administration > Settings > Integrated Products > VMware > vSphere Client VCM Plug-In.
2. Select the setting you want to configure and click Edit Settings.
3. On the Settings Wizard page for each setting, configure the options.
Option Description
Machine group against which the external reports
will be run
Type the name of the machine group.
The default value is All Machines.
Role to use for external report access Type the name of the user role to be used to
access the reports.
The default value is Read-Only. Users other
than Admin must have the role selected here
in order to see reports in the vSphere Client.
User name to use for assessments Type the name of the user who will be
running assessments to obtain data for
generating reports.
4. Click Next.
5. Verify your settings and click Finish.
What to do next
You manage machines by running compliance, patching, and reports. See "Manage Machines from the
vSphere Client" on page 145.
Manage Machines from the vSphere Client
vSphere Client-managed machines are available in the vSphere Client VCM Plug-In when they licensed
and have the VCM Agent installed. Using the vSphere Client VCM Plug-In, you can continue to manage
the machines. The available actions include collecting new data and running compliance, patching, and
reports for the selected machines.
Prerequisites
n
License Windows and UNIX\Linux virtual machines. See "Licensing Windows Machines" on page 75
and "Licensing UNIX/Linux Machines" on page 98.
n
Install the Agent on the virtual machine. See "Installing the VCM Windows Agent on your Windows
Machines" on page 77 and "Installing the Agent on UNIX/Linux Machines" on page 99.
Procedure
1. Start the vSphere Client.
2. Click the VCMActions tab.
What to do next
Click help on the VCMActions tab for more information about the actions.
Upgrade the vSphere Client VCM Plug-In
Upgrading the plug-in is necessary only if you have a vSphere Client VCM Plug-In version 5.3 or earlier,
or if the URL to the VCM instance has changed.
Getting Started with VCM for Virtualization
VMware, Inc. 145