Lync For Mac 2015

On November 11, 2014, Microsoft announced that Lync would be renamed Skype for Business in 2015, also adding support for video calls with Skype users. On September 22, 2015, Skype for Business 2016 was released alongside Office 2016. On October 27, 2016, the Skype for Business. Skype for Business 2015 is a full-featured client for Skype for Business Server 2015 or 2019. The Skype for Business user interface has been fully redesigned and includes newly integrated features, such as Call Monitor, Skype directory integration, emoticons, and more. For a summary of changes, see Lync is now Skype for Business — see what's new. Source: July 2015 update for Lync for Mac 2011 14.1.1 (KB3074981) Download: Download the Lync for Mac 2011 14.1.1 update package now Fixes: KB 3074996 Call forwarding option for. High Point › Lync Training › Training › Sharing Desktop for Mac. Sharing Desktop for Mac Posted on: 04.8.2015. Leave a Reply Cancel reply. 3054946 July 14, 2015, update for Lync 2013 (Skype for Business) (KB3054946) Notes. Method 2 is available to customers who have the Lync 2013 (Skype for Business) update published in or after September 2015.

Introduction

This article contains information about the AllowAdalForNonLyncIndependentOfLync setting in Skype for Business 2016, Skype for Business 2015, Lync 2013, and Exchange Online. This article also describes which Exchange Online and Skype for Business deployments require this setting.

More information

The information in this article helps IT and Office 365 administrators in the following scenarios:

• Setting up Lync 2013 and Skype for Business users to be homed on Skype for Business Server 2015 or Lync Server 2013 on-premises.
• Setting up mailboxes in Exchange Online in Office 365 by using Modern Authentication and Multi-factor Authentication (MFA) with OAuth.

In these scenarios, the available functionality in the previous environment is as follows:

• The Skype for Business Desktop and Lync 2013 clients connect to Skype for Business Server by using NTLM or the Kerberos authentication protocol, a user name and password, or Windows Integrated Authentication.
• After you sign in, Skype for Business or Lync 2013 connects to the user's mailbox in Exchange Online by using Exchange Web Services (EWS). Although the EWS service advertises OAuth settings (the authorization URI), the client ignores this and falls back to a non-MFA sign-in by using an OrgID channel. This limits sign-in protocols to a user name and password or to Windows Integrated Authentication.

The new AllowAdalForNonLyncIndependentOfLync setting lets Skype for Business Desktop or Lync 2013 clients unblock MFA in Exchange Online in situations in which the IT administrator must enforce MFA on Exchange Online. You can apply this new setting by using Group Policy in the Windows registry or as an in-band endpoint policy setting on the Skype for Business server.

After you apply this setting to the client computer, the environment functionality is as follows:

• The Skype for Business Desktop or Lync 2013 clients connects to Skype for Business Server by using NTLM or the Kerberos authentication protocol. Specifically, a user name and password or Windows Integrated Authentication will be required for a successful connection (as it was previously).
• After you sign in, Skype for Business or Lync 2013 connects to Exchange Web Services (EWS). If the EWS service advertises OAuth settings (authorization URI), the client uses MFA. Additionally, if a credentials refresh is necessary, the user will be prompted through the Modern Authentication dialog box.

Note

This setting is not required for cloud-only topologies or if Exchange and Skype for Business are both configured for a hybrid environment that has Modern Authentication enabled. For detailed information about the topologies, see Skype for Business topologies supported with Modern Authentication.

In some cases (specifically, Mixed 1, Mixed 3, and Mixed 5 topologies as described in Skype for Business topologies supported with Modern Authentication), you have to set the AllowADALForNonLynIndependentOfLync registry key correctly for Windows desktop clients.

Important

Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

Warning

Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Use either of the following methods to apply the AllowAdalForNonLyncIndependentOfLync setting.

Method 1: Use Group Policy

Note

The option to enable this setting through Group Policy is available only after you apply the July 2015 Public Update (PU).

Lync For Mac 2015 Laptop

For Skype for Business or Lync 2013 clients 15.0* (available from the September 2015 PU only):

HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice15.0Lync

For Skype for Business or Lync 2013 clients 16.0*:

HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice16.0Lync

Then, apply the AllowAdalForNonLyncIndependentOfLync registry key setting:

'AllowAdalForNonLyncIndependentOfLync'=dword:00000001

Method 2: As an in-band setting on the Lync server

Note

This option is available through the September PU only.

To enable the in-band setting on the Lync server, run the following cmdlet:

Important

To enable Modern Authentication for Office 2013 applications on a Windows-based device, you must set the following additional registry key.

More information

The information in this article helps IT and Office 365 administrators in the following scenarios:

