Justin Morris OUCB334 Source walkaboutbydesignblogspotcouk Source tumblrcom Source girlonrawcom Source Wikimediaorg Source eatdrinkflycom Source lhs204stellpflugcom Source ID: 704920
Download Presentation The PPT/PDF document "Migration and Coexistence with Microsoft..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1Slide2
Migration and Coexistence with Microsoft Lync Server 2013
Justin Morris
OUC-B334Slide3
Source: walkaboutbydesign.blogspot.co.ukSlide4
Source:
tumblr.comSlide5
Source:
girlonraw.comSlide6
Source:
Wikimedia.orgSlide7
Source:
eat-drink-fly.comSlide8
Source:
lhs204.stellpflug.comSlide9Slide10
Source:
buzzfeed.comSlide11
Source:
thelife-animal.blogspot.co.ukSlide12
Quiz!
How species of spiders are there in Australia?
A – 10
B – 500
C - 2000Slide13
Source:
Wikimedia.orgSlide14
Source:
thechinawatch.comSlide15
Source:
rosettathurman.comSlide16
Migration and Coexistence with Microsoft Lync Server 2013
Justin Morris
Lync MVP and Senior Consultant
Modality Systems
OUC-B334Slide17
Migration and Coexistence with Microsoft Lync Server 2013
Justin MorrisLync MVP and Senior Consultant
Modality Systems
OUC-B334Slide18
AgendaSlide19
Agenda
Initial Migration Considerations
Migrating from OCS 2007 R2
Migrating from Lync Server
2010
What about R2+2010 Environments?
Client Coexistence and Interoperability
Understanding the Autodiscover Service
Edge Server Migration
External Web Services
Migration
Group Chat
Migration
Mobility Coexistence
Lync Management during Coexistence
Bespoke Migration Scenarios
Key
TakeawaysSlide20
Initial Migration ConsiderationsSlide21
Initial Migration Considerations
What 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 lastSlide22
Initial Migration Considerations
A/V Conferencing Server and Monitoring Server are now collocated
New
SQL databases cannot be deployed on existing instances used by previous versions
Tri-existence is not
supportedSlide23
Migrating from
OCS 2007 R2Slide24
Migrating from OCS 2007 R2
Install latest cumulative updates on OCS 2007 R2 servers
Apply AD updates and define Lync topology
Deploy Lync Server 2013 pool
Merge OCS 2007 R2 topology into Lync topology
Import legacy policies and settings
Configure Lync Server 2013 pool
Migrate users
Complete Post-Migration Tasks
Decommission OCS 2007 R2Slide25
Merge OCS 2007 R2 Topology
Populates Lync topology with all legacy OCS 2007 R2
servers
Creates
BackCompat
S
ite
WMI Backwards Compatibility Package
required
Source:
Modality SystemsSlide26
Importing Legacy Policies and Settings
Import
OCS 2007 R2 voice, conferencing, external access and archiving policies into Lync Server
2013
Run cmdlet
Import-CsLegacyConfiguration
after topology has been
merged
Once imported, legacy policies can be viewed in Lync Server Control
PanelSlide27
Configure Lync Server 2013 Pool
Connect
to Legacy Edge Servers in Topology
Builder
Configure Legacy Edge Servers to allow connections from Lync Server 2013
pool
Configure any new
policies and configurationsSlide28
Migrate Users
Move-CsLegacyUser
How will you migrate – scripting?
Assign any new policies
Send communication and provide trainingSlide29
Complete Post-Migration Tasks
Migrate Response Groups
Migrate Dial-In Access Numbers
Migrate Voice Routes
Move Exchange UM Contact Objects
Remove Legacy Archiving and Monitoring Servers
Deploy Lync 2013 ClientsSlide30
Decommission OCS 2007 R2
Move Conference Directories
Update DNS SRV Records
Decommission OCS 2007 R2 Servers
Remove BackCompatSite from
TopologySlide31
Migrating from
Lync Server 2010Slide32
Migrating from Lync Server 2010
Install latest cumulative updates on all Lync Server 2010 servers
Apply AD updates and download topology from existing deployment
Define and deploy Lync Server 2013 pool
Migrate users
Complete Post-Migration Tasks
Decommission Lync Server 2010Slide33
Migrate Users
Move-CsUser -MoveConferenceData
How
will you migrate – scripting?
Assign any new
policies
Send communication and provide
trainingSlide34
Complete Post-Migration Tasks
Migrate Existing Meetings and Meeting Content
Migrate Dial-In Access Numbers
Migrate Call Park Settings
Migrate Response Groups
Migrate Common Area Phones and Analogue Devices
Redeploy Survivable Branch Appliances
Deploy Lync 2013
ClientsSlide35
Redeploy Survivable Branch Appliances
Move branch users to another
pool
Remove Lync Server 2010 SBA from
topology
Add Lync Server 2013 SBA to topology and configure FE pool as Backup
Registrar
Move users back to the new
SBASlide36
Decommission Lync Server 2010
Update DNS SRV Records
Move the CMS to Lync Server 2013
Remove Archiving and Monitoring
Servers
Remove Lync Server 2010 Pool and SQL Server
databasesSlide37
Migrating the CMS to Lync Server 2013
Prepare 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> Slide38
What about R2+2010 Environments?Slide39
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 todaySlide40
Client Coexistence and InteroperabilitySlide41
Client Coexistence and Interoperability
Client
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
SupportedSlide42
Lync 2013 Client Considerations
Lync 2013 not supported on Windows XP or Vista
Office 2007 not supported
Live Meeting not supported against Lync Server 2013
No Gallery View on OC 2007 R2 or Lync 2010Slide43
Server or Client First? You decide
Lync 2013 can connect to Lync Server
2010
Lync 2010 can connect to Lync Server
2013
Provides added flexibility when planning client migration – independent of server
migration
N.B. User will only see Lync 2013 features when homed on a 2013
poolSlide44
What happens to Attendee?
Lync Attendee no longer
necessary
All
attendees joining conferences without
Lync 2013 installed will use Lync Web App
2013Slide45
Changes to Lync Phone Edition
No new devices
expected
Existing Aries
devices will work with
Lync Server 2013
Latest firmware works with both Lync Server 2010 and
2013
3PIP – 3
rd
Party IP Phone. Story is developingSlide46
Understanding the Autodiscover ServiceSlide47
Understanding the Autodiscover Service
Lync 2013 clients (including Windows 8 app) will attempt to connect to:
lyncdiscoverinternal.contoso.com
lyncdiscover.contoso.com
New clients use Autodiscover service to locate their registrar. SRV record is being
de-emphasized
lyncdiscoverinternal
A record must point to internal
poolSlide48
Edge Server MigrationSlide49
Edge Server Migration
Two o
ptions:
Rip
and Replace
Side by Side
Transition
Federation
Using closed federation? Update your partner
organizations
Public IM Connectivity
Providers need to be notified if Access Edge FQDN changesSlide50
External Web Services MigrationSlide51
External Web Services Migration
Create
two new web
publishing
rules:
One that publishes external web services URL of the
Lync Server 2013 pool
One that publishes external web farm URL of Office Web Apps pool
Point Simple URLs at Lync Server 2013 Director/Front End Pool Virtual
IPSlide52
Group Chat MigrationSlide53
Group Chat Migration
Deploy the Lync 2013 Persistent Chat
Server
Migrate legacy chat room
data
Decommission the legacy Group Chat
serversSlide54
Migrating Legacy Chat Room Data
Stop services on all legacy Group Chat
servers
Export all legacy chat room data:
Export-CsPersistentChatData -DbInstance <LegacySQLServerFQDN> -Filename <filepath>
Stop services on all Lync Server 2013 Persistent Chat
serversSlide55
Migrating Legacy Chat Room Data
Import legacy chat room data:
Import-CsPersistentChatData -DbInstance <NewSQLServerFQDN> -Filename <filepath>
Port the Lookup Server URI to Lync Server 2013
Delete
ocschat@domain.com
New-CsPersistentChatEndpoint with same URI
Start services on Lync Server 2013 Persistent Chat
serversSlide56
Decommission Legacy Group Chat Servers
Uninstall Group Chat from legacy
servers
Remove trusted application and trusted application pool entries from
topologySlide57
Mobility CoexistenceSlide58
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.””Slide59
Lync Management During CoexistenceSlide60
Lync Management during Coexistence
Any new changes to OCS 2007 R2 topology require
re-merge
Once Lync Server 2013 has been deployed, Lync Server 2010 tools can no longer be
usedSlide61
Bespoke Migration ScenariosSlide62
Bespoke Migration Scenarios
Situations where Front End pools cannot be easily migrated (cross-forest, mergers/acquisitions)
Leverage dbimpexp.exe and Import-CsUserData
Group Chat Database
Lift-and-ShiftSlide63
Key TakeawaysSlide64
Key Takeaways
Tri-existence is not supported, so know before you go
Plan your client/server deployments and migrations well. Do you need to double hop?
Understand new client access via Autodiscover serviceSlide65
Q&ASlide66
Related content
Breakout 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 @
justimorrisSlide67
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 Slide68
Complete an evaluation on CommNet and enter to win!Slide69
Evaluate this session
Scan this QR code
to evaluate this session and be automatically entered in a drawing to
win a prize
Required Slide
*delete this box when your slide is finalized
Your MS Tag will be inserted here during the final scrub. Slide70
© 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.