Hi all,

I've just installed TSM for Mail (Exchange) 7.1 on two Exchange 2010 SP3 
servers running on Windows 2008R2 SP1 and both servers rebooted twice during 
the installation of the prerequisites, without any warning...

Same behavior with 7.1.0.0 and 7.1.0.2...

It should not behave that way.

-- 
Best regards / Cordialement / مع تحياتي
Erwann SIMON

----- Mail original -----
De: "Bill Boyer" <bjdboyer AT COMCAST DOT NET>
À: ADSM-L AT VM.MARIST DOT EDU
Envoyé: Mardi 22 Juillet 2014 21:28:36
Objet: Re: [ADSM-L] TSM BA installer rant

Double-click on the client installer .EXE and if the install says it needs to 
install the VC++ libraries or any other pre-req's, cancel out f the client 
install. Then go to the " C:\tsm_images\TSM_BA_Client\ISSetupPrerequisites" 
directory. There are directories for each of the pre-req's. Run them manually 
and if a reboot is required, you can say no and reboot at your leisure. Then 
come back and run the setup.exe and continue the TSM client install.

As for client upgrades I've found that if you make sure to stop any of the TSM 
client services that running (JBB, CAD,Scheduler,...) before running the 
install I don't get asked for a reboot.


Bill Boyer
“If 'something' 'somewhere' gives 'some' error, expect random guesses or no 
replies at all.” - ??



-----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