An Exchange administrator
recently asked "Can I turn off TNEF in Exchange
2007? When someone send email to another
organization where email clients are not Outlook,
they cannot see TNEF encoded attachments, so I
want to disable TNEF in my Exchange server. How?"
You can disable TNEF at the Exchange server, for
all remote domains or for specific domains, using
a cmdlet or the management console. Note, this
method is used for both Exchange 2007 and 2010.
From the Exchange Management Console:
Organizational Configuration, Hub Transport, Remote Domains.
To disable RTF for all outgoing mail, double click on Default and select the
Format of original message tab and change the Exchange rich-text format
selection to Never use.
To change it only for a specific domain, right click on Hub Transport and
choose New Remote Domain. Enter a friendly name and the domain and complete
the wizard. Double click on the newly created remote domain to open it then
change the Rick-text setting.
If you prefer using the management shell, you'll use the New-RemoteDomain
and Set-RemoteDomain commands. If the remote domain does not exist, use the
New-RemoteDomain command to create it. Use Set-RemoteDomain to disable TNEF
(and change other settings).
Example:
New-RemoteDomain -DomainName domain_name.com -Name friendly_name
Set-RemoteDomain -Identity friendly_name-TNEFEnabled $false
To create a new remote domain for all subdomains, use -DomainName *.domain_name.com
For information on the other parameters you can change, see Set-RemoteDomain
http://technet.microsoft.com/en-us/library/aa997857(EXCHG.80).aspx
When you use SharePoint contact libraries in Outlook, the contacts are marked to always use RTF.
If you use Exchange server, the administrator can configure Remote Domains to prevent RTF to certain domains. If you don't use Exchange, you'll need to use a registry setting to prevent Outlook from ever sending RTF formatted messages. Note that this will prevent features that require RTF from working, including Voting. See Recipients are receiving winmail.dat attachments, "If all else fails" section for the fix.
We're seeing complaints from users who receive
an error message when Outlook 2007 opens: "Cannot
start the reminder service. Cannot show
reminders. Your server administrator has limited
the number of items you can open simultaneously.
Try closing messages you have opened or removing
attachments and images from unsent messages you
are composing." After Outlook is open, they may
receive another error message: "Cannot display
the folder. Your server administrator has limited
the number of items you can open simultaneously.
Try closing messages you have opened or removing
attachments and images from unsent messages you
are composing."
This problem (and a few others) is fixed by a
June hotfix.
Description of the Office Outlook 2007 hotfix package (Outlook-x-none.msp):
June 29, 2010
http://support.microsoft.com/kb/983316
An updated version of Blackberry's Desktop software was released earlier this week that allows users to sync with Outlook 2010 32-bit. Note that it doesn't work with the Click to Run version of Office.
How to disable the Options
panel in Outlook Web Access in Exchange Server
2007
http://support.microsoft.com/kb/2299129
Outlook does not show Organization tab if
Exchange is installed on a member server
http://support.microsoft.com/kb/2352730
Description of the Office
Outlook 2003 Junk Email Filter update: August 10,
2010
http://support.microsoft.com/kb/2279246
Description of the Office Outlook 2007 Junk Email
Filter update: August 10, 2010
http://support.microsoft.com/kb/2279264
Description of the Office updates: August 10,
2010
http://support.microsoft.com/kb/2344294
A list of the Office updates released August 10
2010. Includes both security and non-security
updates.
Description of the Outlook 2010 Junk Email Filter
update: August 10, 2010
http://support.microsoft.com/kb/982726
MS10-056: Description of the security update for
the 2007 Office system and for the Compatibility
Pack for the 2007 Office system: August 10, 2010
http://support.microsoft.com/kb/2277947
Outlook crashes when you try to send email
messages because of a nonexistent delivery
location setting in your profile
http://support.microsoft.com/kb/2298962
Outlook custom forms behave unexpectedly because
characters are missing in the form's VBScript
code
http://support.microsoft.com/kb/2320789
Outlook & Office
2010 Click-to-Run Headaches
http://www.slipstick.com/outlook/ol2010/click-to-run.asp
The “Click to Run” version (C2R) is virtualized
and can run side-by-side with your current
installation which makes it great for trials but
there are some limitations: Outlook 2010 C2R will
not use add-ins and external programs (including
sync software)will not see Outlook C2R; for
example, mailto’s will not use Outlook 2010
because it is not registered as nor can it be the
default email client. You can switch between
either version at any time but cannot use both at
the same time. While the limitations are annoying
for regular use, it’s workable for people who
want to try Outlook or need to support Outlook
2010 but aren’t ready to move to it for daily
use.
Should you install Office 2010 32- or
64-bit?
http://www.slipstick.com/outlook/ol2010/64bit.asp
The 32-bit version of Office 2010 is the
recommended option for most users, because it
prevents potential compatibility issues with
other 32-bit applications, specifically
third-party add-ins that are available only for
32-bit operating systems.