Skype For Business For Mac Client
The new client is, I’d say, a fair and equitable companion to the Windows Skype for Business client. There are some differences, and (as of now) a few limitations. But overall, I think our Mac customers will enjoy this client very much. After the latest update for Skype for Business (version 16.5.185), I started getting a mac notification for Skype for Business that says 'We're having trouble connecting to the server. If this continues, please contact your support team.'
We just downloaded the Skype for Business Mac Client and are unable to Manually enter the internal discovery FQDN. We're using on premise Skype for Business Servers When going to 'advanced' options and entering the internal server configuration, the save button remains greyed out and I'm unable to utilize our settings. Auto-discovery does not work by design, so this is something we'll need if we're going to roll out Skype for Business. Any help with users facing a similar issues is appreciated. Hi Daniel, The input validation mechanism validates that the following are present in the fields: 1. “autodiscover/autodiscoverservice.svc/root” When the two above are present, the save button should light up. For Skype for Business Online, the correct URL is: Since you are using the on-premises Skype for Business Servers, please use the correct URL and check again.
For more information about features available in Skype for Business Basic in comparison to the Skype for Business client, please visit this page: Skype for Business client comparision chart Note: This Skype for Business Basic MSI desktop client provides presence, instant messaging and conferencing features. If you are licensed for Office 365. Mac and Mobile clients. No word on a new Mac client yet, but the new Skype for Business mobile apps will be available on iOS and Android “in the coming months,” I was told. The new client is, I’d say, a fair and equitable companion to the Windows Skype for Business client. There are some differences, and (as of now) a few limitations. But overall, I think our Mac customers will enjoy this client very much.
Also, our engineering team is aware of the situation and will improve validation code/logic to provide an example of the correct format in the app. Thanks, Franky. Hi, I'm having the same problem as Daniel. First, trying to put 'don't allow my Skype for Business client (Skype Entreprise) to connect. When I enter 'autodiscover/autodiscoverservice.svc/root' as internal / external address, then I can try the connection (otherwise, clicking on the button don't do anything).
Skype For Business For Mac Client For Skype
The connection don't work, I'm stuck with the blue circle rotating endlessly. What should I do? On the other hand, I can connect correctly with the same parameters with Microsoft Lync 2011 for Mac. So I guess my settings are right.
Hi Thib, I'd like to clarify that Skype for Business client for Mac is built on the Unified Communications Mobile Platform, it shares the same stack as iOS and Android mobile applications and communicates with the server via UCWA (Unified Communication Web API) which is different from Lync for Mac client. So, you are not able to sign in to Skype for Business for Mac with the same parameters with Lync for Mac. Free download aperture 3 for mac.
Skype For Business Mac Settings
Please use the parameters which you are using to sign in to mobile client. Thanks, Franky. Hi Jdcarlow, About the same issue, could you confirm if you have issue to save the manually configuration or have issue to sign in to Skype for Business for Mac client with manually configuration? About the URL for manually configuration for Skype for Business for Mac, please refer to the format: About the detailed URL, have you tried to use the URL for mobile client to sign in to Skype for Business for Mac client? Thanks, Franky. Hi Franky, No have no issue in saving the correct autodiscover url in manual configuration. Using the manual configuration with the url format for mobility however in my opinion based on Microsoft's blurb will not work if you have the latest Nov 2016 Cumulative Update - with this update is it the case the Mac client will be treated as a desktop client hence in my case (Nov 2016 CU installed) mobility is not a requirement, I have tried using the correct mobility url but it will not sign-in, however if mobility is not required then the automatic discovery (autodiscover checked) should work (which will look at the local pool fqdn on port 5061).