Quantcast
Channel: Symantec Connect - Products - Discussions
Viewing all articles
Browse latest Browse all 21603

SEP vs. SEP SBE

$
0
0
I need a solution

Hi

We have been utilising SEP for a few years now and it is renewal time.

I have seen the SEP SBE offering which allows either onsite management server or done via the cloud, and like most IT guys, are keen to reduce workload, so having one less job in-house is appealing. Given that we have around 35 users we fit the SBE category.

I loaded up a trial of the onsite management console just to see the differences between SEP and the SBE edition.

I note that one of the differences relates to the fact that you can't configure the auto-protect function to scan only on 'modification' or 'write' of files.  This is something I would like to retain if possible, just to keep the impact of real-time scanning as low as possible.

I must admit I haven't experimented with this switch for a long time so I am wondering what the impact of not having it is likely to be.  One would think the impact is going to be twice as much given you will have the read of the file before the write.

However if we are scanning only selected extensions then it is only going to be a percentage of total files accessed anyway.

Looking at the cloud based management console it appears that the ability to configure settings is even further reduced.  For example you can't even nominate to scan only selected extensions.  (The reverse is the case where you can exclude nominated extensions.) I know simplicity is good - but only if it doesn't severely impact on system performance!

How are other firms going with SBE? Have you switched to it from SEP at all, and was your experience positive?

As we are largely server based, utilising thin clients and remote desktop services I am particularly keen to know how SBE affects server performance compared with traditional SEP.

Thanks for your help.


Viewing all articles
Browse latest Browse all 21603

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>