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
If the change protocol request is from DCOM to HTTP, the simple installer component receives a request
to install the ComSocketServiceListener.
It the change protocol request was from HTTP to DCOM, the simple installer receives a request to remove
the ComSocketServiceListener.
The simple installer does not modify the contents of the installation infrastructure. The simple installer job
is only used to initially deploy the infrastructure using the Registration service as a bootstrap loader.
Beacuae the simple installer job cannot take action on the information it receives, it delegates the work to
the Install Module Installer step.
Store Installation Data in the Database
The store installation data in the database process updates the list of modules in the database.
Install Module Installer
The install module installer action reconciles the information regarding what infrastructure modules are
installed, whether to install or remove the ComSocketServiceListener, and determine the actions to
run.
If you are switching from DCOMto HTTP and the ComSocketServiceListener should be installed, the
install module installer creates a request and sends the work of installing this module to the Registration
Service.
If you are switching from HTTP to DCOM and the ComSocketServiceListener should be removed,
the module installer creates a request and sends the work of uninstalling this module to the Registration
Service.
Fully Release the Synchronization Lock On the Target Machine
The fully release the synchronization lock action clears the runtime Agent lock. Clearing the Agent lock
allows the VCM Agent to inspect the target Windows machine.
1. A connection is made to the module installer.
2. Unlock is called.
Submit Request to Agent
The submit request to Agent action is the first VCM Agent inspection on the Windows machine.
After installing the Agent, a machine environment inspection is performed.
Check If Request Is Complete
The check if request is complete action verifies that the Collector successfully collected from the VCM
Agent on the Windows machine.
The Collector checks to determine if the Windows machine environment collection from the Agent is
complete.
Transfer Request Results
The transfer request results action sends the results of the inspection on the Windows machine to the
Collector as part of the change communication protocol process.
After the Agent completes the machine environment inspection on the Windows machine, the results are
sent back to the Collector.
VCM Troubleshooting Guide
56
VMware, Inc.