Lync

-->

• Lynchburg Hillcats
• Lynch Mob
• Lynchburg Lemonade
• Lynched

Topic Last Modified: 2016-05-25

You should consider the following requirements for users and your network infrastructure while planning for a hybrid deployment.

Infrastructure Requirements

Microsoft Lync, which was previously known as Microsoft Office Communicator is an instant messenger that is used with the Microsoft Lync Server or via Office 365 with cloud connectivity. Microsoft Lync is basically an enterprise product, (unlike Skype or Windows Live Messenger ) and is meant to be used with Microsoft Exchange Server. Lync and Communicator clients when involved in a one to one communication, is often referred to as peer-to-peer. Technically, the two clients are communicating in a one to one conversation, with the Instant Messaging multipoint control unit (IMMCU) in the middle. Microsoft Lync Server 2013. Topic Last Modified: 2014-03-14 Microsoft Lync Server 2013 communications software offers instant messaging (IM), presence, conferencing, and telephony solutions that can support enterprise-level collaboration requirements.

You must have the following configured in your environment in order to implement and deploy a hybrid deployment.

• A Microsoft 365 or Office 365 organization with Skype for Business Online enabled. Note that you can use only a single tenant for a hybrid configuration with your on-premises deployment.

• A single on-premises deployment (infrastructure) of Skype for Business Server or Lync Server that is deployed in a supported topology. See Topology Requirements.

  For information about configuring your Lync Server 2013 or Lync Server 2010 deployment for hybrid, see Configuring Lync Server 2013 hybrid deployments.

• Skype for Business Server 2015 administrative tools. If you are using Lync Server 2013 or Lync Server 2010, you can use the Lync Server 2013 administrative tools.

• To support Single Sign-on with Microsoft 365 or Office 365 so that users can use the same login credentials for signing in to Office as they do on-premises, you can use the password sync features of Azure Active Directory (AAD) Connect. You can also use Active Directory Federation Services (AD FS) for single sign-on with Microsoft 365 or Office 365.

  For more information, see Integrating your on-premises identities with Azure Active Directory.

• A single directory synchronization solution to keep your on-premises and online Active Directory objects synchronized. For details about Directory Synchronization, see Directory Integration Tools.

Lync Client Support

There are some differences in the features supported in Lync clients, as well as the features available in on-premises and online environments. Before you decide where you want to home users in your organization, you can view the client support for the various configurations of Lync Server. The following clients are supported with Skype for Business Online in a Lync hybrid deployment:

• Lync 2010

• Lync 2013

• Lync Windows Store app

• Lync Web App

• Lync Mobile

• Lync for Mac 2011

• Lync Room System

• Lync Basic 2013

For details about client support, see the following topics:

Topology Requirements

To configure your deployment for hybrid with Skype for Business Online, you need to have one of the following supported topologies:

• A Skype for Business Server 2015 deployment with all servers running Skype for Business Server 2015.

• A Lync Server 2013 deployment with all servers running Lync Server 2013.

• A Lync Server 2010 deployment with all servers running Lync Server 2010 with the latest cumulative updates.

  • The federation Edge Server and next hop server from the federation Edge Server must be running Lync Server 2010 with the latest cumulative updates.

  • The Skype for Business Server 2015 or Lync Server 2013 Administrative Tools must be installed on at least one server or management workstation.

• A mixed Lync Server 2013 and Skype for Business Server 2015 deployment with the following server roles in at least one site running Skype for Business Server 2015:

  • At least one Enterprise Pool or Standard Edition server

  • The Director Pool associated with SIP federation, if it exists

  • The Edge Pool associated with SIP federation

• A mixed Lync Server 2010 and Skype for Business Server 2015 deployment with the following servers roles in at least one site running Skype for Business Server 2015:

  • At least one Enterprise Pool or Standard Edition server

  • The Director Pool associated with SIP federation, if it exists

  • The Edge Pool associated with SIP federation for the Site

• A mixed Lync Server 2010 and Lync Server 2013 deployment with the following server roles in at least one site running Lync Server 2013:

  • At least one Enterprise Pool or Standard Edition server in the site

  • The Director Pool associated with SIP federation, if it exists in the site

  • The Edge Pool associated with SIP federation for the site

Important

All user management, including user moves between on-premises and UNRESOLVED_TOKEN_VAL(skypeforbusiness) Online, needs to be done using the latest installed version of the administrative tools. The administrative tools must be installed on a separate server that has connect access to the existing on-premises deployment and to the Internet. The Move-CsUser cmdlet to move users from your on-premises deployment to UNRESOLVED_TOKEN_VAL(skype16_online) must be run from the administrative tools connected to your on-premises deployment.

