[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] A meeting reminder is still active when you configure Outlook to send no reminders to an Exchange Server 2007 user - THE OFFICIAL BLOG OF THE SBS "DIVA"
Mon, Dec 1 2008 19:37 bradley

A meeting reminder is still active when you configure Outlook to send no reminders to an Exchange Server 2007 user


A meeting reminder is still active when you configure Outlook to send no reminders to an Exchange Server 2007 user:
http://support.microsoft.com/kb/945854

After you apply this update rollup, use Notepad to create a file that is named "StoreDriver.config" in the %EXCHINSTALLFOLDER%\bin folder. Make sure that the content of the StoreDriver.config file includes the following text.

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
 <storeDriver>
  <parameters>
   <add key="AlwaysSetReminderONAppointment" value="false" />
  </parameters>
 </storeDriver>
</configuration>

When you compose a meeting request to send to a Microsoft Exchange Server 2007 user, you configure Microsoft Outlook to send no meeting reminders to the attendees. To do this, you click to clear the Reminder check box in Microsoft Office Outlook 2003, or you set the reminder status to None in Microsoft Office Outlook 2007. However, when an Exchange Server 2007 user receives the meeting request, the meeting reminder is still active. Additionally, the reminder time is set to the default value of 15 minutes.

Okay so when do you not want to be alerted of an event?  When the event in question is a co-workers notification of their out of office status and it rings your Windows Mobile/IPhone/GPhone/Whatever Phone at midnight when you are sleeping.

Yeah that's a career limiting move 'eh?

You need to place a file in the bin folder on the Exchange 2007 server to fix this. 

Vote one for the cloud -- is it me or is Exchange becoming this beast that no one person can manage these days.  "Open up notepad"... how about just fix the bugs dude?  Having someone else manage that beast of a platform makes sense in instances like that.  People keep saying that they want to wait for SBS 2008 sp1 before they roll out SBS, how about waiting for Exchange 2007 sp2 instead?  SP1 was more like RTM and you need to install and be aware of all of these issues fixed in these rollup patches.  On SBS 2008 it's a must to have Exchange 2007 rollup 4 installed and if post install your OWA looks funky, install it again.

Less one for the cloud -- how fast do cloud vendors approve/deploy rollup patches for Exchange?  When you go through the cloud in a shared space, you won't be telling Microsoft to go patch their cloud or do notepad entries more often than not, you'll be on their timetable if it's a shared server setup.  Ask the questions of non-security patching....How soon after rollups are released do they patch?  Do they allow for support tickets for these kinds of issues to be addressed? 

Lack of control is good.  Lack of control sometimes has it's issues as well.

Filed under: