Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform 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 Oct 2, 2019

Update status of TEMCLIENT role on VSI does not always happen correctly

Update status of TEMCLIENT role on VSI is not correct.

We found an issue using the IBM Endpoint Manager (IEM) pattern type with updating the status of the
TEMCLIENT role on a Virtual System Instance when unlinking the IEM shared service from the environment profile of the VSI.
The code of the TEMCLIENT role does not hit any exceptions, however the status is set to "green" (BigFix client installed/configured/running).
However as the BigFix client has been stopped and uninstalled at this point, the TEMCLIENT role should have been set to "yellow" indicating licensetracking on the instance is not active. However an hour later the status still gets set to "yellow" as it should (so it is eventually consistent).

Details, including logfiles, are in PMR 84683,211,788.

Idea priority Medium
RFE ID 136966
RFE Product PureApplication System