We have been seeing the same behavior in our 8.6 environment with agent upgrades. Does anyone know if this is maybe due to there being a pending reboot on the server before the upgrade was initiated or does the RSCD agent upgrade actually cause the server to need a pending reboot?
yes - so the rscd install looks to see if there is anything in the PendingFileRename registry key - iirc it's under hklm\system\currentcontrolset\session maanger or something like that. that is where applications leave files that need to get copied on the next boot because the files were in use at the time of the install. so you'd get that message if any application had left something there.
you can get blade to ignore this w/ the PENDINGREBOOTFORCE=1 option to the msi - eg:
msiexec /i rscd.msi /qn REBOOT=ReallySuppress PENDINGREBOOTFORCE=1 /l*v c:\temp\rscd.log
Thanks, Bill. I wondered about using PENDINGREBOOTFORCE=1. Also, thanks for the information regarding the Registry key. I was looking for something like that in order to flag it beforehand in testing.
So it sounds like you're saying that we can in fact use PENDINGREBOOTFORCE=1 to basically ignore the Registry key, and the Agent should be installed successfully. In other words, we won't see the Pending Reboot warning AND the Agent Upgrade itself is unlikely to need a reboot, correct?