I wanted to test how the Lync 2013 client polls for changes in the calendar status and how accurate it is in that regards. My system is Lync2013 server and Exchange 2010.
The results where puzzling.

The Set-csClientpolicy is set up with this:

Lync MapiPollIntervall = 1 minute
Lync WebServicePollInterval = 1 minute

First I created a meeting in Outlook with start 10:40.

10:37 Meeting set up from outlook but not yet in Lync.


10:39 Meeting shows up in Lync but status remains unchanged.


10:40 Meeting time but still Available in Lync


10:49 My meeting status changes to In a meeting
This is a little over 10 minutes from when I scheduled the meeting.

So why does the it take 10 minutes to change my presence when the meeting shows up I Lync 1 minute after it was created? A Puzzle, right?

I found a blog about how the set-csclientpolicy is used to set poll intervals:
But then this article has a different story:
It says that MAPIPollInterval is deprecated for Lync 2013.
Therefore, to me it seems like WebServicePollInterval is the only setting to adjust the Lync client poll interval.
So why does it not change the status after 1 minute as specified with WebServicePollInterval.
Seems to me like regardless of how often Lync clients poll for new status, exchange does not update it more often than every 10 minutes in my system.
Can anyone confirm this?
Would also appreciate if anyone knows if it is possible to �tune� som parameter in exchange for this interval.