Installation guide
Table Of Contents
- VMware vCenter Configuration ManagerAdministration Guide
- About This Book
- Getting Started with VCM
- Installing and Getting Started with VCM Tools
- Configuring VMware Cloud Infrastructure
- Virtual Environments Configuration
- Configure Virtual Environments Collections
- Configure Managing Agent Machines
- Obtain the SSL Certificate Thumbprint
- Configure vCenter Server Data Collections
- Configure vCenter Server Virtual Machine Collections
- Configure vCloud Director Collections
- Configure vCloud Director vApp Virtual Machines Collections
- Configure vShield Manager Collections
- Configure ESX Service Console OS Collections
- Configure the vSphere Client VCM Plug-In
- Running Compliance for the VMware Cloud Infrastructure
- Create and Run Virtual Environment Compliance Templates
- Create Virtual Environment Compliance Rule Groups
- Create and Test Virtual Environment Compliance Rules
- Create and Test Virtual Environment Compliance Filters
- Preview Virtual Environment Compliance Rule Groups
- Create Virtual Environment Compliance Templates
- Run Virtual Environment Compliance Templates
- Create Virtual Environment Compliance Exceptions
- Configuring vCenter Operations Manager Integration
- Auditing Security Changes in Your Environment
- Configuring Windows Machines
- Verify Available Domains
- Check the Network Authority
- Assign Network Authority Accounts
- Discover Windows Machines
- License Windows Machines
- Disable User Account Control for VCM Agent Installation
- Install the VCM Windows Agent on Your Windows Machines
- Enable UAC After VCM Agent Installation
- Collect Windows Data
- Windows Collection Results
- Getting Started with Windows Custom Information
- Prerequisites to Collect Windows Custom Information
- Using PowerShell Scripts for WCI Collections
- Windows Custom Information Change Management
- Collecting Windows Custom Information
- Create Your Own WCI PowerShell Collection Script
- Verify that Your Custom PowerShell Script is Valid
- Install PowerShell
- Collect Windows Custom Information Data
- Run the Script-Based Collection Filter
- View Windows Custom Information Job Status Details
- Windows Custom Information Collection Results
- Run Windows Custom Information Reports
- Troubleshooting Custom PowerShell Scripts
- Configuring Linux and UNIX Machines
- Configuring Mac OS X Machines
- Patching Managed Machines
- VCM Patching for Windows Machines
- VCM Patching for UNIX and Linux Machines
- UNIX and Linux Patch Assessment and Deployment
- Getting Started with VCM Patching
- Getting Started with VCM Patching for Windows Machines
- Check for Updates to Bulletins
- Collect Data from Windows Machines by Using the VCM Patching Filter Sets
- Assess Windows Machines
- Review VCM Patching Windows Assessment Results
- Prerequisites for Patch Deployment
- Default Location for UNIX/Linux Patches
- Location for UNIX/Linux Patches
- Default Location for UNIX/Linux Patches
- vCenter Software Content Repository Tool
- Deploy Patches to Windows Machines
- Getting Started with VCM Patching for UNIX and Linux Machines
- Check for Updates to Bulletins
- Collect Patch Assessment Data from UNIX and Linux Machines
- Explore Assessment Results and Acquire and Store the Patches
- Default Location for UNIX/Linux Patches
- Deploy Patches to UNIX/Linux Machines
- How the Deploy Action Works
- Running VCM Patching Reports
- Customize Your Environment for VCM Patching
- Running and Enforcing Compliance
- Provisioning Physical or Virtual Machine Operating Systems
- Provisioning Software on Managed Machines
- Using Package Studio to Create Software Packages and Publish to Repositories
- Software Repository for Windows
- Package Manager for Windows
- Software Provisioning Component Relationships
- Install the Software Provisioning Components
- Using Package Studio to Create Software Packages and Publish to Repositories
- Using VCM Software Provisioning for Windows
- Related Software Provisioning Actions
- Configuring Active Directory Environments
- Configuring Remote Machines
- Tracking Unmanaged Hardware and Software Asset Data
- Managing Changes with Service Desk Integration
- Index
Installation Options with Default
Values
Description
CSI_PARENT_LOG_
DIRECTORY=default
Specifies where agent operational log files are kept. The log
directory is CSI_PARENT_LOG_DIRECTORY/CMAgent/log. The
default value indicates to use these values.
n
Mac OS X: log ->private/var/log/CMAgent/log
CSI_KEEP_CSIINSTALL=N Recommend keeping the default value. After a successful
installation, the temp installation directory CSIInstall is deleted.
To keep this installation directory, set this parameter to Y.
Manually Uninstall the Mac OS X Agent
When you install the Agent, an uninstall file, UninstallCMAgent, is created in
<path>/CMAgent/uninstall. You use the file to manually uninstall the Agent from the managed
machine.
The uninstall reverses all changes made by installation. However, the installation log files are retained in
<AgentRoot>/install. <AgentRoot> defaults to the CMAgent directory that was created during
installation.
Prerequisite
To save a copy of the configuration file to use on other machines, copy csi.config to a secure location.
The file is located in <path>/CMAgent/install.
Procedure
1. Navigate up one level from the uninstall directory in the CMAgent directory.
2. Run the # ./uninstall/UninstallCMAgent command to uninstall the Agent.
What to do next
After you run UninstallCMAgent, delete the remaining the CMAgent directory before you install a new
Agent.
Collect Mac OS X Data
When the Mac OS X machines are licensed and the Agent is installed, you collect data from those machines.
Collecting data from machines adds the collected machine information to the VCM database and makes
the machine data available for reporting, running compliance, and other management options. The
collection process for Mac OS X collection is similar to other collections, including Windows, except that
you select Mac OS X data types during the collection instead of Windows data types.
Prerequisites
n
License the target machines. See "License Mac OS X Machines" on page 126.
n
Install the Agent on the target machines. See "Install the Agent on Mac OS X Machines" on page 127.
Procedure
1. Click Collect.
vCenter Configuration Manager Administration Guide
132
VMware, Inc.