NetScaler Deployment Guide for Microsoft Lync 2013

  • View

  • Download

Embed Size (px)


Detailed guide on how to deploy NetScaler to load balance Microsoft Lync 2013. Includes description of Lync and what is new in 2013. Includes information on topology, protocol and port requirements. Provides detailed steps for a DMZ/Perimeter Network scenario to load balancing Edge Server Pools.

Text of NetScaler Deployment Guide for Microsoft Lync 2013

  • MS Lync 2013 Deployment Guide Microsoft Lync 2013 Citrix NetScaler Deployment Guide Version 1.2 Microsoft Lync 2013 Citrix NetScaler Deployment Guide Version 1.2

2. 2 MS Lync 2013 Deployment Guide Citrix NetScaler Application Delivery Controller (ADC) optimizes availability, scalability, performance and security for Microsoft Lync 2013 deployments. NetScaler hardware as well as virtual appliance models can be used for Lync 2013 deployments. Citrix is strongly committed to its partnership with Microsoft. For several years, Citrix has completed certifications and provided deployment guides for Microsoft. Citrix has shown continued commitment to Microsoft communication products, with many deployment guides and certifications for Microsoft Office Communicator 2007 R2 (commonly known as OCS) and Microsoft Lync 2010 already available. Whats new in Microsoft Lync 2013 Server-Side New Management and Administration Features Topology Changes New Disaster Recovery and High Availability Features New Virtualization Features New IM and Presence Features New Conferencing Features New Features for External User Access New Enterprise Voice Features New Monitoring Features New Archiving Features New Exchange Server Integration Features New Persistent Chat Server Features New IPv6 Features New Unified Contact Store Feature Client-Side Integration with Office Setup Group Policy Deployment Outlook Scheduling Add-in Updates Virtual Desktop Infrastructure Plug-in Video Enhancements Chat Room Integration Lync Web App Updates Lync 2013 for Mobile Clients Updates Lync 2013 User Interface Updates Device-Side Lync Phone Edition Lync Mobile Clients Email, Instant Messaging (IM), call and audio conferencing can be launched with a single touch from mobile clients such as Windows Phone, iPhone, iPad, or Android device. Additionally, manage productivity time better by publishing when available reducing costly interruptions. 3. 3 MS Lync 2013 Deployment Guide Microsoft Office Web Apps Server 2013 for sharing Lync Server 2013 uses the new Microsoft Office Web Apps Server 2013 for sharing Microsoft PowerPoint presentations between computers running the Lync 2013 client. Overview of Microsoft Lync Lync Server Roles Standard Edition Server The Standard Edition server is designed for small organizations, and for pilot projects of large organizations. It enables many of the features of Lync Server, including the necessary databases, to run on a single server. This enables you to have Lync Server functionality for a lower cost, but does not provide a true high- availability solution. Standard Edition server enables instant messaging (IM), presence, conferencing, and Enterprise Voice, to run on a single server. The main difference between Lync Server 2013 Enterprise Edition and Lync Server 2013 Standard Edition is that Standard Edition does not support the high- availability features included with Enterprise Edition. For high-availability, multiple Front-End servers must be deployed to a pool and the SQL Server needs to be mirrored. It is not possible to pool Standard Edition servers. Front-End Server and Back-End Server In Lync Server Enterprise Edition, the Front-End Server is the core server role, and runs many basic Lync Server functions. The Front-End and Back-End Servers are the only server roles required to be in any Lync Server Enterprise Edition deployment. A Front-End Pool is a set of Front-End Servers, configured identically, that work together to provide services for a common group of users. A pool of multiple servers running the same role provides scalability and failover capability. The Front-End Server includes the following roles: User authentication and registration Presence information and contact card exchange Address book services and distribution list expansion IM functionality, including multi-party IM conferences Web conferencing, PSTN Dial-in conferencing and A/V conferencing (if deployed) Application hosting for applications included with Lync Server (for example, Conferencing Attendant and Response Group application) and third-party applications 4. 4 MS Lync 2013 Deployment Guide Option: monitoring-collection of usage information in the form of call detail records (CDRs) and call error records (CERs). This information provides metrics about the quality of the media (audio and video) traversing the network for both Enterprise voice calls and A/V conferences. Web components of supported web-based tasks such as Web Scheduler and Join Launcher. Option: Archivingarchival of IM communications and meeting content for compliance Option: Persistent Chat Web Services for Chat Room management and Persistent Chat Web Services for File Upload/Download [if persistent chat is enabled] NOTE: In Lync Server 2010 and prior versions, Monitoring and Archiving were separate server roles, not collocated on Front End Server. Front-End Pools are also the primary store for user and conference data. Information about each user is replicated among Front-End Servers in the pool, and backed up on the Back-End Servers. Additionally, one Front-End Pool in the deployment also runs the Central Management Server, which manages and deploys basic configuration data to all servers running Lync Server. The Central Management Server also provides Lync Server Management Shell and file transfer capabilities. The Back-End Servers are database servers running Microsoft SQL Server that provide the database services for the Front-End Pool. The Back-End Servers serve as backup stores for the pools user and conference data, and are the primary stores for other databases such as the Response Group database. A deployment with a single Back-End Server is possible but a solution that uses SQL Server mirroring is recommended for failover. Back-End Servers do not run any Lync Server software. Edge Server Edge Server enables users to communicate and collaborate with users outside the organizations firewalls. These external users can include the organizations own users who are currently working offsite, users from federated partner organizations, and outside users who have been invited to join conferences hosted on your Lync Server deployment. Edge Server also enables connectivity to public IM connectivity services, including Windows Live, AOL AIM, Yahoo! Messenger, and Google Talk. Deploying Edge Servers also enables mobility services, which supports Lync functionality on mobile devices. Users can use supported Apple iOS, Android, Windows Phone, or Nokia mobile devices to perform activities such as sending and receiving instant messages, viewing contacts, and viewing presence. In addition, mobile devices support some Enterprise Voice features, such as click to join a conference, Call via Work, single number reach, voice mail, and missed 5. 5 MS Lync 2013 Deployment Guide calls. The mobility feature also supports push notifications for mobile devices that do not support applications running in the background. A push notification is a notification that is sent to a mobile device about an event that occurs while a mobile application is inactive. Edge Servers also include a fully-integrated Extensible Messaging and Presence Protocol (XMPP) proxy, with an XMPP gateway included on Front-End Servers. Configuring the XMPP components enables Lync Server 2013 users to add contacts from XMPP-based partners (such as Google Talk) for instant messaging and presence. Mediation Server Mediation Server is a necessary component for implementing Enterprise Voice and dial-in conferencing. Mediation Server translates signaling, and, in some configurations, media between your internal Lync Server infrastructure and a public switched telephone network (PSTN) gateway, IP-PBX, or a Session Initiation Protocol (SIP) trunk. You can run Mediation Server collocated on the same server as Front-End Server, or separated into a stand-alone Mediation Server pool. Director Directors can authenticate Lync Server user requests but they do not store user accounts, provide presence, or conferencing services. Directors are most useful to enhance security in deployments that enable external user access. The Director can authenticate requests before sending them on to internal servers. In the case of a denial-of-service attack, the attack ends with the Director and does not reach the Front-End Servers. Persistent Chat Front-End Server Persistent chat enables users to participate in multiparty, topic-based conversations that persist over time. The Persistent Chat Front-End Server runs the persistent chat service. The Persistent Chat Back-End Server stores the chat history data, and information about categories and chat rooms. The optional Persistent Chat Compliance Back-End Server can store the chat content and compliance events for the purpose of compliance. Servers running Lync Server Standard Edition can also run Persistent chat collocated on the same server. You cannot collocate the Persistent Chat Front- End Server with Enterprise Edition Front-End Server. Workload Types IM and Presence Instant messaging (IM) enables users to communicate with each other in real time on their computers using text-based messages. Both two-party and multiparty IM sessions are supported. A participant in a two-party IM conversation can add a third participant to the conversation at any time. When this happens, the Conversation window changes to support conferencing features. 6. 6 MS Lync 2013 Deployment Guide Presence provides information to users about the status of others on the network. A users presence status provides information to help others decide whether they should try to contact the user and whether to use instant messaging, phone, or email. Presence encourages instant communication when possible, but it also provides information about whether a user is in a meeting or out of the