Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 1978 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

EPS 9 and Datacontrol with USB/mass storage drives

MawfTech

Hi,

Why does EPS v.9 data control not allow any access from other applications to USB or other Mass storage devices?

If I switch on data contol in 'observe only' mode, it immediately switches off all access to drives from applications (actually makes word 2000 crash randomly ??). We do see the warning saying use explorer to transfer file but come on, when looking at presentations or files from customers handed over on pen drives, we cannot update content and just click save? I now have to save as, stick it e.g. on my desktop then drag it back to the pen drive. Seems a  really bad option to me, duplication, version loss, copy shortcut instead of file - I can think of lots of problems this causes.

Are we ever going to get that fixed? Surely this is just a standard journal trigger (ok I realise FATx doesn't journalise but you can still capture directory triggers). Do we really have to have such a restriction?

I realise this has been brought up before and dismissed as a 'by design' feature. What a feature though, loss of standard capability!!!!! Even in 'observe only' mode.

Matt

:2032


This thread was automatically locked due to age.
Parents
  • 0

    Hi Matt,

    Longer term we're looking into ways to make the behavior of removable storage data control more transparent.

    Bit of background information: one of our design goals was to implement a solution which intercepted data prior to it touching the removable storage device (to avoid the scenario where the end user pulls out the device during a write). To achieve this we intercept data transferred onto removable storage using Windows Explorer but don't intercept individual application writes to the storage device. This is why the agent forces data to be transferred via Windows Explorer when a "request user authorization" or "block" rule is in place. Essentially its a trade off between data exposure, interception complexity and user transparency.

    In monitor / observe only mode the restriction is not active - although the data control rules will only trigger on transfers made using Windows Explorer.

    Hope this helps,

    John

    Product Manager

    :2040
Reply
  • 0

    Hi Matt,

    Longer term we're looking into ways to make the behavior of removable storage data control more transparent.

    Bit of background information: one of our design goals was to implement a solution which intercepted data prior to it touching the removable storage device (to avoid the scenario where the end user pulls out the device during a write). To achieve this we intercept data transferred onto removable storage using Windows Explorer but don't intercept individual application writes to the storage device. This is why the agent forces data to be transferred via Windows Explorer when a "request user authorization" or "block" rule is in place. Essentially its a trade off between data exposure, interception complexity and user transparency.

    In monitor / observe only mode the restriction is not active - although the data control rules will only trigger on transfers made using Windows Explorer.

    Hope this helps,

    John

    Product Manager

    :2040
Children
No Data
Unfiltered HTML