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
To troubleshoot this process, review the job history, identify the step that failed, and determine what
might be impeding the removal of the Agent.
Detect Previous Install
The detect previous install action evaluates the Windows machine from which you are removing the VCM
Agent to determine whether a version of the Agent is installed that must be uninstalled.
The detect previous install action determines if a previous Agent is present by attempting to connect to the
Agent installation DCOM components, the Basic and Agent Installers. If a connection is made to either of
these components, the detect previous install action sets a state member that the Validate Installation
Environment, Interrogate Target Environment, and Resolve Uninstall Dependencies actions use to
determine if they should run.
These actions remove the previous Agents and are included in all types of install and uninstall requests.
Validate Installation Environment
The validate installation environment action ensures that the target Windows machine is available so that
the Collector can uninstall the VCM Agent.
1. If the validate job can contact the Module Installer, it calls methods on that component to obtain all the
installation manifests on the target. It also checks the registry for conditions that might prevent the
installation.
This job fails if the following conditions are satisfied:
n The Agent is locked. The HKEY_LOCAL_
MACHINE\SOFTWARE\Configuresoft\ECM\4.0\Agent\IsLocked, for 32-bit Windows servers,
or HKEY_LOCAL_
MACHINE\SOFTWARE\Wow6432Node\Configuresoft\ECM\4.0\Agent\IsLocked, for 64-bit
Windows servers, the registry entry is evaluated by this job to determine if the Agent is locked. If
this key exists and has a value other than 0, then the Agent is locked.
The installation infrastructure cannot remove or modify this value.
n The Agent is a Collector. The HKEY_LOCAL_
MACHINE\SOFTWARE\Configuresoft\ECM\4.0\Installer\CDInstallor or HKEY_LOCAL_
MACHINE\SOFTWARE\Wow6432Node\Configuresoft\ECM\4.0\Installer\CDInstall
registry entry is evaluated by this job to determine if the Agent is on a Collector machine. If this
key exists and has a value of 2, then the target Windows machine is identified as a Collector
machine.
The installation infrastructure cannot remove or modify this value.
2. If the validate job cannot communicate with the installation infrastructure, it flags the installation as
valid and the request continues.
3. If an error is generated by an attempt to communicate with the installation infrastructure, the
validation fails, as does the installation process, usually with an error that mandates that an uninstall
action must occur before installing. An error is any result other than Install required or Success.
4. If the validation job can communicate with the Module installer, it gathers all the module information
available from the various installation manifests and stores this information as a state variable so that
other installation jobs can use the information to determine what was installed. The validation job does
this in the RecordModuleInstallerVersion method and stores the module names and versions in
the install_module state parameter . The module installer job uses this parameter to determine
which parts of the installation infrastructure must to be installed.
VCM Windows Agent
VMware, Inc.
49