5.6
Table Of Contents
- VMware vCenter Configuration Manager Administration Guide
- Contents
- 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
- Resolve Noncompliant Virtual Environments Template Results
- Configure Alerts and Schedule Virtual Environment Compliance Runs
- Configuring vCenter Operations Manager Integration
- Auditing Security Changes in Your Environment
- Configuring Windows Machines
- Configure Windows Machines
- Verify Available Domains
- Check the Network Authority
- Assign Network Authority Accounts
- Discover Windows Machines
- License Windows Machines
- Install the VCM Windows Agent on Your Windows Machines
- 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
Option Description
n
Duplicate mount points are not allowed.
n
For a swap partition, the mount point and the file system type should be
swap.
n
When naming mount points, you can use letters, digits, ., -, _, and +. Spaces
are not allowed.
Volume
Name
Type the name of the logical partition.
For example, LogVol00.
The volume names must meet specific criteria.
n
When naming volumes, you can use letters, digits, ., or _. Spaces are not
allowed.
n
The name limit 16 characters.
n
If you assign a volume name, you must assign a volume group name.
n
If you assign more than one volume name in a volume group, you cannot
use the same name for each volume name.
Volume Size The the size of the partition in megabytes or gigabytes.
For example, 10MB or 1GB.
If you select Grow partition to use all remaining space, you can specify a
value of 0MB. If Grow is not selected, you must specify a valid partition size.
File System Select the type of file system.
For a swap partition, the mount point and the file system type should be swap.
Supported File System options by operating system.
Operating
System
Supported
File System
swa-
p
/boo-
t
/
/home, /tmp, /usr, /var,
/usr/local
RHEL 6.0
ext2, ext3,
ext4, swap,
vfat, xfs
swap
ext2,
ext3,
ext4
ext2,
ext3,
ext4
ext2, ext3, ext4,xfs
RHEL 5.4
and 5.5
ext2, ext3,
ext4, swap,
vfat
swap
ext2,
ext3
ext2,
ext3,
ext4
ext2, ext3, ext4
RHEL 5.0
and 5.2
ext2, ext3,
swap, vfat
swap
ext2,
ext3
ext2,
ext3
ext2, ext3
SLES 10.0
and 11.1
reiser, ext2,
ext3, xfs, jfs,
swap
swap
reiser,
ext2,
ext3,
reiser,
ext2,
ext3,
reiser, ext2, ext3, xfs, jfs
vCenter Configuration Manager Administration Guide
186
VMware, Inc.