Contact Expert v7.5

Migrating Contact Expert from Microsoft Lync 2013 to Microsoft Skype for Business 2015

Objectives

This chapter describes how to migrate CE from a Microsoft Lync Server 2013 pool to a Microsoft Skype for Business Server 2015 pool. Migration means

terminating the association between the Lync Server 2013 pool and CE
removing CE specific configuration from the Lync Server 2013 topology
upgrading the Lync Server infrastructure to Skype for Business
recreating CE specific configuration in the Skype for Business Server 2015 topology
upgrading CE and the underlying UCMA runtime
associating CE with the new Skype for Business 2015 pool

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:

Upgrading the Lync Server infrastructure happens in a single step from CE perspective meaning that CE will be either connected to a Lync Server 2013 pool or a Skype for Business Server 2015 pool. No need to communicate with both Lync Server 2013 pool and Skype for Business Server 2015 pool at the same time.
Host certificates issued for the CE servers in the Lync Server 2013 environment remains valid in the Skype for Business Server 2015 environment.
SIP domains are migrated from Lync to Skype for Business 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 campaigns (queues) and recorder endpoints and their associated SIP URIs and PSTN dial-in numbers are at hand.
There are no secondary CE servers; there is no high availability on CE side

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” means the same FQDN in this case, too.

Preparation

Shutting Down CE Services

Log on to the CE Core Host with local administrator privileges.
Using the CE Server Manager tool stop CE components both on the CE Core Host and the CE Recorder Host.
Close CE Server Manager.

Removing CE Specific Configuration from the Lync Server 2013 Topology

Log on to one of the the Lync 2013 Front-End Servers with CsAdministrator privileges.
Launch the Lync Server 2013 Management Shell.
Remove CE campaign and recorder endpoints by executing the following command repeatedly (using the campaign and recorder endpoint URIs):
```
Remove-CsTrustedApplicationEndpoint -Identity [endpoint SIP URI]
```

Remove CE core application by executing the following command:

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

Remove CE recorder application executing the following command:

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

Remove CE core application pool by executing the following command:

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

Remove CE recorder pool by executing the following command:

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

Upgrading the Lync Server 2013 Infrastructure to Skype for Business Server 2015

Perform in-place or side-by-side upgrade from Lync Server 2013 to Skype for Business Server 2015 by following the associated documents from Microsoft.

Migrating CE

Recreating CE Specific Configuration in the Skype for Business Server 2015 Topology

Log on to one of the Skype for Business 2015 Front-End Servers with CsAdministrator privileges.
Launch the Skype for Business Server Management Shell.

Execute the following command:

New-CsTrustedApplicationPool -Identity [FQDN of the CE Core Host] -Registrar [FQDN of the Skype for Business Front-End pool] -Site [Lync SiteId]

You can list your Skype for Business site ids using the Get-CsSite cmdlet

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 to as CECoreGruu.

Use the following command to recreate the same campaign endpoints which were removed from the Lync Server 2013 topology:

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

Execute the following command (note: you do not need to execute this command if CE core and recorder components are loated on the same Windows Server):
```
New-CsTrustedApplicationPool -Identity [FQDN of the CE Recorder Host] -Registrar [FQDN of the Skype for Business Front-End pool] -Site [Lync SiteId]
```
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 to as CECoreGruu.

Use the following command to recreate the same recorder endpoints which were removed from the Lync Server 2013 topology:

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

Upgrading CE Servers from UCMA 4.0 to UCMA 5.0

Perform the following steps both on the CE Core Host and CE Recorder Host

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

Upgrading CE Server Software

Upgrade CE to the latest version following all the steps described in the Upgrade Guide. Please make sure you select the Upgrade to SfB Platform option.

Associating CE with the New Skype for Business Server 2015 Pool

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

Execute the following command:

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

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

Execute the following command:

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

Log on to the CE Portal website and open the Infrastructure → Voice Infrastructure → Voice Gateways screen.
Set the FQDN property to the FQDN of the Skype for Business 2015 Front-End pool.
Open up the Infrastructure → Recording → Recording Gateways screen and provide the Media serverFQDN and Signaling server FQDN properties to the FQDN of the Skype for Business 2015 Front-End pool.

Starting up CE services

Log on to the CE Core Host with local administrator privileges.
Use the CE Server Manager tool to start each CE component on both the CE Core Host and CE Recorder Host servers.