Smart Upgrade from 6.5 to 6.5.1

I am trying to test the Smart Upgrade before having it deployed. We have the users and servers on 6.5. I have created the kit database and created a kit document for upgrade from 6.5 to 6.5.1. The setup files are on a shared server (files in this folder are decompressed). I have also updated the configuration document in the domino directory with the database link and have also created the neccessary desktop policy document for the Smart upgrade and used an explicit policy for the test user.

I am not getting the notification for the Upgrade. I tried changing the “Destination version” field in the Kit database to Release V6.5.1, Release v6.5.1, V6.5.1 and v6.5.1. None of these seem to get the notification to work.

Is there something I am missing/doing wrong.

Thanks

Srivaths Ramaratnam

Subject: Can’t use a policy for Smart Upgrade from 6.5 to 6.5.1

I think if you remove the desktop policy setting, your test user will be prompted to upgrade. The problem is that the policy doesn’t understand the V6.5.1 workaround. You can test by clicking File–>Tools–>Notes Smart Upgrade for the test user. When the policy is still set, I suspect you will see something like “cannot find an upgrade as specified in the policy”. When the user is not subject to the policy, the smart upgrade will work.

Even without the policy, users will be prompted to upgrade as long as they are in the “Allowed Users & Servers” group. You just can’t set an Upgrade Deadline without it.

That’s my experience with it, anyway. YMMV

Subject: Smart Upgrade from 6.5 to 6.5.1

I think you want to be changing the Source Version field in the kit database to Release v6.5 not the Destination version field

Subject: RE: Smart Upgrade from 6.5 to 6.5.1

Yep. and unless there really is a “V” in the release number of your version as you typed it in your post, then that had better not be there either. It sould be typed exactly as it displays in the “Help About” dialog.

Subject: Smart Upgrade from 6.5 to 6.5.1

Hi,

You want to make sure that your destination version is: V6.51 (without the “.” between 5 and 1)

Also for the allowed users, make sure to include the users who you want to upgrade as well as the group LocalDomainServers.

If the above is set properly and the user is still not prompted to upgrade, check the following notes.ini parameters in the client’s notes.ini:

UPDATE_TIMER=

and there’s another one with the word “Remind” in it. I forget the full notes.ini parameter. I believe its SM_RemindInDays (something to that effect).

set UPDATE_TIMER to a date that has already passed and set SM_RemindInDays to 0

have the user close down the client, open it back up and authenticate with the server.

the user should then be prompted for the upgrade.