We made the jump from 5.x to 6.5, so are just now setting up Smart Upgrade on my test domain. I’ve updated the configuration doc with a link to the Smart Upgrade database, the desktop settings doc (deploy “Release 6.5.1”), and the policy and created a kit document to upgrade from “Release 6.5” to “Release 6.5.1” running the downloaded kit from a network shared UNC.
Not even worrying about it automatically driving the upgrade yet, I thought I would test it through Tools - Notes Smart Upgrade. It says there is no upgrade available because “this Notes client is already upgraded to Release 6.5 which is specified from Smart Upgrade DB.” In addition to murky grammar, I know I’m on 6.5. I want to be on 6.5.1. Actually I want to wave my hand and have everyone be on 6.5.1 but I’m starting small. I’ve been through the redbooks, LDD forums and a few other places (thanks for pointing out the “Release …” gotcha) and still don’t find anything to address it correctly finding the Smart Upgrade but not wanting to upgrade me.
Any other ideas for things to check?
I’m running all three clients on Win2K. The kit
is the 3-client kit. Will it upgrade the client-only desktops without installing the designer or admin?
Subject: Smart Upgrade not triggering on 6.5 → 6.5.1
Hey Eric, although a little quirky, I was able to get my Smart Upgrade working by not using “release” in the destination version, I used “v6.5.1” and it works like a champ. I did use “Release 6.5” in the source version though. Strange, but it works.
Subject: RE: Smart Upgrade not triggering on 6.5 → 6.5.1
I am experiencing the same issue as Eric described in his message. I followed the settings from Tony, but I am still having the same problem. Any additional ideas.
Subject: RE: Smart Upgrade not triggering on 6.5 → 6.5.1
The Notes client “Release 6.5” and “Release 6.5.1” are the special release string between these two versions.This is a bug. We are going to fix it in V6.52.
Please use the work around for your “Release 6.5” Notes client by configuring your Notes kit as
From Version: “Release 6.5”
Destination Version: “Release V6.5.1”
It will solve your problem for your current Notes version “Release 6.5”.
Subject: RE: Smart Upgrade not triggering on 6.5 → 6.5.1
I was having the same problem and was still unable to get the upgrade to work for 6.5 users (our 6.0.2 CF1 versions upgrade without a problem using the same kit) even after specifying the destination version as “Release V6.5.1”.
I tried every combination and finally left the kit as From Version: “*” to destination version “Release V6.5.1” with the intent to solve the problem later.
I finally discovered that removing “Release 6.5.1” from the Deploy version in the Desktop Settings Policy caused the 6.5 clients to see the smart upgrade kit correctly.
For this reason, please make sure to follow Gary’s suggestion and have a different kit for only the 6.5 users (don’t use “*” for the From Version). Otherwise, those that are already upgraded to 6.5.1 will receive the smart upgrade prompt again (presumably because the smart upgrade doesn’t know not to prompt those that are already using “Release 6.5.1” because it is not the same string as “Release V6.5.1”).
Subject: RE: Smart Upgrade not triggering on 6.5 → 6.5.1
I have the same problem trying to get smart upgrade to prompt some users. I just discovered that if the users location document does not have the server name in the correct case and stored in it’s hierarchical format (CN=Servername/O=Domain) it did not prompt.
I stopped by a users desk and opened up the location document and saw the server was listed as servername/domain. I typed in Servername/Domain re-saved the document exited notes and started it again and immediately received the prompt.
Subject: Smart Upgrade not triggering on 6.5 → 6.5.1
The Notes client “Release 6.5” and “Release 6.5.1” are the special release string for these two release versions.This is a very special case as a minor bug because the string “Release 6.5” is a sub string of “Release 6.5.1”.
We are going to fix it in V6.52.
Please use the work around for your “Release 6.5” Notes client by configuring your Smart Upgrade kit as
From Version: “Release 6.5”
Destination Version: “Release V6.5.1”
It will solve your problem for your current Notes version “Release 6.5”.