About Task Status Reporting

Version 18

    Verified Product Versions

    Endpoint Manager 9.6Endpoint Manager 2016.xEndpoint Manager 2017.x

    The purpose of this document is to convey the process Ivanti EPM uses to handle Status Updates for Scheduled Tasks, and what to look for if things aren't working as desired.

     

    What is SOAP and why does Ivanti EPM use it?

     

    SOAP (Simple Object Access Protocol) is a protocol specification used for exchanging information for implementation by Web Services. SOAP features include:

    • Extensibility, Neutrality, and Independence
    • Uses Extensible Markup Language (XML) Information Set for its message format, which allows processes running on various Operating Systems (Windows, Linux, Etc.) to communicate freely.
    • Relies on Application Layer protocols, usually Hypertext Transfer Protocol (HTTP) for message transmission.

     

    For more information, please reference this Microsoft Document.

     

    Ivanti EPM clients utilize SOAP actions to communicate Task Status updates to the core. The following is an example of a client doing so in the SendTaskStatus.exe log:

     

    Sun, 32 Sep 2016 36:57:24 SendRequest: SOAPAction:http://tempuri.org/ResolveDeviceID
    

     

    Task Start

    When a task is first initiated from the console, the core is responsible for updating the status of the task until the policy has been made available. The applications involved are:

     

    Console.exe

    • Saves the task to the Ivanti EPM Database (LDTASK Table) in an "Active" state.

    TaskHandlerProxy.exe

    • Initiates PolicyTaskHandler.exe with the specified ID of the task being run.

    PolicyTaskHandler.exe

    • Attempts to resolve the devices within the Task and create Policies for each device. Once PolicyTaskHandler is finished, the client is responsible for updating the status going forward.

     

    Send Task Status Flow (2016)

    2016 FlowChart2.png

    Send Task Status Process (2016)

     

    Software Distribution:

    • Resolve Device ID
      • Sdclient.exe > SendTaskStatus.exe > ProxyHost.exe - WSVulnerabilityCore/Vulcore.asmx.
        • The Web Method ResolveDeviceID is then invoked utilizing the COMPUTER table in the Ivanti EPM Database.
    • Status Update
      • Sdclient > SendTaskStatus > ProxyHost - WSStatusEvents/EventHandler.asmx.
        • The Web Method SetPatchInstallStatus2 is then invoked utilizing the LDTASK table in the Ivanti EPM Database.

    Patch Manager:

    • Resolve Device ID
      • Vulscan.exe > ProxyHost.exe - WSVulnerabilityCore/Vulcore.asmx.
        • The Web Method ResolveDeviceID is then invoked utilizing the COMPUTER table in the Ivanti EPM Database.
    • Status Update
      • Vulscan.exe > ProxyHost - WSStatusEvents/EventHandler.asmx.
        • The Web Method SetPatchInstallStatus2 is then invoked utilizing the LDTASK table in the Ivanti EPM Database.

     

    Send Task Status Flow

    96 FlowChart2.png

    Send Task Status Process

     

    Software Distribution:

    • Resolve Device ID
      • Sdclient.exe > SendTaskStatus.exe > ProxyHost.exe - WSVulnerabilityCore/Vulcore.asmx.
        • The Web Method ResolveDeviceID is then invoked utilizing the COMPUTER table in the Ivanti EPM Database.
    • Status Update
      • Sdclient > SendTaskStatus > ProxyHost - WSVulnerabilityCore/Vulcore.asmx.
        • The Web Method SetPatchInstallStatus2 is then invoked utilizing the LDTASK table in the Ivanti EPM Database.

    Patch Manager:

    • Resolve Device ID
      • Vulscan.exe > ProxyHost.exe - WSVulnerabilityCore/Vulcore.asmx.
        • The Web Method ResolveDeviceID is then invoked utilizing the COMPUTER table in the Ivanti EPM Database.
    • Status Update
      • Vulscan.exe > ProxyHost - WSVulnerabilityCore/Vulcore.asmx.
        • The Web Method SetPatchInstallStatus2 is then invoked utilizing the LDTASK table in the Ivanti EPM Database.

     

    Troubleshooting

    A client may occasionally fail to upload its status as it works through a task. This section can help pinpoint the location that the problem occurred.

     

    Log Locations

    IIS:

    • C:\inetpub\logs\LogFiles
    • C:\Windows\System32\LogFiles\HTTPERR

    Core:

    • WSVulnerabilityCore.dll.log - %ldms_home%\log
    • StatusEvents.dll.log - %ldms_home%\log
    • Console.exe.log - %ldms_home%\log
    • PolicyTaskHandler.exe.log - %ldms_home%\log
    • TaskHandlerProxy.log - %ldms_home%\log

    Client:

    • ProxyHost.log - C:\Program Files (x86)\LANDesk\Shared Files
    • SendTaskStatus.log - C:\ProgramData\LANDesk\Log
    • Sdclient_Task#.log (Distribution) - C:\Program Files (x86)\LANDesk\LDClient\Data
    • Vulscan.log (Patch Manager) - C:\ProgramData\LANDesk\Log

    If opening a Support Ticket with Ivanti Support regarding Task, please replicate the issue and gather these logs. Zip them up and attach them to the case incident for the assigned Engineer to review.

    IIS Manager

    Internet Information Services (IIS) Manager can be used to verify that LANDESK Web Application Pools are up and running.

    Application Pools.png

    In terms of Task Status Reporting, the applicable Application Pools are LDAppStatusEvents and LDAppVulnerability . Ensure that they are both in a Started state. It might be worth "Recycling" each Application Pool as shown in the screenshot above.

    When using 9.6, LDAppStatusEvents does not exist in IIS Manager. This Application Pool was first introduced in 2016 as it alleviates the stress on LDAppVulnerability by handling status updates in 2016

    IIS Reset

    If IIS on the core is found to be unresponsive, sometimes running an IIS Reset can resolve the issue.

     

    Open an administrative command prompt on the core and run "iisreset." Once this completes, attempt to produce the issue again.

    IISRESET.png