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
a. Run the chmod u+x csi.config command to add write file permissions if the file has only read
permissions set.
b. Modify the csi.config file options based on your local requirements and save the file.
c. Copy the modified and saved csi.config file to the extracted location.
For example, # cp /<safelocation>/csi.config
/<extractedlocation>/CSIInstall/csi.config.
7. Run InstallCMAgent in either silent mode or interactive mode.
Option Action
Silent mode Run the # ./CSIInstall/InstallCMAgent -s
command.
Install the Agent using the silent mode if you
manually edited the csi.config file, if you modified
the csi.config file using the interactive method, or
if you are using a custom configuration file that you
saved from a previous Agent installation. This mode
uses the values specified in csi.config without
prompting for input.
When the silent installation finishes, a summary of the
installation process and status appears. Verify that the
installation finished without errors.
Interactive mode Run the # ./CSIInstall/InstallCMAgent
command.
Install the Agent using the interactive mode if you did
not modify the csi.config and to respond to each
prompt to accept or change each parameter in the
csi.config file as it runs. As a result of your
responses, the csi.config is modified.
The preinstallation stage of interactive mode checks
for a valid user, CSI_USER. If the user exists, you are
not prompted for these configuration values.
n
CSI_USER_NO_LOGIN_SHELL
n
CSI_USER_PRIMARY_GROUP
n
CSI_USER_PRIMARY_GID
n
CSI_USER_USE_NEXT_AVAILABLE_LOCAL_GID
You are prompted for these values only when the
CSI_USER user account is not found.
You can check the installation status in the installation log file. The file is located in <CSI_PARENT_
DIRECTORY>/log/install.log.
8. Run ls –la /CSI_PARENT_DIRECTORY/CMAgent to verify that all the required files and directories
were installed.
/CSI_PARENT_DIRECTORY/CMAgent is the default directory. If you changed the directory name
during installation, modify the ls -la command to display the custom directory name.
vCenter Configuration Manager Administration Guide
112
VMware, Inc.