Sep 15, 2011  I was told the official word is Lync 2011 for Mac does NOT work with 365. They are aware that web sites and product documentations state that it does, but it does not. They said they were working on this but could not tell me when something would be released. They indicated it. This fixed things for me when Lync for Mac 2011 got broken by the macOS Sierra upgrade. Lync would work off-net but not when I was on the company network. Hi Sean, can you let me know how this can be done?

Adium doesn’t provide all of the functionality of Lync on your Mac but it includes all the most essential features such as chat and file sending. If this doesn’t work for you or you need the fully functional version of Lync 2013 for Windows on your Mac, your only other option is to. Alternatively, you’ll have to wait until. If you have any other questions about connecting Adium to Microsoft Lync, let us know in the comments below.

It takes a couple of minutes to appear which is odd. Macphun's Aurora HDR 2016 crashes trying to send a file from Lightroom. I reported that to MacPhun weeks ago on the GM releases.

To use AutoUpdate, start Microsoft Lync or another Microsoft Office application, and then click Check for Updates on the Help menu. Lync users prompted for Keychain access rights Lync stores user credentials in the keychain. If you don’t want to see the keychain access dialog, select Always Allow. Cannot sign into Lync if the computer’s system date is set to an older date Make sure your computer’s system date is current. Enabling logging can cause performance issues Turn off logging after troubleshooting is completed. If you do not turn off logging, the log files continue to increase in size and can cause performance issues.

In fact, it looks like Mac users will have to wait until Skype For Business has been released on all mobile platforms before it finally arrives on Mac next year. So if you’re sick of Lync not working on Mac, hogging your Mac’s resources, crashing, missing IM chats, dropping calls and unreliable screensharing, fear not – here’s how to use Adium as an alternative to Lync on Mac so you can kiss goodbye to Microsoft Lync for good. How To Setup Lync For Mac Alternative Adium Note that this method of connecting Adium to Lync works for those with and without an Office 365 account. Those with an Office 365 account only need their Office 365 login details. Those that don’t, will need their Lync Server and Port connection details. Adium is probably the best open source messenger client available for Mac and even better, it not only allows you to add a Lync account to it but almost any other IM client too.

So you’re getting several messaging clients in one for free. To connect Adium to Lync, you’ll also need the SIPE plugin. Note that Adium works on OS X 10.6.8 and above but there are also.

This scenario isn't supported in Skype for Business Online. For the best experience, you should use both Skype for Business Online and Exchange Online. Microsoft office for mac 2011 home and student.

The individual applications - Excel, PowerPoint, Outlook and Word - will continue to operate after support ends, but companies will be taking a risk, however small, that malware exploiting an unpatched flaw will surface and compromise systems. To receive security and non-security updates after Oct. 10, IT administrators must deploy Office for Mac 2016 or instruct workers covered by Office 365 to download and install the newer suite's applications from the.

Launch Microsoft Lync 5. On relaunch, the prompt no longer appeared.

That versions 15.34 and earlier are not supported, and you may not be able to launch the apps. You are advised to update to 15.35 or later, but even that’s no guarantee. Not all Office functionality may be available, and you may encounter stability problems where apps unexpectedly quit.

I'm on running Lync 14.4.1 on macOS 10.12 using a MacBook Pro (Retina, 15-inch, Mid 2015). At first I was getting the weird keychain password prompt that I was able to get rid of after deleting the file in the /Library subdirectory. Not when I enter a password and hit sign in the spinning progress wheel freezes, the rainbow wheel shows up, then it finally un freezes and says: 'Sign in to Microsoft Lync failed because the service is not available or you may not be connected to the Internet.' To resolve the 'Sign in to Microsoft Lync failed because the service is not available or you may not be connected to the Internet.' You need to reimport your Lync server certificate. Ask your system administrator of the Lync server to export the server certificate and provide to you: - Log into Lync server - Open MMC > Add/Remove Snap-in > Select Certificates > Click Add > Select Computer account > Click Next > Local computer > Finish > OK - Expand Certificates > Personal > Certificates - Click on the certificate with the fully qualified domain name (i.e.

