5.8
Table Of Contents
- VMware vRealize Configuration ManagerAdministration 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
- Using Linux and UNIX Custom Information Types
- File Types that VCM can Parse
- Parsers for Supported File Types
- Identification Expressions
- Parser Directives
- Parser Directives for Linux, UNIX, and Mac OS X
- Creating Custom Information Types for Linux and UNIX
- Custom Information Types for Linux, UNIX, and Mac OS X
- Add, Edit, or Clone Custom Information Types for Linux and UNIX
- UNIX Custom Information Data View in the Console
- Path Panel in the VCM Collection Filter
- 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
- Configuring Active Directory Environments
- Configuring Remote Machines
- Tracking Unmanaged Hardware and Software Asset Data
- Managing Changes with Service Desk Integration
- Index
Parser Directive
Type
Parser Directive Mandatory
Description
WFF Parser
The Well Formed Formulae
(WFF) parser handles well
formed formulae, such as XML,
but can be defined to handle
any well-structured document.
AELEMENT Name for the element that
wraps attributes.
ATTRRS Separates records in an
attribute value.
CDATARS Separates records in a CDATA
section.
CLOSEREGEX Regular expression that
recognizes a CLOSE.
DATARS Separates records in a DATA
section.
OPENREGEX Regular expression that
recognizes an OPEN.
TERMRS Regular expression that
separates terms within a
formula.
Creating Custom Information Types for Linux and UNIX
You can create custom information types (CITs) and filters so that VCM can collect data from
configuration files on Linux and UNIX platforms to monitor and enforce the compliance of those
platforms.
You determine which custom files to monitor for compliance, then you create your own CITs and
collection filters. VCM monitors the content of the custom files, and returns properties and values from
those files so that VCM can enforce compliance on them. You can add, edit, clone, and delete your own
CITs.
VCM provides built-in custom information types for standard files on Linux and UNIXmachines. For
example, VCM provides the builtin:profile custom information type for the /etc/profile file on
Linux and UNIXplatforms, which is a login file that Linux and UNIX platforms use to set up login and user
parameters for a user's shell when the user is logged on to the platform. You can use this custom
information type to ensure that /etc/profile is compliant on your Linux and UNIXmachines.
In the following procedure, you collect the configuration file from Linux and UNIX managed machines
before you create compliance rule so that you have collected the property names and values to create the
compliance rule.
Configuring Linux, UNIX, and Mac OS X Machines
VMware, Inc.
145