While we have been implementing Trend Micro's AntiVirus solution at our client sites, a few of them have also expressed an interest in the spam filtering offered by Trend.
Our first client was setup using the Email Hosted Reputation Services (EHRS). The service did help to reduce spam over the Exchange IMF setup.
Recently, Trend went through an update of their antivirus products and the hosted spam filtering. The new filtering is called InterScan Messaging Hosted Security (IMHS).
We switched one of our existing clients over to the new IMHS service and unfortunately have been having nothing but grief since. Spam that was not coming through before is now coming through in spades.
We waited the obligatory 48-72 hours to make sure the MX record changes had taken, and still things have not improved.
The straw that broke the camel's back: A bounce message forwarded by one of their clients saying that the attachment size was too large ... at 4MB ... with Trend's server name listed as the culprit.
Since this client is one of our key clients, we are not about to go any further with the service.
Since the previous EHRS services will no longer be in effect, we will default back to the Exchange IMF for now.
For the most part, things were working fine before EHRS, worked a bit better with EHRS, but have taken a big step back with IMHS.
While we are relatively happy with Trend's A/V, we will no longer be selling what is now the Worry-Free Business Security Advanced which includes IMHS. We will stick with the Worry-Free Business Security product for now.
The other side to this pickle: With the advent of SBS 2008, which will include ForeFront and Windows Live OneCare 120 day trials out of the box, if we choose to install them, we may look at going Microsoft on the entire platform. This reduces our install and configuration time too.
Since we are selling 100% Open Value Agreements to all of our clients, and have been for quite a while now, adding ForeFront and OneCare to our client's Open Value Agreements when it comes time to upgrade their refreshed hardware will be a small step.
We shall see ...
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.
SBS, SMB, SME, Hyper-V Failover Clusters, Technology, System Builder Tips, views from the I.T. Trenches, and more.
Showing posts with label ForeFront Client Security. Show all posts
Showing posts with label ForeFront Client Security. Show all posts
Monday, 28 July 2008
Wednesday, 9 January 2008
From Symantec to Trend Micro and a little ForeFront Client Security
We are moving away from Symantec.
In one case, we have a relatively new install at a long time client who moved offices and needed a fresh start.
It is now almost 18 months later, and we have finally worked out getting the Symantec licensing .slf file problems worked out ... almost. The management console keeps telling us that certain clients are in license violation mode and won't update the client's definition files when this happens. And there are seemingly no good answers forthcoming from Symantec ... even with the Gold Support.
*sigh* and a deep breath.
So, we are going to try out the Trend Micro NeatSuite with a new client.
Trend's name passes through the RSS reader every once in a while. Sometimes good, and sometimes bad, but from what we can tell, a number of leading SBSers out there rely on it for protection.
What this means is a heavy investment of time to learn a new product. Hopefully the Trend setup will be fairly straight forward.
By the way, we did look into ForeFront Client Security as a possible option, but the management console requires a full version of SQL2005 server installed. SQL 2005 Workgroup on SBS 2K3 R2 Premium does not cut it. Even on the Open Value Licensing scheme it was too expensive for SMB to include SQL. While we can install the workstation client in a "not managed" mode, this does not strike us as the right direction to go in a server/client environment.
So, a new product adventure begins! :D
And, in the case of our existing clients, once their Symantec licensing lapses we will move them over to Trend.
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.
In one case, we have a relatively new install at a long time client who moved offices and needed a fresh start.
It is now almost 18 months later, and we have finally worked out getting the Symantec licensing .slf file problems worked out ... almost. The management console keeps telling us that certain clients are in license violation mode and won't update the client's definition files when this happens. And there are seemingly no good answers forthcoming from Symantec ... even with the Gold Support.
*sigh* and a deep breath.
So, we are going to try out the Trend Micro NeatSuite with a new client.
Trend's name passes through the RSS reader every once in a while. Sometimes good, and sometimes bad, but from what we can tell, a number of leading SBSers out there rely on it for protection.
What this means is a heavy investment of time to learn a new product. Hopefully the Trend setup will be fairly straight forward.
By the way, we did look into ForeFront Client Security as a possible option, but the management console requires a full version of SQL2005 server installed. SQL 2005 Workgroup on SBS 2K3 R2 Premium does not cut it. Even on the Open Value Licensing scheme it was too expensive for SMB to include SQL. While we can install the workstation client in a "not managed" mode, this does not strike us as the right direction to go in a server/client environment.
So, a new product adventure begins! :D
And, in the case of our existing clients, once their Symantec licensing lapses we will move them over to Trend.
Philip Elder
MPECS Inc.
Microsoft Small Business Specialists
*All Mac on SBS posts are posted on our in-house iMac via the Safari Web browser.
Subscribe to:
Posts (Atom)