Ran the DST admin upgrade agents late Friday 3/9/2007. Worked like a charm with a clean report.
However, a user who is another users calendar delegate still has 3 meeting dates 3/12, 19, 26 of a series that read on mouse over as 11:30am est and also show as 11:30am est when he entry is opened. The calendar’s chair person shows these same entries as 10:30 am est.
The delegate has edited these entries (prior to the DST agent) to remove the location of the meeting. Is it possible that beause he elegate was able to edit her entry and save it that the DST agent did not update the time ? all other meeting times for the delegate refleect 10:30 am (in the legacy DST zone.)
Subject: DST and Delegated User
Glad to hear that almost all entries were updated properly!
To investigate a given entry not updating you’d want to look at the doc properties itself from the view level. The key items to see if the agent would touch it or not are simply
-
does it have the $TimeZoneAgent field present and what value is it set to? ("0"would indicate that a given calendar entry is “orphaned” meaning that we couldn’t find the document referenced in $Ref or some other C&S workflow problem exists that prevents us from doing a reschedule and “1” would indicate that it was processed at some point.)
-
does it have the “old” rules in the StartTimeZone and EndTimeZone fields? We have seen some cases where documents were created that don’t have this information due to DST being disabled on the client, use of a button to add the invitation where the calendar entry is not “complete” and a non-Notes 6.x+ client doing the accept function (such as a mobile client etc.)
*updated thought - if the delegated user was updated when the change was made, the rules could have been updated, but not had the time merged properly by the agent because the new rules excluded it from execution. As noted on the daily call referenced in this post -
Hope that helps - if you’d like to post the fields on the doc they could potentially reveal what happened to it, or if you’d like to just make it correct the chair could remove and readd this particular recipient.
Subject: RE: DST and Delegated User
Interesting. We do not have a $TimeZoneAgent field in any cal entry docs in the DST window. Checked mine and this user. Although looks like the calendar times have been updated. Do I need to be concerned that this field is absent (i.e. ran the agent via the console.)
Here are the values for the other fieldson a cal entry that was in the DST update window but not updated as described above (re: delegate) :
StartTimeZone = Z=5$DO=1$DL=3 2 1 11 1 1$ZX=28$ZN=Eastern
EndTimeZone = Z=5$DO=1$DL=3 2 1 11 1 1$ZX=28$ZN=Eastern
Subject: RE: DST and Delegated User
Hi Rick -
No need to be worried at all! The StartTimeZone and EndTimeZone posted look good. What this means is that you rolled out the OS patch early enough that users had not scheduled into this period yet (either that, or your users were so ahead of the curve that they did not schedule meetings in this 3 weeks knowing that they would require remediation :-).
I might suggest a quick review of the agent log which would be Drafts folder of the mail file that the agent was run from just to make sure it did not register any errors.
I can tell you though that for installations that go the MS patch out before the end of 2006, there were FAR fewer calendar invites created. I would assume because people just don’t schedule into the next year as aggressively as they do into your typical “next month” situation.
Michael