How To: Enable XTrace Diagnostic Logging for the LANDESK Core and Clients

Version 41

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6Endpoint Manager 2016.x

    XTrace for LDMS 9.6 and newer

     

    As of LDMS 9.6 all that is needed to enable XTrace verbose logging on client machines it to modify the following registry keys on the target client machine:

     

    64-bit:

    ||HKLM|SOFTWARE|Wow6432Node|landesk|managementsuite|LogOptions

           

    32-bit:

    ||HKLM|SOFTWARE|landesk|managementsuite|LogOptions

           

     

    To enable the logging options change their value to "1", or back to "0" to disable the verbose logging. The keys you can modify to enable verbose logging are:

    • logInfo
    • logType
    • logVerbose
    • logXTrace

     

    Once the logging options are enabled the existing logs for the various components will simply become more verbose instead of a new logs being generated. You will still gather the same logs you would have before.

     

     

    XTrace for LDMS 9.5 and older

     

    XTrace functionality is in the registry only.

     

    To activate Xtrace manually create any or all of the following registry entries in the following location:

    32Bit OS

    [HKEY_LOCAL_MACHINE\\SOFTWARE\\Intel\\LANDesk\\XTrace]

         

    64Bit OS

    [HKEY_LOCAL_MACHINE\\SOFTWARE\\Wow6432Node\\Intel\\LANDesk\\XTrace]

         

     

    Note: The registry entries should be a DWORD value with a "Value data" of 1

     

    An executable that can automatically set these registry key values is attached here:

     

      LDDebugLogEnabler.zip

     

    Note: The executable is not supported by LANDESK but is written independently by Jared Barneck.

     

    Application NameValue
    amslib.dllamslib
    apmapi.dllapmapi
    ampservice.exeapmservice
    cbaxfr.dllcbaxfr
    custjob.execustjob
    iao.exeiao
    lddwnld.dlllddwnld
    ldinv32.exeldinv32
    localsch.exelocalsch
    ltapi.dllltapi
    msgsys.dllmsgsys_dll
    msgsys.exemsgsys_exe
    netmap.ocxnetmap
    nts.dllnts
    ntsu2t.dllntsu2t
    pds.dllpsd
    qipclnt.exeqipclnt
    qipsrvr.exeqipsrvr
    schedsvc.exeschedsvc
    sdclient.exesdclient
    sdiskhk.exesdisthk
    sdmakini.dllsdmakini
    sdstinst.dllsdstinst
    tmcclnt.dlltmcclnt
    tmcsrvr.dlltmcsrvr
    tmcsvc.exetmcsvcexe
    wcustjob.exewcustjob
    wscfg32.exewscfg32
    xfr.exexfr

     

    The name of the XTrace log is the value name with a .XLG extension. This log file will show up in the same directory as the application that is being traced.

     

    Note: To enable Xtrace for LANDESK Provisioning, the following method can be used:

     

    1. Modify the Provisioning template
    2. Add a Wait action as the first action in the OS Deployment section.  (5 to 10 minutes should be enough to make the changes to the registry)
    3. Remote control the client and make the appropriate registry changes to turn on Xtrace.
    4. After the template has finished, collect the XTRACE logs you have turned on.  These will end with a .XLG extension.