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
Action Description
To extract data from Linux and UNIX
shell scripts and return the data to
VCM, use the Sh parser.
The Sh parser extracts data such as environment variables,
exported variables, and umask settings from Linux and
UNIXshell scripts.
n Environmental Variables: The Sh parser extracts
settings of environmental variables in the form of
variable=value, and handles multiple variables on a
line (such as variable1=value1;
variable2=value2). This parser also handles
variables where the values are read from a file, and the
value is set to the content of the file. Read-only
variables are extracted and identified.
n Exported Variables: Includes multiple variables
exported at simultaneously.
n Umask settings for file permissions on files and
directories.
To handle tabular data, use the
tabular parser.
Tabular data usually consists of a grid of data. The
separator between fields can be any regular expression.
To handle well-formed XML files and
other files, use the 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.
To handle Windows configuration
files, use the INI parser.
The INI parser (key/value data) handles all types of
Windows-style configuration files, key/value files, and
some files that contain blocks of data. The key/value files
can use any delimiter, including white space. The delimiter
is a regular expression. Any value other than the delimiter
is allowed in the value and data blocks.
To handle tree-based data, use the
tree parser.
Tree-based data is key/value data in which path
information is contained in the key.
To break a file into tokens, use the
Tokenizer Parser
Breaks a file into a series of tokens of varying types.
Directives describe the types of tokens to collect and the
regular expressions required to collect those tokens.
Identification Expressions
The identification expression is a regular expression that identifies the file to be parsed. VCM matches the
file identified by a custom information collection filter against this expression. The parser directive obtains
the desired content of the file when the file name matches this expression.
For example, the identification expression for several custom information types appears as follows:
n builtin:profile identification expression is \/[.]?profile$
n builtin:krb5.conf identification expression is \/etc\/krb5\.conf$
n builtin:pamd identification expression is \/etc\/pam\.d\/.*$
n builtin:httpd_conf identification expression is apache[2]?\/.*\.conf$
Configuring Linux, UNIX, and Mac OS X Machines
VMware, Inc.
139