Module 12

Planning a Migration to Lync Server 2013

MVA Jump Start

Module Overview

• Overview of Coexistence and Migration

• Migration Steps
• Planning for Clients and Devices
• Designing a Client Migration and Device Migration Strategy
Lesson 1: Overview of Coexistence and Migration

• Overview of Migration
• Migration Approach
• Support Boundaries
• Pre-requisites for Migration
• Overview of Service Migration
• Voice Routing Coexistence
• Migrating from Legacy Versions
Overview of Migration

• Lync Server 2013 migration refers to migrating users and devices,

and not upgrading
• The benefits of migration versus upgrading are huge
• Migration results in clean installation where there are no leftovers
from earlier versions
• Migration in Lync Server 2013 may also be migrating from an
existing voice infrastructure to Lync Server 2013
Terms

• Migration
– Moving your production deployment from a previous version of Office
Communications Server 2007 R2/Lync 2010 to Lync Server 2013
• Upgrade
– Installing a newer version of software on a Server or client computer

• Coexistence
– The temporary environment that exists during migration when some
functionality has been migrated to Lync Server 2013 and other functionality
still remains on a prior version (Office Communications Server 2007 R2/Lync
2010)
• Interoperability
– The ability of your deployment to operate successfully during the period of
coexistence
Migration Approach

Lync Server 2013 infrastructure deployed side-by-side with existing

infrastructure
• Similar to previous migrations
• In place upgrade not supported

Migrate Side-by-side, Site-by-site

• Ensures service continuity, low end user impact
• Enables rollback, resiliency to logistical issues

Build  Pilot  Production

• Minimize initial hardware requirements
• Trial builds administrator and end user confidence and minimizes risk
Support Boundaries

Server supports migration from N-1 or N-2

• N (15): Lync 2013
• N-1 (14): Lync 2010*
• N-2 (13): Office Communications Server (OCS) 2007 R2*
Client support depends on workload
• N-1 client (Lync 2010) against Lync Server 2013
• N client (Lync 2013) against Lync 2010 Server
Voice Coexistence
• Support Legacy Mediation Servers (N-1, N-2)
• Lync 2013 SBA cannot use the Lync 2010 Pool

* With latest Updates

Support Boundaries

Persistent Chat supports migration from

• N-1 (14): Lync 2010* Group Chat
• N-2 (13): Office Communications Server (OCS) 2007 R2* Group Chat
Persistent Chat Client support
• N-1 chat client (Lync 2010) against Lync 2013 Persistent Chat Server
• N-2 chat client (Communicator 2007 R2) against Lync 2013 Persistent Chat Server
Lync 2013 cannot connect to Legacy Group Chat Servers

* With latest Updates

Pre-requisites for Migration

• Topology requirements
• Microsoft OCS 2007 R2 / Lync 2010 Server and Client updates
• Microsoft SQL Server
• Telephony pre-requisites
Overview of Service Migration

Company ISV/developed applications

Microsoft Unified Communications Application Server
Response Groups
Dial-in Conferencing
Exchange Server Unified Messaging
Voice Routing Coexistence
Outbound Calls Survivable Branch Appliance (SBA)
Home Mediation Lync 2010 Lync 2013
Server Server Pool Pool
Lync Server 15 15 Supported
2013 Lync 2010 Supported Supported *
SBA
Lync Server 15 14 Supported
2013 – Lync 14 15 Supported Lync 2013 Not Supported
Server 2010
SBA Supported
Lync Server 15 13 Supported
2013 – OCS 13 15 Not * Contents from 2010 SBA will write monitoring and
2007 R2 Supported archiving contents to Lync 2010 store

Inbound Calls
Mediation Next Hop Server Home Server
Server
Lync Server 2013 15 15 15 Supported
15 15 14 Supported
Lync Server 2013 – Lync 14 14 15 Supported
Server 2010
15 15 13 Supported
Lync Server 2013 – OCS 15 15 13 Supported
2007 R2
13 13 15 Supported
Migrating from Legacy Versions
Lync Server 2010
Uses CMS (Central Management Store)
Lync 2010 client, no Live Meeting client
Easy migration path
OCS 2007 R2
No CMS (Central Management Store)
Configuration stored in Active Directory
Live Meeting and Office Communicator
client
Migration to Lync Server 2013 similar to
Lync 2010 migration
Migrating From Lync Server 2010

