Contact Expert v7.6

Migrating Contact Expert from Microsoft Lync 2010 to Microsoft Lync 2013

Objectives

This chapter describes the migration of CE from a Microsoft Lync 2010 environment to Microsoft Lync 2013. This migration means removing CE specific Lync Server configuration on the old Lync platform and recreating them on the new one. There might be alternative approaches for this migration, however this is the tested approach introducing the least risk and therefore endorsed by Geomant.

Assumptions

The process described below assumes the followings:

  • Migrating Lync infrastructure happens in a single step from CE perspective. Meaning that CE will be connected to a single Lync environment at any point in time during the migration – either Lync 2010 or 2013. CE will not be required to communicate with both Lync 2010 and 2013 at any point.
  • Host certificates issued for the CE servers in the Lync 2010 environment remains valid in the Lync 2013 environment.
  • The Lync SIP domains are migrated without changing the domain names.
  • Lync user accounts designated as CE agents are migrated without changing their AD distinguished names and their SIP URI.
  • PSTN dial-in numbers assigned to CE campaigns remain unchanged during the migration.
  • The list of CE campaign (queue) and recorder endpoints and their associated SIP URIs and PSTN dial-in numbers are at hand.

If the CE core and recorder components are located on the same Windows Server, then CE Core Host and CE Recorder Host refer to the same Windows Server in the following description. Obviously, FQDN of the CE Core Host and FQDN of the CE Recorder Host mean the same FQDN in this case.

Preparation

Shutting Down Contact Expert

  1. Log on to the CE Core Host and CE Recorder Host(s) (if separate) with local administrator privileges.
  2. Using the CE Server Manager tool stop each CE component both on the CE Core Host and the CE Recorder Host.
  3. Close CE Server Manager.

Removing CE Specific Configuration from Lync Server 2010 Infrastructure

  1. Log on to the Lync 2010 Front-end server with CSAdministrator privileges.
  2. Launch the Lync Server 2010 Management Shell application to access the PowerShell interface.

  3. Remove each CE campaign and recorder endpoints by executing the following command repeatedly (using the campaign and recorder endpoint URIs):

    Remove-CsTrustedApplicationEndpoint –Identity [endpoint SIP URI]

  4. Remove CE core application executing the following command:

    Remove-CsTrustedApplication –Identity [FQDN of the CE Core Host]/ACE

  5. Remove CE recorder application executing the following command: 

    Remove-CsTrustedApplication –Identity [FQDN of the CE Recorder Host]/ACE_Recorder

  6. Remove CE core application pool executing the following command:

    Remove-CsTrustedApplicationPool –Identity [FQDN of the CE Core Host]

  7. Remove CE recorder pool executing the following command:

    Remove-CsTrustedApplicationPool –Identity [FQDN of the CE Recorder Host]

Migration

Lync Side Migration

Perform the Lync side migration – this is not detailed in this documentation.

Upgrading UCMA on CE Core Hosts

  1. Uninstall Microsoft Unified Communications Managed API 3.0, Runtime.
  2. Uninstall each Microsoft Server Speech Text to Speech Voice (xxx, yyy) package.
  3. Uninstall each Microsoft Server Speech Recognition Language - xxx (yyy) package.
  4. Uninstall Microsoft Server Speech Platform Runtime (x64).
  5. Uninstall Microsoft Lync Server 2010, Bootstrapper Prerequisites Installer Package.
  6. Install Microsoft UCMA 4.0 Runtime (you can find the installer on CE iso image: UcmaRuntimeSetup.exe).
  7. Install the Microsoft TTS Language Package you need (you can find the language package installers on CE iso image; in the UCMA 4.0 subfolder).
  8. Keep in mind that you need to run the latest Lync Server 2013 Cumulative Update installer in order to keep UCMA 4.0 up to date.

Creating CE Specific Configuration on Lync Server 2013 Infrastructure

  1. Log on to the Lync 2013 Front-end server with CSAdministrator privileges.
  2. Launch the Lync Server 2013 Management Shell application to access the PowerShell interface.

  3. Execute the following command:

    New-CsTrustedApplicationPool –Identity [FQDN of the CE Core Host] –Registrar [FQDN of the Lync Front End] –Site [Lync SiteId]

    You can list your Lync site ids using the Get-CsSite cmdlet.

  4. Execute the following command:

    New-CsTrustedApplication –ApplicationId ACE –Port 9000 -TrustedApplicationPoolFqdn [FQDN of the CE Core Host]

    Remember (copy) the ServiceGruu property returned by the command. This will be referred as CECoreGruu.

  5. Use the following command to create the same campaign endpoints which were removed from Lync 2010:

    New-CsTrustedApplicationEndpoint –ApplicationId ACE –TrustedApplicationPoolFqdn [FQDN of the CE Core Host] –SipAddress   [endpoint SIP URI] –DisplayName [campaign display name] –LineURI [PSTN dial-in number]

  6. Execute the following command (note: you do not need to execute this command if CE core and recorder components are located on the same Windows Server):

    New-CsTrustedApplicationPool –Identity [FQDN of the CE Recorder Host] –Registrar [FQDN of the Lync Front End] –Site [Lync SiteId]

  7. Execute the following command:

    New-CsTrustedApplication –ApplicationId ACE\_Recorder –Port 9100 -TrustedApplicationPoolFqdn [FQDN of the CE Recorder Host]

    Remember (copy) the ServiceGruu property returned by the command. This will be referred as CECoreGruu.

  8. Use the following command to create the same recorder endpoints which were removed from Lync 2010:

    New-CsTrustedApplicationEndpoint –ApplicationId ACE\_Recorder –TrustedApplicationPoolFqdn [FQDN of the CE Recorder Host] -SipAddress [endpoint SIP URI] –DisplayName [recorder display name]

Configuring CE with the New Lync 2013 Front-End

  1. Log on to the CE Core Host with local administrator privileges then find and launch the CE PowerShell icon.

  2. Execute the following command:

    Set-CESfbConnectorProperties -ApplicationName ACE -ApplicationFqdn [FQDN of the CE Core Host] -ApplicationPort 9000 -ApplicationGruu "[CECoreGruu]"

  3. Log on to the CE Recording Host with local admin privileges then find and launch the CE PowerShell icon.

  4. Execute the following command:

    Set-CESfbRecorderProperties -ApplicationName ACE_Recorder -ApplicationFqdn [FQDN of the CE Recorder Host] -ApplicationPort 9100 -ApplicationGruu "[CERecorderGruu]"

  5. Log on to the CE Administration website and open the Infrastructure → Voice Infrastructure → Voice Gateways menu.

  6. Set the Host property to the FQDN of the Lync 2013 Front-end pool – or in case of a Standard Edition Lync instance: the standalone Front-End server.
  7. Open up the Infrastructure → Recording → Recording Gateways screen and point the Media server FQDN and Signaling server FQDN properties to the FQDN of the Lync 2013 Front-end pool (or standalone Front-end server for Standard Edition).

Upgrading CE

In order to install UCMA 4.0 components, upgrade CE to the latest version following all the steps described in Upgrade Guide. Please ensure that "Legacy system update for Microsoft Lync Server 2010" option is left unchecked.

Starting Up the Migrated Systems

  1. Log on to the CE Core Host with local administrator privileges.
  2. Use the CE Server Manager tool to start each CE component on both the CE Core Host and CE Recorder Host servers.
Sorry, your browser does not support inline SVG. article updatedarticle updated3/4/2024 9:59:25 AM (UTC)3/4/2024 9:59:25 AM (UTC)