5.8
Table Of Contents
- VMware vRealize Configuration Manager Troubleshooting Guide
- Contents
- About This Book
- Troubleshooting Overview
- Types of Problems
- Gathering Diagnostic Information
- What to Send to VMware Technical Support
- Capture a Desktop Image
- Capture a Window Image
- Set the Debug Log to Store all Message Types
- Extract the Debug Log
- Extract SQL Server Logs
- Collect IIS Logs
- Collect ARS Files
- Collect the UNIX Syslog Messages
- Collect Import/Export Tool Logs
- Extract Windows Event Logs
- Extract Windows System Information
- Collect UNIX ETL Logs
- Collect VCM Installation Logs
- Enable VCM Patching Logging
- Collect VCM Patching Logs
- Collect Agent Logging
- Troubleshooting Problems with VCM
- Patch Content Does Not Download for Red Hat and SUSE Machines
- Signed Patch Content Cannot Be Validated
- Mismatched Security Setting for AIX Patch Staging with NFS
- UNIX Patch Deployment Fails
- UNIX Patch Assessment Returns No Results
- Patch Deployment Jobs Might Time Out
- UNIX Bulletins Missing from the Required Location
- Report and Node Summary Errors
- Report Parameter Errors
- Protected Storage Errors
- SSL Becomes Disabled
- Troubleshooting the vSphere Client VCM Plug-In
- vSphere Client VCM Plug-In Is Not Enabled
- Cannot Register the vSphere Client VCM Plug-In
- Invalid Certificate on a vSphere Client
- Collector Not Running
- HTTPS/SSL Is Not Configured on the Collector
- Collection Unsuccessful
- Machines Not Listed in the Collect Available List
- Machines Not Listed in the Available List for Any Action
- ESX Servers Are Not Displayed
- VCM Windows Agent
- Windows Agent Installation Environment
- Windows Agent Installation Process
- Detect Previous Install
- Validate Installation Environment
- Interrogate Target Environment
- Resolve Uninstall Dependencies
- Uninstall Module
- Uninstall Module Installer
- Install Simple Installer
- Install Module Installer
- Resolve All Versions of Modules Based on Highest Version Number
- Install Module
- Fully Release the Synchronization Lock on the Target Machine
- Submit Request to Agent
- Check If Request Is Complete
- Transfer Request Results
- Acknowledge Successful Data Transfer
- Prepare Request Results for Insert
- Insert Data Into Database
- Transform Inserted Data
- Cleanup Machine Data
- Partially Release the Synchronization Lock on the Target Machine
- Cleanup Request Data
- Windows Agent Uninstallation Process
- Detect Previous Install
- Validate Installation Environment
- Interrogate Target Environment
- Resolve Uninstall Dependencies
- Uninstall Module
- Uninstall Module Installer
- Fully Release the Synchronization Lock on the Target Machine
- Partially Release the Synchronization Lock on the Target Machine
- Cleanup Request Data
- Windows Agent Upgrade Process
- Windows Agent Manual Installation Process
- Windows Agent Communication Protocols
- Communication Protocol Change Process
- Detect Previous Install
- Uninstall Agent
- Uninstall Package Installer
- Uninstall Basic Installer
- Validate Installation Environment
- Install Simple Installer
- Store Installation Data in the Database
- Install Module Installer
- Fully Release the Synchronization Lock On the Target Machine
- Submit Request to Agent
- Check If Request Is Complete
- Transfer Request Results
- Acknowledge Successful Data Transfer
- Prepare Request Results For Insert
- Insert Data Into Database
- Transform Inserted Data
- Cleanup Machine Data
- Partially Release the Synchronization Lock on the Target Machine
- Cleanup Request Data
- Debug Window Agent Installations
- VCM UNIX Agent
- UNIX Agent Directory Structure After Installation
- /opt/CMAgent
- /opt/CMAgent/Agent
- /opt/CMAgent/CFC
- /opt/CMAgent/data
- /opt/CMAgent/data/db
- /opt/CMAgent/data/db/DtmDB/RDM
- /opt/CMAgent/data/db/PDS
- /opt/CMAgent/data/db/SM/RDM
- /opt/CMAgent/ECMu
- /opt/CMAgent/ECMu/x.x/bin
- /opt/CMAgent/ECMu/x.x/scripts
- /opt/CMAgent/install
- /opt/CMAgent/Installer
- /opt/CMAgent/ThirdParty
- /opt/CMAgent/ThirdParty/x.x/PatchAssessment
- /opt/CMAgent/uninstall
- Directories Created During an Inspection
- Directory of Executed Scripts and Results
- Collector Certificates
- Patch Assessment
- Exploratory UNIX Agent Troubleshooting
- UNIX Agent Directory Structure After Installation
- Index
Acknowledge Successful Data Transfer
The acknowledge successful data transfer action is a record of the data from the VCM Agent inspection on
the Windows machine during the change communication protocol process.
The Collector records the receipt of the data from the Windows machine environment inspection.
Prepare Request Results For Insert
The prepare request results for insert action prepares the data from the Windows machine inspection for
insertion into the VCM database during the change communication protocol process.
A bulk insert of the machine environment inspection data is prepared for insertion in the VCM database.
Insert Data Into Database
The insert data into database action adds the data collected from the Windows machine by the VCM Agent
to the database as a step in the change communication protocol process.
The data from the machine environment inspection is inserted in the VCM database.
Transform Inserted Data
The transform inserted data action takes data collected from the Windows machine by the VCM Agent
during the change communication protocol process and transforms it from the temp tables to the proper
database format for the VCM database.
The inserted machine environment data is transformed in the database from temp tables and the meta
data is updated
Cleanup Machine Data
The cleanup machine data action cleans up the files on the target Windows machine after changing the
communication protocol.
The data on the target Windows machine is cleaned up.
Partially Release the Synchronization Lock on the Target Machine
The partial release of the synchronization lock on the target Windows machine action is a finalization job
that runs even if any of the previous steps fail during the change communication protocol process.
The goal of this action is to clear out the Agent runtime lock so that if another installation of the Agent is
attempted, it succeeds.
This step does not clear the action type in the lock. Because this condition is a result of an invalid
installation, this action is a partial release that renders the Agent incapable of doing useful work.
The Agent is available for collections only if the Fully release the synchronization lock on the Agent action
runs successfully.
Cleanup Request Data
The cleanup request data action removes unneeded and transformed data on the Collector and the final
action in the change communication protocol process.
The VCM Collector cleans up the inserted and transformed data, the request is removed, and the state of
the request is complete.
VCM Windows Agent
VMware, Inc.
57