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
A couple years ago I described how to reconcile hard deletes for BES 4.x, and with BES 5.0 and the new web-based administration tool the process has changed a little bit. In an Outlook/Exchange environment you can Hard Delete selected objects by pressing shift+delete, bypassing the Deleted Items folder and immediately deleting the item.
Enabling Hard Delete Reconciliation
Log into the BAS and from the Servers and Components drill down to BlackBerry Solution topology > BlackBerry Domain > Component View > Email > YourServer_EMAIL. Click on YourServer_EMAIL and you'll be presented with the configuration screen for the Messaging Agent.
Click the Messaging tab, and click the 
Edit instance link.
Change Hard deletes reconciliation to True and click 
Save All to apply the changes. That's it, no need to restart the service.
If you're using Outlook with RPC over HTTP(s) (rebranded as Outlook Anywhere with Exchange 2007) one of the most useful tools in your arsenal is the /rpcdiag command line switch which will launch with the Connection Status window.
But what if you don't want to relaunch Outlook? It's surprisingly simple – just hold down the Control key and right-click on the Outlook icon in the system tray.
Normal Outlook Tray Menu
Outlook Tray Menu with extra options
The new options provide you with the Connection Status window, very useful for diagnosing connection and performance issues, and an option to test AutoConfiguration. If you're having an issue with Exchange 2007 Autodiscover this is very helpful.
Outlook's Exchange Connection Status window
Outlook – Test AutoConfiguration
Here's a somewhat common scenario; you're running Exchange 2003. You'd like to be running Exchange 2007. Perhaps you'd like a firewall? Maybe you want Exchange 2007 AND a firewall on the same server.
What to choose, what to choose. Actually your choices are simple. Exchange 2003 only runs on 32-bit Server 2003 or Server 2000. If you want Exchange 2007 you need a 64-bit OS. If you want ISA 2006 you need a 32-bit Server 2003. If you want ISA's successor Forefront TMG your only option is 64-bit Server 2008. Oh, and Forefront TMG is still in beta.
Best practices aside, it's quite common for smaller organizations to cram as many services onto a single server as possible, and that's a bit more difficult now.
Many of you looking at this are probably asking yourselves "Boy, how did Corey create such a breathtakingly awesome Venn diagram". Well wonder no more, I make my diagrams in Photoshop bitches.
