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
Create Compliance Rules Based on Software Provisioning Data
A Compliance rule based on software provisioning data detects any packages or sources that are out of
compliance. You can configure remediation actions to bring the machines back into compliance.
In this example the Compliance rule checks whether the source, where the values are platform=Any and
section=Release, was added to selected Package Managers as a source. If not, then add the repository
source to the machines where the rule fails.
Procedure
1. Click Compliance.
2. Select Machine Group Compliance > Rule Groups.
3. Expand your rule group and select Rules.
4. On the Rules data grid, click Add.
5. Type a Name and Description for your rule and click Next.
6. On the Data Type page, expand Windows and select the data type on which you are basing the rule
and click Next.
In this example, select Software Provisioning - Package Managers - Sources.
7. On the Rule Type page, select Conditional (if/then) and click Next.
8. On the Conditional Data page, configure the options.
a. In the IF area, click Add.
b. Select Source Repository URI = YourRepository.
c. Select Must Exist.
d. In the THEN area, click Add and select Platform = Any and Section = Release.
e. Click Next.
9. On the Options page, configure the settings.
a. Select a Severity in the drop-down menu.
b. Select Make available for enforcement where possible.
c. Select Software Provisioning action.
d. Select Add Source in the drop-down menu and click Define Action.
e. On the Software Provisioning Compliance Remediation page, select Add source to the beginning
of existing source list.
f. Click Browse Sources and select the repository URI where the Platform=Any and Section=Release
exist, and click OK.
The Platform and Section update with Any and Release respectively.
g. Click OK.
h. Click Next.
10. On the Collection filters page, select the Provisioning - Package Managers collection filter and click
Next.
11. On the Important page, review the information and click Finish to save your rule.
Provisioning Software on Managed Machines
VMware, Inc.
189