You are on page 1of 72

MVA Jump Start

Core Solutions of
Microsoft Lync Server 2013
Meet Aaron Steele | @steeleaaron
Senior Consultant, Microsoft
Voice architecture; enterprise
deployment & implementation
Specializes in Lync Server 2013
Microsoft Unified Communications stack since LCS 2005
Exchange since Exchange 5.5
More than 15 years experience in IT industry
Tribune Co., PointBridge, University of Chicago, DePaul,
Michigan State University
Meet Brian Ricks | @bricomp
Lead Architect, BriComp Computers
Unified Communications Architect
Microsoft MVP since 2006
Enterprise Microsoft collaboration solution design,
development, configuration, administration & maintenance
More than 20 years experience in IT industry
Network Infrastructure Corp., Resolute, Phelps Dodge
Course Topics
Core Solutions with Lync Server 2013
01 | Architecture And Design 07 | Persistent Chat
03 | Configuring Users and Rights 08 | Archiving & Monitoring
03A| Users and Rights Demo 08A | Demo
04 | Client & Devices 09 | Administration and Maintenance
05 | Conferencing 10 | High Availability
05A | Conferencing Demo 11 | Disaster Recovery
06 | External Access 11A| HA and DR Demo
12 | Migration
Setting Expectations
Target Audience
IT and telecommunications professionals who design, plan, deploy, and
maintain solutions for unified communications (UC)
Experienced and looking for accelerated certification prep for Exam 70-336:
Core Solutions of Microsoft Lync Server 2013
Suggested Supporting Material
Exam 70-336: Core Solutions of Microsoft Lync Server 2013
Visit http://aka.ms/MCSE-Lync
Join the MVA Community!
Microsoft Virtual Academy
Free online learning tailored for IT Pros and Developers
Over 1M registered users
Up-to-date, relevant training on variety of Microsoft products
Earn while you learn!
Get 50 MVA Points for this event!
Visit http://aka.ms/MVA-Voucher
Enter this code: Lync336 (expires 7/1/2013)
MVA Jump Start
Module 1
Architecture and Design
of Microsoft Lync Server 2013
Module Overview
Overview of Lync Server 2013 Architecture& Core Capabilities
Introduction to the Lync Server 2013 Design Process
Assessing Infrastructure Requirements and Updating the Design
Planning for all Microsoft Solutions Framework Phases
Planning Infrastructure Requirements for Lync Server 2013
Using the Lync Server 2013 Planning Tool & Topology Builder
Planning the Server Infrastructure
Designing Documentation Using Microsoft Office
Lesson 1: Overview of Lync Server 2013 Architecture
Deployment Options
Lync Server 2013 Architecture
Lync Server 2013 Server Roles
Lync Server 2013 Clients
Lync Server 2013 Administrative Tools
Central Management Database
Session Initiation ProtocolBased Foundation
Lync 2013 Hybrid Coexistence
Enterprise Voice in Lync Server 2013
Deployment Options
Microsoft Office 365,
Lync Online
Partner-hosted multi-
tenant
Single domain and
directory
Users split server /
online
Lync Server 2013
Private cloud / dedicated
Cloud Hybrid On-Premises
Enabling gradual migration and coexistence between
Lync private and public cloud
Lync Server 2013 Architecture
Internal
External
Perimeter
Network
Reverse
proxy
Lync
Edge
Hybrid
Federated
Network
Public
Providers
PSTN
AD MIIS
Identity
Edge
More Secure
Federation and
Interoperability
External User
Ingress
Pool
Fewer,
Consolidated
Servers
Virtualized and
Higher Scale
Services
Consolidated
Archiving
SCOM, AD, DFS
Exchange
Voicemail/
Archive
SCOM
Monitoring
DFS
Files Store
Office Web Apps
Web Access
SQL
CDR/QoE/
ReportDB
UC End Points
EE Pool Back-end
Front-end
IP-PSTN
Gateway
Persistent
Chat (optional)
Mediation Server
(optional)
PBX
Lync Server 2013 Server Roles
Mediation Server
Front End Server Back End Server
Director
Persistent Chat
Compliance Back
End Server
Standard Edition Server
Edge Server
Lync Server 2013
Server Roles
Persistent Chat
Back End Server
Persistent Chat
Server
Lync Server 2013 Clients
Lync 2013 Web App
Lync Server 2013
Clients
Lync 2013 Lync 2013 Basic
Lync 2013 Mobile
Lync 2013 Phone
Edition
Lync Win Store App
Lync Server 2013 Administrative Tools
Administrative tools and enhancements in Lync Server 2013 include:
Lync Server Deployment Wizard
Lync Server Control Panel
Lync Server Management Shell
Lync Server Topology Builder
Central management database
Role-based access control
DNS load balancing
Lync Centralized Logging Service
Central Management Database
The Central Management Database:
Provides a robust, schematized storage of the data needed to
define, set up, maintain, administer, describe, and operate a Lync
Server 2013 deployment
Validates data to ensure configuration consistency
Replicates read-only copies of data to all servers in the topology,
including Edge Servers
Session Initiation ProtocolBased Foundation
SIP as an application-layer control or signaling protocol for
creating, modifying, and terminating sessions among one or more
participants
Sessions include Internet-based telephone calls, multimedia
distribution, and multimedia conferences
SIP-related RFCs and over 200 IETF Internet drafts and proposed
standards form the basis of the Microsoft Unified Communications
design
Lync 2013 Hybrid Coexistence
Active
Directory
Lync 2010
Pool
Microsoft
Federation
Gateway
Lync
Federation Edge
AD FS v2
(Geneva)
DirSync provisioning, GAL
Federation for SSO
Lync Hybrid Interoperability
Integration between local
IT systems and the cloud
Office 365
Exchange Online
Lync Online
SharePoint Online
Legacy OCS
2007 R2
Lync 2010+ Pool Directory Sync
Edge
Same as
Exchange
Enterprise Voice in Lync Server 2013
Enhanced Routing
Support for M:N MS:GW
Improved Caller ID management
Improved delegate routing
Response Group Manager
Inter-trunk routing (session management)
Hosted Voice
Lync-to-Phone, IP phone devices in Office 365
IPv6 Support for IPv6 in all Lync components
VDI Support for VDI for audio and video
Lesson 2: Overview of Lync Server 2013 Core Capabilities
Lync 2013 Features
Lync Server 2013 Conferencing Clients
External User Scenarios
External User Capabilities
Lync 2013 Features
Lync 2013 Features
Enhanced user interface Video enhancements Multiparty video
Me area Administrative enhancements
Contact card Call park and retrieve
Privacy enhancements Pre-call and in-call diagnostics
Sharing feature enhancements Improved device handling
Polling Emergency services support
Improved meeting join experience Call handling
Conferencing attendance and scheduling Enhanced phone experience
PSTN dial-in conferencing enhancements Office and Windows 8 integration
Lync 2013 Feature descriptions
Feature Description
Polling Enhances collaboration by enabling presenters to quickly determine participants
preferences
Conferencing attendance and
scheduling
Sending invitation is simplified through a shorter http:// URL, which mobile users
can also use to join conferences
PSTN dial-in conferencing
enhancements
Users can join calls with minimal prompts and can wait in the lobby if the
receiver is not available to pick up the call
Video enhancements Provides support for full screen, panoramic video, multipoint video, subscription
video, and Video Graphics Array (VGA) video in conferences
Administrative enhancements Delegates do not have to switch between Lync 2013 and Attendant console
Call handling Delegates can support their manager easily because of shared lines
Emergency services support When a caller makes an emergency call, emergency responders can retrieve the
physical location of the phone from which the call was placed
Lync 2013 Feature descriptions
Feature Description
Enhanced phone experience Includes a tally of call logs and voice mail that alerts the user of activity
Microsoft Office and Windows 8
Integration
Users can start IM or phone conversations from Microsoft Office applications,
without having to switch to Lync 2013
Contact card Offers extended contact card options with information about the user, the
organization, or distribution groups
Privacy enhancements Users can assign contacts various levels of access, depending on their relationship
with them, such as Family or Workgroup
Sharing feature enhancements Provides users desktop sharing, application sharing, meeting recording, playback,
whiteboard, and annotation tools
Call park and retrieve Calls can be sent to a general holding area for pickup or retrieval, by the
appropriate response group or individual
Pre-call and in-call diagnostics Alert users when the network quality is poor so that the user can choose
to take the call from a landline phone or mobile phone
Improved device handling Allows multiple devices, including Universal Serial Bus (USB) devices for
calls
Lync Server 2013 Conferencing Clients
Feature/capability Lync 2013 Lync Win Store App Lync 2013 Basic Lync Web App
Add computer audio X X X X
Add video X X X X
View multiparty video X X X
Use in-meeting presenter controls X X X
Access detailed meeting roster X X X
Participate in multiparty IM X X X
Share the desktop (if enabled) X X (need plugin)
Share a program (if enabled) X X (need plugin)
Add anonymous participants (if enabled) X X
Use dial-in audio conferencing X X X X
Initiate a meeting X X
Add Microsoft PowerPoint files X X X
Navigate Microsoft PowerPoint files X X X
Use OneNote meeting notes X X
Use a whiteboard X X X
Conduct polls X X X
Share files x X X
External User Scenarios
Access Edge
Server
Access Edge
Server
Adatum.com
Contoso.com
Federated Users
Internal Users
Remote User
Anonymous User
XMPP Partner
PIC User
External User Capabilities
Scenario Remote
User
Federated
User
PIC Anonymous
User
XMPP
Presence
IM peer-to-peer
IM conferencing
Collaboration
A/V peer-to-
peer
*
A/V
conferencing
File transfer
Communications capabilities by type of user:
* = For PIC A/V peer-to-peer support, you must use the
new version of Windows Live Messenger.
Lesson 3: Introduction to the Lync Server 2013 Design Process
Phases in a Lync Server 2013 Deployment
Lync Server 2013 Brick Model Approach
Sequence of Lync Server 2013 Deployment Phases
Converting Business Drivers to Design Decisions
Stakeholder Participation in the Design Phase
Discussion: Importance of User Education
Phases in a Lync Server 2013 Deployment
Envision
Initial State
Environment
End State
Environment
Scenarios
Plan
Planning
Infrastructure
Requirements
Planning Lync
Server 2013
Requirements
Planning
External Access
Planning
Enterprise
Voice
Stabilize
Testing
Considerations
Deploy
Preparing Active
Directory
Deploying
Clients
Deploying Lync Server
2013 Server Pool
Configure, Archiving and
Monitoring
Deploying
External User
Access
Deploying
Enterprise Voice
Validate
Deployment
Operate
Maintaining the
Lync Server 2013
Environment
Maintaining the
Client Experience
Troubleshooting
Lync Server 2013 Brick Model Approach
SQL as bottleneck preventing larger pools
Brick model based on
Front End Servers manage user state
Front End Servers and back end database are loosely coupled
Lazy writes for rehydration and disaster recovery
User Groups
Users are partitioned into UserGroups automatically
Each UserGroup is assigned to three Front End Servers (primary, secondary, tertiary)
Three copies of each users data are stored on Front End Servers through replication WindowsFabric
When one Front End Server dies, user groups are automatically transitioned to a secondary Front End
Server
Minimum healthy servers to start a pool quorum
Scale-out: Multiple Front End Servers per pool
Sequence of Lync Server 2013 Deployment Phases
Order of Lync Server 2013 Deployment Phases
1. Internal Deployment
2. PSTN Dial-in Conferencing
3. External Deployment
4. Enterprise Voice or PBX integration
Converting Business Drivers to Design Decisions
Identifying the business drivers
Does the organization require Presence and instant messaging?
Does the organization want to use conferencing and do they want to invite internal
and/or external users to conferences?
Do they want to deploy Enterprise Voice features using Lync 2013 as a voice client?
Will remote users, work-from-home users, or travelling users need full communication
capabilities?
Will features for integrating presence and click-to-dial work with the organizations
existing telephony solution?
Will you need to enable access to business applications in the organization for
contextual collaboration?
User Modelling Which users in each site will use which modalities ?
Converting business drivers to design decisions
Answers to questions indicate the various scenarios and the related functionality that
you should implement to support these scenarios.
Stakeholder Participation in the Design Phase
Lync Server 2013 Project
Management
Network
Server
Client Desktop
Education
Operations
Telephony
Users
Security
Discussion: Importance of User Education
Do you think user education is a necessary part of a Lync Server 2013
implementation? What may go wrong if users are not convinced with
the solution?
What has been your experience in trying to educate users about
unified communicationsbased solutions?
Adoption and Training Kit
Lesson 4: Assessing Infrastructure Requirements and Updating the
Design
Components of a Lync Server 2013 Design
Assess Required SIP Domains and Update the Design
Assess Exchange Server Integration and Update the Design
Assess Client Integration and Update the Design
Assess Voice Requirements and Update the Design
Discussion: Importance of Documenting the Business and Technical
Requirements
Components of a Lync Server 2013 Design
1. Identify and document the requirements
2. Create the conceptual design
3. Transform the conceptual design into a logical design
4. Implement the physical design from the logical design
5. Refine the physical design
6. Review the design
Assess Required SIP Domains and Update the Design
You need to assess and determine the SIP domain to be used in the
Lync Server 2013 deployment. You could:
Use only one SIP domain
Use one SIP domain for every SMTP domain
Decide how to choose one SIP address for users using different e-mail
addresses such as claus.hansen@contoso.com, claush@contoso.com, and
claus@contososales.com
If there are limitations, you can choose to use only a few SIP domains
Assess Exchange Server Integration and Update the Design
To support Lync 2013 integration, both Lync 2013 and Microsoft
Outlook 2013 read and write information directly to Exchange Server.
You need to plan for Exchange Server interfaces used by Lync 2013
and Microsoft Outlook 2013. You need to plan for:
Exchange Server Communication Interfaces based on their function
Publishing Free/Busy information
Controlling integration
Lync 2013 and Exchange Server compatibility
Assess Client Integration and Update the Design
You need to assess and determine requirements for client integration
that could include:
Client features required
Client deployment
Hardware and software requirements
Policies and in-band settings
Compatibility of client versions
Assess Voice Requirements and Update the Design
You need to assess and determine voice requirements, and options
for voice deployment could include:
Using SIP-to-PSTN gateways, which include Survivable Branch Appliances
(SBA)
Direct SIP by using PBX
SIP-to-PSTN Gateway to PBX
SIP Trunking
Current dialing habits and dial plans
Devices
Discussion: Importance of Documenting the Business and Technical
Requirements
Why should business and technical requirements be documented?
How do you document and ensure that all project requirements are
met?
Why should you receive feedback from stakeholders and update the
design at key milestones?
Lesson 5: Planning for all Microsoft Solutions Framework Phases
Microsoft Solutions Framework Project Approach
Discussion: Design Decisions in the Envisioning and Planning Phases
Plan for Project Extendibility
Initial State and End-State Environment
Components of a Functional Specification
Microsoft Solutions Framework Project Approach
Deployment
Complete
Release
Readiness
Approved
Vision /
Scope
Approved
Project Plans
Approved Developing
Phase
Scope
Complete
Start End
Features
Discussion: Design Decisions in the Envisioning and Planning Phases
Do you usually involve team members from operations during the
initial envisioning phases?
What benefits do you think can be reaped, if any, from the early
involvement of stakeholders other than the business and IT
management and a few select IT architects?
Critical Success Factors
Acceptance Criteria or Critical Success Factors define the metrics that
must be met in order for Contoso and the project team to know that the
end solution meets the defined requirements.
Plan for Project Extendibility
MSF foundational principles recommend that organizational stakeholders should:
Work toward a shared vision
Empower all team members
Foster open communications
Focus on delivering business value
Establish a shared project vision
Ensure clear accountability and shared responsibility
Invest in quality
Stay agile; expect change
Learn from all experiences
Initial State and End-State Environment
A sample deployment scenario that illustrates initial state and end state environments:
Sample Scenario
Phase UC1: Deployment of Lync Server 2013 internally
Presence in IM and Conferencing
Audio/video
Phase UC2: Deployment of Lync Server 2013 externally
Inviting customers/partners to meetings
Federation
Phase UC3: Deployment of Voice
Dial-in conferencing
Lync Server 2013 as soft phone
Phase UC4: Build Contextual Communication into business applications
Presence-enabling ERP and CRM
Building workflows around business processes or applications
Components of a Functional Specification
The functional specification is the technical description of the solution and
represents the contract between the organization and the project team
A functional specification should include:

