Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-12441

Improve Assets Discovery tool in order to fully support the deployment of agents through SCCM

XMLWordPrintable

    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      At the moment in order to install agents on multiple target clients and copy over the same customised file (ex. agent.cfg), the available solution is to use the Service tab of the Discovery tool (or the Collector).

      However in Enterprises infrastructure where there are hundreds+ of remote clients which need the agent installed and those are located across highly segmented networks, it become hard to populate the ip range sections to identify the right clients.

      Note that if no ip ranges can be added to whatever reason, you have to use the sftp-transfer to get the scanned data to the Discovery Tool Server and the settings for this need to be provided through the agent.cfg file.

      Therefore many of our customers would like to use the SCCM MS tool to deploy/install the agents and also to copy over agent.cfg and/or patterns files.

      However by using SCCM for this matter, the following issues have been reported when taking into consideration Agent.cfg file as example:

      • If the file is copied after the installation, the configuration works, but it is not possible to verify successful copy operation, since “file exists” is always true and “file last modified” gets touched and updated, the moment the service kicks in, and writes the file with a new date (and modifies “NextScanDate”)
      • If the modified Agent.cfg file is copied and present before the installation, the installer replaces it with the default file. So no communication can occur (missing credentials)
        If the Agent.cfg is only modified by means of xml content remediation the password gets discarded, the other settings persist
      • if the file is replaced by Group Policy Preferences, there will be an old file (hence “NextScanDate” in the past), and a scan will be triggered everytime the file gets written back / every gpupdate.

      Suggestions:

      • It would be great if the mechanism to add/update the NextScanDate for the agent would be changed in order to guarantee full supportability for widely used SCCM tool for sysadmins.
      • As an alternative we should provide instructions for customers to customise the installer in order that a custom file (agent.cfg) can be used.

          Form Name

            [JSDSERVER-12441] Improve Assets Discovery tool in order to fully support the deployment of agents through SCCM

            Christian Schneider added a comment -

            Dear Zakhar,

            I just got an email, notifying me that this issue will be fixed with version 7.0.0. Is there a preview of any documentation? I am very keen on having a short look into it.

             

            Thank you,

            Chris

            Christian Schneider added a comment - Dear Zakhar, I just got an email, notifying me that this issue will be fixed with version 7.0.0. Is there a preview of any documentation? I am very keen on having a short look into it.   Thank you, Chris

            Christian Schneider added a comment -

            With the current CVE affecting Discovery Agents, this missing feature is really painful. We need to find a work around to push the new version of the Agent out to our Clients.

            Christian Schneider added a comment - With the current CVE affecting Discovery Agents, this missing feature is really painful. We need to find a work around to push the new version of the Agent out to our Clients.

            Christian Schneider added a comment -

            Hi Tiziana,

            I know, that the discovery tool was developed for Jira Server. As there is a native SCCM-to-Insight-integration in Insight, there is no need for the Discovery Agent to be available on Windows Clients. In Jira Server, we got all the needed asset-data from that integration. As the integration does not exist in Assets Cloud, we were looking for alternatives. (Discovery Agent combined with the Atlassian Discovery Collector is one option, the other would be to user our Enterprise Service Bus to collect data from SCCM and then use the Assets-Rest-API to push data into Assets Cloud.)

            I am surprised that you do not face more inputs by big customers and I am wondering, how big companies, that are using Assets, get their windows client data into assets.

            Christian Schneider added a comment - Hi Tiziana, I know, that the discovery tool was developed for Jira Server. As there is a native SCCM-to-Insight-integration in Insight, there is no need for the Discovery Agent to be available on Windows Clients. In Jira Server, we got all the needed asset-data from that integration. As the integration does not exist in Assets Cloud, we were looking for alternatives. (Discovery Agent combined with the Atlassian Discovery Collector is one option, the other would be to user our Enterprise Service Bus to collect data from SCCM and then use the Assets-Rest-API to push data into Assets Cloud.) I am surprised that you do not face more inputs by big customers and I am wondering, how big companies, that are using Assets, get their windows client data into assets.

            Tiziana Marchionni added a comment -

            Hi Chris,

            Just to clarify on your note number 2, that as Discovery is in fact an On prem tool, it is fully supported by the On prem Team, which I am a member of.

            That's why I raised the suggestion under JSM Server. Nevertheless I also cloned this for visibility in JSM Cloud here: https://jira.atlassian.com/browse/JSDCLOUD-12326

            Tiziana Marchionni added a comment - Hi Chris, Just to clarify on your note number 2, that as Discovery is in fact an On prem tool, it is fully supported by the On prem Team, which I am a member of. That's why I raised the suggestion under JSM Server. Nevertheless I also cloned this for visibility in JSM Cloud here: https://jira.atlassian.com/browse/JSDCLOUD-12326

            Tiziana Marchionni added a comment -

            Thanks Chris for adding this important point. I just added it to the suggestion.

            Tiziana Marchionni added a comment - Thanks Chris for adding this important point. I just added it to the suggestion.

            Christian Schneider added a comment - - edited

            Please note: if no ip ranges can be added to whatever reason, you have to use the sftp-transfer to get the scanned data to the Discovery Tool Server. It is this config, that has to be provided in the Agent.cfg.

             

            please note 2: this is not only relevant for Jira Server, but even more for Cloud. (For Jira Server, there is the native SCCM-Integration to import data directly into Insight.)

            Christian Schneider added a comment - - edited Please note: if no ip ranges can be added to whatever reason, you have to use the sftp-transfer to get the scanned data to the Discovery Tool Server . It is this config, that has to be provided in the Agent.cfg.   please note 2: this is not only relevant for Jira Server, but even more for Cloud. (For Jira Server, there is the native SCCM-Integration to import data directly into Insight.)

              Unassigned Unassigned
              tmarchionni@atlassian.com Tiziana Marchionni
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: