Nobody likes a snitch, especially a spammy one that results in more messages in your inbox. With Exchange 2007 if you forward – manually or with a rule – a calendar appointment, Exchange will tattle send the meeting organizer a notification.

Your meeting was forwarded

XXXXXXX has forwarded your meeting request to additional recipients.

	Meeting
	Evaluate PostPath

	Meeting Time
	Friday, July 31, 2009 2:00 PM-3:00 PM.

	Recipients
	YYYYYYYY
	ZZZZZZZZ

Disabling Notifications

Use the following PowerShell commands on your Exchange server to disable meeting forward notifications.

Disable External Meeting Forward Notifications

Set-RemoteDomain -MeetingForwardNotificationEnabled $false

Disable Internal Meeting Forward Notifications for a Single User

Set-MailboxCalendarSettings -Identity user_email@example.com -RemoveForwardedMeetingNotifications $true

Disable Internal Meeting Forward Notifications for All Mailboxes

Note that this only affects current users, new users will still have the default forwarding enabled.

Get-Mailbox -ResultSize unlimited | Set-MailboxCalendarSettings -RemoveForwardedMeetingNotifications $true

First, don't show me a window with a progress bar when I'm deleting a single file.  Second, whatever is going on behind the scenes to hang like this, is very, very wrong.  And it happens all the time.

It only gets better when you try to cancel:

It's much easier then enabling telnet on Vista. Open a command prompt and type:

servermanagercmd -i telnet-client
The result will be similar to:

c:\>servermanagercmd -i telnet-client
.
 
Start Installation...
[Installation] Succeeded: [Telnet Client].
<100/100>
 
Success: Installation succeeded.

That's it, enjoy telnet.exe again.

The Outook team quietly slipped out a hotfix for Outlook 2007 containing quite a few major performance enhancements.  Dubbed the Outlook 2007 SP1 February 2009 cumulative update, the KB 961752 patch fixes over 100 individual bugs.

The Outlook team has revised their mailbox/OST size guidelines too, welcome news to anyone using cached Exchange mode.  Before installing the 961752 patch if your OST was larger than about 1GB Outlook's performance would start to suffer.  The new OST guidelines say:

• Up to 5 gigabytes (GB): This size should provide a good user experience on most hardware.
• Between 5 GB and 10 GB: This size is typically hardware dependent. Therefore, if you have a fast hard disk and much RAM, your experience will be better. However, slower hard drives, such as drives that are typically found on portable computers or early generation solid state drives (SSDs), experience some application pauses when the drives respond.
• More than 10 GB: This size is where short pauses begin to occur on most hardware.
• Very large, such as 25 GB or larger: This size increases the frequency of the short pauses, especially while you are downloading new e-mail. Alternatively, you can use Send/Receive groups to manually sync your mail.

Prior to the Outlook 2007 SP1 February 2009 cumulative update if you had more than 10,000 items in a single folder you'd experience performance issues. After the February update you can usually have around 50,000 items in a folder before experiencing the same issues.

Apparently all cumulative updates for Office are only released as hotfixes, which means it won't be showing up in Windows Update anytime soon (until it's officially released as part of Office/Outlook 2007 SP2).  To download it you need to request a link from Microsoft (it's easy), or you can download the KB961752 patch from Mediafire directly.

Read more about the patch on the Exchange Team's blog or at the descriptively titled "Outlook 2007 improvements in the February 2009 cumulative update" KB 968009 page.