1 Reply Latest reply on Nov 2, 2018 7:18 AM by cwinning

    Patch for Windows / Powershell:  Detailed Scan and deploy results.

    rcahill Rookie

      I developed serveral powershell scripts to scan and deploy Windows patches.   Thus far the only very general information is being gathered.  Is there a method to report on the patches found missing and a listing of the deployed patches?

       

       

      Example transaction script output:   What I can not seem to output is the listing of patches.   It seems I need to run a report for that information.

       

      Scan Starting .........................

       

      Name         : API - n.n.n.n

      StartedOn    : 8/29/2018 2:58:46 PM

      TemplateName : Dechert - Full Scan

      Uid          : 938f3cee-720e-4705-a9b3-253939cba097

       

      Name                 Elapsed    Ended On             Expected   Completed  Is

                           Time                            Machines   Machines   Complete

      ----                 ---------- --------             ---------- ---------- ----------

      API - n.n.n.n   0:01:32    8/29/2018 11:00 AM   1          1          True

       

       

      Name                 Installed  Missing    Missing SP Completed On         Error

                           Patches    Patches

      ----                 ---------- ---------- ---------- ------------         -----

      xxxxxxxxxxx     542        35         0          8/29/2018 11:00 AM

       

       

      Name                 Elapsed    Ended On             Expected   Completed  Is

                           Time                            Machines   Machines   Complete

      ----                 ---------- --------             ---------- ---------- ----------

      API - n.n.n.n   0:01:32    8/29/2018 11:00 AM   1          1          True

       

      Name                 Installed  Missing    Missing SP Completed On         Error

                           Patches    Patches

      ----                 ---------- ---------- ---------- ------------         -----

      xxxxxxxxxx     542        35         0          8/29/2018 11:00 AM

       

       

       

      ScanUID : 938f3cee-720e-4705-a9b3-253939cba097

      Machines : 1

      Update : 8/29/2018 3:00:23 PM

      Complete: True

      The scan took hh:mm to complete:  0:2

      .

      .

      Scan Finished,

      Deploy Starts  .........................

      Deploy UID : 5ce68ec8-2639-4060-8125-369f0ef28080

       

       

      Name                 Elapsed    Ended On             Expected   Completed  Is

                           Time                            Machines   Machines   Complete

      ----                 ---------- --------             ---------- ---------- ----------

      Standard with Off... 0:40:54    8/29/2018 11:41 AM   1          1          True

       

      Name                 Address         Overall State  Status                 Last Updated         Error Code

      ----                 -------         -------------  ------                 ------------         ----------

      xxxxxxxxxx     n.n.n.n    Complete       Finished               8/29/2018 11:41 AM

       

       

      Name                 Elapsed    Ended On             Expected   Completed  Is

                           Time                            Machines   Machines   Complete

      ----                 ---------- --------             ---------- ---------- ----------

      Standard with Off... 0:40:54    8/29/2018 11:41 AM   1          1          True

       

       

       

      Name                 Address         Overall State  Status                 Last Updated         Error Code

      ----                 -------         -------------  ------                 ------------         ----------

      xxxxxxxxxx     n.n.n.n   Complete       Finished               8/29/2018 11:41 AM

       

       

      The scan and deploy took hh:mm to complete:  0:43

        • 1. Re: Patch for Windows / Powershell:  Detailed Scan and deploy results.
          cwinning CommunityTeam

          Actions that you drive from the API will be reflected in the Ivanti Patch for Windows Servers user interface. They are labeled to distinguish between API-initiated runs and console-initiated runs. Actions receive the same level of tracking regardless of whether they are initiated from the user interface or at the API level.

           

          The results of patch scans and deployments performed from the API are identified within the Results pane in the Source column.

           

          Patch deployments performed from the API can be tracked using Deployment Tracker.

          Our next version of Patch for Windows Servers (new name is Security Controls) will include more features for our API interface.

           

          Thanks,

          Charles