Landesk : Useful log files on Client and Core
On CLIENT : C:\Program Files\LANDesk\LDClient
|
FILE NAME |
COMMENTS |
|
INSTMSXML.log |
Appears to be checking to see if msxml3.dll is the correct version |
|
\data\GatherProducts.exe log |
Getting info for SLM. If you look in the exe log file you will see it has time stamps included with what it is doing. |
|
Remote control logs C:\Program Files\LANDesk\ManagementSuite\ |
Remote Control LOGS |
|
\LOCALSCH.log |
The local scheduler on the PC launches the other LANDesk functions, like software policy installs, Inventory, Patch vulnerability, etc.. This log shows the line parms executed for these functions |
|
ResidentAgent.log C:\Program Files\LANDesk\Shared Files |
Seems to be a more useful and the “real” install log file |
On SERVER: C:\Program Files\LANDesk\ManagementSuite
|
RAINSTALL.log |
Installation of client ??? Shows setting up the PC with certificates, may help in diagnosing CLIENT INSTALLS Seems to be dealing with the install of lclxsvc.dll – referred to as an Extension library; having to do with the CBA-Common base agent..? |
|
\log\{log files} |
TASK progress. Not sure what these files are used for.. they ARE task related |
|
GLOBAL SCHEDULER LOG? Appears to be three |
|
|
Application policy management.. shows behavior of POLICIES? During deployment? |
|
|
\log\{log files} |
TASK progress. Not sure what these files are used for.. they ARE task related |
|
Xxx is the task ID which is the “job” – this example is flowcal. You can see each PC in here and the execution of the task (sdclient) |
|
|
GTHOU-APLND02P-task-776.pmf.approved.xml |
Appears to be a task *target log* of some sort, in this case 776 is winzip. Also… thes appear to be a “daughter file” from \landesk\files. Perhaps landesk needed to change it into an xml file |
|
Non-eventful |
|
|
Logs a routine performed at 11pm.. Goes to (https://patch.landesk.com) and d/loads patches |
|
|
You can see the STATUS CODE of the task being set |
|
|
Resolves (landesk?) queries to tasks.. matches up the targets in the query? |
|
|
Shows Landesk resolving ldaps object to task |
|
|
|
|
|
“Landesk Policy Server |
Is a log of the APMservice running on the server. Shows problems communicating the TCS/APM packet with the client |
|
Shows pinging, then “performing remote execute” on an IP w/ hash number.. possible update from landesk server in utah? |
|
|
OSD related.. not updated daily |
|
|
Console Change? |
|
|
Database tasks |
|
|
Landesk.managementsuite.licensing.activationservice.exe.log |
|
|
Landesk.managementsuite.licensing.usageservice.exe.log |
|
|
SchedQry.exe.log |
Inspect for Queries not resolving. Performing global scheduler synchronization as needed.? |
Other log files:
|
Directory |
logs |
|
\Program Files\LANDesk\ManagementSuite\Install Only Files |
SetNTFSPermissions.log Launchapp.log |
|
\Program Files\LANDesk\ManagementSuite\ldlogon |
Rainstall.log |
|
\Program Files\LANDesk\ManagementSuite\log |
Custjob logs (1 log file per Custjob task) LANDesk Management Suite Patch Install logs |
|
\Program Files\LANDesk\Shared Files |
serviceHost.log alert.log rainstall.log residentagent.log |
|
\Program Files\LANDesk\Shared Files\Keys |
Installkey.log Genkey.log \Windows Inst32.log AMS2INST.LOG |
|
\Windows\system32\inetsrv |
W3wp.exe.log |
|
\Windows\System32\LogFiles\W3SVC1 |
Various log files |
/image%2F0881799%2F20140610%2Fob_a8c7fe_logo2.jpg)
Commenter cet article