Lync Group Conversation Timeout Mystery RRS feed

  • Question

  • Hello Experts,

    I was having a IM group conversation and see that after 4 hours of idle time, meaning none of the recipients were sending messages, the group conversation got timed out. The ConferenceIMIdleTimeout is not set within the client policy and as per documentation the maximum value that can be set for it is 60 minutes. Also the status within my Lync client is set to 50 minutes.

    Why does the Group Conversation then expire after 4 hours? I know the same question was asked earlier too but there was no answer to it to close the thread.

    Steps to replicate the scenario:

    1. Select more than 1 user within the Lync client for an IM chat (Group Conversation).

    2. Whether you send messages or not, does not matter, keep the conversation open for 4 hours. During this time no one should be sending any messages to this IM window

    3. After 4 hours you will see the message "You have been removed from this conversation".

    Waiting for an answer experts.


    Wednesday, May 1, 2013 1:14 PM

All replies

  • Hi,

    Please try to sechdule the meeting in outlook ans start it instead of Meeting Now on client.

    Please try to enable logging tool to see how it works.

    Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

    Kent Huang
    TechNet Community Support

    • Proposed as answer by Kent-Huang Tuesday, May 7, 2013 9:21 AM
    • Unproposed as answer by HeadBreaking Tuesday, May 7, 2013 8:50 PM
    Friday, May 3, 2013 6:22 AM
  • Hi,

    The trace does not give any information as to where the 4 hour window is mentioned. Kent, this is regarding the Group Conversation and not scheduling a meeting. I have mentioned in my original question on how to replicate.

    I know this is a feature where if a conversation or meeting is being on idle for sometime then to free the resources Lync will be doing this clean up.

    My question is where on the server or which setting has this value of 4 hours set for the cleanup.


    Tuesday, May 7, 2013 8:52 PM
  • Hi,

    As for as I know there is no setting which can set this value of 4 hours. I will open a meeting and monitor if the same behavie happen in my lab. I will update the result later.

    Kent Huang
    TechNet Community Support

    • Proposed as answer by Kent-Huang Friday, May 17, 2013 8:31 AM
    Wednesday, May 8, 2013 7:48 AM
  • Thank you Kent. As far as I logically think about this, there has to be a mention of the timeout time in the product for this behaviour to happen.
    Wednesday, May 8, 2013 12:32 PM
  • Hi,

    The same behavior happen in my lab. This is by design but I did not find any switch or setting that we can change this value. I will send a mail to Lync experts to see if we can get further information.

    Kent Huang
    TechNet Community Support

    Friday, May 10, 2013 8:46 AM
  • Hello,

    Thank you for looking into this. I am investigating the same issue as we are attempting to have a group chat open during our business day (8-10 hours) and the four hour timeout makes this impossible.

    How might this setting be changed so that we can use the group conversation / meeting feature for a seamless session during the work day?

    Thank you.

    Thursday, June 27, 2013 5:25 PM
  • Hello Mr. Huang,

    We too anxiously await clarification on this issue.  We have a Call Center that managed work flow using LCS with multiple Group IMs for 8+ hours a day without issue.  Now that we've upgraded everyone to Lync 2010 their productivity has been impacted by time-outs and blank messages.  Could this be clarified as a bug, limitation, or configuration issue please?


    Wednesday, August 7, 2013 4:59 PM
  • Found this regarding Time-out and blank conversations:

    Friday, August 9, 2013 6:28 PM