You should remove Objectives from your key request exclusions list immediately. Doing this tells our software to NEVER provide the EEFF key to that process. This means that it won't be able to encrypt or decrypt files on the fly.
I have not seen this in the field before, so the best I can do is recommend that you open a support ticket on this one.
Thanks, raising a ticket now with my support provider...
I was asked to try a couple of things to see if that would help, they were:
- If you are not encrypting folders on shares (thus to using NW encryption) you could easily try to set off the NW encryption by opening the "Network" policy under EEFF and unchecking the "enable encryption" option.
I hadn't actually turned this feature on, so left it unchecked
- Other thing that you can do would be opening the policy called "Encryption Options" and insert the software you are talking about in the blocked processes and see if this helps.
I added the processes that Objective uses to the Blocked Processes list, checked that the
policy had updated on the PC... same result when attempting to save to network.
I've logged a Product Enhancement Request as I've also been told that Objective has never been QA'd with EEFF. As Objective is a much used product in the public sector I'm hoping something will come of this!