Top 5 Things to Know When Deploying your
first Lync 2013 Server
Tom Arbuthnot
Lync MVP
Managing Consultant, Modality Syste...
What’s the “Good Stuff” in 2013?
• Mobile Clients with Audio and Video
• Lync Web App A/V Meeting Join in Browser
• Galler...
OK, You’ve convinced me, I want to try Lync 2013

• Assuming you have a Lync 2010 environment,
adding a Lync 2013 Standard...
1. Schema Updates and New Management Tools
• Lync 2013 will require an AD Schema update
• From Publishing Lync 2013 Topolo...
2. Archiving and Monitoring Changes
• You no longer need a dedicated Arch/Mon Server
Role, it’s all on the FE
• However, y...
3. You’ll need an “Office Web Apps” Server
• You lost Arch/Mon, you gained Office Web
Apps/WAC 
• Actually a SharePoint S...
4. For Mobile to work you need Reverse Proxy and Edge

• Lync 2013 Mobile Clients Require routing
signalling via the rever...
5. Don’t forget to Update Desktop QoS GPOs
• Lync 2013 Client is now called Lync.exe not
communicator.exe, update Desktop ...
3 Bonus Gotcha’s
• You can’t setup a 2010 and a 2013 server in
backup Registrar Relationship – consider resilience
• You c...
Questions

08/11/2013

Microsoft Unified Communications User Group London (MUCUGL)

10
Upcoming SlideShare
Loading in …5
×

MUCUGL October 2013 - Top 5 Things To Know When Deploying Your First Lync 2013 Server

4,480 views

Published on

Tom Arbuthnot shares his advice for the top 5 things to know when deploying your first Lync 2013 server

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
4,480
On SlideShare
0
From Embeds
0
Number of Embeds
3,544
Actions
Shares
0
Downloads
29
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

MUCUGL October 2013 - Top 5 Things To Know When Deploying Your First Lync 2013 Server

  1. 1. Top 5 Things to Know When Deploying your first Lync 2013 Server Tom Arbuthnot Lync MVP Managing Consultant, Modality Systems @tomarbuthnot http://lyncdup.com tom@tomarbuthnot.com
  2. 2. What’s the “Good Stuff” in 2013? • Mobile Clients with Audio and Video • Lync Web App A/V Meeting Join in Browser • Gallery View - Multiple Video participants on Screen • Persistent Chat in single client • Pool Pairing/SQL Mirroring 08/11/2013 Microsoft Unified Communications User Group London (MUCUGL) 2
  3. 3. OK, You’ve convinced me, I want to try Lync 2013 • Assuming you have a Lync 2010 environment, adding a Lync 2013 Standard Edition Server is a great way to start testing/using/piloting Lync 2013 • However there are a few things to know/consider before pulling the trigger on that install…. 08/11/2013 Microsoft Unified Communications User Group London (MUCUGL) 3
  4. 4. 1. Schema Updates and New Management Tools • Lync 2013 will require an AD Schema update • From Publishing Lync 2013 Topology forward, you must use the Lync 2013 Topology builder • Lync 2013 has it’s own PowerShell Tools, generally the 2010 tools should be used for 2010 and 2013 tools to manager 2013/2013 users • Your Lync 2010 (or OCS) Environment should be patched to the current CU • sip. and meet. DNS pointing to Lync 2010 will seamlessly redirect users to the 2013 pool (so no need for internal DNS changes, but may need additions) 08/11/2013 Microsoft Unified Communications User Group London (MUCUGL) 4
  5. 5. 2. Archiving and Monitoring Changes • You no longer need a dedicated Arch/Mon Server Role, it’s all on the FE • However, you need a new/additional Archiving Database Target, you can’t use the 2010 one • You’ll also need the 2013 SQL reports deployed for Reporting • Consider that your compliance/support teams now need to consider two databases for information 08/11/2013 Microsoft Unified Communications User Group London (MUCUGL) 5
  6. 6. 3. You’ll need an “Office Web Apps” Server • You lost Arch/Mon, you gained Office Web Apps/WAC  • Actually a SharePoint Server (don’t panic) • Required for any PowerPoint scenarios (2013/Web/Mobile) • Office Web Apps only works with a Valid HTTP/HTTPS Certificate Revocation List – you may not have this setup on your internal CA by default • Don’t skip this to save a couple of cores and a few GB of RAM on a VM 08/11/2013 Microsoft Unified Communications User Group London (MUCUGL) 6
  7. 7. 4. For Mobile to work you need Reverse Proxy and Edge • Lync 2013 Mobile Clients Require routing signalling via the reverse proxy (lyncdiscover / External UCWA) • Lyncdiscover must be routable to the outside RP on internal WiFi • Consider that you will need some additional RP SAN names in your public certificate • Lync 2013 Mobile Client Media will route directly if it can (Mobile IP is offered as an SDP Candidate), and/or via Edge. 08/11/2013 Microsoft Unified Communications User Group London (MUCUGL) 7
  8. 8. 5. Don’t forget to Update Desktop QoS GPOs • Lync 2013 Client is now called Lync.exe not communicator.exe, update Desktop GPO accordingly • Lync 2013 Mobile Client’s can’t mark for QoS directly, if using at Scale/busy network consider marking/optimising on Wifi 08/11/2013 Microsoft Unified Communications User Group London (MUCUGL) 8
  9. 9. 3 Bonus Gotcha’s • You can’t setup a 2010 and a 2013 server in backup Registrar Relationship – consider resilience • You can’t use a 2010 Backend SQL for your 2013 Backend SQL (even with a different instance setup!) • You need Exchange 2013 for High Res Photos/Unified Contact Store/Archiving into Exchange 08/11/2013 Microsoft Unified Communications User Group London (MUCUGL) 9
  10. 10. Questions 08/11/2013 Microsoft Unified Communications User Group London (MUCUGL) 10

×