#LYNC 2013 UPGRADE TO SKYPE FOR BUSINESS HOW TO#

There are no secondary CE servers there is no high availability on CE side.

The list of CE campaigns (queues) and recorder endpoints and their associated SIP URIs and PSTN dial-in numbers are at hand.

PSTN dial-in numbers assigned to CE campaigns remain unchanged during the migration.

Lync user accounts designated as CE agents are migrated without changing their AD distinguished names and their SIP URI.

SIP domains are migrated from Lync to Skype for Business without changing the domain names.

Host certificates issued for the CE servers in the Lync Server 2013 environment remains valid in the Skype for Business Server 2015 environment.No need to communicate with both Lync Server 2013 pool and Skype for Business Server 2015 pool at the same time. 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.The process described below assumes the followings:

There might be alternative approaches for this migration, however this is the tested approach introducing the least risk and therefore endorsed by Geomant. associating CE with the new Skype for Business 2015 pool.upgrading CE and the underlying UCMA runtime.recreating CE specific configuration in the Skype for Business Server 2015 topology.upgrading the Lync Server infrastructure to Skype for Business.removing CE specific configuration from the Lync Server 2013 topology.terminating the association between the Lync Server 2013 pool and CE.

#LYNC 2013 UPGRADE TO SKYPE FOR BUSINESS HOW TO#

This chapter describes how to migrate CE from a Microsoft Lync Server 2013 pool to a Microsoft Skype for Business Server 2015 pool. Contact Expert v7.1 for Skype for Business Server Migrating Contact Expert from Microsoft Lync 2013 to Microsoft Skype for Business 2015 Objectives

Lync 2013 upgrade to skype for business