Re: Trend CSM 3.0 beta suggestions, please!

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I wouldn't think it would be advisable to mix the versions, and there
wouldn't be any point anyway. v3 antivirus doesn't give you anything v2
didn't have.

The antispam application in v2 was eManager, actually a stand-alone product
in it's own right. One might be able to install that, but I really don't
think anyone wants a 'custom' solution. We asked for a more integrated
product, now we have it.

Email antivirus (Scanmail) and file space scanning (Officescan) has always
been solid, and still is. Allthough Officescan has changed a bit - the added
bits are causing some issues (firewall, most notably) and there seems to be
some flakiness in the exclusion lists from time to time.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:ePPQA8gQGHA.532@xxxxxxxxxxxxxxxxxxxxxxx
Good points, Les.

Question: I know that V3 keys will work to install V2 CSM. Is it possible,
or desirable, to install the V2 messaging antispam component, yet install
the V3 CS antivirus protection?

Is the V2 antivirus for the server and workstations any less effective
than the V3 antivirus?

Thanks for your time.

Gregg Hill



"Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
wrote in message news:eG8EUjfQGHA.1676@xxxxxxxxxxxxxxxxxxxxxxx
It should be obvious.

Businesses pay their employees to do their jobs, not sift through spam.
Even 5 minutes per day will cost a business $400 per year, multiply that
x 10 users and enough said.

Besides, EUQ doesn't co-exist very well with Outlook JMF.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and I'll
understand." - Confucius


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:uHvdlGcQGHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
Hello, everyone!

Hypothetically speaking (wink, wink), if a Trend project manager were to
tell me that returning the server-side quarantine has been considered,
and if that person were to ask for reasons to bring back the server-side
quarantine, what you would say?

I have David's reasons. How about some more?

Gregg Hill




Well, my beta contact escalated my suggestions to the project manager,
who just sent an email stating that they are considering bring back the
"David Elders" <david_elders@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23ykeeevPGHA.2080@xxxxxxxxxxxxxxxxxxxxxxx
Hi Les,

I kinda semi-agree too! :-)

My main gripe with EUQ being forced on us all is that [particularly for
those users who work either frequently or mainly remotely] that it
almost totally does away with the point of spam filtering in the first
place - i.e. to stop the user being deluged with it. I'm meaning mainly
in terms of such remote users using Cached Exchange Mode having to
download all of the junk in addition to their legit mail, which in some
users cases will far outweigh the legit side.

Users who don't get hit with the main spam stuff won't mind too much
but those who have main company email addresses pointing at their
mailboxes [info@ etc] will get hit with a lot of crap with no option of
having it not hit their mailbox. If one [or more] of such users work
remotely a lot they're having to download a lot of crud...

Yes, I know that because we're still on POP3 [not for long, yippee!]
that we're hit more because our protection is less than it would be
with SMTP and the likes of IMF, but I just think that Trend made a
wrong assumption here in that everyone would prefer this - I'm
surprised they didn't offer the option of both, given that the
functionality was already there for server-side-quarantine. Did they
even query the beta testers opinion on this issue at any stage?

I still think the CSM suite is quality - I just still think v2 rocks
more than v3 [so far]. I'd like to think Trend have their ears open and
are receptive to possibly offering the option - I just hope it doesn't
take too long...

Regards,


David



"Les Connor [SBS Community Member - SBS MVP]" <les.connor@xxxxxxxxxxxx>
wrote in message news:%23qA%23aJtPGHA.3804@xxxxxxxxxxxxxxxxxxxxxxx
I semi-agree ;-).

If a customer is on CSM v2, in most cases they will throw a fit if you
upgrade them to v3. But they're very happy to stay with v2.

But new sites are OK with v3. They get to try EUQ without giving up
something because they never had it in the first place. Then, if/when
an option for server side quarantine is added, and spam detection rate
is improved - they'll be that much happier.

From an adminsitrators perspective - IMHO it's better to have CSM v3
installed on a new system than installing CSM v2 and then doing an
upgrade at a later date. I'd prefer to avoid the upgrade wherever
possible - there are enough differences in the two versions that it
really is about equal to an uninstall/reinstall to get it right. But I
only think this way because I have some faith that Trend will actually
come through with a release that includes all the features we all have
listed. I hope that doesn't come back to bite me.

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and
I'll understand." - Confucius


"David Elders" <david_elders@xxxxxxxxxxxxxxxxxx> wrote in message
news:%23YuA3zqPGHA.2692@xxxxxxxxxxxxxxxxxxxxxxx
Until and unless they sort out having both server and client-side
quarantine, Trend CSM will only be getting installed at v2 by me at
any customer sites...

