ADSM-L

Re: [ADSM-L] TSM BA installer rant

2014-07-04 11:25:41
Subject: Re: [ADSM-L] TSM BA installer rant
From: "Prather, Wanda" <Wanda.Prather AT ICFI DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 4 Jul 2014 15:23:31 +0000
Thanks for the warning; I wasn't aware of this and it's going to save me some 
grief!

I just looked in the client install guide, and it says " As part of the Windows 
client installation process, one or more Microsoft C++
redistributable packages are installed, if they are not already installed on 
the Windows workstation."

But it doesn't tell me *what*  packages are needed so I can check if they are 
already installed and find out if I'm exposed to this problem, nor is it listed 
on the web pages in the system requirements.  
Angela, can we get this documented in the manual please?

Thanks!
Wanda


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Hans Christian Riksheim
Sent: Friday, July 04, 2014 7:55 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM BA installer rant

As many has experienced the 7.1 BA client for Windows not only requires a 
reboot, it will in the middle of the install reboot right into your face 
without any warning or prompt. On top of this it will do so despite you telling 
it not to. The same goes for the TDP SQL client btw.

Cause is some C++ Windows things that must be installed for the GUI to work.

For the BA client there is a warning in the Info Center on this. For the TDP it 
is not so clear, that crucial information is hidden in a technote.
IBM therefore thinks they are not to blame but in practise a lot of users fall 
in that trap and breach their SLAs all over the place. With a GUI one has 
certain expectations on how it should behave and if no unprompted reboot 
happened in earlier versions why should it happen now?

My opinion on this:

   1. IBM should set as a design principle that no customer server should
   ever need a reboot when installing, upgrading or removing TSM software.
   2. There should be no exceptions, but if there are at least make the
   installer prompt a warning so that the user can delay the reboot until
   service hours.
   3. Software versions that will reboot a server without warning should be
   immediately removed from PA and other repositories until they are fixed.


Regards,

Hans Chr. Riksheim
<Prev in Thread] Current Thread [Next in Thread>