Skip to Main Content

This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Is a defect
Created by Guest
Created on Sep 21, 2021

suppress finding by finding and data source computer id

ILMT can either exclude or suppress findings.

If finding will be excluded all findings on the system will ne excluded.

If finding will be suppressed only the finde will not show up on the system.

If we got a duplicate on BigFix BigFix weill generate a new Computer Id wich will show up within ILMT as datasource computer id.

It can happen that ILMT is counting the finduing for the old and the new computer id (twice counting) and you will not be able to supress one of the finding because the datasource computer id is not part of ILMTs finding suppression process.

Idea priority High
  • Guest
    Nov 8, 2021


    after further discussion we concluded, that this Idea is about ability to independently suppress the software instances reported by two computers in LMT which represent the same endpoint, but got assigned different BigFix IDs, causing the duplicates. In such situation, one should be able to suppress software on one of these computers and this should not affect the software status on the other computer. If this does not work, please report this under support ticket as this needs to be investigated and fixed/clarified.

    Closing this Idea now with the above comment/explanation and plan of action.

  • Guest
    Oct 18, 2021


    we need some more data in relation to this Idea.

    Can you explain in more details why suppressing would not work in case of two computers in LMT (representing the same endpoint) with duplicated BigFix Ids?

    Is this because of the fact that one would loose the whole history related to the suppresses (or excluded) software?

    If yes, would it be acceptable to generate two audit snapshots covering time before duplicates were created and after and excluding/supppressing first the computer with new ID and then the one with old ID?

    Would it address this requirement if ILMT would be acapable of excluding/suppressing the software only for a defined period of time?