Client Management Suite

 View Only
  • 1.  data flow in CMS

    Posted Jun 20, 2013 06:37 AM

    In a standard environment,kindly suggest what are the data flowing and their approx size to and fro from the below:

    NS to End point

    End point to NS

    Task server to End point

    End point to Task server

    Package server to Endpoint (when no patch management or software distribution is happenin)

    Endpoint to Package server (when no patch management or software distribution is happenin)

    NS to Package Server (when no patch management or software distribution is happenin)

    Package Server to NS (when no patch management or software distribution is happenin)

    NS to Task Server

    Task Server to NS

     

     



  • 2.  RE: data flow in CMS

    Posted Nov 19, 2013 01:56 PM

    NS to End point - The NS does not send data it receives it.  Obviously, if you perform a tickle or RTSM action, or something similar, then some small command like data will be sent.

    End point to NS - This depends on what plugins are installed.  The SMA's basic inventory NSE is usually over 1MB; however, the SMA compresses files that are over 200KB by default (this can be changed).  Each type of inventory scan will create a different size of NSE file, and most inventory scans have a delta capability.

    Task server to End point - Small action data.

    End point to Task server - Results data.

    Package server to Endpoint (when no patch management or software distribution is happenin) - Nothing.

    Endpoint to Package server (when no patch management or software distribution is happenin) - Nothing.

    NS to Package Server (when no patch management or software distribution is happenin) - Nothing.

    Package Server to NS (when no patch management or software distribution is happenin) - Package status data.  Size depends on how many packages the PS has, but the NSE files will be compressed as previoulsy mentioned.

    NS to Task Server - Small action data.

    Task Server to NS - Summary data containing endpoint result data.