
This construction may be confusing. A user might intuitively create a conditional statement that describes
the abnormal condition they want to eliminate. As a result, they find that VCM returns a list of nearly all
their machines and flags them as non-compliant with the abnormal rule. In reality, nearly all these systems
might be compliant and VCM has merely performed exactly as requested.
The first step to troubleshooting VCM, therefore, is to first verify that the suspect behavior is a negative
behavior or one that is not within the normal operating parameters of VCM. The VCM Help file is the
perfect tool to use when trying to determine normal behavior. There is a Help button on almost every
screen of each VCM wizard as well as in the upper-right corner of the Portal. The Help buttons, on the
Portal or in a wizard, display context-sensitive help topics relevant to the area of VCM in which you are
currently working.
Validate that the message or behavior seen is not described in the online Help before assuming the
behavior is negative or undesirable.
Isolate the Behavior
The next step to take when troubleshooting an undesired behavior is to try to isolate it. This is done by
eliminating, one by one, all factors that may be contributing to the behavior until the bare minimum
number of factors are in play when the error occurs.
For example, if you encounter some problem on a single machine during a collection for 50 machines and
10 data types per machine, the first step would be to eliminate the 49 machines that did not exhibit the
same behavior, and run a collection for the same 10 data types against the single problem machine. You
can usually isolate which machine failed by viewing the details of the job in the Job History screen on the
Administration slider. If you witness the same behavior, you then eliminate data types (one or two at a
time) until you find the data type that is causing the behavior. Again, the job details on the Job History
screen (as seen below) may give you some indication as to which data types failed.
VCM Troubleshooting Guide
8 VMware, Inc.
Komentarze do niniejszej Instrukcji