Log file locations by LANDesk component for 9.x

Version 3

    Log file locations by
    LANDesk component for 9.x

     

    Management Suite Installer

    When installer first runs, it generates a "todo" list, hard coding the paths.

    C:\ProgramData\LANDesk\ManagementSuite\Install\9.50\setup.xml

     

    C:\ProgramData\LANDesk\ManagementSuite\Install\9.50\Log\ConsoleConfiguration.msi.log

    C:\ProgramData\LANDesk\ManagementSuite\Install\9.50\Log\IIS7_Scripted_Config.log

    C:\ProgramData\LANDesk\ManagementSuite\Install\9.50\Log\IIS7_Scripted_Install.log

    C:\ProgramData\LANDesk\ManagementSuite\Install\9.50\Log\LANDesk.Install.LDMS_Date Time.log

    C:\ProgramData\LANDesk\ManagementSuite\Install\9.50\Log\LANDesk.Setup.LDMS95.msi.log

    C:\ProgramData\LANDesk\ManagementSuite\Install\9.50\Log\NETFX35_dism.log

    C:\ProgramData\LANDesk\ManagementSuite\Install\9.50\Log\ServerConfiguration.msi.log

    C:\ProgramData\LANDesk\ManagementSuite\Install\9.50\Log\WebSiteConfiguration.msi.log

     

     

     

    Agent

    http://community.landesk.com/support/docs/DOC-23482

    Agent Install
    Install Log - install information to wscfg32.xlg. Log is written to %TEMP% folder in Windows.
    (This log appears when WSCFG.exe, located on the core server in the ldlogon share, is run with the "/L" switch)

     

    Server Agent and Advance Agent

    \Program Files (x86)\LANDesk\Managementsuite\Ldlogon\AdvanceAgent\ [Agent Name].exe.log
    \Program Files (x86)\LANDesk\Managementsuite\Log\ scheduledtaskhandler_#.log (For Agent Deployment tasks)
    \Program Files (x86)\LANDesk\Managementsuite\Ldlog\ cab_#.log

    Client Agent and Advance Agent - http://community.landesk.com/support/docs/DOC-9828
    WINDOWS\TEMP\ AdvanceAgent.log
    Log file for advanceagent.msi install.

    Program Files (x86)\LANDesk\LDClient\AdvanceAgent.log
    Log file for LANDesk Advance Agent service, this will log the download of the EXE file. After the EXE file is downloaded successfully, this log file will be deleted. But if the EXE file is not downloaded successfully, the log file will be there.

    Alerting and Monitoring

    http://community.landesk.com/support/docs/DOC-10653

    Server Alerting
    \Program Files (x86)\LANDesk\ManagementSuite\log\ alertdetail.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ alertname2table.exe.Information.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\alertname2table.exe.Licensing.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\alertname2table.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\alertruleset2table.exe.Information.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\alertruleset2table.exe.Licensing.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\alertruleset2table.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ AlertService.log

    Client Alerting
    C:\Program Files (x86)\ LANDesk\shared files\alert.log
    C:\Program Files (x86)\LANDesk\LDClient\alertsync.log
    C:\Program Files (x86)\LANDesk\LDClient\lddetectsystem.log
    C:\Program Files (x86)\LANDesk\LDClient\createmonitorroot.log

     

    AMT/vPro

    http://community.landesk.com/support/docs/DOC-23304
    Server AMT

    \Windows\Temp\ AMTConfigDll.log
    \Users\<logged-in user>\Local Settings\Temp\ AMTConfigDll.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\AMTDiscService.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\AMTNotifyService.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\IpmiRedirectionService.log

    Client AMT
    C:\Program Files (x86)\LANDesk\LDClient\amtmon.Log

     

    Software Deployment

    Server Policy Software Deployment
    \Program Files (x86)\LANDesk\ManagementSuite\ log\apmservice.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\schedpkgupdate.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ scheduledtaskhandler_#.log

    C:\inetpub\logs\LogFiles\W3SVC1\u_exXXXXXX.log (NOTE: The location of the IIS logs can be changed in the properties of the Web Site)

     

     

    Client Policy Software Deployment
    C:\Program Files (x86)\LANDesk\LDClient\policy.cgi.log
    C:\Program Files (x86)\LANDesk\LDClient\policy.client.portal.log
    C:\Program Files (x86)\LANDesk\LDClient\policy.client.invoker.log
    C:\Program Files (x86)\LANDesk\LDClient\policy.sync.log

    Server Software Deployment
    \Program Files (x86)\LANDesk\ManagementSuite\log\ scheduledtaskhandler_#.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ landesk.scheduler.globalscheduler.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ landesk.scheduler.globalscheduler.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\landesk.scheduler.globalscheduler.skeleton.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\landesk.scheduler.globalscheduler.skeleton.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ MCC-[xxxxxxxxxxxxxxxxx].log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\MCS-[xxxxxxxxxxxxxxxxx].log
    \Program Files (x86)\LANDesk\Managementsuite\ log\PreferredServerConfig.exe.log
    \Program Files (x86)\LANDesk\Managementsuite\log\ raxfer.log

    Client Software Deployment
    C:\Program Files (x86)\LANDesk\LDClient\data\sdclient_task#.log
    C:\Program Files (x86)\LANDesk\LDClient\sdclient.log
    C:\Program Files (x86)\LANDesk\LDClient\tmcsvc.log
    C:\Program Files (x86)\LANDesk\LDClient\SDClientTask.[Core-Name].[task#].log
    C:\Program Files (x86)\LANDesk\LDClient\[MSI Name].log (created during installation of MSI packages)

    Server Scheduler Service – Queries and LDAP targeted tasks, Recurring scheduled jobs on the core
    \Program Files (x86)\LANDesk\ManagementSuite\log\ schedqry.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\schedsvc.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\schedsvc.log

    Local Scheduler tasks
    C:\Program Files (x86)\LANDesk\LDClient\localsch.log
    C:\Program Files (x86)\LANDesk\LDClient\LDSystemEventCapture.log

     

    Server Web Console and Component calls to LANDesk Core Web Services

    C:\inetpub\logs\LogFiles\W3SVC1\u_exXXXXXX.log (NOTE: The location of the IIS logs can be changed in the properties of the Web Site)

    C:\WINDOWS\system32\LogFiles\HTTPERR\ httperr#.log
    C:\WINDOWS\system32\inetsrv\ w3wp.exe.log

     

    Asset Lifecycle Manager

    http://community.landesk.com/support/docs/DOC-5564
    Service Management Logs
    \Program Files (x86)\LANDesk\Service Management\log\LANDesk.ServiceManagement.TaskEngine.exe.log
    \Program Files (x86)\LANDesk\Service Management\log\ServiceManagement.log
    \Program Files (x86)\LANDesk\Service Management\log\Synchronizer.log
    \Program Files (x86)\LANDesk\Service Management\log\Web.log
    \Program Files (x86)\LANDesk\Service Management\log\LaunchSchedule\[date/time stamp]_LaunchSchedule.log
      

    OS Deployment - Provisioning

    http://community.landesk.com/support/community/systems/osd

    Server Provisioning
    \Program Files (x86)\LANDesk\ManagementSuite\log\provisioning\ provisioning.log
    C:\WINDOWS\system32\LogFiles\W3SVC1\exXXXXX.log (NOTE: The location of the IIS logs can be changed in the properties of the Web Site)
    C:\inetpub\logs\LogFiles\W3SVC1\u_exXXXXXX.log (on Windows 2008 R2)

    Server OS Deployment
    \Program Files (x86)\LANDesk\ManagementSuite\log\custjob.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ corewebservices.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ CJ-OSD-[SCRIPT NAME].log

    C:\inetpub\logs\LogFiles\W3SVC1\u_exXXXXXX.log (NOTE: The location of the IIS logs can be changed in the properties of the Web Site)

    \Program Files (x86)\LANDesk\Managementsuite\log\ raxfer.log

    Client OS Deployment
    %WINDIR%\System32\Sysprep\Panther
    %WINDIR%\Panther\Setup.etl - Windows Setup performance events
    (wevtutil qe /lf c:\windows\panther\setup.etl – exports to log file)
    Unattend.xml - %WINDIR%\Panther\ and ???

     

    Core Activation

    \Program Files (x86)\LANDesk\ManagementSuite\ landesk.managementsuite.licensing.activatecore.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\ landesk.managementsuite.licensing.usageservice.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\ landesk.managementsuite.licensing.activationservice.exe.log

     

    Cloud Services

    Server Management Gateway
    \Program Files (x86)\LANDesk\ManagementSuite\ logBrokerService.log

    C:\inetpub\logs\LogFiles\W3SVC1\u_exXXXXXX.log (NOTE: The location of the IIS logs can be changed in the properties of the Web Site)

     

    Client Cloud Services Appliance - Gateway
    C:\Program Files (x86)\LANDesk\shared files\proxyhost.log
    C:\Program Files (x86)\LANDesk\LDClient\brokerconfig.log

     

    Console

    Server 32-bit Console
    \Program Files (x86)\LANDesk\ManagementSuite\ console.exe.log

     

    Patch Manager

    Server Security and Patch Manager
    \Program Files (x86)\LANDesk\ManagementSuite\ vaminer.exe.log

    C:\inetpub\logs\LogFiles\W3SVC1\u_exXXXXXX.log (NOTE: The location of the IIS logs can be changed in the properties of the Web Site)

    Client Security and Patch Manager
    C:\Users\All Users\Application Data\vulScan\vulscan.log
    C:\Users\All Users\Application Data\vulScan\vulscan.#.log
    The vulscan log will roll and create a vulscan.1.log, vulscan.2.log, etc)
    C:\Program Files (x86)\LANDesk\LDClient\vulscan.log
    C:\Users\All Users\Application Data\vulScan\softmon.log

     

    HIPS – Endpoint Security

    Client Endpoint Security
    Files within C:\Program Files (x86)\LANDesk\LDClient\HIPS:
    DCM.log (Device Control – Logs Device Information)
    DCMVolumes.log (Device Control – Logs Volume Information)
    ERROR.LOG (Shows Endpoint Security service errors)
    NetworkDetection.log (Shows Network Location Awareness information)
    ShadowCopy.log (Device Control – Shadow copy information)

    Files within C:\Users\All Users\Application Data\LDSec
    LDSECSETUP32-HIPS-debug.log (Debug level log for installation)
    LDSECSVC-DCM-debug.log (Debug level log for Device Control)
    LDSECSVC-HIPS-debug.log (Debug level log for HIPS)

    Files within C:\Users\All Users\Application Data\Vulscan
    Vulscan.log (logs Endpoint installation, settings changes, etc)

     

    Software License Monitoring (SLM)

    C:\Program Files (x86)\LANDesk\LDClient\data\gatherproducts.log
    C:\Program Files (x86)\LANDesk\LDClient\data\proddefs\*.xml

     

    Antivirus - Antispyware

    Server Antivirus and Spyware
    \Program Files (x86)\LANDesk\Managementsuite\Ldlogon\antivirus\cab\ cab.log
    \Program Files (x86)\LANDesk\Managementsuite\Ldlogon\antivirus\bases\ cab.log
    \Program Files (x86)\LANDesk\Managementsuite\Ldlogon\spyware\ vulscan.log

    Client Antivirus (LANDesk)
    C:\Program Files (x86)\LANDesk\LDClient\Antivirus\UpdateVirusDefinitions.log
    C:\Program Files (x86)\LANDesk\LDClient\Antivirus\UpdateVirusDefinitions.old
    C:\Users\All Users\Application Data\LANDeskAV\avservice.log
    C:\Users\All Users\Application Data\LANDeskAV\avservice_channel.log
    C:\Users\All Users\Application Data\LANDeskAV\AVScanShExt.log
    C:\Users\All Users\Application Data\LANDeskAV\LDAV.log
    C:\Users\All Users\Application Data\LANDeskAV\avservice_update.log

     

    Inventory

    Inventory Server
    \Program Files (x86)\LANDesk\ManagementSuite\log\ LDInv32.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ LDInv32.log
    Windows Application Event Viewer - Most LANDesk Inventory Server errors or exceptions are logged to the Application Log
    \Program Files (x86)\LANDesk\ManagementSuite\ log\LDInv32.exe[xxxx_xxxx].log
    (Note:  This is the rolling log and must be manually enabled in Configure | Services | Inventory |
    Advanced Settings | Rolling Log = 1)

    Inventory Scanner
    C:\Program Files (x86)\LANDesk\LDClient\ldiscn32.log
    C:\Program Files (x86)\LANDesk\LDClient\data\ldiscn32.log
    (This log appears when ldiscn32.exe is run with the "/debug" switch)
    C:\Program Files (x86)\LANDesk\LDClient\ldiscnupdate.log
    Add /o=c:\output.txt to Inventory Scan target string in start menu. – Scan log

     

    Rollup Core

    Rollup Core
    \Program Files (x86)\LANDesk\ManagementSuite\log\ Rollup_[LinkName].log
    NOTE:  Create the following dword value in the registry to log rollup tasks - HKLM\Software\LANDesk\ManagementSuite\Core\rollup log
    The DWORD "rollup log" must be lower case and the value must be set to 1.
    The log file will be called Rollup_LinkName.log and will be located in the folder where dbrollup.exe was run from.

    Executive Dashboard 
     
    \Program Files (x86)\LANDesk\Managementsuite\ log\dashboardreportservice.exe.log

     

    Remote Control

    Remote Control
    \Program Files (x86)\LANDesk\ManagementSuite\ log\console.exe.log
    \Program Files (x86)\LANDesk\ManagementSuite\log\ UserValidatorErrLog.txt
    \Program Files (x86)\LANDesk\ManagementSuite\ log\LANDeskManagementSuite.Information.log
    Connection messages.txt – This is the text in the Remote Control Viewer interface

    C:\inetpub\logs\LogFiles\W3SVC1\u_exXXXXXX.log (NOTE: The location of the IIS logs can be changed in the properties of the Web Site)

    C:\WINDOWS\system32\LogFiles\HTTPERR\ httperr#.log
    C:\WINDOWS\system32\inetsrv\ w3wp.exe.log

     

    Apple - Macintosh

    Macintosh
    \library\application support\LANDesk

     

    Asset Lifecycle Manager

    http://community.landesk.com/support/docs/DOC-5564

    Service Management Logs

    \Program Files\LANDesk\Service Management\log\LANDesk.ServiceManagement.TaskEngine.exe.log

    \Program Files\LANDesk\Service Management\log\ServiceManagement.log

    \Program Files\LANDesk\Service Management\log\Synchronizer.log

    \Program Files\LANDesk\Service Management\log\Web.log

    \Program Files\LANDesk\Service Management\log\LaunchSchedule\[date/time stamp]_LaunchSchedule.log

     

    Avocent Management Platform Logs

    \Program Files\Avocent\Amp\logs\amp-esb.log

    \Program Files\Avocent\Amp\logs\global.log

    \Program Files\Avocent\Amp\logs\servicemix.log

     

    You will normally only need to look at the Avocent Management Platform Logs if you have a problem with activation/licensing or with AMP synchronization.The Service Management logs will generally by more useful.

     

    The logging can be increased for any of the Service Management logs by editing the corresponding log4net.xml file. These are the log4net.xml files:

     

    \Program Files\LANDesk\Service Management\LANDesk.ServiceManagement.TaskEngine.exe_log4net.xml

    \Program Files\LANDesk\Service Management\ServiceManagement_log4net.xml

    \Program Files\LANDesk\Service Management\Synchronizer_log4net.xml

    \Program Files\LANDesk\Service Management\Web\ServiceManagement_log4net.xml

    \Program Files\LANDesk\Service Management\LaunchSchedule_log4net.xml

     

    Edit the log4net.xml files, setting debug to true and setting the logging level appropriately. Be sure to turn off the logging when done:

     

    debug="true"

     

    threshold value="DEBUG"

     

    The threshold can be set to any of the following values: DEBUG, INFO, WARN, ERROR and FATAL