They indicated it might be a separate client. This feels like a bait and switch on customers who were promised this service, not communicated that it would not work, and not being given an ETA on availability. How the author of this blog was able to connect and states he knows others who are is confusing at best. I'd like to understand if this is some kind of pre-release software or if indeed its on prem Lync that is being used. I have a purchased copy of Office 2011 for the Mac, and the Office365 E3 plan. Office365 advertises Lync as one of the benefits it offers.

However, the SIPE plugin only works on OS X 10.8 Mountain Lion and above so you need to be using OS X 10.8 or higher on order to connect Lync to it. Just follow these steps to set up Lync via Adium on your Mac: After you have installed Adium, make sure it is closed. Download the and it will appear in your downloads folder. Unizip it and copy it to the folder: /Users//Library/Application Support/Adium 2.0/PlugIns The easiest way to find this folder is to make sure that Finder is selected in the bottom left corner of your Dock and select “Go” in the Menu Bar at the top of the screen and hold down the “Alt” key.

To do this, follow these steps: • Open the Keychain Access certificate management utility via open Finder > click Applications > Utilities > Keychain Access. • In the left pane, click login, and then click Certificates. • In the right pane, find a certificate that's named Unknown or Communications Server, select it, and then delete it.

Once imported, double click the certificate in Keychain and in the Trust section change 'When using this certificate' to 'Always Trust'. Start Lync back up, and you should be able to log in.

An interesting thing about this OC_KeyContainer keychain and associated password entry is that the persistence of it appears to be tied to whether or not Lync is set to save the user’s account password. If the password is set not to be saved: The OC_KeyContainer__username@company.com keychain and OC_KeyContainer__username@company.com password entry in the user’s login keychain are created when Lync connects to the Lync server. Once the Lync application is quit, the OC_KeyContainer__username@company.com keychain and application password entry are automatically deleted. On relaunch, a new OC_KeyContainer__username@company.com keychain and application password entry in the user’s login keychain are created. If the password is set to be saved: If they do not already exist, the OC_KeyContainer__username@company.com keychain and OC_KeyContainer__username@company.com password entry in the user’s login keychain are created when Lync connects to the Lync server. A Microsoft Lync password entry is also created in the user’s login keychain if one does not already exist.

Unfortunately, this didn’t fully solve the issue. • I decided to delete the Lync directory in the Documents>Microsoft User Data>Microsoft Lync Data, you will be able to find it through “Finder”. • Under the advanced tab on the Lync login screen I added the server name sipdir.online.lync.com:443. Afterwards the error message changed. • Unfortunately I still couldn’t login. The weird idea, as mentioned in Tom Laciano’s post, to use a wrong user id (I used a “ ” in front of my user name) finally made it work. Of course it didn’t work with this wrong user name, it generated a login error message again. But once I entered the right username afterwards it worked.

Lync has limited support for devices and device settings. Note: This issue is resolved in the. Please install the latest update. Lync updates are also available from Microsoft AutoUpdate. AutoUpdate is a program that automatically keeps Microsoft software up-to-date.

Yep same damn app crash. I sent the data to Macphun and they told me they were working on something.

I am afraid that something in Aurora 2017 which should be out by the end of October. Not impressed with Macphun at all.

Don’t forget to quit the application before updating and restarting. It should work with Office 365 Recently, we’ve migrated from Google Apps to Office 365. Both solutions have pro’s and con’s, but that’s not what this post is about. It’s quite easy to benefit from Office 365 if you are using Office 2011 for Mac. But the same seemed not directly applicable to Lync.

Hi clancifer, Welcome to post in our forum. Would you please tell us did the issue only appeared on the specific client? Did you try to use another Mac device, is that the same issue? If the issue only appeared on the specific Lync client, please make sure the Lync client with latest update and test again. In order to avoid the impact of DNS, you could try to manually sign in Lync client, for more details, please refer to If all users have this issue, it may be something wrong with your Lync server side. You could use Microsoft remote connectivity analyzer to test if there is any error occurred. Moreover, make sure you Lync server with the latest update.

