locked
Skype/Lync Patches Force Chat to Close Unexpectedly RRS feed

  • Question

  • Having a bit of a dilemma with patching Skype for Business 2016 via SCCM2012 Software Updates.  Corporate users don't like it when their chat closes without warning.  Our company has disabled chat history and requires workstations to be patched during the business day.  Although, I realize that Skype needs to be forced close in order to apply patch, it is causing issues for our Business users.  From their perspective, they are working and then out of the blue their chat closes without warning.  They loose the data they had in the open chat.  What are other companies doing to help alleviate this annoyance?  Does Microsoft have any plans to add a simple warning message to the Sykpe or Lync patches that would warn business users that their chat is about to close?  A simple warning message would resolve this!!!

    Thanks,

    PhillyJoe

    Friday, September 2, 2016 4:45 PM

Answers

  • Hi PhillyJoe,

    Welcome to post in our forum.

    I am not very familiar with SCCM, but based on my understanding, you may try the following steps to configure software updates:

    Step 1: Install and configure a software update point

    Step 2: Synchronize software updates

    Step 3: Configure classifications and products to synchronize

    Step 4: Verify software updates client settings and Group Policy configurations

    For more details, please refer to

    https://technet.microsoft.com/en-us/library/gg712312.aspx

    For more information about SCCM, you could get more suggestions from the forum below:

    https://social.technet.microsoft.com/Forums/en-US/home?category=systemcenter2012configurationmanager


    Alice Wang
    TechNet Community Support


    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.

    • Proposed as answer by Alice-Wang Monday, September 12, 2016 10:06 AM
    • Marked as answer by Alice-Wang Friday, September 16, 2016 10:04 AM
    Monday, September 5, 2016 9:13 AM

All replies

  • This is a good idea but in the meanwhile you could configure SCCM to ask the user for accept the update or not.

    Maybe this link will help?

    https://social.technet.microsoft.com/Forums/en-US/9cf1ff55-9295-498c-9a0e-b642e388d229/sccm-2012-sup-user-notification?forum=configmanagersecurity


    regards Holger Technical Specialist UC

    Saturday, September 3, 2016 8:39 AM
  • please check this link

    http://www.infoworld.com/article/2909525/security/re-issued-patch-kb-3013769-crashes-skype-for-business-rolls-win10-nagware-kb-2990214-resurfaces.html

    Saturday, September 3, 2016 8:54 AM
  • Hi PhillyJoe,

    Welcome to post in our forum.

    I am not very familiar with SCCM, but based on my understanding, you may try the following steps to configure software updates:

    Step 1: Install and configure a software update point

    Step 2: Synchronize software updates

    Step 3: Configure classifications and products to synchronize

    Step 4: Verify software updates client settings and Group Policy configurations

    For more details, please refer to

    https://technet.microsoft.com/en-us/library/gg712312.aspx

    For more information about SCCM, you could get more suggestions from the forum below:

    https://social.technet.microsoft.com/Forums/en-US/home?category=systemcenter2012configurationmanager


    Alice Wang
    TechNet Community Support


    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.

    • Proposed as answer by Alice-Wang Monday, September 12, 2016 10:06 AM
    • Marked as answer by Alice-Wang Friday, September 16, 2016 10:04 AM
    Monday, September 5, 2016 9:13 AM
  • Thanks to everyone for your suggestions.  Although Lync 2010 did exhibit unexpected chat session closing whenever a patch was applied, it doesn't appear that Sykpe for Business 2016 exhibits the same behavior.  This is a non-issue in Skype for Business 2016.  Thanks again for the suggestions.

    Regards,

    PhillyJoe

    Friday, November 4, 2016 2:42 PM