5.3
Table Of Contents
- Copyright
- About This Book
- Preparing for Installation
- Installing VCM Using Installation Manager
- Upgrading VCM and Related Components
- Getting Started with VCM Components and Tools
- Getting Started with VCM
- Discover, License, and Install Windows Machines
- Verifying Available Domains
- Checking the Network Authority
- Assigning Network Authority Accounts
- Discovering Windows Machines
- Licensing Windows Machines
- Installing the VCM Windows Agent on your Windows Machines
- Performing an Initial Collection
- Exploring Windows Collection Results
- Getting Started Collecting Windows Custom Information
- Discover, License, and Install UNIX/Linux Machines
- Discover, License, and Install Mac OS X Machines
- Discover, License, and Collect Oracle Data from UNIX Machines
- Customize VCM for your Environment
- How to Set Up and Use VCM Auditing
- Discover, License, and Install Windows Machines
- Getting Started with VCM for Virtualization
- Virtual Environment Configuration
- ESX 2.5/3.x,vSphere 4, and ESXi Servers Collections
- vCenter Server Collections
- Configuring Agent Proxy Virtualization Collections
- Configuring Agent Proxy Machines
- Configuring ESX/vSphere Servers
- Configuring Web Services for ESX/vSphere Server Communication
- Performing an Initial Virtualization Collection
- Exploring Virtualization Collection Results
- Configuring vCenter Server Data Collections
- About the vSphere Client VCM Plug-in
- Further Reading
- Getting Started with VCM Remote
- Getting Started with VCM Patching
- Getting Started with Software Provisioning
- VMware vCenter Configuration Manager Package Studio
- Software Repository for Windows
- Package Manager for Windows
- Overview of Component Relationships
- Installing the Software Provisioning Components
- Using Package Studio to Create Software Packages and Publish to Repositories
- Using VCM Software Provisioning for Windows
- Related Software Provisioning Actions
- Further Reading
- Getting Started with VCM Management Extensions for Assets
- Getting Started with VCM Service Desk Integration
- Getting Started with VCM for Active Directory
- Getting Started with VCM for SMS
- Getting Started with Windows Server Update Services
- Accessing Additional Compliance Content
- Installing and Getting Started with VCM Tools
- Maintaining VCM After Installation
- Troubleshooting Problems with VCM
- Configuring a Collector as an Agent Proxy
- Index
Troubleshooting Problems with VCM
A
Troubleshooting Problems with VCM
This chapter provides important information that will help you troubleshoot issues that may occur during
the VCM software installation, upgrade, or use. This chapter describes resolving the following issues:
n
Missing Patch Assessment Results
n
Reports and Node Summaries Problems
n
Protected Storage Errors
n
Resetting the Require Secure Channel (SSL)
n
Report Parameter Error
Evaluating Missing UNIX Patch Assessment Results
Before you can install patches, VCM Patchingfor UNIXpatch assessments must complete successfully by
displaying the assessment results. If a UNIXpatch assessment does not return any results, the problem
may be due to one of the following reasons.
n
The assessment template may contain patch bulletins that do not match the selected machine type.
n
The selected patch may not match the machine architecture; you must select 32-bit patches for 32-bit
machines, and 64-bit patches for 64-bit machines.
n
If you have defined a custom filter for Patch Assessment, it may not be including any of the bulletins
that apply to the selected machine type. Certain filter attributes may not apply to bulletins across all
platforms. For example, Severity is not used by some platforms. If you have defined a filter based on
Severity, you would not include in your assessment any bulletins that do not have Severity set.
n
The bulletins may not be in the required location on the Agent machine, which could occur for several
reasons. Review the following list, and then check your UNIX Agent machine to confirm whether the
bulletins exist in the correct location. Consider updating your UNIX Agents to 5.3.
n
The Agent version and UNIX platform support for Patch Assessment may not match.
o
Agent versions prior to 5.0 do not support UNIX Patch Assessment.
o
Support for Patch Assessment was added for some UNIX platforms in 5.0, but the patch
assessment required manual distribution of bulletin information to the UNIX Agent
machine to perform the assessment.
o
Support for additional UNIX platforms was added in 5.1, along with the automated
distribution of bulletin information to Agent machines.
n
The process of distributing the bulletin information to UNIX Agent machines has failed.
VMware, Inc. 259