Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps 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 Future consideration
Created by Guest
Created on Dec 5, 2023

To offer TADDM WMI extention update as a .msi file to simplify automating deployment in environments where the autodeploy feature is not an option

With each TADDM Fixpack, an updated TADDM WMI extention is offered. This WMI extention has to be installed on all Windows systems  to ensure the Session and Windows Computer Sensors continue to work properly.

One can use the WMI Autodeploy feature in TADDM to update the Windows target systems during discovery, however this only works if the discovery credentials being used also have administrator privileges on each Windows system. 

In many customer evironments, only the minimal permissions needed to perform the individual TADDM discoveries for each particular sensor are allowed, so more often than not the WMI Autodeploy is not a viable option to update the TADDM WMI extention locally on each Windows system. 

TADDM Support has made a powershell script available to install the WMI update for non-admin accounts. This also works but the standard format for most automation tools in customer environments is a .msi file.

My request for enhancement is as follows:

Could TADDM Development create an officially supported  .msi file that installs the WMI extention updates as in the script or the WMI-Autodeploy? Customers are asking for this in a .msi format, the most common format for Windows Automation Tools (SCCM or GPO update policies in Active Directory).

This would make the rollout of new TADDM versions easier as the WMI updates would be installed faster in environments where the WMI Autodeploy is not a viable option. 


Idea priority Medium