Smart Upgrade and Chained Kits

Hi,

I’ve been successfully testing the upgrade of our Notes 6.5.4 users to Notes 8.5.1 using SmartUpgrade.

Following of the release of Fix Pack 1 for Notes 8.5.1 I’ve been trying to include this in my test upgrade by using the SmartUpgrade Chaining feature (see http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=/com.ibm.help.domino.admin.doc/DOC/H_USING_SMART_UPGRADE_TO_RUN_A_SERIES_OF_CLIENT_UPGRADES_OVER.html ). However I’ve been unable to make this feature work.

In researching this feature I located a post by an IBMer in this forum - see http://www-10.lotus.com/ldd/nd85forum.nsf/5f27803bba85d8e285256bf10054620d/61ec36088b4884ac85257601003ba8ac?OpenDocument

Both documents seem to imply that to use the chaining feature, I should:

  • add a kit to upgrade from 6.5.4 to 8.5.1

  • add another kit to go from 8.5.1 to 8.5.1 FP1

  • set the policy to upgrade to 8.5.1 FP1

If I do this however, SmartUpgrade on the R6.5.4 client reports that no upgrade is available. If however I change the policy to just 8.5.1, then the client will happily upgrade to 8.5.1 - just not with the FP1 extra.

Can you advise what I may be doing wrong please. Is chaining even supported for the R6.5.x client platform.

Thank you

Iain Chapman

Subject: i have a similar issue with chained smart upgrade kits

I’m attempting to use chained kits as well.

I have a kit set to go from Release 8.5 to 8.5.1 and one to go from 8.5.1 to 8.5.1 FP2. Policy is set to go to 8.5.1 FP2.

I can manually start the upgrade (and it works) via tools–>Notes smart upgrade… but one it’s own… a user is never prompted like they usually are.

What’s up here?