Product Documentation

Upgrade

Dec 22, 2016

To have access to all the RealTime Optimization Pack 2.2 features, you must upgrade your Skype for Business 2.x to the  June, 2016 PU (15.0.4833.1001) or subsequent PU or your RealTime Optimization Pack 1.x to this version.

Optimization Pack 2.0.x or 2.1 to this version

  • HDX RealTime Optimization Pack supports flexible upgrade from Optimization Pack 2.0.x to  2.2. To upgrade from Optimization Pack 2.0.x or 2.1 to this version, be aware of the following considerations:
  • You must have Optimization Pack 2.0.x or 2.1 (RealTime Connector and RealTime Media Engine) and Skype for Business 2015 deployed throughout your network. 
  • To upgrade the Optimization Pack to this version, you must also upgrade Skype for Business 2015 to minimum Product Update 15.0.4833.1001 or Skype for Business 2016 to minimum Product Update 16.0.7341.2032 (for Click-to-Run). 
  • You can upgrade RealTime Connector from 2.0.x or 2.1 to this version without immediately upgrading the RealTime Media Engine 2.0.x or 2.1 on the endpoints, but you must update the RealTime Media Engine eventually to receive all the new features and fixes to known issues. This applies to major, minor, and patch releases. 
  • You can upgrade the RealTime Connector and Skype for Business independently:
    • Upgrade the RealTime Connector 2.0.x or 2.1 to this version, and then upgrade Skype for Business 2015 to at least June, 2016 Product Update 15.0.4833.1001.  For Skype for Business 2016, you must upgrade to minimum Product Update 16.0.7341.2032.

      OR

    • Upgrade Skype for Business 2015 to the June, 2016 Product Update or subsequent Product Update and then upgrade the RealTime Connector 2.0.x or 2.1 to this version. For Skype for Business 2016, you must upgrade to minimum Product Update 16.0.7341.2032.
  • When doing a staged upgrade for a minor or major release (for example, from 2.0 to this version), you must upgrade RealTime Connector first, before RealTime Media Engine; otherwise you get fallback behavior rather than optimized behavior.
  • Upgrades to a patch release (for example, 2.0 to 2.0.100) can be done in either order.

Important

If you are upgrading from 1.x to 2.1, you must upgrade both RealTime Connector and RealTime Media Engine to retain optimized operation. 

Upgrade requirement for Linux

If you are running the 32-bit Citrix Receiver for Linux and 32-bit RealTime Media Engine on 64-bit systems, you can use the 32-bit RealTime Media Engine package to upgrade.

If you want a 64-bit RealTime Media Engine, first uninstall both  32-bit Citrix Receiver for Linux and 32-bit RealTime Media Engine, and then install the 64-bit Citrix Receiver for Linux, version 13.2 or later and 64-bit RealTime Media Engine

Optimization Pack 1.x to 2.x

During 2015, Citrix and Microsoft co-developed a new architecture for delivering Skype for Business in virtualized environments. This new architecture provides smooth upgrades from one 2.x release to the next by allowing customers to upgrade the HDX RealTime Connector on the XenApp and XenDesktop servers before upgrading the RealTime Media Engine on all user devices. But upgrading from the original 1.x architecture to 2.x is more challenging because 1.x versions of the RealTime Media Engine are not compatible with the new RealTime Connector 2.x . Therefore, during the interval between upgrading the RealTime Connector and upgrading the RealTime Media Engine on user devices, optimized delivery of the Skype for Business client is not possible.

For the smoothest possible upgrade, we recommend using Electronic Software Delivery mechanisms to update the RealTime Connector and the RealTime Media Engine on user devices as close to simultaneously as possible. To manage server load if some users need to use Skype for Business audio-video services while a major version mismatch still exists between the RealTime Connector and the RealTime Media Engine, the HDX RealTime Connector provides fallback controls (introduced in the 2.1 release). These controls enable administrators to configure whether to totally deny audio-video service until the RealTime Media Engine is upgraded to 2.x, permit only audio, or permit both audio and video. Server-side video processing has the greatest impact on CPU usage and server scalability. 

Microsoft Lync VDI Plug-in migration to RealTime Optimization Pack

The Lync 2013 client version 15.0.4859.1002 (released in September 2016) includes a fix to support co-residency of the Lync VDI Plug-in with this version of HDX RealTime Media Engine, facilitating migration. The migration procedure:

  1. Apply all the latest updates for the Lync/Skype for Business client on the XenDesktop server and for the Lync VDI Plug-in on the users' Windows devices. Note that migration support is available only with the latest updates for both components. Make sure the client is running in Skype for Business UI mode, because only this mode is supported by this version of the HDX RealTime Optimization Pack.
  2. Deploy this version of the HDX RealTime Media Engine on the endpoints in parallel with the Lync VDI Plug-in. At this point, the Lync VDI Plug-in is still used for audio/video calls.
  3. Deploy the HDX RealTime Connector for Skype for Business on the XenDesktop server. At this point, the system switches to using the HDX RealTime Optimization Pack for audio/video calls.
  4. Uninstall the Lync VDI Plug-in from the Windows devices.