Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage 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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Nov 9, 2014

Repackage the Visual C++ installer to install to same folder as TSM Client during installation to avoid conflict with apps

We need the TSM Client to install its VC++ component into a different
directory than the default common/shared directory that other apps use. This is so that when we install or upgrade the tsm client, it does not upgrade the shared VC++ that other apps rely on.

What is occurring is that when the TSM client gets installed, it is
upgrading the shared VC++ which is affecting other applications on the same server which depend on the earlier version of VC++. By having the TSM Client install its own version of VC++ into the TSM Client directory, we can separate the different versions of VC++ and not impact other applications.

We need the TSM Client to behave like a Portable Application by installing the runtime in the same directory as the TSM Client. This way the the Client does not use the shared runtime which is used by other applications.

Idea priority High
  • Guest
    Reply
    |
    Aug 6, 2015

    After a lot of investigation and discussion, IBM has determined that this is not a feature that TSM will implement. The primary reason is that it goes against Microsoft recommendations (https://msdn.microsoft.com/en-US/library/ms235299.aspx
    ). In addition, there are some technologies coming from Microsoft that will help address this application portability concept referred to in this RFE. We are investigating those following Microsoft best practices.

  • Guest
    Reply
    |
    Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family