I still haven't got an answer to my main question though. Is it necessary to have an antivirus itself for an exchange server considering the condition I mentioned above? We are not really worried about the spam From your post, it seems to me that having an antivirus or not is not really a big deal. Is that correct?
Well NOT having an antivirus is a big deal for me Bottom line is never rely on a security system that you don't have control on. Paying for an antivirus is a lot cheaper than having to clean up after the damage is done.
My self have an experience before the antivirus has corrupt the hub transport database because i didnt exlcude the hub database. It was out of my knowledge that in exchange hub transport also have database need to be excluded. So sometimes the risk you taking are bigger than the virus will spread to your local server. Barracuda networks and GFI both make quality filters. I personally like to use them both together to filter before the server and again on the server.
In all honesy you really get what you pay for and avoiding protection because of budget isnt a good idea because its going to cost a lot more if your server gets compromised or infected with a nasty virus.
Have you tried the File-level scanner antivirus software? File-level antivirus does not protect against e-mail viruses, they will not clean your mailbox if you get a virus through a received message. A best practice is to use the File-level antivirus software on all servers and the client operating system, and also creating a procedure to keep all the antivirus software signatures up-to-date across the organization. Before starting to play with the file-level antivirus software keep in mind that Exchange Server has a new architecture.
By default, these files are located in subfolders based on the name of the database. Mailbox servers Process exclusions Many antivirus programs support the scanning of processes, which can adversely affect Microsoft Exchange if the incorrect processes are scanned.
Therefore, you should exclude the following Exchange or related processes from process scanning. Edge Transport servers fms. Mailbox servers hostcontrollerservice. Mailbox servers ParserServer. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. In a CCR environment our Quorum is located in a remote share; we can use the cluster utility to figure out where the file share witness is and then configure, in the listed machine, the exception on that directory.
Figure The file share witness used by CCR. Now, we know the server and shared folder. We must log into that server and configure the directory exclusion list for that specific folder. Using SCC we have to see which disk is being used by Quorum through the Cluster Administrator and configure that disk in the exclusion list.
We have to do these steps in all the Cluster nodes. Some antivirus software vendors allow us to exclude file extensions from real time antivirus, the following extensions must be defined for Exchange Server Some antivirus software allows the exclusion of processes from the file-level antivirus software.
We can use the following table to exclude each listed process for each Exchange Server role. In this tutorial we have seen how to deploy file-level antivirus software on Exchange Server independently of the file-level antivirus software installed.
We have also seen which directories must be excluded from the file-level antivirus software, specific extensions, and the services running in memory as well.
More Information Exchange Server antivirus software. Anderson contributes to the Microsoft Community with articles, tutorials, blog posts, twitter, forums and book reviews. He is a regular contributor here at Techgenix.
Your email address will not be published. The voice prompts, greetings and informational message files. The temporary files generated by Unified Messaging. By default, the compression folder for IIS 7. Many file-level scanners now support the scanning of processes, which can adversely affect Microsoft Exchange if the incorrect processes are scanned. Therefore, you should exclude the following processes from file-level scanners.
In addition to excluding specific directories and processes, you should exclude the following Exchange-specific file name extensions in case directory exclusions fail or files are moved from their default locations. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No.
0コメント