It is _just_ an hour, after all… An open note to Microsoft

I won’t bore anyone with the details but I want to go on the record, officially, as stating that both the approach and the solution to the DST change in Microsoft Exchange that Microsoft have chosen are absolutely terrible. Yes, Microsoft (and Google), I said TERRIBLE. It is a testiment to your bad message storage schema that you are having this problem - my other mail servers by other vendors are not having this calendaring problem. I have applied every single patch you’ve given me. I have run every vbs script to give my users every permission required. I have run your little cheap-ass “lets use a single user tool but give the admin a wrapper in the form of a DOS batch file - no MONAD?, come on, DOS?” solution. All of this for about a 70% success solution.

I’m hoping that you fix this shyte during the summer so that I don’t have this problem when George’s DST fiasco rears its ugly head again. Between the two of you I am going gray enough that I shaved my beard to hide it.

Don’t make me shave something else.