Jump to content

MBAM & Clarion Databases


Recommended Posts

History: Sage technical support insisted that MSE and MBAM must be set to ignore one of their Medicalware Applications - written in Clarion.

Even tho' MBAM (& MSE) were setup to ignore the aforementioned Clarion MedWare App. - it still cratered! In true Clarion fashion it was only fully repaired after 2 days worth of Clarion DBase Utility Repairs and the requisite 3 foot high stack of report paper!!

Current Status: Sage now recommends what they refer to as "Business Class" Security Software and, in the same breath, trot out the words "Symantec Endpoint". But, interestingly enough, Sage Software support continues to recommend that their Medical Software App. is ALSO excluded from Symantec's Endpoint Scanner.

This begs the question: Why, if MBAM (& MSE) are being blamed for corrupting the Sage Medical Apps. Clarion Database - even with "Ignore" on - will Symantec's Endpoint not manifest the same behaviour?

My own experience with SEP is that it is a) not very effective and b) high maintenance($) to setup efficiently (for a small business).

Given all the above can anyone please speak to MBAM and Clarion Databases or, as I suspect, are we, in this instance, getting a run around from Sage.

Thanks.

Link to post
Share on other sites

I haven't heard of any issues from our Support/Corporate Support team about any such issues (that doesn't mean they don't exist, it could just be that we haven't had anyone report it to us directly yet). That being said, if more advanced exclusions are required, they can be set up, at least in MBAM by using the Add function in the Ignore List tab and adding the Program Files folder for the program (exclusions are recursive, so individual files need not be excluded) and any temp folder/data folder used by Clarion (some programs use a folder they create under C:\Program Files\Common Files or a data folder under the current user's or all users' Application Data/ProgramData folder). Other than that, if the software installs any executables anywhere else, such as in C:\Windows or C:\Windows\System32, then that individual file (not the entire folder obviously) should be added to the Ignore List as well.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.