Features. Document the complete set of planned features for the solution

Security requirements. Specify the strength of security to be used

Legal requirements. State any legal requirements to adhere

Risk analysis documents. Include descriptions of potential risks to the project and mitigation strategies
A functional specification should not include:

Details of software architecture

Detailed database schema

Details about programming languages


Lesson 6: Planning Infrastructure Requirements for Lync Server 2013
Planning for Server Hardware in a Physical Server-Based Topology.
Planning for Server Hardware in a Virtualized Server Topology
Planning for Lync Server 2013 Server Software
Planning for Lync Server 2013 Network and Infrastructure
Dependencies
Planning for Client Hardware and Software Requirements
Planning for Web Browser Requirements
Planning for Server Hardware in a Physical Server-Based Topology.
Hardware Recommendations for
Front-End, Back-End, Standard Edition
and Persistent Chat Servers
Hardware Support for Edge Servers,
Standalone Mediation Servers and
Directors
CPU: 64-bit dual processor, hex-core, 2.26 GHz or higher CPU: 64-bit dual processor, quad-core, 2.0 GHz or higher
or 64-bit 4-way processor, dual-core, 2.0 GHz or higher
Memory: 32 GB Memory: 16 GB
Disk: 8 or more 10,000 RPM hard disk drives with at least
72 GB free disk space. Two of the disks should use RAID 1,
and six should use RAID 10. or Solid state drives (SSDs)
which provide performance similar to 8 10,000-RPM
mechanical disk drives.
Disk: 4 or more 10,000 RPM hard disk drives with at least
72 GB free disk space or Solid state drives (SSDs) which
provide performance similar to 4 10,000-RPM mechanical
disk drives.
Network: 2 network adapters, each 1 Gbps Network: 2 network adapters, each 1 Gbps
Planning for Server Hardware in a Virtualized Server Topology
Base Hardware Recommendations
for
Virtualization Hosts
CPU: capable of supporting 24
virtual cores
Memory: 4 GB for the Host Disk: 2
10,000 RPM hard disk drives with at
least 72 GB free disk space in RAID
1.
Network: 2 network adapters, each 1
Gbps with support for Single Root
I/O Virtualization
Standard Edition
Server Topology
Lync Server 2013
Supported
Technologies
Enterprise Edition
Topology
Planning for Lync Server 2013 Server Software
Plan for installing the same operating system on all servers and use the latest
version of the operating system for administrative efficiency
Plan for operating systems that support Lync Server 2013 for server roles
Plan for operating systems for other servers because requirements may vary
depending on the software that you plan to install on those servers
Plan for database software for the back end database, the archiving database,
and the monitoring database
Plan for mirroring and log shipping support, if you intend to use High Availability
and Disaster Recovery
Planning for Lync Server 2013 Network and Infrastructure
Dependencies
You need to plan for these network and infrastructure dependencies:
Active Directory Support
Locked Down AD DS Support
Network Infrastructure Support
Certificate Infrastructure Support
DNS Infrastructure Support
Audio/Video Network Requirements Support
RODC Support
IIS Support
IP and Networking Protocol Support
Planning for Client Hardware and Software Requirements
Ensure that client hardware meets the minimum requirements
Evaluate the current hardware utilization in the user environment
Evaluate whether there are still XP and Vista clients deployed
Evaluate whether users need Lync Server 2013 features that are
available only with Microsoft Office 2013 and Microsoft Exchange
2013.
Planning for Web Browser Requirements
Operating system 32-bit
Internet
Explorer
10
64-bit
Internet
Explorer 10
32-bit
Internet
Explorer 9
64-bit
Internet
Explorer 9
32-bit
Internet
Explorer 8
64-bit
Internet
Explorer 8
32-bit
Version of
Firefox 12.X
64-bit
Version of
Safari 5.X
32-bit
Version of
Chrome 18.x
Windows 8 (Intel
based)
Yes Yes N/A N/A N/A N/A Yes N/A Yes
Windows 7 with
SP11
Yes Yes Yes Yes Yes Yes Yes No Yes
Windows Vista with
Service Pack 2 (SP2)
2
Yes No Yes No Yes No Yes No Yes
Windows XP with
Service Pack 3 (SP3)
2
N/A N/A N/A N/A Yes No Yes No Yes
Windows Server
2008 R2 with SP1
1
Yes Yes Yes Yes Yes Yes Yes No Yes
Windows Server
2008 with SP2
2
Yes No Yes No Yes No Yes No Yes
Mac OS-x (Intel-
based)
N/A N/A N/A N/A N/A N/A Yes Yes Yes
Lesson 7: Using the Lync Server 2013 Planning Tool
Capabilities and Benefits of the Planning Tool
Exploring Deployment Scenarios by Using the Planning Tool
Capabilities and Benefits of the Planning Tool
Planning Tool
Simplifies the planning and deployment processes
Provides a diagram of the topology to be used in Visio
Allows you to export the topology for use with Topology Builder
Facilitates you to explore and experiment various deployment scenarios
Planning Tool
Topology
Exploring Deployment Scenarios by Using the Planning Tool
Example Output #1
Global Hardware and Online Resources
4 Enterprise Edition Servers
4 Front End SQL Databases
230 concurrent calls using at least 2 Gateways
2 Consolidated Edge Servers
2 Reverse Proxies
2 Load-Balanced Virtual IP Addresses
2 Enterprise Edition Directors
4 Exchange Um Servers
3 Survivable Branch Appliances
Example Output #2
Global Hardware and Online Resources
2 Standard Edition Servers
305 concurrent calls using at least 5 Gateways
1 Consolidated Edge Servers
1 Reverse Proxy
1 Enterprise Edition Directors
2 Exchange UM Servers
Lesson 8: Using Topology Builder
Lync Server 2013 Topology Setup Process
Topology Builder Tool
Demonstration: Demonstration: How To Save and Publish a Topology
by Using Topology Builder
Overview of Central Management Store
Lync Server 2013 Deployment Model
Central and Branch Office Sites
Demonstration: How To Design a Site Topology by Using Topology
Builder
Lync Server 2013 Topology Setup Process
Lync Server 2013
SQL Backend
SQL
SQL Instance
Central
Management
Topology and
Configuration
SQL Backend
SQL DBs setup
performed
by Topology Builder
If first pool is Standard
Edition: SQL instance is
SQL Express
Add/
Remove
Domain Joined
System
Active Directory
Setup
Install Topology
Builder
Author Topology
Publish Topology
Active
Directory
Certificate
Maintenance
Certificates
Install
Components
Retrieve Topology
Local Setup Install
Comp
Activate
Topology Builder Tool
The Topology Builder Tool:
Is a graphical tool used to configure servers and server settings in a topology
Is used to complete and publish the topology before the Microsoft Lync
Server 2013 is installed on servers
Overview of Central Management Store
Central
Management
Store
Central Management
Database
Schema Documents
Central Management Server
Replica
Lync Server 2013 Deployment Model
Pools
Data Center Sites
Global
Microsoft
Redmond
Tukwila-1 Tukwila-2
Dublin
Dublin-1
Central and Branch Office Sites
PSTN Gateway/
Mediation Server
Lync Server
2013 Sites
Central Site
Branch Site
Or
Front End
Pool
Standard
Edition Server
Each branch
site is linked
with one
central site
Standard
Edition
Server
Survival
Branch
Appliance
PSTN Gateway/
Mediation Server
Lesson 9: Planning the Server Infrastructure
Plan for Server Editions
Types of Pools
Capacity and Scaling Considerations
Plan for Server Editions
Lync Server 2013 Lync Server 2013 Enterprise Edition
Needs a single computer to configure the
primary server components and the database
Enables separation of server functionality and
data storage
Is ideal for organizations that do not require
high availability through load balancing
Is ideal for organizations that require high
availability through load balancing
Provides Failover through Pool Pairing with
secondary SE Pool
Can facilitate more users per pool
Types of Pools
Types of Lync 2013 Pools:
Persistent Chat Pool
Enterprise Edition Front End Server Pool
Mediation Server Pool
Director Server Pool
Edge Server Pool
Capacity and Scaling Considerations
Lync Server 2013 Standard Edition
Topology with
Limited High Availability
Lync Server 2013 Enterprise Edition Front End
Reference Topology with High Availability and a
Single Data Center
Use the topology for organizations with 5,000 or fewer
users
Consider it for a small-to-medium size organization with
one central site
Can accommodate more users or provide a failover
scenario with High Available Enterprise Voice if you add
another Standard Edition server to this topology
Use the topology for organizations with 5,000 to 80,000
users in a pool.
Can be associated with a Survivable Branch Appliance for
basic High Available Enterprise Voice
Can support up to 6660 users per Front End Server.
Can support more users if you add another Front End pool
to the site
Can be paired up with another Enterprise Edition Front End
Pool for Disaster Recovery.
Additional Capacity and Scaling Considerations
Cater for Large Meetings Lync Server 2013 Persistent Chat
Deploy a separate Front End Pool with 2 Front
End Servers for the meeting organizers to
support meetings from 250 to 1000
participants
A Persistent Chat pool can host up to 80.000
active users
A pool will have 4 active front ends, 4 passive
front ends maximum
A Persistent Chat Pool can be provisioned for
up to 150.000 users
Lesson 10: Designing Documentation Using Microsoft Office
Benefits of Documenting the Design
Options for Design Documentation
Server Infrastructure Design in Microsoft Office Visio
Benefits of Documenting the Design
Characteristics of Good Design Documentation
Should describe the conceptual and logical design
Should be well-structured and organized
Should be correctly layered and easily maintainable
Benefits of Documenting the Design
Shows the direction and progress of a project
Guides new hires, consultants, or other members working with the solution
Increases the probability of regular updates
Simplifies upgrade of the solution when required, by providing a clear
understanding of the current design
Options for Design Documentation
Microsoft Office Word
Conceptual, logical, and physical design
Embedded drawings and tables
Microsoft Office Visio
Server and Network Architecture
Edge Design
Certificates design
Microsoft Excel
Firewall design
Sites, networks, and subnets
Server sizing and configuration
Server Infrastructure Design in Microsoft Office Visio
Lync Edge Server
(Consolidated)
LON SERVER VLAN
NY OFFICE
LON HQ OFFICE VLAN
LON
Firewall
BRI Interfaces
Basic VoIP Gateway
Gateway
Gateway
Routing
Interface
Exchange UM
Server
SQL Server Instance
used for Lync
Lync 2013 Enterprise Edition
Consolidated Front End Servers
Pool
F5 Internal
Load
Balancers
1
1: Internet
MPLS primary to
NY Internet
secondary
2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics 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.