®
Microsoft
Lync Ignite
Microsoft Lync 2013
* With Latest Updates
* With Latest Updates
Outbound Calls
Lync Server 2013
Lync Server 2013—Lync Server 2010
Lync Server 2013—OCS 2007 R2
Survivable Branch Appliance (SBA)
Home Server
Mediation Server
15
15
Supported
15
14
Supported
14
15
Supported
15
13
Supported
13
15
Not Supported
Lync 2010 Pool
Lync 2013 Pool
Lync 2010 SBA
Supported
Supported *
Lync 2013 SBA
Not Supported
Supported
* Contents from 2010 SBA will write monitoring and archiving
contents to Lync 2010 store
Inbound Calls
Lync Server 2013
Lync Server 2013—Lync Server 2010
Lync Server 2013—OCS 2007 R2
Mediation Server
Next Hop Server
Home Server
15
15
15
Supported
15
15
14
Supported
14
14
15
Supported
15
15
13
Supported
13
13
15
Supported
** Assume certified Gateways for the release of MS shown in the tables above
Lync Server 2010
Uses CMS (Central Management Store)
Lync 2010 client, no Live Meeting client
Easy migration path
OCS 2007 R2
No CMS
Configuration stored in Active Directory
(AD)
Live Meeting and Office Communicator
client
Migration to Lync Server 2013 similar to
Lync 2010 migration
State 1: Plan
sequence: site
by site, side by
side
Plan
Define migration strategy
Select sites, locations
Identify users and define migration
groups
Legacy
Remote Access
Prepare
Deploy most recent updates
(clients/server)
Backup Legacy deployment
Run Best Practice Analyzer and ensure
healthy deployment
Upgrade Active Directory Domain
Services (AD DS) schema, forest,
domain preparation
Legacy
Federation
Production
Apply updates
Legacy Edge
Apply updates
Legacy Director
Apply updates
Legacy Pool
Upgrade schema
AD
Introduce first Lync
Server 2013 Pool
Deploy pilot Lync 2013 Pool side by side
with existing deployment
Activation of Lync Server 2013 adds
product references into Legacy Active
Directory
Does not require deployment of all Front
End Servers
For OCS 2007 R2 Only:
Merge 2007R2 topology onto CMS
Merge-CsLegacyTopology
Import the configuration items:
Import-CsLegacyConfiguration
Legacy
Remote Access
Legacy and
Latest Federation
Production
Pilot
Legacy
Edge
Legacy
Director
Front end
Latest
Pool
Legacy
Pool
Back end
AD
Legacy
Remote Access
Legacy and
Latest Federation
Production
Routing
Mixed version routing from Lync 2013 pool
to Legacy Director
External access through Legacy Director
and Legacy Edge Server
Pilot
Legacy
Edge
Legacy
Director
Front end
Latest
Pool
Legacy
Pool
Back end
AD
Legacy
Remote Access
Legacy Federation
Production
Pilot with subset
of users
Subset of users moved to Lync 2013 pool
Majority of users remain on Legacy pool
Validate functionality and interoperability
Deploy Lync 2013 clients to some trial
users on Lync 2013 pool, Legacy clients for
others
Pilot
Legacy
Edge
R2 Only:
Merge-CsLegacyTopology
Import-CsLegacyConfiguration
Import-CsLegacyConferenceDirectory
Move-CsLegacyUser
Latest
Pool Front End
Back End
Legacy
Director
Legacy
Pool
AD
Legacy
Remote Access
Legacy and
Latest Federation
Production
Introduce the Lync
2013 Edge Servers
Deploy Lync 2013 Edge Server in parallel
to the existing Legacy deployment
Optional, deploy Lync 2013 Director
Latest
Remote Access
Pilot
Legacy
Edge
Latest
Edge
Legacy
Director
Latest
Director
Front end
Latest
Pool
Legacy
Pool
Back end
AD
Legacy
Remote Access
Routing and Validation
Route Lync 2013 remote access through
Lync 2013 Director (if applicable)
Route Lync 2013 federation through
Legacy Edge Server and Director (if
applicable)
Keep federation and remote access
through Legacy Edge Server and Director
Validate all remote access scenarios
(except Federation)
Legacy and
Latest Federation
Production
Latest
Remote Access
Pilot
Legacy
Edge
Latest
Edge
Legacy
Director
Latest
Director
Front end
Latest
Pool
Legacy
Pool
Back end
AD
Scale pool to
production
Expand hardware in Lync Server 2013 Pool
to handle remaining users from Legacy
pool
No changes to existing routing
No changes to coexistence
Legacy
Remote Access
Latest
Remote Access
Production
Production
Legacy and
Latest Federation
Legacy
Edge
Latest
Edge
Legacy
Director
Latest
Director
Front end
Latest
Pool
Legacy
Pool
Back end
AD
Move all users to
new pool
Lync 2010 Legacy
Move-CsUser
OCS 2007 R2 Legacy
Move-CsLegacyUsers
Legacy
Remote Access
Latest
Remote Access
Production
Production
Legacy and
Latest Federation
Legacy
Edge
Latest
Edge
Legacy
Director
Latest
Director
Front end
Latest
Pool
Legacy
Pool
Back end
AD
Legacy
Remote Access
Legacy and
Latest Federation
Production
Migrate other pools
and sites
Using the same methodology, migrate
remaining pools within the first site
and other sites
Latest
Remote Access
Legacy and
Latest Federation
Production
Pilot
Legacy
Edge
Latest
Edge
Legacy
Director
Latest
Director
Front end
Legacy
Pool
Front end
Latest
Pool
Back end
Latest
Pool
Back end
AD
Legacy
Remote Access
Legacy and
Latest Federation
Production
Latest
Remote Access
Legacy and
Latest Federation
Production
Legacy
Edge
Latest
Edge
Legacy
Director
Latest
Director
Front end
Latest
Pool
Back end
Legacy
Pool
AD
Front end
Latest
Pool
Back end
Enable Lync 2013
Edge for production
Route remote access to Lync 2013
edge
Route federation through the Lync
2013 Edge
Deactivate Legacy Edge, unmerges
Legacy from AD DS
Uninstall Legacy Edge, recover
hardware
Merge Topology Wizard to remove
Legacy topology from Lync Server
2013 CMS
Latest
Remote Access
Legacy &
Latest Federation
Production
Latest Edge
Latest Director
Latest Pool
AD
-
Feature
Client
Lync 2013 Rich Client
IM
Presence
Voice
Video
App Sharing*
File Transfer**
X
X
X
X
X
X
Lync 2013 Web App
Lync 2013 Mobile
N/A – conference only until 15.1 which will support sign in
X
Lync 2013 Phone Edition
Lync 2010 Rich Client
X
X
X
X
X
X
X
X
X
Lync 2010 Web App
N/A—conference only
Lync 2010 Attendee
N/A—conference only
Lync 2010 Attendant
X
X
Lync 2010 Mobile
X
X
Lync 2010 Phone Edition
X
X
X
X
X
X
X
Public IM Connectivity (PIC) (AOL, Yahoo)
X
X
PIC (Messenger)
X
X
X
X
X
X
X
Office Communicator 2007 R2 Rich Client
X
* App Sharing: Disable new features as appropriate, and handle OCS 2007 R2 Desktop only sharing
** P2P File Transfer works differently with OCS 2007 R2 and Lync 2010 clients (both in IM region, but Lync 2010 uses a media
channel)
Client/Add-in
Server Versions
Lync 2013 Outlook add-in for Outlook
2003, 2007, 2010, Outlook 2013
Lync Server 2013
Lync Server 2010*
Lync 2013 web scheduling
Lync Server 2013
Lync 2010 Outlook add-in
Lync Server 2013
Lync Server 2010
Office Communicator 2007 R2
Conferencing add-in
Lync Server 2013*
Lync Server 2010
OCS 2007 R2
New in Lync 2013 add-in: Attendee mute controls for audio and video
Details/Comments
* Older versions need to maintain existing feature
support (no new Lync 2013 features)
*Needed for postmigration
(before clients are upgraded)
Client
Supported
Auto-Join
Comments/details
Lync 2013 Rich Client
Y
Y
Auto-join via Join Launcher page
Lync 2013 Web App
Y
Y
Auto-join if a Lync 2013 Rich client is not installed
Lync 2013 Mobile
Y
Y
Auto-join via Join Launcher page
Lync 2013 Phone Edition
Y*
Y
*When tethered to Lync 2013 Rich client, supports audio
Lync 2010 Rich Client
Y
N
Admin configured on Join Launcher page to allow join
and auto-join
Lync 2010 Web App
N/A—joining to a Lync 2013 Server uses Lync 2013 Web App
Lync 2010 Attendee
Supported as an option, but auto-joins with Lync 2013 Web App
Lync 2010 Mac
Supported as an option, but auto-joins with Lync 2013 Web App
Lync 2010 Attendant
N/A
Lync 2010 Mobile
Supported
Lync 2010 Phone Edition
Supported
Office Communicator 2007
R2 Rich Client
Not supported. Lync 2013 Web App auto-joins instead, with A/V support
Lync 2013 clients can join Lync 2010 hosted meetings with scaled down, compatible functionality
Video
App
share
Lync
2010PPT
Lync
2013
PPT
File
Transfer
White
Board
Poll
X
X
X
X
X
X
X
X
X
X
X
X
X*
X
X
X
X
Lync 2010 Rich Client
X
X
X
X
X
X**
X
X
X
Lync 2010 Attendee
X
X
X
X
X
X**
X
X
X
People
Presence
Chat
Voice
Lync 2013 Rich Client
X
Lync 2013 Web App
Client
* Navigate, not upload.
** View only for Office PowerPoint content when uploaded by a Lync 2013 Rich client
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, 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.