VMware VCM 5.3 Guia de Resolução de Problemas descarregar pdf (Página 32)

I am uncertain if the package requires a reboot to install or I only want the

installation to reboot sometimes

Conditional reboots are not supported. You must either require a reboot or not. Whether or not an

installation requires a reboot depends on running applications, state of the machines, the operating

system, and other criteria. If you are uncertain if a reboot is required, but you do require a functioning

system at the end of the installation or removal process, you should require a reboot.

Gathering Software Provisioning Logs on the Collector

Turn on the AreResultsSaved to view the following files from collections. See "ARS Files" on page 21 for

instructions for turning on the logs.

Provider.log: Provides information on what the provider did, how it interacted with Package Manager

(wasp.exe), and any problems encountered when formatting the results. The AgentBridge also writes

to this log, recording any problems formulating provider instructions or transforming CDIF into

element-normal xml.

CDIF files: Provides the raw results written by the various providers. These files are useful in

identifying special characters that are preventing the transformation element-normal xml.

RequestInterop.xml: Provides a request document generated by the AgentBridge, which is used to

invoke the providers. An error in the provider log will usually tell you which field you should evaluate.

Python output from Stdout: Provides python output for both collections and actions. Stedout includes

all provider/AgentBridge collection results and wasp output in an xml format.

Python output from Stderr: Provides python output for both collections and actions. Stderr includes

any result determined to be an error condition.

Gathering Software Provisioning Logs on the Agent

Modify the logging configuration file on the Agent.

1. Locate Logging.conf. The default location is <Agent path>\Installers\Providers.

2. Make a copy of Logging.conf so you can later restore the file.

3. Open the file with a text editor, such as Notepad.

4. Locate the section labeled [handler_fileHandler].

5. Change the args setting in this area to the directory to which you want to write the logs. For example,

args=('c:\tmp\provider.log', 'a').

6. Run the problematic action from the Collector.

7. Restore the Logging.conf file to the previous state.

8. Review the log. It contains all the output from the pre-collection, the action, and the post-collection.

Turn on the Info logging for the Agent, allowing you to see how python is invoked in the Debut Event

Log.

1. In VCM, select Administration | Settings | Settings | Windows | Agent - General. The Agent

General Settings data grid appears.

2. Select Type of information that should be logged, and then click Edit Settings. The Edit Settings

page of the General Settings wizard appears.

3. Select the following options: Exception, Error, and Info.

VCM Troubleshooting Guide

32 VMware, Inc.

1 2 ... 27 28 29 30 31 32 33 34 35 36 37 ... 67 68

Sem comentários

VMware VCM 5.3 Guia de Resolução de Problemas Página 32