Embed Size (px)
Citation preview
Source: walkaboutbydesign.blogspot.co.uk
Source:tumblr.com
Source: girlonraw.com
Source: Wikimedia.org
Source: eat-drink-fly.com
Source:lhs204.stellpflug.com
Source:buzzfeed.com
Source:thelife-animal.blogspot.co.uk
Quiz!How species of spiders are there in Australia?
A – 10B – 500C - 2000
Source: Wikimedia.org
Source:thechinawatch.com
Source:rosettathurman.com
Migration and Coexistence with Microsoft Lync Server 2013Justin MorrisLync MVP and Senior ConsultantModality Systems
OUC-B334
Agenda
AgendaInitial Migration ConsiderationsMigrating from OCS 2007 R2Migrating from Lync Server 2010What about R2+2010 Environments?Client Coexistence and InteroperabilityUnderstanding the Autodiscover ServiceEdge Server MigrationExternal Web Services MigrationGroup Chat MigrationMobility CoexistenceLync Management during CoexistenceBespoke Migration ScenariosKey Takeaways
Initial Migration Considerations
Initial Migration ConsiderationsWhat version are you migrating from?Which features/what topology will you deploy?Deploy and migrate ”inside-out”Internal servers first (Front End pool, Mediation Servers, etc)Edge Servers last
Initial Migration ConsiderationsA/V Conferencing Server and Monitoring Server are now collocatedNew SQL databases cannot be deployed on existing instances used by previous versionsTri-existence is not supported
Migrating from OCS 2007 R2
Migrating from OCS 2007 R21. Install latest cumulative updates on OCS 2007
R2 servers2. Apply AD updates and define Lync topology3. Deploy Lync Server 2013 pool4. Merge OCS 2007 R2 topology into Lync topology5. Import legacy policies and settings6. Configure Lync Server 2013 pool7. Migrate users8. Complete Post-Migration Tasks9. Decommission OCS 2007 R2
Merge OCS 2007 R2 TopologyPopulates Lync topology with all legacy OCS 2007 R2 serversCreates BackCompatSiteWMI Backwards Compatibility Package required
Source:Modality Systems
Importing Legacy Policies and SettingsImport OCS 2007 R2 voice, conferencing, external access and archiving policies into Lync Server 2013Run cmdlet Import-CsLegacyConfiguration after topology has been mergedOnce imported, legacy policies can be viewed in Lync Server Control Panel
Configure Lync Server 2013 PoolConnect to Legacy Edge Servers in Topology BuilderConfigure Legacy Edge Servers to allow connections from Lync Server 2013 poolConfigure any new policies and configurations
Migrate UsersMove-CsLegacyUserHow will you migrate – scripting?Assign any new policiesSend communication and provide training
Complete Post-Migration TasksMigrate Response GroupsMigrate Dial-In Access NumbersMigrate Voice RoutesMove Exchange UM Contact ObjectsRemove Legacy Archiving and Monitoring ServersDeploy Lync 2013 Clients
Decommission OCS 2007 R2Move Conference DirectoriesUpdate DNS SRV RecordsDecommission OCS 2007 R2 ServersRemove BackCompatSite from Topology
Migrating from Lync Server 2010
Migrating from Lync Server 20101. Install latest cumulative updates on all
Lync Server 2010 servers2. Apply AD updates and download topology
from existing deployment3. Define and deploy Lync Server 2013 pool4. Migrate users5. Complete Post-Migration Tasks6. Decommission Lync Server 2010
Migrate UsersMove-CsUser -MoveConferenceDataHow will you migrate – scripting?Assign any new policiesSend communication and provide training
Complete Post-Migration TasksMigrate Existing Meetings and Meeting ContentMigrate Dial-In Access NumbersMigrate Call Park SettingsMigrate Response GroupsMigrate Common Area Phones and Analogue DevicesRedeploy Survivable Branch AppliancesDeploy Lync 2013 Clients
Redeploy Survivable Branch AppliancesMove branch users to another poolRemove Lync Server 2010 SBA from topologyAdd Lync Server 2013 SBA to topology and configure FE pool as Backup RegistrarMove users back to the new SBA
Decommission Lync Server 2010Update DNS SRV RecordsMove the CMS to Lync Server 2013Remove Archiving and Monitoring ServersRemove Lync Server 2010 Pool and SQL Server databases
Migrating the CMS to Lync Server 2013Prepare the Lync Server 2013 pool for the CMS:Install-CsDatabase -CentralManagementDatabase -SQLServerFQDN <FQDN of your SQL Server> -SQLInstanceName <name of instance>
Move the CMS from 2010 to 2013 pool:Move-CsManagementServer
Verify replication has completed:Get-CsManagementStoreReplicationStatus
Remove the CMS databases from the 2010 pool:Uninstall-CsDatabase -CentralManagementDatabase -SqlServerFqdn <FQDN of SQL Server> -SqlInstanceName <Name of source server>
What about R2+2010 Environments?
What about R2+2010 Environments?Decommission Lync 2010, Move to Lync 2013 Move to 2010, Decommission R2 and Move to
2013
Client Strategy
• R2 clients can use 2013 server for IM/P• Live Meeting console will NOT work against
2013 server• Lync Client will need to be deployed at
migration• Live Meeting meetings will need to be
rescheduled• R2 users can attend Lync meetings via LWA
• R2 clients can use 2010 server for IM/P/Live Meeting meetings
• Live Meeting console client will work against 2010 Server
• Live Meeting meetings will need to be rescheduled
Server Strategy
• Decommission Lync 2010• Build parallel 2013 server infrastructure• Migrate OCS 2007 R2 users to 2013
• Migrate R2 users to 2010• Decommission OCS 2007 R2• Migrate 2010 users to 2013
Advantages • Single Server Migration • Managed migration for Live Meeting meetings
Disadvantages
• Multiple client migrations• Requires decommission and rollback of all
2010 clients
• Two server migration
Recommended Approach
• Recommended for customers who are not heavy users of conferencing features in OCS 2007 R2 today
• Recommended for customers who are heavy users of conferencing features in OCS 2007 R2 today
Client Coexistence and Interoperability
Client Coexistence and InteroperabilityClient Lync Server 2013 Lync Server 2010 Office Communications
Server 2007 R2
Lync 2013 Supported Supported Not Supported
Lync Web App 2013 Supported Not Supported Not Supported
Lync 2010 Supported Supported Not Supported
Lync 2010 Attendant Supported Supported Not Supported
Lync 2010 Group Chat Interoperable, manual config required
Supported Not Supported
Lync Web App 2010 Not Supported Supported Not Supported
Lync 2010 Attendee Not Supported Supported Not Supported
Office Communicator 2007 R2
Interoperable, only for IM Supported Supported
OCS 2007 R2 Attendant Not Supported Supported Supported
Office Communicator 2007 Not Supported Supported Supported
Live Meeting 2007 Not Supported Supported Supported
Lync 2013 Client ConsiderationsLync 2013 not supported on Windows XP or VistaOffice 2007 not supportedLive Meeting not supported against Lync Server 2013No Gallery View on OC 2007 R2 or Lync 2010
Server or Client First? You decideLync 2013 can connect to Lync Server 2010Lync 2010 can connect to Lync Server 2013Provides added flexibility when planning client migration – independent of server migrationN.B. User will only see Lync 2013 features when homed on a 2013 pool
What happens to Attendee?Lync Attendee no longer necessaryAll attendees joining conferences without Lync 2013 installed will use Lync Web App 2013
Changes to Lync Phone EditionNo new devices expectedExisting Aries devices will work with Lync Server 2013Latest firmware works with both Lync Server 2010 and 20133PIP – 3rd Party IP Phone. Story is developing
Understanding the Autodiscover Service
Understanding the Autodiscover ServiceLync 2013 clients (including Windows 8 app) will attempt to connect to:lyncdiscoverinternal.contoso.comlyncdiscover.contoso.com
New clients use Autodiscover service to locate their registrar. SRV record is being de-emphasizedlyncdiscoverinternal A record must point to internal pool
Edge Server Migration
Edge Server MigrationTwo options:Rip and ReplaceSide by Side Transition
FederationUsing closed federation? Update your partner organizations
Public IM ConnectivityProviders need to be notified if Access Edge FQDN changes
External Web Services Migration
External Web Services MigrationCreate two new web publishing rules: One that publishes external web services URL of the Lync Server 2013 poolOne that publishes external web farm URL of Office Web Apps pool
Point Simple URLs at Lync Server 2013 Director/Front End Pool Virtual IP
Group Chat Migration
Group Chat MigrationDeploy the Lync 2013 Persistent Chat ServerMigrate legacy chat room dataDecommission the legacy Group Chat servers
Migrating Legacy Chat Room DataStop services on all legacy Group Chat serversExport all legacy chat room data:Export-CsPersistentChatData -DbInstance <LegacySQLServerFQDN> -Filename <filepath>
Stop services on all Lync Server 2013 Persistent Chat servers
Migrating Legacy Chat Room DataImport legacy chat room data:Import-CsPersistentChatData -DbInstance <NewSQLServerFQDN> -Filename <filepath>
Port the Lookup Server URI to Lync Server 2013Delete [email protected] with same URI
Start services on Lync Server 2013 Persistent Chat servers
Decommission Legacy Group Chat ServersUninstall Group Chat from legacy serversRemove trusted application and trusted application pool entries from topology
Mobility Coexistence
Mobility Coexistence
Lync Server 2010 with Mobility
Service
Lync Server 2013 (prior to CU1 update)
Lync Server 2013, CU1 –
Mobility Enabled
Lync Server 2013, CU1 –
Mobility Disabled
Lync 2010 mobile clients
Notification to upgrade to the latest version of
the mobility client.
Error: “Can’t sign in because you are not setup to use
Lync 2013. Please contact your
support team.””
Lync 2013 mobile clients
Error: “You can't sign in with this version of Lync.
Please install Lync 2010.”
Error: “You can't sign in with this version of Lync. Please install Lync 2010.”
Error: “Can’t sign in because you are not setup to use
Lync 2013. Please contact your
support team.””
Lync Management During Coexistence
Lync Management during CoexistenceAny new changes to OCS 2007 R2 topology require re-mergeOnce Lync Server 2013 has been deployed, Lync Server 2010 tools can no longer be used
Bespoke Migration Scenarios
Bespoke Migration ScenariosSituations where Front End pools cannot be easily migrated (cross-forest, mergers/acquisitions)Leverage dbimpexp.exe and Import-CsUserDataGroup Chat Database Lift-and-Shift
Key Takeaways
Key TakeawaysTri-existence is not supported, so know before you goPlan your client/server deployments and migrations well. Do you need to double hop?Understand new client access via Autodiscover service
Q&A
Related contentBreakout Sessions (session codes and titles)
Hands-on Labs (session codes and titles)
Book - Lync Server 2013 Unleashed
Related Certification Exam
Find Me Later at the Lync booth and on Twitter @justimorris
msdn
Resources for Developers
http://microsoft.com/msdn
Learning
Microsoft Certification & Training Resources
www.microsoft.com/learning
TechNet
Resources
Sessions on Demand
http://channel9.msdn.com/Events/TechEd
Resources for IT Professionals
http://microsoft.com/technet
Evaluate this session
Scan this QR code to evaluate this session.
© 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.
