Call forwarding settings - bug identified RRS feed

  • Question

  • We have recently found what seems to be a bug with Skype for business 2015 client. Users can't edit the team call group in Skype for business client although the function is enabled.  They were trying to edit the team call group but it will show their previous setting after they made the changes.  This all started after we enabled call forward no answer feature for end users using Sefautil tool.  As soon as we use Sefautil to enable any feature on end user, call forwarding settings cannot be changed what so ever with Skype for business client.  

    We found a work around for that, we just have to temporarily try enabling call forward settings to a new number (say a dummy number - 1234). Interestingly the feature will turn on so all we have to do is turn off the feature post that users are able to edit the team call group in Skype for business client just fine and issue seems resolved.

    Note - Skype for business client 2015 is updated with latest May 2017 client patch and Servers with May 2017 CU.

    Anyone had similar experience? Any permanent fix for this?

    Thursday, June 22, 2017 8:44 PM

All replies

  • Hi shadythang,

    Thanks for sharing your workaround for us.

    Based on my research, there is no official document indicates this is a bug for the situation.

    For this issue, did this only appear on the specific SFB 2015 client, is that the same issue with Lync 2013 and Skype for business 2016?

    Please try to use other clients test if there is the same issue.

    If the issue just appeared on the specific client, please try to rebuild user profile test again. Moreover, you could try to repair your office then test again.


    Alice Wang

    Please remember to mark the replies as an answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 23, 2017 1:52 AM
  • Hello Alice,

    We had the same issue with SFB 2015 and SFB 2016, we do not have Lync 2013 client in our environment so never checked for it.  This sure seems to be bug.

    Friday, June 23, 2017 2:42 PM
  • How do we report this bug to MS?  Can anyone help me?
    Monday, June 26, 2017 5:47 PM
  • Maybe you can try to provide the feedback

    Monday, July 3, 2017 8:23 AM
  • Thanks touchtro, I have submitted the idea.
    Wednesday, July 12, 2017 7:33 PM