Bob, Thanks for the info, I had not ran across that tech note. I could see where it may be a characteristic of the MS component install and not the SP client, but minimally during a manual install it would be nice to have a message box or something warning of the potential unprompted restart.
I am planning on deploying it where I can to address the Installshield vulnerability but certainly cannot have countless clients performing unscheduled restarts. Guess I will have to see about having the prerequisite packages deployed prior to the SP client upgrade, perhaps along with the monthly MS Tuesday updates. -Rick Adamson -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert Talda Sent: Friday, August 19, 2016 3:34 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows Client Upgrades Rick, et al: I’m going to wade in cautiously here, as in my experience, every situation is different. We’ve experienced the reboot issue here at Cornell when installing or upgrading the TSM client for Windows, but the reboots always seem to be associated with the redistributable library installers provided by Microsoft. These appeared in v6.3.1 (for us), and while the reboot issue was documented for silent installs: https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibm.com_support_knowledgecenter_SSGSG7-5F6.3.0_com.ibm.itsm.client.doc_t-5Finst-5Fwinclient.html&d=DQIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=eqh5PzQPIsPArLoI_uV1mKvhIpcNP1MsClDPSJjFfxw&m=zfhvQqOljOX6I3IRnYjCcHBSr3IwiOZSzTLrAY5VobA&s=IsQLDWFhzE9cTTI9BsvdnIeEWCOW_DDthcKbmUcW_1Q&e= we certainly missed it. When the issue was highlighted in the next release of the client (v.6.4): https://urldefense.proofpoint.com/v2/url?u=http-3A__www.ibm.com_support_knowledgecenter_SSGSG7-5F6.4.0_com.ibm.itsm.client.doc_c-5Finst-5Fwinclientreboot.html&d=DQIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=eqh5PzQPIsPArLoI_uV1mKvhIpcNP1MsClDPSJjFfxw&m=zfhvQqOljOX6I3IRnYjCcHBSr3IwiOZSzTLrAY5VobA&s=bRhtHNNpYKGVABxUVZRShZbR2qrD1GkXL3JEY2CPpeA&e= we figured we weren’t the only ones. We worked with the various support groups on campus to separate the update of the redistributable libraries from the install/update of the client itself; most such groups included the redistributable libraries in with security patches known to require a reboot, so there were no “surprise” reboots. Flash foward to the current client (v 7.1.6.0) which we are evaluating for rollout to our users. While the main install documentation has remained unchanged, cautioning about the possibility of reboot, there is an interesting update to the documentation in this tech note: https://urldefense.proofpoint.com/v2/url?u=http-3A__www-2D01.ibm.com_support_docview.wss-3Fuid-3Dswg27039350&d=DQIGaQ&c=AzgFQeXLLKhxSQaoFCm29A&r=eqh5PzQPIsPArLoI_uV1mKvhIpcNP1MsClDPSJjFfxw&m=zfhvQqOljOX6I3IRnYjCcHBSr3IwiOZSzTLrAY5VobA&s=_wLgYVEc_dHI7sLMyyC9a4eWjHjiBdVftb38LZm-tqY&e= In the section "Per APAR IT14776” there are examples of invocations of the redistributable library package (vcredist_x86.exe) with switches that appear to quash the restart. I emphasize the “appear” - it hasn’t happened yet in our testing, but I am sharing this in the interest of learning what others experience. Bob Robert Talda EZ-Backup Systems Engineer Cornell University +1 607-255-8280 r...@cornell.edu<mailto:r...@cornell.edu> On Aug 19, 2016, at 8:22 AM, Rick Adamson <rickadam...@segrocers.com<mailto:rickadam...@segrocers.com>> wrote: Roger, Agree. I should clarify the issue I mentioned happens even on new installs. -Rick Adamson -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Roger Deschner Sent: Friday, August 19, 2016 12:37 AM To: ADSM-L@VM.MARIST.EDU<mailto:ADSM-L@vm.marist.edu> Subject: Re: [ADSM-L] Windows Client Upgrades My experience has been that you can avoid the reboot IFF you stop all scheduler and/or Client Acceptor Daemon processes before you begin installing the new version. It also helps to remove schedulers and/or C.A.D., using the wizard in the old-version GUI client before upgrading. Then put them back after the upgrade, so that they are guaranteed to be running on the new version, and you shouldn't have to reboot. This actually makes sense. Roger Deschner University of Illinois at Chicago rog...@uic.edu<mailto:rog...@uic.edu> ======I have not lost my mind -- it is backed up on tape somewhere.===== On Thu, 18 Aug 2016, Rick Adamson wrote: I have experienced random "unprompted" reboots performing manual installs on Windows clients from 7.1.1.0 to 7.1.6.0 Haven't nailed down exactly why yet, still gathering info.... On one machine MS updates had been applied and may not have been restarted, on another it seemed to happen after installing the first C++ prerequisite. -Rick Adamson -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Kamp, Bruce (Ext) Sent: Thursday, August 18, 2016 10:40 AM To: ADSM-L@VM.MARIST.EDU<mailto:ADSM-L@vm.marist.edu> Subject: Re: [ADSM-L] Windows Client Upgrades If all prerequisites are already installed & all TSM processes are stopped you shouldn't need to. From what I have seen even if it asks to reboot basic functionality remains. Bruce Kamp GIS Backup & Recovery (817) 568-7331 e-mail: mailto:bruce.k...@novartis.com -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David Ehresman Sent: Thursday, August 18, 2016 9:31 AM To: ADSM-L@VM.MARIST.EDU<mailto:ADSM-L@vm.marist.edu> Subject: [ADSM-L] Windows Client Upgrades Can one upgrade a Windows 7.1.x client to a 7.1.somethinghigher client without a reboot or do all Windows 7.1 upgrades require a reboot? David
