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
Adding a source gives the Package Manager on the selected machines access to the packages available in
specified section. The sources are numbered in priority order. When you add a new one, you can specify
whether to add it to the beginning or to the end of the list. You can also remove sources.
Prerequisites
n
Verify that you collected Package Manager data from the target machines. See "Collect Package
Manager Information from Machines" on page 201.
n
Verify that you collected repository data from software repository. See "Collect Software Repository
Data" on page 202
Procedure
1. Click Console.
2. Select Windows tab > Operating System > Software Provisioning > Package Managers.
3. Select one or more machines, and click Add Source.
4. On the Select Machines page, verify that the machines displayed in the lower pane are the machines to
which you want to add the source and click Next.
5. On the Enter or Select Source page, configure the options, and click Next.
a. Select either Add source at the beginning of existing source lists or Add source at the end of the
existing source list.
b. Click Browse Sources.
c. On the Browse Sources page, select one of the following in the Show Sources from drop-down
menu.
n
Package Manager Source Lists: Select this option if you have already added sources to at least
one Package Manager and you want to add the source to other Package Managers. When you
click OK, the selected source populates the Platform and Section on the Enter or Select Source
page.
n
VCM Managed Repositories: Select this option if the source has not yet been added to a
Package Manager. When you return to the Enter or Select Source page, you must type the
platform and section names in the appropriate text boxes.
d. Select the URI and click OK.
e. Verify that the Platform name and the Section name are exactly the names used in the repository.
6. On the Schedule page, select one of the scheduling options and configure as needed.
7. On the Confirmation page, review the information and click Finish.
The added source is displayed in the Package Manager - Sources data grid.
What to do next
Install software packages on target machines. See "Install Packages" on page 203.
Install Packages
The process of installing packages includes identifying and processing dependencies and conflicts; running
any specified prescripts; running the installation using any specified command arguments; and running
any specified post-scripts. You can also remove packages.
Provisioning Software on Managed Machines
VMware, Inc.
203