David



"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:u7ZokgnPGHA.1216@xxxxxxxxxxxxxxxxxxxxxxx
Les,

I am hoping that as a beta tester they will listen more to the
suggestions. Probably not for this release, but maybe for future
ones.

Client\Server\Messaging for SMB 3.0 SP1 includes the following issue
resolution:

Item 1: Desktop\Server\Message Client disappears from the Security
Dashboard

Item 2: Improvement of spam detection rate

Item 3: MSA page not found or Error 403

Item 4: Unable to complete CSM installation during Remote Web
Workplace (RWW) on SBS

Item 5: Messaging Security Agent installation fails

Item 6: CSM notification is blocked as spam


Gregg Hill



"Les Connor [SBS Community Member - SBS MVP]"
<les.connor@xxxxxxxxxxxx> wrote in message
news:udZb7klPGHA.5400@xxxxxxxxxxxxxxxxxxxxxxx
Send all the suggestions in - by all means ;-).

But AFAIK, CSM SP1 is intended to fix some things that should work,
but don't. Not to add features. The included fixes have already
been made known to you beta testers, no? Beta testing will most
likely turn around making sure the announced fixes work, nothing
more.

Fortunately, I believe the spam catch rate is one of the fixes to
be tested ;-).

--
Les Connor [SBS Community Member - SBS MVP]
-----------------------------------------------------------
SBS Rocks !
----------------------
"Tell me and I'll forget. Show me and I'll remember. Involve me and
I'll understand." - Confucius


"Gregg Hill" <bogus@xxxxxxxxxxx> wrote in message
news:eeFiufiPGHA.3064@xxxxxxxxxxxxxxxxxxxxxxx
Hello!

As some of you know, Trend Micro is beta testing
Client\Server\Messaging for SMB 3.0 SP1 beginning March 6th.

I would like people to give me their product improvement
suggestions so I can pass them along to the beta team.

I already have:

1) Need to improve spam catch rate!!!
2) Give us back the V2 server-side spam quarantine and console,
but keep the EUQ for those who want it
3) Ability to have EUQ on some mailboxes, server-side quarantine
for others
4) I already recommended Bayesian spam filtering (think GFI
MailEssentials)
5) Give us a spot to put in RBL servers (Symantec Mail Security
has it) (Yes, IMF does it, but all in one spot would be easier)
6) Right now, if spam makes it into the Inbox by mistake, there is
no way to mark it as spam. Need a feature like the Outlook Junk
E-Mail filter where you can right-click a suspect message to block
the sender, block the sender's domain, approve sender (they have
this already), approve sender's domain (you can do this, but not
via right-click menu), etc.
7) Add a "Report to Trend Micro as spam" choice that automatically
reports the message back to Trend, kind of like Yahoo mail.

Any more suggestions?

Thank you for your time!

Gregg Hill



















.

Relevant Pages

  • Re: Trend CSM 3.0 beta suggestions, please!
    ... I know that V3 keys will work to install V2 CSM. ... Businesses pay their employees to do their jobs, not sift through spam. ... Les Connor [SBS Community Member - SBS MVP] ...
    (microsoft.public.windows.server.sbs)
  • Re: Trend Micro CSM spam folder
    ... How good is the anti-spyware stuff in CSM 2? ... Was I correct about the Bayesian filtering? ... Les Connor [SBS Community Member - SBS MVP] ... I believe the spam filtering provided by eManager ...
    (microsoft.public.windows.server.sbs)
  • Re: Trend CSM 3.0 beta suggestions, please!
    ... If a customer is on CSM v2, in most cases they will throw a fit if you ... Les Connor [SBS Community Member - SBS MVP] ... I am hoping that as a beta tester they will listen more to the ... Improvement of spam detection rate ...
    (microsoft.public.windows.server.sbs)
  • Re: Trend Micro CSM spam folder
    ... Neither CSM 2, 3, or IMF is picking those up ATM. ... Les Connor [SBS Community Member - SBS MVP] ... gets a bunch of spam that makes it into ... I have Recipient Filtering and tarpitting at 45 seconds to cut ...
    (microsoft.public.windows.server.sbs)
  • Re: TrendMicro Installation Advice
    ... Here's the procedure for Trend CSM for SMB. ... another account. ... Run setup - install on IIS is generally the only selection available. ... Accept the client installation for the SBS (installs the Officescan ...
    (microsoft.public.windows.server.sbs)