- Title Page
- Copyright Page
- Dedication
- Contents at a Glance
- Table of Contents
- About the Authors
- Acknowledgments
- We Want to Hear from You!
- Reader Services
- Introduction
- Part I. Overview
- Chapter 1. What Is Microsoft Lync Server?
- Chapter 2. What Is New in Microsoft Lync Server?
- Introducing New Management Tools
- Topology Changes
- New Enterprise Voice Features
- New Call Management Features
- Integrated Mediation Server
- New Presence Features
- New Conferencing Features
- DNS Load Balancing
- Survivable Branch Appliances
- Operating System Support
- New Lync Client Features
- Client Appearance
- The “Me” Area
- Enhanced Contacts
- Privacy Relationships
- Integration with Office and Windows 7
- Whiteboarding and Application Sharing
- Improved Meeting Join Experience
- Conferencing Attendant and Scheduling
- PSTN Dial-In Conferencing Improvements
- Video Improvements
- Manager/Admin Improvements
- Improved Phone Experience
- Summary
- Chapter 3. Feature Overview of Microsoft Lync Server
- Chapter 4. Benefits of Microsoft Lync Server 2010
- Part II. Microsoft Lync Server 2010 Server Roles
- Chapter 5. Microsoft Lync Server 2010 Front End
- Chapter 6. Microsoft Lync Server 2010 Edge
- Chapter 7. Microsoft Lync Server 2010 Monitoring
- Overview
- Installation
- Configuration
- Administration
- Troubleshooting
- Best Practices
- Summary
- Chapter 9. Director
- Part III. External Dependencies
- Chapter 10. Dependent Services
- Chapter 11. SQL
- Chapter 12. Firewall and Security Requirements
- Part IV. Administration and Management
- Chapter 13. Monitoring Microsoft Lync Server 2010
- Overview
- OpsMgr Lync Server 2010 Monitoring
- What Is New in OpsMgr R2?
- How OpsMgr Works
- OpsMgr Architecture
- How to Use OpsMgr
- OpsMgr Component Requirements
- Advanced OpsMgr Concepts
- Understanding OpsMgr Deployment Scenarios
- Multiple Configuration Groups
- Deploying Geographic-Based Configuration Groups
- Deploying Political or Security-Based Configuration Groups
- Sizing the OpsMgr Database
- Defining Capacity Limits
- Defining System Redundancy
- Monitoring Nondomain Member Considerations
- Securing OpsMgr
- Installing Operations Manager 2007 R2
- Installing Edge Component Monitoring Certificates
- Installing the Lync Server 2010 Management Pack
- Best Practices
- Summary
- Chapter 14. Backup and Restore of Microsoft Lync Server 2010
- Chapter 15. Administration of Microsoft Lync Server 2010
- Chapter 13. Monitoring Microsoft Lync Server 2010
- Part V. Migrating from Older Versions
- Part VI. Voice
- Chapter 17. PBX Integration
- Chapter 18. Enterprise Voice
- Chapter 19. Audio Conferencing
- Part VII. Integration with Other Applications
- Chapter 20. Exchange 2010 and SharePoint 2010 Integration
- Overview
- Exchange 2010 Unified Messaging
- Call Answering Rules
- Exchange 2010 Unified Messaging Architecture
- Unified Messaging Users
- UM Web Services
- Supported IP/VoIP Hardware
- Unified Messaging Protocols
- Unified Messaging Installation
- Postinstall Configuration
- Data Storage in Unified Messaging
- Exchange 2010 Outlook Web Application
- SharePoint 2010 Integration
- Best Practices
- Chapter 21. UCMA
- Chapter 20. Exchange 2010 and SharePoint 2010 Integration
- Part VIII. Clients
- Chapter 22. Microsoft Communicator Client for Macintosh
- Chapter 23. Windows, Browser, and Silverlight Clients
- Chapter 24. UC Endpoints
- Part IX. Planning for Deployment
- Chapter 25. Virtualization
- Chapter 26. Planning for Internal Non-Voice Deployment
- Chapter 27. Planning for Deploying External Services
- Chapter 28. Planning for Voice Deployment
- Index
High Availability
When adding high availability to a Lync Server Edge Server deployment, an organization must make a decision about how it will provide load-balancing features. The only options available for load-balancing Edge Servers are to use DNS-based load-balancing or to leverage a hardware load-balancing solution.
Note
Windows Network Load Balancing (NLB) is not supported for load balancing any of the Lync Server roles, including Edge Server features.
DNS load balancing seems like an attractive feature at first, but does have some limitations. Organizations should review these limitations and then make a decision about whether a hardware load balancer is required. The main limitation of DNS load balancing is that it does not work with some features or legacy endpoints, including
Endpoints running previous versions of the Communicator client
Federated organizations running previous versions of Communications Server
• Public IM connectivity
• XMPP Gateway
• Exchange Server 2007 and 2010 RTM Unified Messaging Signaling and Audio
• Exchange Server 2010 SP1 Unified Messaging for Audio
Not all organizations are affected by these limitations and might still be able to deploy DNS load balancing for their Lync Server infrastructure.
-
No Comment