Overview

When logging a support incident with ENGL it is often useful to attach a log file (or several log files) to help diagnose the issue you are experiencing.


Log files

Log files allow us to analyse what has happened or what might be happening with your build process. Log files should always be attached to the support ticket.

The table below shows which log files are required depending on the type of issue you are having.

IssueLog filesLog file location
An error has occurred during imagingzim.log/zimbin/zim.log within Imaging Environment RAM disk (Linux).
An error has occurred during the Build Processztoolkit.log
Support Zip 		c:\ztoolkit\ztoolkit.log
Created by Build Console
ZENworks registration has failedztoolkit.log
zac.log
zmd-messages.log 		c:\ztoolkit\ztoolkit.log
c:\ztoolkit\zac.log
%ZENWORKS_HOME%\Logs\LocalStore\zmd-messages.log
Active Directory join has failedztoolkit.log
netsetup.log 		c:\ztoolkit\ztoolkit.log
%systemroot%\Debug\netsetup.log
AutoAdminLogon has reported an error during the build processztoolkit.log
Novell Client Configuration files		c:\ztoolkit\ztoolkit.log
ENGL TID-2010013: Troubleshooting AutoAdminLogon
Windows activation or licensing issuesztoolkit.log
slmgr.log 		c:\ztoolkit\ztoolkit.log
c:\ztoolkit\slmgr.log

More information


zim.log

The zim.log file, when enabled, records everything that Zim does in the imaging session. Logging is not enabled by default in the ZENworks imaging Environment (PXE boot to Linux). When logging is enabled the zim.log file is saved in the RAM disk and is lost when the machine reboots. This log is automatically captured if Deployment Monitor is being used. For steps to enable and extract the zim.log file without Deployment Monitor, please review ENGL TID-2006018: Extracting the zim.log.

If there are issues with your zim.cfg file it may be useful to upload the following files from your tftp/zimfiles folder:

  • zim.cfg
  • projects.ini
  • images.ini
  • sites.ini (if used)


ztoolkit.log

The ztoolkit.log file, when enabled, records information about what is done to the machine as it is deployed. The log file is enabled by default in a new project and can be configured by modifying a projects expert view settings as follows:

Expert view > Customisation > Debug

Debug 
Level3

The log file is created in C:\Ztoolkit and is called ztoolkit.log. This folder is removed at the end of the Build Process by default.  This log is automatically captured if Deployment Monitor is being used. To gain access to the log file without Deployment Monitor, the project can be modified to either keep the C:\Ztoolkit folder or to copy the log file to an alternative location.

To retain the c:\ztoolkit folder post build:
  1. Launch Build Console

  2. Open project file

  3. Select Expert View

  4. Select Customisation - Post-build

  5. Change

    Cleanup 
    Remove Build FilesTrue 

    to

    Cleanup 
    Remove Build FilesFalse


  6. Save changes to the project

  7. Recreate the ztoolkit image and copy to imaging server for testing.

The C:\Ztoolkit folder will no longer be removed post-build. The C:\Ztoolkit\ztoolkit.log file is now available for attachment to the incident.

To copy the c:\ztoolkit\ztoolkit.log file to a different location after phases 2, 3 and 4:

  1. Launch Build Console

  2. Open project file

  3. Select Expert View

  4. Select Customisation - Post-build - Copy Log file

  5. Change

    Copy Log File Value
    EnabledFalse
    Target Path

    to

    Copy Log File Value
    EnabledTrue
    Target Pathc:\%computername%.log


    The Target Path can be set to any location that is accessible during the build process. A network driver or share ( \\<server>\<share>\%computername%.log) is commonly used

  6. Save changes to the project

  7. Recreate the ztoolkit image and copy to imaging server for testing.

The C:\Ztoolkit\ztoolkit.log file will now be copied to the target path at the end of phases 2, 3 and 4. The log file can now be easily attached to the incident.

zac.log

The zac.log file records the output of the zac reg command used in phase 2 to register a machine against a ZENworks Zone. This log file can be found in the C:\Ztoolkit\ folder on a machine being built. If registration has reported an error then the ztoolkit folder will still exist on the machine however if the build has continued then the c:\ztoolkit\ folder may be deleted. Should the folder have been deleted then the following changes can be made to the project to ensure that for future testing the c:\ztoolkit folder is not removed.


To retain the c:\ztoolkit folder post build:

  1. Launch Build Console

  2. Open project file

  3. Select Expert View

  4. Select Customisation - Post-build

  5. Change

    Cleanup Value
    Remove Build FilesTrue 

    to

    Cleanup Value
    Remove Build FilesFalse


  6. Save changes to the project

  7. Recreate the ztoolkit image and copy to imaging server for testing.

The c:\ztoolkit folder will no longer be removed post-build. The c:\ztoolkit\zac.log file is now available for attachment to the support ticket.


Support.zip

This is a Zip archive of the current open project. It contains a copy of the project XML, project folder and custom files folder. To create this file open the appropriate project within Build Console then select Tools > Create Support Zip. When prompted browse for a suitable folder and enter a file name for the zip file. Once the file has been created attach it to the support ticket.   



netsetup.log

The Netsetup.log file provides information about the attempts to join domains and records any errors that might be preventing the join from being successful. The file is located in the %SystemRoot%\debug folder on a windows machine and can now be attached to the incident. 



Novell Client Configuration files

When troubleshooting Novell Client install or Autoadmin login issues it is useful to upload the Novell Client Configuration files. To identify the client folder in the file library, right click on the appropriate Novell Client entry then select Open folder in Windows Explorer then attach the files to the incident.

  • Novell Client 2 SP2 for Windows (or newer)
    • install.ini
    • ncpf.txt

For more information on troubleshooting AutoAdminLogin review this TID ENGL TID-2010013: Troubleshooting AutoAdminLogon


zmd-messages.log

The ZENworks Adaptive Agent logs all its information to the %zenworks_home%\logs\LocalStore\zmd-messages.log file. If there are any issues with ZENworks Registration, Application delivery or Policy configuration then it is useful to extract this log file from a machine along with the corresponding c:\ztoolkit\ztoolkit.log. We compare the timestamps on the two log files (ztoolkit.log and zmd-messages.log) to attempt to match what we see in the ztoolkit.log file and what the ZENworks Adaptive Agent reports so it is essential that the log files come from the same build/machine. Attach the files to the incident.  Running the command "zac zeninfo" will capture all of the ZENworks logs into one zip file, and is the best way to ensure that all necessary information is captured, in one operation.


slmgr.log

The slmgr.log file records the output of the Windows Software Licensing Management Tool (slmgr.vbs) that is used by Windows to manage licensing and activation.
This log file can be found in the c:\ztoolkit\ folder on a machine being built.
If the build has completed then the c:\ztoolkit\ folder may be deleted.
If this has occurred then the following changes can be made to the project to ensure that for testing the c:\ztoolkit folder is not removed:

To retain the c:\ztoolkit folder post build:

  1. Launch Build Console

  2. Open project file

  3. Select Expert View

  4. Select Customisation - Post-build

  5. Change

    Cleanup Value
    Remove Build FilesTrue 

    to

    Cleanup Value
    Remove Build FilesFalse


  6. Save changes to the project

  7. Recreate the ztoolkit image and copy to imaging server for testing.

The c:\ztoolkit folder will no longer be removed post-build. The c:\ztoolkit\slmgr.log file is now available for attachment to the incident.