Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Exchange Server / Design / March 2005

Tip: Looking for answers? Try searching our database.

Exchange Antivirus design

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Tim - 29 Mar 2005 04:48 GMT
I have two Exchange 2003 Enterprise servers setup as a frontend and a
backend.  The frontend server is currently acting as an smtp gateway by
recieving inbound internet email.  I would like to configure the antivirus
solution in a "best practice" format.

Is it best to install the antivirus on the frontend server, or both?
Al Mulnick - 29 Mar 2005 14:41 GMT
That's not really enough information to make a good suggestion.

Best practice?  Who's?  What're the business drivers?  Why?

Everybody does this differently but the thinking is generally to have AV
protection on the edge (SMTP GATEWAY or in this case the FE server) as well
as mail-server-type-aware AV on the mailstore server.  In this case, on the
BE server you would additionally install Exchange-aware software that uses
the AVAPI.

But if you don't have business drivers or a strategy in place, it's hard to
say if this makes sense for you or meets your goals overall.

Al

>I have two Exchange 2003 Enterprise servers setup as a frontend and a
>backend.  The frontend server is currently acting as an smtp gateway by
>recieving inbound internet email.  I would like to configure the antivirus
>solution in a "best practice" format.
>
> Is it best to install the antivirus on the frontend server, or both?
Dave Hodge - 29 Mar 2005 17:00 GMT
Tim,

It is best practice to use multiple tiers of antivirus software in your
defense strategy.

Typically I recommend AV products be installed at the SMTP Gateways, Mailbox
Servers, and a Client Side AV product with MAPI client scanner.

Additionally it is also a good idea to configure the Outlook Security Patch.
More information on this can be found in the office resource kit. If you are
using Exchange 2003 for OWA clients, there is a corresponding registry hack
available that performs the same function.

>I have two Exchange 2003 Enterprise servers setup as a frontend and a
>backend.  The frontend server is currently acting as an smtp gateway by
>recieving inbound internet email.  I would like to configure the antivirus
>solution in a "best practice" format.
>
> Is it best to install the antivirus on the frontend server, or both?
semmal - 30 Mar 2005 18:42 GMT
The best suggestion .. is

Gateway Server have SMTP virus software like  Trend Micro IMSS-->  --> Back
End Server (virus scanner for mailbox , File Scanner)

                                      So all the incoming  mails hit to the
gateway server, Anti virus SMTP software will scan all the mails and forward
to the back end server that is having virus scanner for mailboxes.so totally
three level virus protection

1. File Scanner --> protect Operation System
2.  SMTP Gateway server --> it will scan all the incoming / outgoing mails
and  protect the LAN from virus attack from external network
3  virus scanner for mailbox --> additional level anti-virus protection

Cheers
Semmal

>I have two Exchange 2003 Enterprise servers setup as a frontend and a
>backend.  The frontend server is currently acting as an smtp gateway by
>recieving inbound internet email.  I would like to configure the antivirus
>solution in a "best practice" format.
>
> Is it best to install the antivirus on the frontend server, or both?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.