Hi, I'm currently looking into why users with iphones cannot enable Push notifications. When entering into the settings of the SfB application, it says under Push Notifications Status, 'Not Supported. Please contact your system admin for additional information on how to enable Push Notifications'. Having to convert standard keyboard for mac use. You can see this in the attached screen shot. We have enable push notifications for Microsoft and Apple devices, and also have the federated partners set up. I have run the following synthetic transactions to test the configuration which all returned success. Test-CSFederatedPartner –targetfqdn –domain push.lync.com Test-CSMCXPushNotification – AcessEdgeFQDN Any help would be appreciated.

May 8, 2017 - Skype for Business Mac - You're not configured to connect to the server. I've been using Skype for Business Mac preview since its release.

Thanks Michael. I do believe it was already depricated with Lync2013 client and don't think it's needed for SfB either actually. ' If you use Windows Phone with Lync 2010 Mobile or Lync 2013 Mobile client, push notification is an important consideration. If you use Lync 2010 Mobile on Apple devices, push notification is an important consideration. Using photos on macbook. If you use Lync 2013 Mobile on Apple devices, you no longer need push notification.' Is only mention the MPNS and not APNS right? Do you experience issues on apple devices?

I have the same issue in my organisation. Skype for Business is patched up to the November cumulative update. Push notifications work fine on Windows phones but work for about 30 seconds on iPhones until the screen locks and they stop working. All notification settings are set correctly on the device and push is enabled server side with the correct CSHosting Provider. I built a single server lab environment applied all patches and saw that it was working fine on iPhone. I then decided to test re-installing the web components server element to see if this was preventing the push notification from working in my prod environment. Since then my lab push notification functionality no longer works.

I am struggling to find what changes have caused this. Hopefully it is something microsoft are re-introducing intentionally in the next update release cycles.

So I redid my S4B servers in a test envirionment. I am still unable to get Push notifications working. I didn't install ANY updates this time around. This is what leaves me to believe that maybe it's the client side that has the issue. But, I do have all the history updates as I save them.

With that, are you saying you think it was working in the June udpate? I will try and update the server to June's update and see what happens. I have a fealing it's not going to solve anything though:( And just FYI, both Test-CsFederatedPartner and Test-CsMcxPushNotification commands are curently a success but still no push notification. I have confirmed on multiple environments that once you apply the Febuary update, the Mobile client now says supported. If you do a get-CsMobilityPolicy the Global Policy already has EnablePushNotifications set to True. Push Notifications do seem to be working as well as conversation history. However All Front End Servers have the following errors: Ucwa Service can't connect to the configured Push Notification Proxy: Cause: The Push Notification Proxy is currently unreachable.