Smart Upgrade is a good idea. However, it becomes a company LIABILITY if the environment uses roaming or Multi-User Installs...or if someone just happens to log onto another's computer with their ID.
If I have a car payment on my car each month...I wish for that payment to be made on my car and not on my friends car or to the bus or train operators just because I happen to use them as temporary transportation.
How it Manifests:
User has a policy applied to them for an upgrade. Currently the upgrade process does not distinguish between a users
primary computer from one that may have been borrowed or exists in a public area such as a conference room.
The Cost: The cost of this need....Smart Upgrade becomes almost unusable from the perspective of creating new user experience problems when the goal had been to make life easier for either the user or the IT staff.
The Lotus Notes client collects and updates the Person Doc of a user with the computer hostname of the computers used to
access the server. I am not sure what the real value of this information currently is.
Allow the profile or upgrade kit reference administrator set information about what computer to apply the upgrade.
Allow admin to set a rule for how the system should identify a users primary PC. This could be referncing a Win
registry entry. Using free inventory such as OCSInventory...you can easily set an asset tag to a registry entry. Of course
you could then point that lookup to the MS Sql table that holds the information. So....I do know that we dont want to limit
the feature to a particular product....but right now we have nothing.
The person doc shows that last x number of hostnames used by the user to connect to Domino with Notes. Set a
time check.....so that if user1 runs Notes but then goes to a second PC...the user is prompted with something like
"You have logged onto Notes with the following computers in the past 3 days, an auto upgrade has been scheduled for your Primary computer.... is this your primary computer?"