Question

How to enable Trace level logging for Network Discovery 7.x

Answer

There are a few options for logging, including outputting additional logs to the Altiris Logs, or creating additional log files.  All of the following entries should be created as STRING values in the registry.

The following value may be set in the key "HKLM\Software\Altiris\DiscoveryTasks":

LogDebug
If this value is set to 1, additional debug messages are sent to the Altiris Log by network discovery tasks. This value is optional; if omitted, 0 is assumed. For example, if set, periodic progress messages (percent done) are sent to the Altiris Log.

The following values may be set in the key "HKLM\Software\Altiris\DiscoveryTasks\Engine Log":

LogWanted
Determines whether or not log files are generated. This value provides an easy way to disable log files without deleting the "Engine Log" registry key (or having to rename it). This value is required for logging; it should be 1 to enable logging, or 0 to disable it.

LogLevel
Determines which types of messages get logged. Can be set to "Critical", "Error", "Warn", or "Inform". In this list, each option includes the options that precede it (e.g. "Warn" includes Critical and Error level logs, but not Inform level). This value is optional; if omitted, "Error" is used.

LogFilePath
This value provides the folder in which log files will be created, and also provides a template for the log file names. The value up to the final backslash is the destination folder. The remaining value is the template for the filename; the task instance GUID is inserted just before the last period (dot) in that template name, with a period preceding it. This value is optional; if omitted, "C:\DiscoveryLogs\DiscLog.txt" is used. The specified folder must exist for the logs to be created.

Restart SMP services.

A new log file is created for each task instance, so enable logging only as needed for troubleshooting.