Kieran Reid

I hadn't heard this one before, gave me a laugh.....



A SPANISH Teacher was explaining to her class that in Spanish, unlike  English, nouns are designated as either masculine or feminine.

'House' for instance, is feminine: 'la Casa.'
'Pencil,' however, is masculine: 'el lapiz.'

A student asked, "What gender is 'computer'?"

Instead of giving the answer, the teacher split the class into two groups, male and female, and asked them to decide for themselves whether computer' should be a masculine or a feminine noun. Each group was asked to give four reasons for its recommendation.

The men's group decided that 'computer' should definitely be of the feminine gender ('la computadora'), because:

1. No one but their creator understands their internal logic;

2. The native language they use to communicate with other computers is incomprehensible to everyone else;

3. Even the smallest mistakes are stored in long term memory for possible later retrieval; and

4. As soon as you make a commitment to one, you find yourself spending half your paycheck on accessories for it.

The women's group, however, concluded that computers should be Masculine ('el computador'), because:

1. In order to do anything with them, you have to turn them on;

2. They have a lot of data but still can't think for themselves;

3. They are supposed to help you solve problems, but half the time they ARE the problem; and

4. As soon as you commit to one, you realize that if you had waited a little longer, you could have gotten a better model.

The women won.

Powered by ScribeFire.

This seems to be an under-utilized resource of Sametime 8 so I thought I'd highlight it
to see what you think and breakdown the steps to implement it. When I say under-utilized
I mean I've only ever had one question about it in pmr work. Maybe it's so easy, no-one
has ever had a problem with it!  :D

I've worked off the steps in the InfoCenter here and the example I use upgraded an 8.0
client, with minimal interaction from the end user, to the 8.0.2 Connect client release.
All Windows based but changes to other OS types should be minimal.

N.B. If you plan on upgrading 8.0 Connect clients, you'll need to check out this technote first
http://www-01.ibm.com/support/docview.wss?rs=463&uid=swg21291831
If you're upgrading 8.0.1 clients, this fix is included and you're OK.


1. Download the 8.0.2 network installer
IBM Lotus Sametime Connect Client Network Installer 8.0.2 Windows, Linux Multilingual (C1JZ2ML)

2. I also needed the standalone installer to get the install.xml file for 8.0.2
IBM Lotus Sametime Connect Client Standalone Installer 8.0.2 Windows, Linux Multilingual (C1JZ1ML)

3. Create a folder in your update site directory and add this to the policy document update site field.
Adding it to this field as opposed to the optional update field will force the update down and the
end users are prompted to restart once it's finished in the background.



4. The InfoCenter says to "Extract the sametime.802.upgrade.patch.update.site.zip file
to the upgrade
site's directory". The file is actually called sametime.80.upgrade.patch.update.site.zip and is inside
the upgrade directory of the 8.0.2 Network Installer package.

5. Make a folder called 'manifest-updates' under the update site directory

6. Take the install.xml from the deploy' folder of the 8.0.2 standalone installer package and name it
802.install.xml before copying it into the manifest-updates folder. The name of the xml is up to you
but make it descriptive.

7. From the network installer package, in the upgrade folder, copy out the file Windows-Linux-update.site.zip
and paste it into your update site folder.

8. Create a file called manifest-updates.xml in the manifest folder. The following content upgraded my 8.0
client to 8.0.2 with two restarts.

<manifest-updates>
<manifest-update id="st802" os="windows" manifest="st802.install.xml" coreBundleVersion="8.0.0"
   match="compatible">
  <updateSitePkg url="http://server1.demo.com/sametime/update/Windows-Linux-update.site.zip"/>
</manifest-update>
</manifest-updates>

Restart #1



Restart #2



Ta Da!




Summary: This was the contents of my update site directory



and the contents of the manifest-updates directory

Powered by ScribeFire.