Here is a recent Live Meeting issue that I wanted to make people aware of. While looking at reports of Live Meeting usage (using the MessageStats Report Pack for OCS from Quest Software), it showed some Live Meetings were taking upwards of 3+ hours, when we had first-hand knowledge that the meeting ‘ended’ after 30 minutes.
After some digging we discovered that the Live Meeting was still active long after the Presenter thought it had ended by virtue of one or more participants not closing (exiting) their Live Meeting consoles (the consoles were minimized or in the background). The meeting Presenter in this example just closed their console to exit the meeting.
How many resources do lingering Live Meetings consume is a question mark, and it is probably negligible if the all the media sharing (e.g. Presentations or Desktop Sharing) has been closed down, but nevertheless a meeting channel is still open.
The best solution we can find for this problem is to educate meeting Presenters to “Exit and End Meeting” in the Live Meeting GUI when the meeting is finished; which is different (and somewhat hidden in the GUI) from merely closing the Live Meeting Console or selecting “Exit” in the menu.
I would be interested to know whether other deployments have this issue and what (if anything) they do about it.
Twitter
LinkedIn
Wow – interesting. I would like to more about the resource consumption after the meeting as ended.
It works very similarly on the IBM product offering ‘Sametime Meetings’. As you’ll see in the below link the Host of the meeting can just close the window or leave the meeting, however the meeting stays open till the last participant leaves unless the Host specifically chooses to end the meeting.
Sametime Meeting Example