Support for Symantec Endpoint Protection's Optional Outlook Plug-In on Outlook 2010

Article:TECH141640  |  Created: 2010-10-11  |  Updated: 2011-11-16  |  Article URL http://www.symantec.com/docs/TECH141640
Article Type
Technical Solution


Issue



The optional Symantec Endpoint Protection (SEP) client Outlook AntiVirus plugin does not display in the Microsoft Outlook 2010 client interface.  Is it functioning?


Environment



Outlook 2010 is the mail client included with Microsoft Office 2010.


Cause



Outlook 2010 has dropped support for Exchange Client Extensions (ECE). 
SEP 11.x and SEP 12.0 Outlook Antivirus plug-in is based on ECE, so is not compatible with Outlook 2010.

See the following Microsoft Document:
 http://technet.microsoft.com/en-us/library/cc179110.aspx#BKMK_WhatsRemoved  "Third-party Exchange client extensions do not load on Outlook 2010."


Solution



For SEP 11.0 and SEP 12.0, users are encouraged to support the proposed product enhancement for this feature or funtionality to be included in future versions.

Workaround: use Outlook 2007, Outlook 2003 or another mail client. 
However the SEP 11.X Outlook plug-in is only supported on 32 bit versions of the operating systems even with the earlier versions of Outlook. 

Alternately, do not use this optional mail plug-in.  If a mail security program like Symantec Mail Security for MS Exchange (SMSMSE) is installed on the company's Exchange server or elsewhere in the mail flow (a dedicated mail scanning appliance, for instance) then any threats or other unwanted content should be cleaned long before the messages reach the end users.  SEP's optional mail scanning components are of most use only in very small offices or unmanaged deployments. If a proper solution is implemented elsewhere in the mail architecture, then the SEP plug-in adds provides very limited return for its resource usage.

The SEP 12.1 Outlook plug-in is supported for Microsoft Outlook 2010 on both 32 and 64 bit versions.




Article URL http://www.symantec.com/docs/TECH141640


Terms of use for this information are found in Legal Notices