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
Operating
System
Supported
File System
swa-
p
/boo-
t
/
/home, /tmp, /usr, /var,
/usr/local
xfs,
jfs
xfs,
jfs
Volume
Group Name
Type the name of the logical group.
For example, VolGroup00. You can specify only one volume group on the
target machines. You may add volume groups after the OS distribution is
installed.
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
(SLES only) You can assign only one volume group when partitioning the
disk.
n
(RHEL 5.x and 6.0, and SLES 10.3 and 11.1 only) You cannot use /boot as part
of the volume group name.
Add Click to add the configuration data to the Custom Volume Plan list.
Custom
Volume Plan
list
Displays the disk configuration data.
Grow
partition to
use all
remaining
space
Select the option to allow the logical volume to fill available space up to the
maximum size specified for the volume.
You can select the option for only one partition.
If you select this option, you can specify a Volume Size of 0MB.
Remove Click to delete the selected row from the custom volume plan list.
12. On the Confirmation page, click Finish.
The OS Provisioning Server starts jobs for each of the selected target machines. Each job creates a
configured session for the specified machines. The configured session includes information about the
target machine, the OS distribution, the configuration information for the selected combination of
target machine and operating system, and the VCM Agent.
13. Reboot the target machines.
You must cycle the power on the machines either manually or using a remote administration
mechanism. The machines must be configured to network boot from the OS Provisioning Server,
which identifies the configured session that is waiting and the installation begins. If the session does
not exist, then the target machine remains provisionable and is not provisioned until a session is
created and the target machine is rebooted.
Provisioning Physical or Virtual Machine Operating Systems
VMware, Inc.
187