Topology
• Download existing topology in Lync Server
2013 Topology Builder
• Define new Lync 2013 Pool & publish the
new topology
• Use Lync Server 2013 Topology Builder,
Lync 2010 topology builder cannot be used
Configuration
• Data exists in Lync 2010 (CMS)
• Lync Server 2013 uses Lync 2010 CMS
instance
Users (Performed on Lync 2013 System)
• Via Lync Server Control Panel
• From Management Shell:
Move-CsLegacyUser
• Rollback from Management Shell:
Move-CsUser
Migrating From Office Communicator Server 2007 R2

Topology Users
• Merger topology using the Topology • Via Lync Server Control Panel
builder • From Management Shell: Move-CsLegacyUser
• Imports Legacy topology and • Roll back from Management Shell: Move-CsUser
conference directories
• Rerun when Legacy topology changes
• Publish the new topology

Configuration
• Merge other configuration from
Lync Management Shell:
Import-CsLegacyConfiguration
• Rerun when legacy configuration has
changed with -ReplaceExisting
Lesson 2: Migration Steps

• Overview of Migration Steps

• Defining a Site and Server Migration Strategy
• Process of Migrating to Lync Server 2013
• Additional Considerations
• Deactivating and Migrating Office Communications Server 2007 R2
• Best Practices for Designing a Migration Strategy
• Discussion: Best Practices for Pilot Implementation
Overview of Migration Steps

Prepare for deployment

• Plan sequence: site-by-site and side-by-side
• Deploy most recent updates, backup Legacy deployment
• Prep Active Directory schema, prep, domain AD DS forest
Start in the first site, migrate pools side-by-side
• Pilot Pool
• Pilot Edge and Director
• Take Pool in production
• Take Edge Servers in production
• Repeat for remaining Pools
Pick next site, repeat side-by-side
Defining a Site and Server Migration Strategy

• Sequence deployment • Start with site containing • Scales down for non-global
site by site federated Edge deployment
Process of Migrating to Lync Server 2013 Stage 1

Plan
• Define migration strategy
• Select sites, locations
• Identify users and define migration groups
Process of Migrating to Lync Server 2013 Stage 2

Prepare Legacy Legacy

Remote Access Federation
• Deploy most recent updates
Production
(Clients/Server) Apply
• Backup Legacy deployment updates Legacy
Edge
• Run Best Practice Analyzer and
ensure healthy deployment Apply Legacy
updates Director
• Upgrade AD DS schema, forest,
domain preparation
Apply
updates Legacy Pool

Upgrade Active
schema Directory
Process of Migrating to Lync Server 2013 Stage 3

Introduce first Lync Server 2013

Legacy Legacy & latest
Pool Remote Access Federation
• Deploy pilot Lync 2013 Pool side-by-side
with existing deployment
Production Pilot
• Activation of Lync Server 2013 adds
product references into Legacy Active Legacy
Directory Edge
• Does not require deployment of all Front
End Servers Legacy
• For OCS 2007 R2 Only: Director
Lync front end pool
Merge 2007R2 toplogy onto CMS
Merge-CsLegacyTopology
Import the configuration items:Import- Legacy Pool
CsLegacyConfiguration

Active
Directory
Process of Migrating to Lync Server 2013 Stage 4

Routing Legacy Legacy & latest

• Mixed version routing from Lync Remote Access Federation
2013 Pool to Legacy Director
Production Pilot
• External access through Legacy
Director and Legacy Edge Server
Legacy
Edge

Legacy
Director Lync front end pool

Legacy Pool

Active
Directory
Stage 4 continued

Pilot with subset of

users
Subset of users moved to Lync Production Pilot
2013 Pool R2 Only:
Merge-CsLegacyTopology
Majority of users remain on Legacy Import-CsLegacyConfiguration
Legacy Pool Edge Import-CsLegacyConferenceDirectory
Move-CsLegacyUser
Validate functionality and
interoperability
Deploy Lync 2013 clients to some Legacy
Director front end pool
trial users on Lync 2013 Pool,
Legacy clients for others

Legacy Pool
Back end

Active
Directory
Process of Migrating to Lync Server 2013 Stage 5

