Mar 31, 2017  Skype for Business Mac Client March 2017 Update Summary – Note UCWA dependencies There been a new March 2017 update released for the Skype for Business Mac Clients. This could be cumulative update 4 i cant see it mentioning cu version anywhere at the mo so its march update for the SfB Mac Client with a lot of new features and bugs addressed.

I was having issues with a desk phone (Specifically a Polycom VVX310 running 5.4.0.10182) signing in to Lync 2013 with Ext/Pin. When attempting auth the phone would simply return “Lync Sign in Failed”. Pin Auth had been previously working and no changes to DNS or DHCP had been made and all certificates were valid.

Sinevibes drift feat. korg minilogue (free download for mac pro. Which things in thi.:Chain D.L.K.: Hi folks! Did you have a manifesto? How are you?Filewile: Daniel: Fine, thanks. We're preparing our South African tour!Mago: A bit nervous before leaving Europe to play in Africa.Andreas: And of course promoting our New Album, and already working onnew tracks and remixes.Chain D.L.K.: ccor.:Chain D.L.K.: Hydrophonic Records was born at the end of the 90s.

I cranked up the logs on the device and still couldn’t see any issues. It was grabbing the CA on boot and would contact Lync and get a webticket, however the following in the log raised an eyebrow.

Doubting the HTTPS certificate on the certificate service, I opened and confirmed that it was still valid and trusted.

The next step was to test an alternate phone and an alternate site. Same issue. This points us back to the issue being lync wide.

Luckily there are a few powershell cmdlets that we can use to test the web ticket service.

Test-CSClientAuth will allow us to test NTLM authentication against the web ticket service. TechNet article here

Test-CSPhoneBootsrap will allow us to test PIN/EXT auth against the web ticket service. TechNet article here

When testing these directly from your lync server you will need to fill out -TargetFqdn and -TargetURI to avoid DHCP lookups/failure. You can alternatively install the module on a PC that has DHCP and test from there.

Typical usage and responses for these cmdlets:

As you can see above, the reason reported back was invalid pin. In my case I wasn’t getting a response from the web-ticket at all (Above shown as demonstration)

So the issue was with the web service not responding. I restarted the internal web service within IIS and tested again. This resolved the issue and users were able to use ext/pin sign in again.

-->

Read this topic to learn about hardware, software, and infrastructure requirements for running Skype for Business on a Mac.

The Skype for Business on Mac Client is available for download.

Hardware and software requirements for Skype for Business on Mac

The Skype for Business on Mac client requires Mac OS X El Capitan and higher, and uses at least 100MB of disk space. We support the use of all built-in audio and video devices. External devices must be in the Skype for Business Solutions Catalog.

Note

This list is preliminary and some devices may be qualified for Lync, but not supported on Skype for Business on the Mac.Refer to the System requirements for the minimum hardware required.

Legacy Mac clients

Skype for Business Server 2015 also supports the following legacy clients on computers that are running Mac OS 10.5.8 or latest service pack or release (Intel-based) operating systems (Mac OS 10.9 operating system is not currently supported). For details about supported features, see Desktop client feature comparison for Skype for Business.

• Microsoft Lync for Mac 2011 (see Lync for Mac 2011 Deployment Guide)

• Microsoft Communicator for Mac 2011 (see Communicator for Mac 2011 Deployment Guide)

These clients are not supported by Skype for Business Server 2019. Climate app for mac free.

Infrastructure requirements for Skype for Business on Mac

The Skype for Business on Mac client leverages both the Unified Communications Management Platform (UCMP) as well as the Unified Communications Web API (UCWA) that our mobility clients use.

The client has the same requirements as our mobility clients in that you must have an Access Edge Server and Reverse Proxy deployed in a supported configuration.

Authentication

The Skype for Business on Mac client supports Cert-based authentication, Microsoft Modern Authentication, and Multi-Factor Authentication when deployed and enabled.

Note

Due to a current limitation, the user's Exchange credentials must be the same as their Skype for Business credentials.

Certificates

Certificates in use on the Access Edge, Reverse Proxy and Front End servers must not use the SHA-512 hash algorithm.

The HTTP Certificate Revocation List must be defined and accessible by the client. For example, we don't support an LDAP entry in the certificate as your Certificate Revocation List.

DNS

Mobility must be properly deployed for the Skype for Business on the Mac client to function properly. A common failure scenario is to have both of the following DNS entries resolvable on the internal network:

• lyncdiscoverinternal.<sipdomain>

• lyncdiscover.<sipdomain>

For more information, refer to: Deploying Mobility in Lync Server 2013, and the Microsoft Lync Server 2010 Mobility Guide.

See also