I originally posted this in the Exchange Group but was told my problem is
an Outlook issue and not a Free+Busy problem. Outlook is the interpreter of
our Free+Busy time. This is my original Post in the Exchane Group with the
response I got below it:


Here's a problem I just have not been able to figure out. Pretty much ever
since I installed Exchange 2000 (then did an inplace upgrade to 2003) I have
had an issue creep up every now and again with appointments that have been
set up as recurring ones. I have quite a few Admins working here and they
set up recurring appt's for the execs all the time. Every now and again I
will get a complaint that one of the instances had to be changed and it
produces some form of adverse effect. Those that are effected have stated
they see the changed appointment they have already accepted showing as
'Tentative' or not showing up at all or they see the appointment at the
original time. I've heard them say the appointment they scheduled is far
further out in time and instances than what they actually scheduled the
appointments for. Some of the recipients get the update while others in the
same meeting do not. And other complaints of this sort.
I've checked the event logs and see absolutely nothing noting any form of
corruption (though I have not run any integ or eseutil to check the
integrity of the databases for a while now - with no indication of
corruption I haven't felt the need). However, exclusively, all of the
complaints about Calendar issues are from changing recurring appointment
times.
Is there some kind of utility I can run to see what's going on with the
Free+Busy database or is the integ/eseutil the ones to use? Has anyone else
had this kind of issue and what did you do to try and resolve it? It
appears that if I have the Admin delete the entire series of meetings then
recreate them it seems to fix the issue for that particular meeting and
changes can then occur but it's a crap shoot if they will again experience
issues from it.

Any help would be greatly appreciated -
Jon


Response:
Basically this is an Outlook issue. It's Outlook that interprets and
implements the calendar entries.
Free/busy is just that, an indicator when someone is free or busy, and it's
also controlled by Outlook. A user's Outlook updates free/busy data in the
system public folder when a calendar entry is changed or when he logs off. I
don't read in any of the problems you describe where free/busy would have
anything to do with it.
You might post this to an Outlook newsgroup.



So here I am. Has anyone else had an issue like this and what was the
cure for what's ailing me? Is there some setting in Outlook that I am not
aware of that needs to be set so ALL of the pertinent data to an appointment
change goes to ALL of the recipients correctly?

Thanks again for any Reply -
Jon