ZIMGLOG.XML is a chronological record of all the imaging requests that have been received by the imaging server since it was installed and first started, including requests merely to log information about imaging operations serviced elsewhere. For each imaging request, the imaging server logs information such as the source, type, date/time, and results of the request.
ZIMGLOG.XML is created on a NetWare server in SYS:\SYSTEM or on a Windows server at the root of the drive where NDS is installed (such as C:\).
Viewing the Log File
This is an XML format file. The oldest imaging request is logged at the top of the file and the most recent at the bottom. The file continues to grow unless you trim it manually (using a text editor) or delete it. It isn't cleared if you restart the imaging server.
Each imaging operation is entered in the log as a group of lines. For example, the log file shown below has two entries: one describing a successful upload operation and another describing a failed download operation. (An upload is the taking of a client image and storing it on the imaging server or other available (local) medium. A download is the retrieval of a client image from the imaging server or local medium and laying it down on the client.)
<CN=CV7PB00:C0:4F:DC:2A:B5.O=sales> <Tree>XYZ</Tree> <Status>Failure</Status> <ErrorMessage>Unable to find an image to download</ErrorMessage> <Operation>Download</Operation> <Timestamp>Thur Nov 22 13:13:17 2001 </Timestamp> </CN=CV7PB00:C0:4F:DC:2A:B5.O=sales>
</ZENImageLog>
The table below describes the various XML elements that comprise the log entries shown above. Each element has an opening and closing tag, such as <tree> and </tree>. The outermost element contains all the other elements in the entry.
XML Element
Specifies
Outermost_Container
The distinguished NDS name of the workstation that requested the imaging operation. This name is read by the imaging engine from the workstation's image-safe data. If the workstation name isn't found (for example, if the workstation hasn't been registered as an object in NDS), the name of the imaging server that serviced the request is given instead (for example, XYZ_SERVER).
Tree
The NDS tree containing the workstation or server specified in the Outermost_Container element.
Status
Whether the requested imaging operation succeeded or failed.
ErrorMessage
The reason why the requested imaging operation failed, if applicable.
Operation
Whether the requested imaging operation was an upload or download attempt. An upload is the taking of a client image and storing it on the imaging server or other available (local) medium. A download is the retrieval of a client image from the imaging server or local medium and laying it down on the client.
NOTE: Occasionally, you might see an entry in the log that omits the Operation element. Such an entry is typically a follow-up to the previous operation. For example, you might see an entry indicating that a download operation was successful, but the next entry (time-stamped a few seconds later and specifying no operation) might indicate that the imaging server failed to get image-safe data from NDS. In this case you could assume that the client that just received the download didn't have its own image-safe data, and so the imaging server was trying to get that data from NDS to apply it to the client.
ImageType
Whether the image that was created or retrieved is a base image or an add-on image. With a base image, all existing partitions and data are removed before the image is laid down. With an add-on image, the existing partitions are left intact and are merely augmented with additional data.
ImagePath
The full path and filename of the image that was created, retrieved, or requested.
Timestamp
The time when the results of the requested imaging operation were logged by the imaging server, including the week day, month, date, 24-hour time (including seconds), and year.
