Installation guide
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 for Virtual Environment Management
- 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
- 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
- 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, UNIX, and Mac OS X Machines
- Linux, UNIX, and Mac OS X Machine Management
- Linux, UNIX, or Mac OS X Installation Credentials
- Configure Collections from Linux, UNIX, and Mac OS X Machines
- Configure Installation Delegate Machines to Install Linux, UNIX, and Mac OS X...
- Configure the HTTPS Bypass Setting for Linux Agent Installations
- Enable Linux, UNIX, and Mac OS X Agent Installation
- Add and License Linux, UNIX, and Mac OS X Machines for Agent Installation
- Install the VCM Agent on Linux, UNIX, and Mac OS X Operating Systems
- Collect Linux, UNIX, and Mac OS X Data
- Linux, UNIX, and Mac OS X Collection Results
- Configure Scheduled Linux, UNIX, and Mac OS X Collections
- Patching Managed Machines
- Patch Assessment and Deployment
- Prerequisite Tasks and Requirements
- Manually Patching Managed Machines
- Getting Started with VCM Manual Patching
- Configuring An Automated Patch Deployment Environment
- Deploying Patches with Automated Patch Assessment and Deployment
- Configure VCM for Automatic Event-Driven Patch Assessment and Deployment
- Generate a Patch Assessment Template
- Run a Patch Assessment on Managed Machines
- Add Exceptions for Patching Managed Machines
- Configure the VCM Administration Settings
- Generate a Patch Deployment Mapping
- Configure VCM for Automatic Scheduled Patch Assessment and Deployment
- How the Linux and UNIX Patch Staging Works
- How the Linux and UNIX Patching Job Chain Works
- How the Deploy Action Works
- Patch Deployment Wizards
- Running Patching Reports
- 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
Procedure
1. On target machines, configure the BIOS to network boot.
2. Start the machines on your provisioning network.
3. In VCM, click Administration.
4. Select Machines Manager > OS Provisioning > Provisionable Machines.
5. On the data grid toolbar, click Refresh.
This action collects data from the OS Provisioning Server and the provisionable machines appear in the
data grid when the collection is finished. The machines are identified by MAC address.
What to do next
Provision the target machine. See "Provision Machines with Operating System Distributions" on page 204.
Provision Machines with Operating System Distributions
The OS provisioning process installs one Windows or Linux operating system distribution on one or more
physical or virtual machines using OS provisioning.
Depending on the distribution you are installing, use one of the following procedures.
n
"Provision Windows Machines" on page 204
Provisioning physical or virtual machines with a Windows operating system installs the selected
operating system and the VCM Agent on one or more of your Windows machines.
n
"Provision Linux Machines" on page 208
Provisioning physical or virtual machines with a Linux operating system installs the selected operating
system and the VCM Agent on one or more of your Linux machines.
Provision Windows Machines
Provisioning physical or virtual machines with a Windows operating system installs the selected operating
system and the VCM Agent on one or more of your Windows machines.
You can install one OS distribution on one or more target machines. To install a different OS distribution,
configure a new OS provisioning action.
Select no more than ten machines per provisioning action.
Prerequisites
n
Verify that the operating system you are installing is compatible with the hardware or configuration of
the target physical or virtual machines. For example, the operating system must support the drivers
required by the hardware.
n
Verify that the OS Provisioning Servers are registered. See "Add Operating System Provisioning
Servers" on page 202.
n
Verify that the OS distributions are collected and appear in the OS Distributions data grid. See "Collect
Operating System Distributions" on page 203.
n
Verify that the target machines are discovered and appear in the Provisionable Machines data grid. See
"Discover Provisionable Machines" on page 203.
vCenter Configuration Manager Administration Guide
204
VMware, Inc.