To ensure all clients have the same features, enable the update policy key to have the server push updates out to the IBM
Administrators can provision new or update existing Sametime
client features in a push
mode so each client employs the same set of features as the others do. The push method enables the client to install Sametime
features or updates automatically when a user logs in to Sametime
Setting up automatic updates
When the user logs in from the client, the client looks in the preferences.ini file located in the update plugin (com.ibm.collaboration.realtime.update\preferences.ini) root directory for the existence of the "runme" property. If the property is present and is set to 'true,' then the update plugin continues. The client then checks the policy key CONNECT_UPDATE_URL on the default Sametime
Community Server. If the server is 7.5.x or later then you, as Administrator, can define the policy to tell the client where the update site is located. If the policy key is not set on the server (see the section on User Policy in this documentation), it is missing for one of two reasons:
- The administrator did not set the key in the stpolicy.nsf file on the Sametime Community Server.
- The Sametime Community Server is a pre-7.5.1 version.
If the key is not found, the client will search the preferences.ini file located in the update plugin (com.ibm.collaboration.realtime.update\preferences.ini) root directory for the adminUpdatePolicyURL value. The client then silently downloads all updated features it finds in the administrator's update site and install them. Updates of features from this site are required so the client does not have the option of not installing them. Once installation is complete, the user receives a message announcing that new updates have been installed and that the user should restart the Sametime
client. The user can click the restart button or press a five-minute delay button. If the user is involved in chats with other users, he or she can continue to delay at five-minute intervals as long as needed. After the restart, the client checks again to see if there are more updates, and if it finds none, the user is not interrupted again. This update process takes place each time the user restarts the client and logs in into the default server.
Parent topic: Distributing updates and optional features to clients