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
Configuring Linux and UNIX Machines
8
Configuring Linux and UNIX Machines
To collect UNIX/Linux data and to manage your physical or virtual UNIX/Linux machines, you must add
the machines, license them for use, and install the appropriate VCM Agent.
Prerequisites
Review the upgrade requirements to determine if the machines on which you are installing the current
Agent are supported platforms and machine type. See "Upgrade Requirements for UNIX/Linux Machines"
on page 107.
Procedure
1. "Add UNIX/Linux Machines" on page 108
Add UNIX/Linux machines to the Available Machines list to make the machines available for licensing.
2. "License UNIX/Linux Machines" on page 109
License UNIX/Linux machines before you install the Agent and begin to manage them. You license the
machines displayed in the Available Machines list.
3. "Install the Agent on UNIX/Linux Machines" on page 109
Install the appropriate version of the VCM Agent on each of your licensed target machines to enable
communication between the Collector and the managed UNIX/Linux machines.
4. "Collect UNIX/Linux Data" on page 116
When the UNIX/Linux machines are licensed and the Agent is installed, you collect data from those
machines.
Continuous machine management is based on the latest data you collect from target machines. You can
view data and run actions, such as reports or compliance, based on the collected data. See "UNIX/Linux
Collection Results" on page 116.
Upgrade Requirements for UNIX/Linux Machines
To use new VCM functionality, you must upgrade the VCM Agent on target machines based on machine
type. You must consider several requirements if you are upgrading from a previous Agent version to the
current version on your managed UNIX and Linux machines.
When you upgrade the UNIX Agent on Red Hat machines, be aware of the licensing changes between
VCM versions. In VCM 5.5, physical and virtual machines are licensed as servers or workstations.
For general UNIX and Linux machine requirements, see the VCM Installation Guide.
VMware, Inc.
107