Introduce the Lync 2013

Edge Servers Legacy Legacy & latest Latest
Remote Access Federation Remote Access
• Deploy Lync 2013 Edge Server in
parallel to the existing Legacy Production Pilot
deployment
• Optional, deploy Lync 2013 Legacy Latest Edge
Director Edge

Legacy Latest
Director Director

front end pool

Legacy Pool

Back end

Active
Directory
Stage 5 continued

Routing & Validation

• Route Lync 2013 remote access through Legacy Legacy & latest Latest
Lync 2013 Director (if applicable) Remote Access Federation Remote Access
• Route Lync 2013 federation through Production Pilot
Legacy Edge Server and Director (if
applicable)
Legacy Latest Edge
• Keep federation and remote access
through Legacy edge Server and Edge
Director
• Validate all remote access scenarios Legacy Latest
(except Federation) Director Director

front end pool

Legacy Pool

Back end

Active
Directory
Process of Migrating to Lync Server 2013 Stage 6

Scale Pool to Legacy Latest Legacy & latest

production Remote Access Remote Access Federation

• Expand hardware in Lync Server Production Pilot

2013 Pool to handle remaining
users from Legacy Pool
Legacy Latest Edge
• No changes to existing routing
Edge
• No changes to coexistence

Legacy Latest
Director Director

front end pool

Legacy Pool

Back end

Active
Directory
Process of Migrating to Lync Server 2013 Stage 7

Move all users to new Pool Latest

Legacy Legacy & latest
• Lync 2010 Legacy Remote Access Remote Access Federation

• Move-CsUser
Production Pilot
• OCS 2007 R2 Legacy
• Move-CsLegacyUsers
Legacy Latest Edge
Edge

Legacy Latest
Director Director

front end pool

Legacy Pool

Back end

Active
Directory
Process of Migrating to Lync Server 2013 Stage 8

Migrate other Pools and Sites

• Using the same methodology, migrate remaining Pools within the first site and
other sites
Process of Migrating to Lync Server 2013 Stage 9

Enable Lync 2013 Edge

Latest Legacy & latest
for production Remote Access Federation
• Route remote access to Lync 2013 edge
Production
• Route federation through the Lync
2013 edge
• Deactivate Legacy Edge, unmerges Latest Edge
Legacy from AD DS
• Uninstall Legacy Edge, recover
hardware Latest
Director
• Merge Topology Wizard to remove
Legacy topology from Lync Server 2013
CMS
Latest Pool

Active
Directory
Additional Considerations

Post Migration
• Migrate Dial-in Access Numbers
• Migrate Address Book (Company_Phone_Number_Normalization_Rules.txt)
• Configure the Meeting Join Page
• Deploy Lync 2013 Clients
• Relocate the Central Management Store

Additional Actions
• Archiving and Monitoring Servers
• Trusted Application Servers
• Enterprise Voice, Mediation Servers, Gateways and SBA’s
• And much more….
Deactivating and Migrating Office Communications Server 2007 R2

To ensure that Active Directory settings are cleaned up when removing the Office
Communications Server 2007 R2 environment, you need to:

• Deactivate server roles to remove associated Active Directory objects

• Remove Enterprise Pools (if using Enterprise Edition)

• Uninstall server components

• Clean up file shares and databases

Best Practices for Designing a Migration Strategy

Pilot user groups

Edge routing
Firewall
DNS-based load balancing support
Dual administration during coexistence
Discussion: Best Practices for Pilot Implementation

• How do you select pilot users?

• How do you get feedback from users?
• How can helpdesk be used in a pilot?
Lesson 3: Planning for Clients and Devices

• Discussion: Assess Business Requirements for Clients and Devices

• Types of Lync Server 2010 Clients and Devices
• Coexistence Options for Clients
• Planning for Client Version Policies
• Planning for Device Support and Device Requirements
Discussion: Assess Business Requirements for Clients and Devices

• Identify the types of clients

• Evaluate the functionality
• Examine the client and device usage
• Assess the deprecation or replacement of features
Types of Lync Server 2010 Clients and Devices

Lync 2013 Server

• Supports Lync 2010 and Lync 2013 clients
• Compatible with OCS 2007 R2
• Lync Web App is supported only for Lync 2013 (and conferencing only)

Lync Server 2010