• Setting up Lync 2013 and Skype for Business users to be homed on Skype for Business Server 2015 or Lync Server 2013 on-premises.
• Setting up mailboxes in Exchange Online in Office 365 by using Modern Authentication and Multi-factor Authentication (MFA) with OAuth.

In these scenarios, the available functionality in the previous environment is as follows:

• The Skype for Business Desktop and Lync 2013 clients connect to Skype for Business Server by using NTLM or the Kerberos authentication protocol, a user name and password, or Windows Integrated Authentication.
• After you sign in, Skype for Business or Lync 2013 connects to the user's mailbox in Exchange Online by using Exchange Web Services (EWS). Although the EWS service advertises OAuth settings (the authorization URI), the client ignores this and falls back to a non-MFA sign-in by using an OrgID channel. This limits sign-in protocols to a user name and password or to Windows Integrated Authentication.

The new AllowAdalForNonLyncIndependentOfLync setting lets Skype for Business Desktop or Lync 2013 clients unblock MFA in Exchange Online in situations in which the IT administrator must enforce MFA on Exchange Online. You can apply this new setting by using Group Policy in the Windows registry or as an in-band endpoint policy setting on the Skype for Business server.

After you apply this setting to the client computer, the environment functionality is as follows:

• The Skype for Business Desktop or Lync 2013 clients connects to Skype for Business Server by using NTLM or the Kerberos authentication protocol. Specifically, a user name and password or Windows Integrated Authentication will be required for a successful connection (as it was previously).
• After you sign in, Skype for Business or Lync 2013 connects to Exchange Web Services (EWS). If the EWS service advertises OAuth settings (authorization URI), the client uses MFA. Additionally, if a credentials refresh is necessary, the user will be prompted through the Modern Authentication dialog box.

Note

This setting is not required for cloud-only topologies or if Exchange and Skype for Business are both configured for a hybrid environment that has Modern Authentication enabled. For detailed information about the topologies, see Skype for Business topologies supported with Modern Authentication.

In some cases (specifically, Mixed 1, Mixed 3, and Mixed 5 topologies as described in Skype for Business topologies supported with Modern Authentication), you have to set the AllowADALForNonLynIndependentOfLync registry key correctly for Windows desktop clients.

Important

Follow the steps in this section carefully. Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur.

Warning

Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

Use either of the following methods to apply the AllowAdalForNonLyncIndependentOfLync setting.

Method 1: Use Group Policy

Note

The option to enable this setting through Group Policy is available only after you apply the July 2015 Public Update (PU).

Lync For Mac 2015 Laptop

For Skype for Business or Lync 2013 clients 15.0* (available from the September 2015 PU only):

HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice15.0Lync

For Skype for Business or Lync 2013 clients 16.0*:

HKEY_CURRENT_USERSoftwarePoliciesMicrosoftOffice16.0Lync

Then, apply the AllowAdalForNonLyncIndependentOfLync registry key setting:

'AllowAdalForNonLyncIndependentOfLync'=dword:00000001

Method 2: As an in-band setting on the Lync server

Note

This option is available through the September PU only.

To enable the in-band setting on the Lync server, run the following cmdlet:

Important

To enable Modern Authentication for Office 2013 applications on a Windows-based device, you must set the following additional registry key.

For more information about the EnableADAL setting, go to the following Microsoft website:

For more information about the Skype for Business Desktop client version for Modern Authentication flow (July update), see the following Knowledge Base article:

3054946 July 14, 2015, update for Lync 2013 (Skype for Business) (KB3054946) Adobe reader for mac os x 10.6 8ate mac os x 10 6 8 to 10 9.

Notes

• Method 2 is available to customers who have the Lync 2013 (Skype for Business) update published in or after September 2015.
• The same September update (or a later version) has more Modern Authentication-related fixes. Customers should plan to upgrade to it after it is published.

Still need help? Go to Microsoft Community.

Microsoft has just released an update for the Lync for Mac client. This update brings E.911 functionality, along with some improvements and enhancements for Video and File Sharing. Read more in the the Lync blog. The update version is 14.0.9. Download the update here.

I recently had a scenario, where clearing up the current Skype for Business Profile solved our problem, I our case the Skype for Business client had problems logging on and it was not related to network or DNS. The desktop client of Skype for Business (or Lync 2010 / Lync 2013) cache a lot of information on the PC. This caching information is used when the client does e.g. The cache is to minimize the bandwidth consumption of the Skype for Business (Lync) client, since it retrieves a lot of information from cache.

