Update free/busy information on the server every X minutes

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

According to page 84 of the "Working with the Exchange Server 2003 Store"
whitepaper Outlook publishes the free/busy data for a user one time every 15
minutes, and again when Outlook shuts down.

Does this really mean that Outlook republishes the data even if no change
has been made by the user?

Is there any background information available why this design is being used?

This is also strange if I compare this to the update schedule used by the
standard Loadsim profiles. For MMB3 the free/busy schedule is updated 4 times
a day and for the Heavy user profile only once per day.

Thanks for any clarifications
Jürgen Haßlauer
 
JH -

Sorry, this is a bit misleading (and I'll email the proper folks). The
Free/Busy info is only updated if there has been a change made to the
calendar. The process is that a change is made to the calendar, which
updates a copy of the Free/Busy generated in the mailbox (the "local
free/busy"). Any time this local free/busy info has been dirtied, Outlook
will publish it to the system folder on a 15 minute schedule, or when
Outlook exits if 15 minute timer has not yet been reached.

I think the emphasis in the whitepaper was meant to be that the complete
free/busy map is republished for the user at this schedule, not just the
delta from the last publish. But again, this only happens if Outlook
believes the calendar (and therefore the local free/busy data) has been
modified.

--
Evan Dodds
Microsoft Exchange Support

****** Disclaimer ******
This posting is provided "AS IS" with no warranties, and confers no rights.

Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.
 
Thanks.
It would be fine if the whitepaper would be changed.
According to my interpretation of the document Outlook would update the data
regardless if it was changed or not, and only OWA and OMA would send an
update to the PF server if the user’s calendar was modified.
We are currently in the process of evaluating the impact of changing the
update interval from 15 to 1 minute (a customer wish).

Regards
Jürgen
 
Back
Top