Yea, I didn't mean to sound so harsh 'cause they do work well in general. But, looking at that long list of these things-you-shall-not-do I had to laugh at how often many of them happen.
For example, why shouldn't someone be able to forward a meeting invite to a friend? Of course the organizer should know about it; but shouldn't that task be taken care of by the software!? Forwarding is a perfectly natural thing to do, people do it all the time and when they do, no errors will pop up to tell them they just did something wrong. BUT watch out if you do it, bad stuff happens and often goes un-noticed. But hey....it's documented :) To me that article is pretty much a list of explained race conditions and a cop out. My question is, why shouldn't development take that list and come up with a solution in the face of how often these things seem to occur? Meeting and their invites are proprietary, so one would think that the architecture could be centralized instead of the data floating around in the invites? Heck, just put meeting-invite-protocol v2 in the Office/Exchange "wave" vNext and call it a day. This is the premier and best of breed corp messaging solution after all so shouldn't it just work? Marketing keeps telling us the software is a business enabler but this kind of stuff is speed bumps and walls to climb. *snaps back to reality* Oh well I guess I'll just live with telling an "I told you so" answer when confronted with user calls on these. If we're all nice maybe we won't get glared at either. Hey and it keeps the L2 helpdesk employed and busy too :) ~JasonG > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Thursday, July 02, 2009 16:58 > To: MS-Exchange Admin Issues > Subject: Re: another Calendar Question > > Indeed. I think they work fairly well considering the various and sundry > ways an "event" can be modified. > We've had our problems but if the users go up what can be an admittedly > steep learning curve, the problems go away. > > We *rarely* even call support on calendar issues any more. By the time > you get all the logging turned up and sent back and forth, you can find > out users didn't send updates like they should, the "same" meetings on > different calendars show as modified by the organizer, the delegate(s)s, > the delegate(s) Mom..... > > > Blackberry > > ----- Original Message ----- > From: Michael B. Smith <[email protected]> > To: MS-Exchange Admin Issues <[email protected]> > Sent: Thu Jul 02 15:36:12 2009 > Subject: RE: another Calendar Question > > At least they are documented. > > ________________________________________ > From: Jason Gurtz [[email protected]] > Sent: Thursday, July 02, 2009 10:55 AM > To: MS-Exchange Admin Issues > Subject: RE: another Calendar Question > > > http://office.microsoft.com/en-us/outlook/HA011276781033.aspx > > Ouch. > > After clicking the No button at the bottom of this article I typed in the > following comment and submitted: > > This is too complicated for the average > user. At least 99% of all users I've ever > worked with will never remember even a > fraction of these "unwritten" rules. > > All these "gotchas" should be entered as > bugs and fixed in Exchange/Outlook > > > I didn't include this link but maybe should have: > <http://www.gapingvoid.com/114446615687.jpg> > > :) > > ~JasonG > > >