Peter is an Exchange specialist with over 15+ years of experience with Exchange Server and certified Microsoft Certified Master (MCM) and Microsoft Certified Solutions Master (MCSM) on Exchange Server. He has been awarded the Microsoft MVP award, every year since 2007. He is active in the Microsoft community and User Group Leader for CoLabora (a danish UC & Cloud User Group).

He works as an Cloud & Infrastructure Architect and Consulent, with primary focus on Exchange, Office 365, Azure and Skype for Business. Related Posts. Hello, I really need some help as I work for a large company and the responses from the off shore help desk are pathetic or lack of a response. Mac os virtualbox image download free. I keep getting the DNS KB System details: Windows 10 Anniversay Build 1607 Office 365 Skype for Business 16.0 I have deleted the SIP and TRACING folders in USERNAME APPDATA LOCAL MICROSOFT OFFICE 16.0 I have used windows doctor to clean the registry. I have rebuilt the windows guest and Skype works for a short period (few days) then has the issue again I am not the server admin I am an end user.

I do not know how to create the SIP entries if I need to. Hi Peter, I'd like to use the phone line from a standalone SIP client. Could be a softphone, physical, doesnt matter. I dont even want all the collab integration, just telephoning. The idea behind this is to be able to telephone without having to log in to skype, so I can call and be called but not bothered via IM.

Also, if this is even posible, i have a physicall SIP phone that would love to use along with skype just for the good old feel of the hardware phone. =) My company provided a DID number along with skype so i'm not using just the integrated Voip, there must be a SIP gateway skype is trunking with!!

Lync For Mac 2015 Download

I noticed today that a large shipment of Polycom phones we were going to deploy were using the RTM version of Lync Phone Edition and were outdated compared to Microsoft's latest version. That being said, here is a guide on how to update the firmware for your phones. At the time of this writing, it appears there are only a few different manufacturers that distribute the Microsoft Lync Phone Edition phones. For reference, here are the Microsoft URLs for each of those phone types:. Microsoft Lync Phone Edition for Aastra 6721ip and Aastra 6725ip. Microsoft Lync Phone Edition for Polycom CX700 and LG-Nortel IP Phone 8540. Microsoft Lync Phone Edition for Polycom CX500, Polycom CX600 and Polycom CX3000.

March 2015 Update For Lync For Mac Download

Microsoft Lync Phone Edition for HP 4110 and HP 4120. Deploying latest firmware for the Microsoft Lync Phone Edition. Download the latest firmware for the Lync Phone Edition device. In my case, I want to push out the latest firmware for the Polycom CX600s, which can be found here (links to the firmware of other phones can be found above in this same article):.

Double click on the downloaded file ( UCUpdates.exe), and run through the wizard. Select your language:. Accept the EULA.

On this step, extract the files to a folder you can recognize. All firmware downloads are called UCUpdates.exe and ucupdates.cab, so I highly recommend you sort out each firmware to a corresponding folder. Click the 'Click this link to open folder in Windows Explorer.' and verify you see the ucupdates.cab file. Here we see the ucupdates.cab file. Copy the ucupdates.cab file over to your Lync Front End Server if you didn't in the first step. Execute the following powershell command (where the WebServer is the Front End Pool or Front End Server in a standalone instance):.

Updates For Lync Server 2013

Import-CsDeviceUpdate -Identity service:WebServer: lync.mydomain.local -FileName ' C: Polycom CX600 ucupdates.cab' -Verbose. Note: I added the optional -Verbose parameter to show the output of what the PowerShell command is doing behind the scenes. Some people have mentioned this step taking awhile to complete, this will at least give you some comfort if things are moving forward or not. Open sourve dvd burner software for mac.

Lync For Mac 2015 User

Once the command has completed successfully, head over to the Lync Server Control Panel (LSCP) (Web GUI), and navigate to Clients Device Update. Here you should see the firmware for your device and you should notice that the version shows up under the 'Pending Version' column. This means that the firmware will NOT be pushed until we manually approve it.

Now we will push out the firmware to one device to ensure the firmware actually works. Inside of the Lync Server Control Panel, click on the Test Device tab. Click the New button and then select Global test device. For Device Name, type in something like Polycom CX600 to identify what will be pushed to it, and then enter in the MAC address of the phone in the Unique identifier field. Note: if you use the MAC address as the Unique identifier, make sure you leave out any special characters, it should be only the hex address. Here is a screenshot below of my test device:. At this point, all you need to do is wait until the phone reboots and applies the update automatically (you don't need to approve the firmware or anything like that, it just starts to deploy to the test device).

If you want to check what is going on, if you login to your front end server and navigate to C: inetpub logs LogFiles, you can see the process of the phone trying to pull the update files and then reconnecting with the updates. In my case, I could see the phone boot, pull the new firmware files, and then reboot and make new requests with the latest version in the headers.