If you are planning a phased approach to upgrading servers, you will have a mix of servers running different versions of Sametime in the same production environment. Keep the following considerations in mind as you plan for this type of migration.
Deferring migration of Sametime meetings
The Sametime Meeting server running on WebSphere Application Server replaces the meeting features included in Sametime Standard 8.0.x and 7.5.1. To defer your migration of meetings to the new platform, you can upgrade Sametime
® 8.0.x and 7.5.1 servers, while maintaining your existing "Classic" meetings until you are ready to migrate them to the new platforms.
Setting up awareness for Community Servers running releases 8.5, 8.5.1, or 184.108.40.206
Starting in Release 8.5.2, the Community Server contains changes in the awareness feature that are not backwards-compatible with Community Servers running 220.127.116.11, 8.5.1 and 8.5. A fix is available that allows these servers to continue providing awareness features to users in a mixed-release environment. Click the link below for more information in Tech Note #1455860.
Maintaining Sametime 8.0.2 community servers
You can extend configuration support from the Sametime
System Console to environments that are still using 8.0.2 Community servers, while taking advantage of new features offered in this release. For instructions, see the following article on the Sametime
wiki: Configuring Sametime 8.5.1 Media and Proxy Servers with an 8.0.2 Community Server using Sametime System Console
Establishing connections with older Sametime community servers on AIX®, Linux®, Solaris, or Windows®
To ensure that new and upgraded community servers can still connect to older community servers, update the VP_SECURITY LEVEL parameter in the sametime.ini file on the older servers as explained in Connecting with older Community Servers on AIX, Linux, Solaris, or Windows
Parent topic: Planning for migration from an earlier release