Source tumblrcom Source girlonrawcom Source Wikimediaorg Source eatdrinkflycom Source lhs204stellpflugcom Source buzzfeedcom Source thelifeanimalblogspotcouk Quiz ID: 472970
Download Presentation The PPT/PDF document "Source: walkaboutbydesign.blogspot.co.uk" 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
Source: walkaboutbydesign.blogspot.co.ukSlide3
Source:
tumblr.comSlide4
Source:
girlonraw.comSlide5
Source:
Wikimedia.orgSlide6
Source:
eat-drink-fly.comSlide7
Source:
lhs204.stellpflug.comSlide8
Source:
buzzfeed.comSlide9
Source:
thelife-animal.blogspot.co.ukSlide10
Quiz!
How species of spiders are there in Australia?
A – 10
B – 500
C - 2000Slide11
Source:
Wikimedia.orgSlide12
Source:
thechinawatch.comSlide13
Source:
rosettathurman.comSlide14
Migration and Coexistence with Microsoft Lync Server 2013
Justin Morris
Lync MVP and Senior ConsultantModality Systems
OUC-B334Slide15
AgendaSlide16
Agenda
Initial Migration Considerations
Migrating from OCS 2007 R2Migrating 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
TakeawaysSlide17
Initial Migration ConsiderationsSlide18
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 lastSlide19
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
supportedSlide20
Migrating from
OCS 2007 R2Slide21
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 R2Slide22
Merge OCS 2007 R2 Topology
Populates Lync topology with all legacy OCS 2007 R2
serversCreates BackCompatS
ite
WMI Backwards Compatibility Package
required
Source:
Modality SystemsSlide23
Importing Legacy Policies and Settings
Import
OCS 2007 R2 voice, conferencing, external access and archiving policies into Lync Server 2013Run cmdlet
Import-CsLegacyConfiguration
after topology has been
merged
Once imported, legacy policies can be viewed in Lync Server Control
PanelSlide24
Configure Lync Server 2013 Pool
Connect
to Legacy Edge Servers in Topology BuilderConfigure Legacy Edge Servers to allow connections from Lync Server 2013
pool
Configure any new
policies and configurationsSlide25
Migrate Users
Move-CsLegacyUser
How will you migrate – scripting?Assign any new policiesSend communication and provide trainingSlide26
Complete Post-Migration Tasks
Migrate Response Groups
Migrate Dial-In Access NumbersMigrate Voice RoutesMove Exchange UM Contact ObjectsRemove Legacy Archiving and Monitoring Servers
Deploy Lync 2013 ClientsSlide27
Decommission OCS 2007 R2
Move Conference Directories
Update DNS SRV RecordsDecommission OCS 2007 R2 ServersRemove BackCompatSite from TopologySlide28
Migrating from
Lync Server 2010Slide29
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 2010Slide30
Migrate Users
Move-CsUser -MoveConferenceData
How will you migrate – scripting?Assign any new policies
Send communication and provide
trainingSlide31
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
ClientsSlide32
Redeploy Survivable Branch Appliances
Move branch users to another
poolRemove 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
SBASlide33
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
databasesSlide34
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> Slide35
What about R2+2010 Environments?Slide36
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 todaySlide37
Client Coexistence and InteroperabilitySlide38
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
SupportedSlide39
Lync 2013 Client Considerations
Lync 2013 not supported on Windows XP or Vista
Office 2007 not supportedLive Meeting not supported against Lync Server 2013No Gallery View on OC 2007 R2 or Lync 2010Slide40
Server or Client First? You
decide
Lync 2013 can connect to Lync Server 2010Lync 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
poolSlide41
What happens to Attendee?
Lync Attendee no longer
necessaryAll attendees joining conferences without Lync 2013 installed will use Lync Web App
2013Slide42
Changes to
Lync Phone Edition
No new devices expectedExisting 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 developingSlide43
Understanding the Autodiscover
ServiceSlide44
Understanding the Autodiscover Service
Lync 2013 clients (including Windows 8 app) will attempt to connect to:
lyncdiscoverinternal.contoso.comlyncdiscover.contoso.comNew clients use Autodiscover service to locate their registrar. SRV record is being
de-emphasized
lyncdiscoverinternal
A record must point to internal
poolSlide45
Edge Server MigrationSlide46
Edge Server Migration
Two o
ptions:Rip and ReplaceSide by Side
Transition
Federation
Using closed federation? Update your partner
organizations
Public IM Connectivity
Providers need to be notified if Access Edge FQDN changesSlide47
External Web Services
MigrationSlide48
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
IPSlide49
Group Chat MigrationSlide50
Group Chat Migration
Deploy the Lync 2013 Persistent Chat
ServerMigrate legacy chat room data
Decommission the legacy Group Chat
serversSlide51
Migrating Legacy Chat Room Data
Stop 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
serversSlide52
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
serversSlide53
Decommission Legacy Group Chat Servers
Uninstall Group Chat from legacy
serversRemove trusted application and trusted application pool entries from topologySlide54
Mobility CoexistenceSlide55
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.””Slide56
Lync Management During CoexistenceSlide57
Lync Management during Coexistence
Any new changes to OCS 2007 R2 topology require
re-mergeOnce Lync Server 2013 has been deployed, Lync Server 2010 tools can no longer be
usedSlide58
Bespoke Migration ScenariosSlide59
Bespoke Migration Scenarios
Situations where Front End pools cannot be easily migrated (cross-forest, mergers/acquisitions)
Leverage dbimpexp.exe and Import-CsUserDataGroup Chat Database Lift-and-ShiftSlide60
Key TakeawaysSlide61
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 serviceSlide62
Q&ASlide63
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 @
justimorrisSlide64
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 Slide65
Evaluate this session
Scan
this QR code
to
evaluate this session.
Required Slide
*delete this box when your slide is finalized
Your MS Tag will be inserted here during the final scrub. Slide66
© 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.