How do you enable logging in Deployment Server?
It is not necessary to enable all the logs listed below for every issue reported to Deployment Server support specialists. Gather the logs (noted by numbers 1 – 11) below as appropriate. A few 6.x examples are given below:
Aclient / Axengine Communication: Gather logs 5, 6, and 7
Bootworks / Axengine Communication: Gather logs 5, 6, and 9
DSINFO: This utility can be useful to gather all server side logs that are enabled PLUS environment information.
This utility is used to gather information about server and client computers. This is a Microsoft Utility.
Click on Start > Run and then type in MSINFO32.
Once open, click on Action and then select Save as System Information File. Make sure it is on the top icon for Windows 2000 systems.
A file called Trace.log is created and will apply to 6.x versions of DS.
DS 6.x also has a utility called DBinstaller.exe that generates a log if the SQL scripts fails during the install.
Enabled by default, a log called RD******.LOG is generated when errors occur during regular RDeploy.exe operations.
The last six characters after RD are the last characters of the clients computer’s MAC address. The logs are stored in the .\deployment server\rdeploy\<appropriate subdirectory>.
These logs are used mainly to troubleshoot the PXE services when the services fail to start, etc.
1) From the Deployment Server console, choose PXE Configuration from the Tools pull-down menu.
2) Select the Data Logs tab.
3) Enable the desired PXE log files and set the error level and log file destination.
4) Click the Save button at the bottom.
Note: Even though some PXE logging may be turned on, log files are not always generated. The PXE logs do not have a size limit and may grow very large; therefore it is advised to make sure that the PXE logging is disabled after use.
To enable engine (axengine.exe) logging in Deployment Server:
The log file can be found in the eXpress share under the name axengine.log.
Enabling these logs allows a comparison of the server-side AClient logs to the client-side AClient logs.
This will create a log file for each client in the C:\Program Files\Altiris\eXpress\Deployment Server\temp\msgs\ directory. The log files are named according to the computer ID, which can be found by right-clicking on the computer in the DS Console and then selecting Properties > General.
Enable this log to troubleshoot communication issues with the Axengine.exe.
Take note of the file name for the log file. The default location is C:\Program Files\Altiris\AClient\AClient.log.
A log called bwinst.log is generated at the root of the target drive if the installation fails.
Enable Bootworks logging to troubleshoot drive mapping issues, copying of configuration files, etc. when imaging and doing any jobs at the DOS level.
Edit AUTOEXEC.BAT in either the Embedded Bootworks Partition or the Bootworks Boot Disk.
Find the statement that says:
REM set DEBUG=-logC:\bootwork.log.bat
and take the REM statement out of this line, so it looks like this:
It is also possible to get an individual bootwork log file for each system by using the following command line arguement:
set DEBUG=-logpath<directory> (e.g. set DEBUG=logpathf:)
The logs that are created will be named according to the MAC address of the machine.
If using a Bootworks Boot Disk then change the path to be A:\bootwork.log. If the path is left as C:\bootwork.log, then no log file will be generated unless the C:\ on the computer is recognized at the DOS level (which means it must be formatted in fat16 format which is not common).
If PXE is being used, go into the PXE Configuration Utility. Select the PXE boot being used, such as Managed PC, Initial Deployment, etc. and then click Make Boot Files. From that point modify the existing PXE boot configuration or create a new configuration.
Edit the autoexec.bat to change:
REM set DEBUG=-logC:\bootwork.log
to look like:
Note that the log file path has been changed to f:\ because the memory space that PXE boots from is lost after the PXE boot is done; this setting will put the Bootworks log onto the network share point.
Also note if there are multiple clients booting PXE at the same time, all clients will be attempting to modify the same bootwork.log file and so the entries will not be unique.
An RInstall.log file may be generated if an error occurs.
RapidInstall can be forced to log by running the RIP package with a VB:4 switch. The log file will show up under the %temp%\altiris\rinstall directory.
Sometimes it is necessary to use the ce.log and an.log files to troubleshoot Deployment Solution’s integration within Notification Server. Consult the appropriate Notification Server troubleshooting documents for additional information.