For more information about supported topologies, see Supported topologies in Lync Server 2013, and Lync Server 2013 Reference Topologies for Enterprise Hybrid Deployments.

For troubleshooting information about hybrid deployments and connecting PowerShell to Lync Online, see Lync Online: Lync PowerShell and Hybrid Troubleshooting.

Lynchburg Hillcats

Requirements for Federation Allowed/Blocked Lists

The Allowed domains list includes domains that have a partner Edge fully qualified domain name (FQDN) configured. These are sometimes referred to as allowed partner servers or direct federation partners. You should be familiar with the difference between Open Federation and Closed Federation, referred to as partner discovery and allowed partner domain list, respectively, in on-premises deployments.

The following requirements must be met to successfully configure a hybrid deployment:

• Domain matching must be configured the same for your on-premises deployment and your Microsoft 365 or Office 365 organization. If partner discovery is enabled on the on-premises deployment, then open federation must be configured for your online tenant. If partner discovery is not enabled, then closed federation must be configured for your online tenant.

• The Blocked domains list in the on-premises deployment must exactly match the Blocked domains list for your online tenant.

• The Allowed domains list in the on-premises deployment must exactly match the Allowed domains list for your online tenant.

• Federation must be enabled for the external communications for the online tenant, which is configured by using the Lync Online Control Panel.

DNS Settings

When creating DNS records for hybrid deployments, all Lync external DNS records should point to the on-premises infrastructure. For details on required DNS records, please refer to Domain Name System (DNS) requirements for Lync Server 2013.

Additionally you need to ensure that the DNS resolution described in the following table works in your on-premises deployment:

Depending on how DNS is configured in your organization, you may need to add these records to the internal hosted DNS zone for the corresponding SIP domain(s) to provide internal DNS resolution to these records.

Firewall Considerations

Computers on your network must be able to perform standard Internet DNS lookups. If these computers can reach standard Internet sites, your network meets this requirement.

Depending on the location of your Microsoft Online Services data center, you must also configure your network firewall devices to accept connections based on wildcard domain names (for example, all traffic from *.outlook.com). If your organization’s firewalls do not support wildcard name configurations, you will have to manually determine the IP address ranges that you would like to allow and the specified ports.

Refer to the Help topic Office 365 URLs and IP address ranges.

Port and Protocol Requirements

In addition to the port requirements for internal Lync Server 2013 communication, you must also configure the following ports.

User Accounts and Data

In a Lync Server 2013 hybrid deployment, any user that you want to home in Lync Online must first be created in the on-premises deployment, so that the user account is created in Active Directory Domain Services. You can then move the user to Skype for Business Online, which will move the user’s contact list.

When you synchronize user accounts between your Lync on-premises and Lync Online deployments with AD FS and Dirsync, you need to synchronize the AD accounts for all Lync users in your organization between your on-premises and online Lync deployments, even if users are not moved to Lync Online. If you do not synchronize all users, communication between on-premises and online users in your organization may not work as expected.

Important

If the user is created by using the online portal for Microsoft 365 admin center, the user account will not be synchronized with on-premises Active Directory, and the user will not exist in the on-premises Active Directory. If you have already created users in Lync Online, and want to configure hybrid with an on-premises Lync Server, see Moving users from Lync Online to Lync on-premises in Lync Server 2013.

You should also consider the following user-related issues when planning for a hybrid deployment.

• User contacts The limit for contacts for Lync Online users is 250. Any contacts beyond that number will be removed from the user’s contact list when the account is moved to Lync Online.

• Instant Messaging and Presence User contact lists, groups, and access control lists (ACLs) are migrated with the user account.

• Conferencing data, meeting content, and scheduled meetings This content is not migrated with the user account. Users must reschedule meetings after their accounts are migrated to Lync Online.

User Policies and Features

• In a Lync Server 2013 hybrid environment, users can be enabled for Instant Messaging, voice, and meetings either on-premises or online, but not both simultaneously.

• Lync Client Some users may require a new client version when they are moved to Lync Online. For Office Communications Server 2007 R2, users must be moved to a Lync Server 2013 pool prior to migration to Lync Online.

  For more information about client support, see Clients for Lync Online and Supported Lync clients and network port configurations.

• On-premises policies and configuration (non-user) Online and on-premises policies require separate configuration. You cannot set global policies that apply to both.

Topic Last Modified: 2014-01-23

Lync Server 2013 supports several types of client software that you can deploy to your organization’s users, including computer-installed client software, web-based clients, and mobile devices. This topic outlines the clients that you can use. For a detailed comparison of the features provided by Lync Server 2013 clients, see Client comparison tables for Lync Server 2013.

Lynch Mob

Lync 2013

