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
The OS Provisioning Server identifies provisionable physical or virtual machines in your environment
when the target machines are set to network boot and attempt to PXE boot.
5. "Provision Machines with Operating System Distributions" on page 162
The OS provisioning process installs one Windows or Linux operating system distribution on one or
more physical or virtual machines using OS provisioning.
Continuous provisioned machine management is based on the latest data you collect from the OS
Provisioning Server. See "Provisioned Machines Results" on page 171.
Add Operating System Provisioning Servers
To register the OS Provisioning Servers, you must add the Red Hat servers that you configured as OS
Provisioning Servers. When the servers are registered, you select the OS Provisioning Server from which
to install operating systems when you are configuring the provisioning action.
Prerequisites
n
Verify that you installed and configured your OS Provisioning Server instances. See the VCM Installation
Guide.
n
Ensure that the Red Hat servers that you configured as OS Provisioning Server are added and licensed
in VCM. See "Configuring Linux and UNIX Machines" on page 107.
n
Ensure that you collected Machines - General data from your OS Provisioning Server instances. See
"Collect UNIX/Linux Data" on page 116.
Procedure
1. Click Administration.
2. Select Machines Manager > OS Provisioning > Registered Servers.
3. Click Add.
4. On the Select OSP Server page, move the selected servers to the lower pane and click Next.
5. Review the Confirmation information and click Finish.
6. Click Refresh, located on the main toolbar, to update the data grid.
What to do next
n
Collect the available distributions from the target OS Provisioning Servers. See "Collect Operating
System Distributions" on page 161.
Set the Trust Status for Operating System Provisioning Servers
You set the trusted status is on Agent machines where you verify that the connection is legitimate. When
you set the trust status, you are marking the Agent certificate as trusted. When transmitting sensitive
information, such as credentials, between the Collector and OS Provisioning Servers, the machines must
be trusted.
If you choose not to use this level of security, you can set the Allow sensitive parameters to be
passed to agents not verified as Trusted option to Yes in the General Settings for the
Collector data grid.
Prerequisites
Verify that your OS Provisioning Server instances are added as registered servers. See "Add Operating
System Provisioning Servers" on page 160
vCenter Configuration Manager Administration Guide
160
VMware, Inc.