• New: Supports Lync 2013 client to allow customers to update Office to Office 2013
before upgrading Lync Servers to Lync 2013
• Also supports OCS 2007, OCS 2007 R2, Lync 2010 clients
Coexistence Options for Clients

Evaluate the affect on users and the client software:

• Changes to Online Meetings in Lync Server 2013

• Default Lync Server 2013 Meeting Options
• Lync Server 2013 Meeting Clients
• Migrating Existing Meetings and Meeting Content
• User Experience during Migration - Before installing Lync Server 2013
• User Experience during Migration - After installing Lync Server 2013
• Meetings with Federated Organizations that Use Previous Clients
• Lync Server 2013 Compatibility with Meetings on Earlier Versions of Office Communications
Server
• Configuring the Meeting Join Webpage
Planning for Client Version Policies

• Client Version Policies enable you to define a set of rules that specify the client
versions that your Lync Server 2013 environment supports.
• When planning for use of Client Version Policies, evaluate the client versions
that are currently in use in the environment that you want to migrate to Lync
Server 2013.
• When migrating your users to Lync Server 2013, plan for deploying the new
client software to these users.
• After deploying Lync 2013 client software, build policies that disallow using the
previous version clients outright, or direct these to download links for updated
client software.
Planning for Device Support and Device Requirements

System and Infrastructure Requirements for Lync Devices

• Power over Ethernet

• LLDP-MED
• Network & Port Requirements
• DNS Requirements
• DHCP Requirements
• Certificates
Lesson 4: Designing a Client Migration and Device Migration Strategy

• Designing Group Policy

• Designing Policies for Devices
• Designing a Software Deployment Strategy
• Client Deployment Strategy
• Live Meeting
• Best Practices for Client, Device, and User Migrations
Designing Group Policy

To design your Group Policy and in-band provisioning settings, you

should:
• Evaluate current Group Policy settings
• Review available client configuration options in Lync Server 2013
• Determine the changes that are needed to current policy settings
• Configure bootstrapping policies for Lync Server 2013
• Configure Lync 2013 client policies
Designing Policies for Devices

When you design policies for phone devices, you should consider
the following:
• The usage profile of the phone devices for which you are designing
policies
• The physical locations where the devices will be located
• The calling features that should be enabled or disabled
• Enabling of hotdesking if common area phones are deployed
Designing a Software Deployment Strategy

When designing for the deployment of Web App and Attendee

clients, you should:
• Decide if you want to support both types of clients
• Always aim to leverage existing software distribution method, which may be
in use in your environment
• Adhere to corporate policies for software distribution
• Decide whether to provide the standard download links or links that are
hosted on your environment
Client Deployment Strategy

Minimum OS support for Lync 2013 is Windows 7 or later, or

Windows Server 2008 SP2 or later

Can deploy Lync 2013 client with Office install/upgrade or standalone

Two paths to deploy client:

• Office/Lync 2013 deployment first, then update Servers (assumes Lync 2010
Servers)
• Update Servers first, then deploy Office/Lync 2013
Live Meeting

Lync 2013 removes the Live Meeting data multipoint control unit (MCU) and
therefore Live Meeting client support
• Use OCS 2007 R2 Outlook Conferencing add-in for Live Meeting Service Meetings (or Live Meeting Service Web
user interface [UI])
While OCS 2007 R2 client (and Outlook add-in) are installed:
• Users homed on OCS 2007 R2 or Lync 2010 Servers can continue to schedule and use Live Meeting

After Lync 2013 is installed and user is homed on Lync 2013 Server:
• Scheduling new Live Meetings is not available - use Lync Online Meeting
• Live Meetings previously on your calendar will not work
• Users must reschedule their Live Meetings to Lync meetings
• Standalone tool planned to assist in migrating meetings in bulk
Best Practices for Client, Device, and User Migrations

The Lync Server 2013 environment should be fully configured before migrating
users
Do not deploy Lync 2013 clients prior to moving users
Educate users on the new conferencing clients prior to deployment
Move users in logical groups
Always do pilot client, device and user migrations
Ensure consistent security update levels for clients and devices across your
deployment.
Module Review and Takeaways

• Review Question(s)
• Real-world Issues and Scenarios
• Tools
©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be
registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the
current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this
presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.