1. Microsoft ® Lync Ignite Microsoft Lync 2013

7. * With Latest Updates

9. Home ServerMediation Server Lync Server 201315 Supported Lync Server 2013—Lync Server 2010 1514Supported 1415Supported Lync Server 2013—OCS 2007 R2 1513Supported 1315Not Supported Mediation ServerNext Hop ServerHome Server Lync Server 201315 Supported Lync Server 2013—Lync Server 2010 15 14Supported 14 15Supported Lync Server 2013—OCS 2007 R2 15 13Supported 13 15Supported Outbound Calls Inbound Calls ** Assume certified Gateways for the release of MS shown in the tables above Lync 2010 PoolLync 2013 Pool Lync 2010 SBASupportedSupported * Lync 2013 SBANot SupportedSupported * Contents from 2010 SBA will write monitoring and archiving contents to Lync 2010 store Survivable Branch Appliance (SBA)

10. 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

15. State 1: Plan sequence: site by site, side by side

16. Plan Define migration strategy Select sites, locations Identify users and define migration groups

17. 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 Apply updates Legacy Pool Upgrade schema Production Legacy Director AD Legacy Federation Legacy Remote Access Legacy Edge

18. Legacy Remote Access ProductionPilot Latest Pool Legacy Director AD Front end Back end Legacy Pool Legacy Edge Legacy and Latest Federation 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

19. Legacy Remote Access ProductionPilot Latest Pool Legacy Director AD Front end Back end Legacy Pool Legacy Edge Legacy and Latest Federation Routing Mixed version routing from Lync 2013 pool to Legacy Director External access through Legacy Director and Legacy Edge Server

20. Legacy Remote Access Production Legacy Pool Legacy Edge Legacy Director AD Legacy Federation 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 Front End Back End Latest Pool Pilot R2 Only: Merge-CsLegacyTopology Import-CsLegacyConfiguration Import-CsLegacyConferenceDirectory Move-CsLegacyUser

21. Legacy Remote Access ProductionPilot Legacy Director AD Latest Remote Access Legacy Pool Legacy Edge Latest Pool Front end Back end Latest Director Latest Edge Legacy and Latest Federation Introduce the Lync 2013 Edge Servers Deploy Lync 2013 Edge Server in parallel to the existing Legacy deployment Optional, deploy Lync 2013 Director

22. Legacy Remote Access ProductionPilot Legacy Director AD Latest Remote Access Legacy Pool Legacy Edge Latest Pool Front end Back end Latest Director Latest Edge Legacy and Latest Federation 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)

23. Legacy Remote Access Production Legacy Director Legacy and Latest Federation AD Latest Remote Access Legacy Pool Legacy Edge Latest Pool Front end Back end Latest Director Latest Edge 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

24. Legacy Remote Access Production Legacy Director Legacy and Latest Federation AD Latest Remote Access Legacy Pool Legacy Edge Latest Pool Front end Back end Latest Director Latest Edge Move all users to new pool Lync 2010 Legacy Move-CsUser OCS 2007 R2 Legacy Move-CsLegacyUsers

25. Production Legacy Remote Access Pilot Latest Pool Front end Back end Production Legacy and Latest Federation Production Legacy Director Legacy Pool Legacy Edge Latest Pool Front end Back end Production Legacy Director Legacy Pool Legacy Edge Latest Remote Access Legacy and Latest Federation Latest Remote Access Legacy and Latest Federation AD Legacy Remote Access Legacy and Latest Federation Latest Pool Front end Back end Latest Director Latest Edge Latest Pool Front end Back end Latest Director Latest Edge Migrate other pools and sites Using the same methodology, migrate remaining pools within the first site and other sites

26. 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 Pool Production Latest Director AD Legacy & Latest Federation Latest Remote Access Latest Edge

33. Feature Client IMPresenceVoiceVideoApp Sharing*File Transfer** Lync 2013 Rich Client XXXXXX Lync 2013 Web App N/A – conference only until 15.1 which will support sign in Lync 2013 Mobile XXX X Lync 2013 Phone Edition XX Lync 2010 Rich Client XXXXXX Lync 2010 Web App N/A—conference only Lync 2010 Attendee N/A—conference only Lync 2010 Attendant XXX Lync 2010 Mobile XX Lync 2010 Phone Edition XX Office Communicator 2007 R2 Rich Client XXXXXX Public IM Connectivity (PIC) (AOL, Yahoo) XX PIC (Messenger) XXXX * 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)

34. Client/Add-inServer VersionsDetails/Comments Lync 2013 Outlook add-in for Outlook 2003, 2007, 2010, Outlook 2013 Lync Server 2013 Lync Server 2010* * Older versions need to maintain existing feature support (no new Lync 2013 features) Lync 2013 web schedulingLync 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 *Needed for postmigration (before clients are upgraded) New in Lync 2013 add-in: Attendee mute controls for audio and video

35. Lync 2013 clients can join Lync 2010 hosted meetings with scaled down, compatible functionality ClientSupportedAuto-JoinComments/details Lync 2013 Rich ClientYYAuto-join via Join Launcher page Lync 2013 Web AppYYAuto-join if a Lync 2013 Rich client is not installed Lync 2013 MobileYYAuto-join via Join Launcher page Lync 2013 Phone Edition Y*Y*When tethered to Lync 2013 Rich client, supports audio Lync 2010 Rich ClientYN Admin configured on Join Launcher page to allow join and auto-join Lync 2010 Web AppN/A—joining to a Lync 2013 Server uses Lync 2013 Web App Lync 2010 AttendeeSupported as an option, but auto-joins with Lync 2013 Web App Lync 2010 MacSupported as an option, but auto-joins with Lync 2013 Web App Lync 2010 AttendantN/A Lync 2010 MobileSupported Lync 2010 Phone EditionSupported Office Communicator 2007 R2 Rich Client Not supported. Lync 2013 Web App auto-joins instead, with A/V support

36. * Navigate, not upload. ** View only for Office PowerPoint content when uploaded by a Lync 2013 Rich client Client People Presence Chat VoiceVideo App share Lync 2010PPT Lync 2013 PPT File Transfer White Board Poll Lync 2013 Rich ClientXXXXXXXXX Lync 2013 Web AppXXXXX*XXXX Lync 2010 Rich ClientXXXXXX**XXX Lync 2010 AttendeeXXXXXX**XXX

38. © 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.