5.3

ManualsBrandsVMware ManualsApplicationsvCenter Configuration Manager

181

182

183

184

185

186

187

188

189

190

Table Of Contents

Copyright
About This Book
Preparing for Installation
- Using Installation Manager
- Understanding Installation Configurations
- Understanding Tools Installation
- Checking Prerequisites for Installation
- Understanding VCM's Use of FIPS Cryptography
Installing VCM Using Installation Manager
- Using the Installation Manager
  - Navigating VCM Installation Manager Screens
  - Installing VCM and the Related Components
Upgrading VCM and Related Components
- Prerequisites
  - Backup and Recovery
  - Assumptions for Upgrading Your VCM Collector and Database
- Upgrading to VCM 5.3
- Upgrading Existing Windows Agents
- Upgrading Existing Remote Clients
- Upgrading Existing UNIX Agents
  - To Upgrade the UNIX Agent(s) with a Local Package
  - To Upgrade the UNIX Agent(s) with a Remote Package
- Upgrading VCM for Virtualization
  - Upgrading an Agent Proxy Machine
  - Upgrading the vSphere Client VCM Plug-in
Getting Started with VCM Components and Tools
- Understanding User Access
- Launching and Logging Onto VCM
  - How to Launch VCM and Log On
- Getting Familiar with the Portal
- Where to Go Next
Getting Started with VCM
- Discover, License, and Install Windows Machines
- 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
Getting Started with VCM for Virtualization
- Virtual Environment Configuration
- ESX 2.5/3.x,vSphere 4, and ESXi Servers Collections
- vCenter Server Collections
- Configuring Agent Proxy Virtualization Collections
- Configuring Agent Proxy Machines
- Configuring ESX/vSphere Servers
- Configuring Web Services for ESX/vSphere Server Communication
- Performing an Initial Virtualization Collection
- Exploring Virtualization Collection Results
- Configuring vCenter Server Data Collections
- About the vSphere Client VCM Plug-in
- Further Reading
Getting Started with VCM Remote
- Getting Started with VCM Remote
- Installing the VCM Remote Client
  - Installing the Remote Client manually
- Making VCM Aware of VCM Remote Clients
- Configuring VCM Remote Settings
  - Creating Custom Collection Filter Sets
  - Specifying Custom Filter Sets in the VCM Remote Settings
- Performing a Collection Using VCM Remote
- Exploring VCM Remote Collection Results
Getting Started with VCM Patching
- Getting Started with VCM Patching
- Getting Started with VCM Patching for Windows Machines
- Getting Started with VCM Patching for UNIX/Linux Machines
- Further Reading
Getting Started with Software Provisioning
- VMware vCenter Configuration Manager Package Studio
- Software Repository for Windows
- Package Manager for Windows
- Overview of Component Relationships
- Installing the Software Provisioning Components
- Using Package Studio to Create Software Packages and Publish to Repositories
  - Creating Packages
- Using VCM Software Provisioning for Windows
- Related Software Provisioning Actions
- Further Reading
Getting Started with VCM Management Extensions for Assets
- Getting Started with VCM Management Extensions for Assets
- Review Hardware and Software Configuration Item Fields
  - Modifying Hardware Configuration Item Fields
  - Modifying Software Configuration Item Fields
- Adding Hardware Configuration Items
  - Editing Values for Devices
  - Modifying Other Devices
- Adding Software Configuration Items
- Further Reading
Getting Started with VCM Service Desk Integration
- Getting Started with Service Desk Integration
- Service Desk Integration in the Console
- Service Desk Integration in Job Manager
- Further Reading
Getting Started with VCM for Active Directory
- Making VCM Aware of Domain Controllers
- Configuring VCM for Active Directory as an Additional Product
- Performing an Active Directory Data Collection
- Exploring Active Directory Collection Results
- Further Reading
Getting Started with VCM for SMS
- Getting Started with VCM for SMS
- Making VCM Aware of the SMS Servers
- Performing SMS Server Collections
- Performing SMS Client Collections
- Exploring SMS Collection Results
- Further Reading
Getting Started with Windows Server Update Services
- Getting Started with Windows Server Update Services
- Making VCM Aware of the WSUS Server
- Performing WSUS Server Collections
- Performing WSUS Client Collections
- Exploring WSUS Collection Results
  - Viewing WSUS Clients
  - Viewing WSUS Reports
- Further Reading
Accessing Additional Compliance Content
- Locating the Content Directory
- Launching the Content Wizard to Import Relevant Content
- Exploring Imported Content Results in the Portal
Installing and Getting Started with VCM Tools
- Installing the VCM Tools Only
- Foundation Checker
- VCM Job Manager Tool
- VCM Import/Export and Content Wizard (CW)
  - VCM Import/Export
  - Content Wizard
Maintaining VCM After Installation
- Customize VCM and Component-specific Settings
- Configure Database File Growth
- Configure Database Recovery Settings
- Create a Maintenance Plan for SQL Server 2005
- Incorporate the VCM CMDB into your Backup/Disaster Recovery Plans
Troubleshooting Problems with VCM
- Evaluating Missing UNIX Patch Assessment Results
- Resolving Reports and Node Summaries Problems
  - To Resolve the Problem
- Resolving Protected Storage Errors
  - To Resolve the Problem
- Resetting the Required Secure Channel (SSL)
- Resolving a Report Parameter Error
Configuring a Collector as an Agent Proxy
- Verifying Membership to CSI_COMM_PROXY_SVC on the Agent Proxy Machine
- Generating Key Pairs on the Agent Proxy Machine
- Uploading Keys to the Database
Index

1. Select Administration | Machines Manager | Licensed Machines | Licensed Windows Machines.

2. In the data grid, locate the machines on which you are verifying the existence of the necessary Agent

Extensions, and then verify that the Agent Ext. For Prov. Version column contains a value of 5.3 or

later. If it does not, you need to either install or upgrade the VCM Agent.

Upgrading the VCM Agent

If an earlier VCM Agent is installed on your machines, you will need to upgrade to the latest Agent. See

Upgrade Agent in the online Help.

Using Package Studio to Create Software Packages and Publish to

Repositories

Package Studio is the application used to build software packages for installation on target Windows

servers and workstations.

Windows packages can include in-house and commercial software installation files, including .msi, .exe,

VBScripts, python, PowerShell.

To add a software installer to a package, it must be able to install and uninstall unmanned or quietly using

command line options, response files, or other similar methods.

Creating Packages

A software package provides the files and metadata necessary to install and remove programs. One of the

most useful features of a package is the metadata regarding dependencies, conflicts, and other

relationships that are not represented by software installation files. This metadata is used to determine if

the necessary dependencies are in place so that an installation is successful, and if not, what is necessary to

make the installation successful. This use of metadata is similar to rpm on Linux.

Packages support commercial and custom software that may be installed using any installation

technology, including .msi, .exe, or scripts (Python, VBScript, PowerShell, and others).

Once a package is created and ready for distribution, it is published to a software repository. You use

Package Manager to download the package from the repository to the local machine and install it on your

Windows systems.

Creating a software package includes creating and saving a project. Projects can be used to create

variations based on platform or version that can then be published as separate packages.

General Process

Detailed steps for creating and publishing packages are provided in the Package Studio online Help and in

the VCMSoftware Provisioning Installation and User's Guide.

Getting Started with Software Provisioning

VMware, Inc. 185