Jump to content

JessePereboom

Techbench
  • Content Count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About JessePereboom

  • Rank
    New Member
  1. Thanks for your assistance. I will get back in touch with my client, and give this a shot. May take me a few days to hook up with them though. I will report back either way.
  2. I can 't access any files on the Q:\ as that isn't an accessible drive. I believe it is a virtual drive as part of Office Click to Run. https://answers.microsoft.com/en-us/office/forum/office_2010-office_install/microsoft-office-click-to-run-protected-q-drive/8ec13e71-30ea-4c01-b97a-c4f374c1007e
  3. When I am using Excel Starter it is flagging this as a false positive. I can't seem to locate how to exclude this as it is on the virtual Q:\ which there is no access to.
  4. I am experiencing this issue with FoxIt Reader, FoxIt Phantom, and Adobe Acrobat not displaying scanners when trying to scan a document with either of those programs. I have created an exception for them in AE and this resolves the issue.
  5. We currently run both MWB Endpoint Protection and Endpoint Security. We are looking at adding in Webroot alongside of these. I just thought I would run it by the group to see if anyone is running this combination before taking the plunge.
  6. This solution worked for me, in conjunction with clearing the logs on the clients. Thanks
  7. Thanks for the info. I don't have that folder on our systems. Looks like that is a SCCM SCCOM folder which we don't use. I guess I will try some of the other methods first and see how that goes. Thanks again.
  8. Having the same issue here. Wondering if it would just be easier to uninstall everything and do a nuke and pave so to speak. We have a little over 100 clients. I am guessing that the logs may still remain after the uninstall, and still have to be deleted via a script.
  9. Windows 10 v1511 MS Surface. Installed the EP client via Endpoint Agent Deployment Tool. Successfully installs and agent communicates with the console. However triggering a scan via the console fails as well as scheduled scan fails. I have also disabled Windows Firewall and bypassing the Sonicwall.
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.