Kerberos authentication fails when the user who signs in is different from the Kerberos Active user During the sign-in process, Lync always uses the Active User ticket to authenticate and if the credentials do not match, the sign-in fails. You need to manually switch the Active User information in the operating system. Cannot transfer files to users who are outside the corporate network You can send files to users within your corporate network only. Cannot request control on a desktop that is being shared by a user using Lync for Mac A device using Lync for Mac 2011 with desktop sharing cannot request control or give control to another device. Cannot convert an appointment in Outlook to an online meeting To create an online meeting from Outlook, you must open a new Outlook meeting request.

With the release of, there was some hope that Microsoft would finally update Mac users from clunky old Lync 2011 for Mac to either Skype for Business for Mac or at the very least, Lync 2016 For Mac. The good news is that but the bad news is that it seems Microsoft won’t be releasing it until 2016. In fact, it looks like Mac users will have to wait until Skype For Business has been released on all mobile platforms before it finally arrives on Mac next year.

Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link. Alice Wang TechNet Community Support Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact. Thank you for the reply. I can confirm that the failure to login only happens on the one MBP that was updated to 10.12 Sierra. I can log into Lync on using my same credentials on any other three macs that are running 10.11.6 (El Capitan).

I reported that to MacPhun weeks ago on the GM releases. Their attitude was.it will all be OK when you get the official release of Sierra. So I upgraded from the GM to official Sierra build yesterday. Yep same damn app crash. I sent the data to Macphun and they told me they were working on something. I am afraid that something in Aurora 2017 which should be out by the end of October.

As mentioned earlier, I received the same OC_KeyContainer password error that others are reporting immediately upon trying to use Lync after installing Sierra update. I did a full uninstall, including removal of all libraries and keychain pieces, and a fresh install of Lync 14.4.1 but still the same error message. As a test, I downloaded Lync 14.4.1 on my personal Mac Book Air running El Capitan and I was able to log into Lync successfully that way. From all indicators, there is something wrong with the way Lync is functioning within the Sierra update. This Fixed My issue, I make sure you always allow the trust in the last step. To resolve the 'Sign in to Microsoft Lync failed because the service is not available or you may not be connected to the Internet.'

Overview: Due to the shortcomings of the current Realtek 81xx Hackintosh drivers (such as lack of or limited support of 8111E, 32/64-bit, sleep issues), I endeavored to port the Linux RTL81xx driver to Mac OS X. Download RealTek RTL8102E-GR Drivers v.2.0.0 for Mac OS 10.x. Download is free of charge. Being asked to add support for Realtek's Fast Ethernet PCIe NICs to my RTL8111 driver I got tired of answering the same old question again and again so that I finally decided to write a separate driver for these chips and to make a few of you guys and gals happy. Tonymacx86.com: Home of the CustoMac Buyer’s Guide, iBoot, MultiBeast, UniBeast, and the world’s most helpful #hackintosh #mac #osx support community. Realtek rlt8102e driver for mac. Free RealTek RTL8101E drivers for Mac OS 10.x. Found 2 files. Select driver to download.

Their attitude was.it will all be OK when you get the official release of Sierra. So I upgraded from the GM to official Sierra build yesterday.

So far from my testing the below work for me. MOD EDIT: This is a wiki post, which is editable by anyone with the appropriate rights. Please update this post with compatible and incompatible apps to ensure the list is comprehensive. For apps with limited compatibility, please include a link to your post explaining the limitations.

If you just install and use the.pkg file, everything works great • Slow Wi-Fi issues with MacOS Sierra: This is an issue I haven’t had, but I’ve received some feedback that this can be an issue. Here is a link to find out more info a out what some have exerpienced as well as a fix if you are experience it – In summaryyou may still find a few minor annoyances here and there, but in my case, there isn’t anything that is blatantly broken or not working outside of Eset Cyber Security. I’m able to perform all my normal activities without being slowed down by something not working or having to work around issues.