SnTT: How to use CCH1 Hotfix for Notes Client 8.0.2 in a Smart Upgrade Kit
Friday 14th November, 2008
Today I created the Smart Upgrade Kit for the CCH1 Hotfix. But guess what? after it is installed, the client release is not 8.0.2 CCH1 as you would have guessed, but Release 8.0.2 HF88, so it returned an "failure" after installing correctly, because the final client build string has not matched "Release 8.0.2 CCH1". doh! So, if you would use it with Smartupgrade you should point your policy document to deploy the Release 8.0.2 HF88 version, and also put this in the "Destination Version" field on the Kit document. See the screenshot below for details on how your kit document should look like.
oh, and if you want an administrative install, so the user is not bothered with the EULA agreement and such, use the following "optional arguments for attached kit:" -s -a /s /v"/qb+"
the quotes around /qb+ and especially the blank space after the /s are mandatory
email:ulrich krause | website: http://www.eknori.de
works like a charme
email:Rob Axelrod | website:
Just finishing up my research on this but I'm pretty sure you need to do the same thing in the policy doc to make the template upgrade.
email:Gregory Engels | website: http://www.kompurity.de
I never used SMU, but yes this Release string is for use with SMU as well. Interesting - the help says, a user do not need designer access to his mailbox to do SMU, but it it a client that initiate the template upgrade... does it creates an adminp request of some sort, or how is this actually working?