Lync 2013 is the full-featured client for Lync Server. The Lync 2013 user interface has been fully redesigned and includes newly integrated features, such as Persistent Chat (Lync 2010 had a separate client for chat functionality), tabbed conversations, video preview, and multiparty video. For a summary of changes, see What's new for clients in Lync Server 2013.

Lync 2013 client setup is part of the Office setup program on the installation media.

Online Meeting Add-in for Lync 2013

The Online Meeting Add-in for Lync 2013 supports meeting management from within Microsoft Outlook messaging and collaboration client. The Online Meeting Add-in for Lync 2013 software installs automatically with Lync 2013.

Lync Web Scheduler

Lync Web Scheduler is a web-based meeting scheduling and management tool for users who don’t have access to Microsoft Outlook, or who are on an operating system not based on Windows. With Lync Web Scheduler, users can create new meetings, modify existing meetings, and send invitations using their preferred email program.

Lync Web App

Lync Web App is the web-based conferencing client for Lync Server 2013 meetings. In this release, the addition of computer audio and video to Lync Web App provides a complete in-meeting experience for anyone who does not have a Lync client installed locally. Meeting participants have access to all collaboration and sharing features and presenter meeting controls.

If Lync 2013 is not installed on a user’s computer and the user clicks a meeting link in a meeting request, Lync Web App opens. T25 workout free download. You can also configure the Meeting Join page to allow users to join meetings by using previous versions of clients; see Configuring the meeting join page in Lync Server 2013 in the Deployment documentation.

Because of the enhancements to Lync Web App, an updated version of Microsoft Lync 2010 Attendee is not available for Lync Server 2013. Lync Web App is the client of choice for participants outside your organization. With Lync Web App, no local client installation is required, although audio, video, and sharing features require installation of a plug-in during first use.

Lync 2013 Basic

Lync 2013 Basic is a downloadable client for customers who have a licensed, on-premises Lync Server 2013 deployment and customers who subscribe to a Microsoft 365 or Office 365 plan that does not include the full Lync 2013 client. The Lync Basic client includes enhanced presence, contacts, instant messaging (IM), Lync meetings, and basic voice functionality. Features not supported in Lync Basic include multiparty video, OneNote integration, virtual desktop infrastructure (VDI) support, skill search, recording, Enterprise Voice features, and advanced call handling (for example, call forwarding and Team Call). For details, see Client comparison tables for Lync Server 2013.

Lync Windows Store App

Lynchburg Lemonade

The Lync Windows Store app is a touch-optimized Lync app designed specifically for Windows 8.1, Windows 8, and Windows RT. Torrent flow the psychology of optimal experience definition. Users can download the app through the Windows Store by searching for 'Lync.' For more information, see Client comparison tables for Lync Server 2013, Lync Windows Store app requirements for Lync Server 2013, and Deploying Lync Windows Store app in Lync Server 2013.

Lync 2013 for Mobile Devices

Lync 2013 mobile apps now include voice over IP (VoIP) and video over IP capabilities, in addition to contacts, presence, and IM features. Mobile users can choose to communicate with others through IM, voice calls, or video calls by using either Wi-Fi or their cellular data connection. With a single click of the meeting link in a calendar item, mobile users can join voice and video meetings. For more information about Lync 2013 mobile apps, see Planning for mobile clients in Lync Server 2013.

Supported Clients from Previous Releases

Lync Server 2013 supports the following clients from previous server releases. You can make certain previous clients available to users when they join meetings. For details, see Configuring the meeting join page in Lync Server 2013 in the Deployment documentation.

Lynched

• Lync 2010 Lync 2010 provides a full desktop experience, including IM, enhanced presence, voice, video, sharing, and telephony. However, none of the new features introduced in Lync Server 2013 will be available until the user’s client is upgraded to Lync 2013.

• Lync 2010 Mobile Lync Server 2013 supports all of the Microsoft Lync 2010 Mobile mobile apps. Microsoft Lync 2010 Mobile provides IM, enhanced presence, and telephony for users in your organization who are connecting from a smartphone or a phone running a Professional edition of Windows Mobile. You can instruct your users to install Microsoft Lync 2010 Mobile by directing them to the app marketplace for their mobile phone. For details, see “Planning for Mobile Clients” in the Lync Server 2010 documentation at https://go.microsoft.com/fwlink/p/?LinkID=235955.

• Lync Phone Edition Lync Phone Edition software for intelligent IP phones (for example, USB-attached phones) has not been updated for Lync Server 2013. Lync Phone Edition continues to be supported in for placing and receiving calls, enhanced presence, and client audio capabilities for conferences.

• Lync 2010 Attendant The Microsoft Lync 2010 Attendant integrated call-management program enables a receptionist to manage multiple conversations at the same time through rapid call handling, IM, and onscreen routing.