Thanks again for your patience, and most of all your support.
Sincerely, Suphatra Twitter: @skprufo Start off your weekend with good news: we’re working on this!
So if my SIP address is [email protected], the two URLs Lync will attempt to connect on will either be: https://autodiscover.justin-morris.net/autodiscover/or https://justin-morris.net/autodiscover/
For Lync to connect to the Exchange Autodiscover service, you need one of these URLs to be accessible.
So now once we’ve retrieved that calendar data from Exchange, Lync needs to actually apply it to your presence, and how often this occurs is controlled by the Calendar State Publication Interval parameter in the Lync Client Policy.
Unlike the MAPIPoll Interval and Web Service Poll Interval parameters, the Calendar State Publication Interval parameter must be set in number of seconds.
Typically the autodiscover.option is the most commonly deployed, as this compliments what is already usually deployed for Outlook 2010 to work.
I did a bit of digging into it and think I’ve worked a few things out that make the whole situation a bit clearer. We need to look at how often Lync polls Exchange for the free/busy information, and then how often your calendar state is published to your Lync presence i.e.So to set it to 5 minutes, the cmdlet would be Set-Cs Client Policy -Calendar State Publication Interval 300.My understanding from perusing Tech Net library articles is that there is a difference between of calendar information in the Lync client.Thanks to everyone who brought this feature to the forefront and shared feedback on their use case scenario. I wrote some more product updates on today’s Teams blog in my weekly column, “Weekend Reading” — https://techcommunity.microsoft.com/t5/Microsoft-Teams-Blog/Weekend-Reading-3/ba-p/65897 Cheers, Suphatra Hi everyone, I need some help from you on this.Can you add to the conversation thread on User Voice — What is more important to you, having the presence be different (i.e.