I had heard that a "late 6.3" version client would force a reboot, apparently following the prerequisite MS packages.
A co-worker had installed 6.3.x on a file server (Win Server 2008) and didn't know it was going to boot while he went for a coffee refill during the install. He had several calls from staff that got clobbered due to the reboot. But, this morning I installed the 6.4.0 client without any reboot on Win Server 2008. The client installer DID install the Microsoft packages. The machine happens to also have TSM Monitoring/Admin 6.3.1 installed. Perhaps the Microsoft packages were already there, and updated, which maybe doesn't force a reboot??? ------------------------------------------------ Harold Vandeventer Systems Programmer State of Kansas - Office of Information Technology Services [email protected] (785) 296-0631 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of RonHextall Sent: Wednesday, November 28, 2012 4:57 AM To: [email protected] Subject: [ADSM-L] Client 6.4 installation causing Win Server 2012 to restart? Hello all, I started the installation of TSM Client version 6.4 on one of our new Windows Server 2012 servers and went to do other things while waiting on the installation to finish. When I went back to the server after about ~5 minutes I realized that the TSM Client installation hade restarted the machine, without installing the client yet, causing angry phonecalls from concerned users. I figure that the installation of the "prerequisite" Microsoft packages is the reason behind this? Has anyone here experienced this before? I've searched through various installation notes from TSM regarding the 6.4 client but I havent really found anything indicating this. I have installed 5 or 6 clients on other Windows Server 2012 machines and numerous of older TSM clients on other servers without experiencing this before. The concerned server is used as an TS-server. +---------------------------------------------------------------------- |This was sent by [email protected] via Backup Central. |Forward SPAM to [email protected]. +---------------------------------------------------------------------- [Confidentiality notice:] *********************************************************************** This e-mail message, including attachments, if any, is intended for the person or entity to which it is addressed and may contain confidential or privileged information. Any unauthorized review, use, or disclosure is prohibited. If you are not the intended recipient, please contact the sender and destroy the original message, including all copies, Thank you. ***********************************************************************
