The Sametime 8 upgrade is not an upgrade in reality - lesson learned from yesterday
Tags :Sametime
I made this posting yesterday to an interesting number of comments and this one might go a bit further. Sametime 8 gets closer to an actual provisioned installation. Much better indeed. I praise Lotus for listening to my rants on provisioning and deployment management. However, this became a noticeable problem here and after consideration and some talks with those deep in the bowels of Lotus Sametime development we (as in they and I) confirmed my fears upon first testing.
Here is what happens. Sametime 8 does not see the previous install path (as shown yesterday) since it is not upgrading your Sametime 7.5.x client. It is installing Sametime 8 and then uninstalling 7.5.x from your system. It reads your settings and places them into a lookaside database to move them across during provisioning of the new 8.0 client. What this means to you is that you then cannot install into the same directory you had 7.5.x at first. If you install 8.0 into that folder and then it goes to uninstall 7.5.x it really removes all the new files also. Quite the conundrum isn't it? I know I want mine in the same path all the time. With this scenario, I cannot hit the site and have it upgrade what I have in place. So if you have company standards on how the client is installed, you may be looking at uninstalling the old version from everywhere, then running the install for 8 afterwards into that same directory.
Lotus also changed the folder structure and naming of the Sametime Connect files. This adds a new level of change for the plug-ins. We will cover more on plug-ins on the next posting.
blog comments powered by Disqus
On Wednesday, December 12th, 2007 by Chris Miller
