Hi, Packages for BA clients (7.1.0.2) are: - Microsoft Visual C++ 2010 x64 Redistributable (SU1 & SP1) Packages for TSM for Mail (6.4.1) are : - Microsoft Visual C++ 2010 x86 Redistributable (SP1) - Microsoft .NET Framework 4.5 Full - Microsoft Report Viewer 2010 Redistributable
Best regards, Yann MEUNIER Ingénierie - Système Stockage Informatique CDC - Etablissement DPI Office : +33 1 58 50 53 01 Mobile : +33 6 62 47 88 56 -----Message d'origine----- De : ADSM: Dist Stor Manager [mailto:[email protected]] De la part de Prather, Wanda Envoyé : vendredi 4 juillet 2014 17:24 À : [email protected] Objet : Re: [ADSM-L] TSM BA installer rant 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:[email protected]] On Behalf Of Hans Christian Riksheim Sent: Friday, July 04, 2014 7:55 AM To: [email protected] 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 Ce message et toutes les pièces jointes (ci-après le « message ») sont confidentiels et établis à l’intention exclusive de ses destinataires. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. Si vous recevez ce message par erreur, merci de le détruire sans en conserver de copie et d’en avertir immédiatement l’expéditeur. Internet ne permettant pas de garantir l’intégrité de ce message, la Caisse des Dépôts et Consignations décline toute responsabilité au titre de ce message s’il a été modifié, altéré, déformé ou falsifié. Par ailleurs et malgré toutes les précautions prises pour éviter la présence de virus dans nos envois, nous vous recommandons de prendre, de votre côté, les mesures permettant d'assurer la non-introduction de virus dans votre système informatique. This email message and any attachments (“the email”) are confidential and intended only for the recipient(s) indicated. If you are not an intented recipient, please be advised that any use, dissemination, forwarding or copying of this email whatsoever is prohibited without Caisse des Depots et Consignations's prior written consent. If you have received this email in error, please delete it without saving a copy and notify the sender immediately. Internet emails are not necessarily secured, and declines responsibility for any changes that may have been made to this email after it was sent. While we take all reasonable precautions to ensure that viruses are not transmitted via emails, we recommend that you take your own measures to prevent viruses from entering your computer system.
